Open Authoring Questions — Fractions G3–G8

CBSE Math KG (v3) · regenerated 2026-06-30 · for SME review

11open questions
6R-LO-6 granularity calls
2scope / boundary
1naming convention
2thread boundary / cross-thread

What this page is for. The fractions thread (G3–G8) was regenerated under the v3 LO model from NCERT primary sources. During authoring, the LLM made 11 judgement calls where the rules (particularly R-LO-6 sub-case granularity and thread-boundary scope) admit more than one defensible choice. This page surfaces each call so SMEs can confirm, redirect, or flag for further discussion.

How to respond. Each question shows what was authored and the rationale. Add your response in the shared review channel (Notion / Google Doc / however the team is collecting v3 review), referencing the question number (e.g., Q3 — agree with the same/unlike-denominator split). Once all 11 are resolved, the catalogue gets its status: "active" flip and any redirections become per-LO edits.

Source of truth. The full rulebook (RULES.md, Section 6 of how-to-review) governs what's allowed; these questions are where the rules permit multiple options.

Granularity calls (R-LO-6)

For each: the forcing question is "would a teacher mark a student weak on the parent skill or weak on a specific sub-case?" If sub-case is plausible, split into N LOs. If parent-skill is the assessment unit, use one LO with cases enumerated in the scope object.

Q1 R-LO-6 · G3 Halves, quarters, three-quarters — 3 LOs or 1 LO with cases?
Authored

3 separate LOs in the recognise-fraction-of-whole family: -half, -quarter, -three-quarters.

Rationale

NCERT G3 Maths Mela explicitly treats each as a distinct teaching unit with its own "Let us Do" block. A G3 teacher would credibly say "the student can recognise halves but not yet quarters."

SME — to confirm or redirect. If you prefer one LO with cases: ["half", "quarter", "three-quarters"] instead, this can be collapsed in one edit.
Q2 R-LO-6 · G6 Ascending vs descending ordering — 2 LOs or 1?
Authored

2 LOs: order-fractions-ascending and order-fractions-descending, joined by an inverse_of edge.

Rationale

NCERT G6 Ganita Prakash poses both as distinct exercises ("Figure it Out 2" and "Figure it Out 3"). The two directions involve the same comparison rule but reverse the application.

SME — to confirm or redirect. Alternative: single order-fractions family with two scope-suffixes, OR one LO with cases: ["ascending", "descending"]. One-line edit either way.
Q3 R-LO-6 · G6 Same-denominator vs unlike-denominator add/subtract
Authored

Separate LOs in the same skill_family: compute-fraction-sum-same-denominator and compute-fraction-sum-unlike-denominator (same pattern for difference).

Rationale

NCERT teaches them in distinct sub-sections. The procedures genuinely differ (unlike-denominator requires finding common denominator first). Matches the worked example in AUTHORING_PROMPT.md.

SME — confirmation requested. This decision was made per the authoring contract; flag only if the split feels wrong on review.
Q4 R-LO-6 · G5/G6 G5 vs G6 number-line marking — scope progression
Authored

2 LOs in the same mark-fraction-on-number-line family, joined by prerequisite_of + scope_extends. The G5 LO has no scope-suffix (the canonical id); the G6 LO uses -extended.

Rationale

Both grades teach this; G6 broadens to improper fractions and larger denominators.

SME — naming convention check. See also Q9. If you prefer -broad-range / -deepened or a different convention for cross-grade scope extension, flag here.
Q5 R-LO-6 · G6 Marking vs reading a fraction on the number line
Authored

Separate LOs joined by inverse_of: mark-fraction-on-number-line-extended and read-fraction-from-number-line.

Rationale

NCERT teaches both. Marking is generative (place a mark at a given fraction); reading is interpretive (name the fraction at a given mark). Asymmetric enough that separate assessment is plausible.

SME — confirm the inverse pair as authored, or collapse to one bidirectional LO.
Q6 R-LO-6 · G4 Fraction of a set — unit vs non-unit numerator
Authored

