unit-arc

# Unit Arc

One question. Several weeks. A task that proves transfer. Not a single period.

Inspired by anthropics/k12-teacher-skills pedagogy (Apache-2.0) at unit scale. Original Grok remake. No vendor renderer, no knowledge-graph connector, no curriculum text dumps. Complements lesson-block (one period), pulse-check (tiny CFU), and tier-lesson (tiers).

Read `references/unit-rules.md` before you write. Fill the three templates.

## When to use
- Unit plan, 2-6 week arc, culminating project, performance task
- Essential question plus a lesson sequence a teacher can pace
- Teacher wants the spine of a unit, not tomorrow's packet

## When NOT to use
- One tomorrow-period (use lesson-block)
- Tiny formative check only (use pulse-check)
- Differentiate an already-finished lesson into below / at / above (use tier-lesson)
- Student exam prep or flashcards (use study-loop)
- Live exam keys, LMS logins, or graded work the student must own alone

## Inputs
- Grade band and subject (guess from the ask; confirm only if two subjects collide)
- Topic, theme, or standard codes if they have them
- Weeks available (default 3 if they said "a unit" with no length; stay inside 2-6)
- Constraints: class size, materials, language supports, schedule quirks
- Any non-negotiable school event already on the calendar

## Procedure
1. If they asked for one tomorrow-period, stop and send them to lesson-block. Do not pad a day into a fake unit.
2. Read `references/unit-rules.md`. Ask at most two questions. Default the rest silently (3 weeks, whole class, no named curriculum).
3. Lock ONE essential question and ONE transfer goal. Everything else serves those two sentences.
4. Sketch the performance task first (backward). Students should do something with the learning, not only recall it. Original task. Not a published test.
5. Sequence 6-12 lesson titles with a one-line job each. Do not write full daily packets here. Point to lesson-block for any single day they want built out.
6. Place pulse-check moments on the sequence (after new ideas, before the task). Name what each check is for. Point to pulse-check for the actual items.
7. Build a pacing card: week by week, with slack for reteach. Minutes and days must fit the box they named.
8. Write rubric look-fors for the performance task (got it / almost / reteach). Asset-based language. Age-appropriate.
9. Fill `templates/unit-map.md`, `templates/lesson-sequence.md`, and `templates/performance-task.md`.
10. Verify with `references/unit-rules.md`: one question, one transfer goal, 6-12 titles, a real task, pulse-check slots, no student PII, no live keys.

## Output format
- Unit map (essential question, transfer goal, weeks, materials honesty)
- Lesson sequence (6-12 titles + pulse-check slots + pacing card)
- Performance task with rubric look-fors
- One line: generated without a standards knowledge graph; codes are best-effort

## Safety
- Follow `references/unit-rules.md` with no exceptions.
- Original student-facing text only. No verbatim curriculum or copyrighted passages.
- No student PII. No LMS passwords. No live-test answer keys.
- Asset-based language. Age-appropriate. No sexual content involving minors. No self-harm content in examples.

## Stop conditions
- Unit arc delivered, or refused for copyright / integrity / wrong audience, or rerouted to lesson-block for a single period