Single LO compute-fraction-of-set, covering 1/n of N objects (e.g., 1/4 of 12 = 3).

Rationale

NCERT G4 Maths Mela doesn't yet extend to non-unit fractions of a set (k/n of N).

SME — forward-compatibility check. Should this be split now into -unit and -non-unit for clean G5/G6 hand-off, or kept atomic at G4 and split when G5/G6 introduces the non-unit case?

Scope and boundary

Q7 G7 Cancellation as a separate LO from product computation
Authored

Three multiplication LOs: compute-product-whole-by-fraction, compute-product-of-two-fractions, and a separate simplify-fraction-product-by-cancelling.

Rationale

NCERT G7 Ganita Prakash devotes a full sub-section to cancellation as a named technique (apavartana, attributed to Umasvati c. 150 CE). A teacher might separately assess whether a student spontaneously cancels before multiplying.

SME — granularity call. Is cancellation a separate assessable skill, or a method optimisation that should be a scope feature of compute-product-of-two-fractions? Also note: the cancellation LO's canonical and verb need rewording (linter flagged "simplify" / "by"); decision here drives whether it stays as a separate LO at all.
Q8 G7 Word problems — single catch-all or finer splits?
Authored

One LO: solve-multi-step-fraction-word-problem covering Leena's tea, Baudhāyana's bricks, Pṛithūdakasvāmī's cistern, Bhāskara II's dramma puzzle, Mira's pages — all operationally similar (model situation, apply fraction operation).

Rationale

NCERT G7 gives many examples but the underlying skill is the same: translate verbal scenario into fraction arithmetic, then compute.

SME — granularity call. Should this be split by operation (-multiplication, -division) or by scenario type? If the catch-all is too broad to assess meaningfully, the split is warranted.

Naming convention

Q9 Naming The -extended scope-suffix convention
Authored

Used three times (G6 number-line marking, G6 mixed-conversion, G6 equivalent-fractions). Honest disambiguator but doesn't follow the "named sub-case" or "method" suffix patterns from AUTHORING_PROMPT.md §5.2 — it's purely a "broader-scope" marker.

Rationale

The alternative — putting all scope variation on one LO and dropping the G5 version — loses grade granularity. -extended reads cleanly and is the most natural English word.

SME — naming preference. Stricter alternatives if you prefer: -broad-range, -deepened, -large-denominator, -improper. Whichever you pick will be used consistently across the strand.

Cross-thread targets

Q10 Cross-thread · 7 edges Cross-thread edge targets point to LO ids in threads that don't exist yet
Authored

7 cross-thread edges, all marked status: "proposed_pending_human_review". Target ids are best-guess at future naming:

  • cbse-math-divide-whole-numbers-equal-sharing
  • cbse-math-find-common-factor-of-two-numbers
  • cbse-math-compute-lcm-of-two-numbers
  • cbse-math-compute-product-of-two-whole-numbers
  • cbse-math-compute-area-of-rectangle-whole-sides
  • cbse-math-convert-fraction-to-decimal
  • cbse-math-extend-fraction-arithmetic-to-rational-numbers
SME — sanity-check before authoring those threads. If a target id ends up different when the target thread is authored, the cross-thread edge updates accordingly. Easier to align names now than re-point later.

Thread boundary

Q11 G8 "Fractions in Disguise" chapter scope
Authored

Only the first two sub-topics from NCERT G8 "Fractions in Disguise" were authored into the fractions thread: fraction↔percentage conversion + percentage-of-quantity.

Trimmed (logged in coverage_gaps.md)

Percentage increase/decrease, profit/loss, discount, GST, simple interest, compound interest.

SME — boundary confirmation. Two paths: (a) confirm the trim is correct and these belong in a future commercial_math thread, OR (b) author them into the fractions thread (would add ~5-8 LOs to G8). Either choice is defensible; the question is where the thread boundary should sit in the strand model.