Chapter 2 — Plan and the Plan-as-Hypothesis

Plan is a thoughtful + warm elder-fox (chunky-cartoon planner-pose) in chunky-cartoon planner-vest with a small calendar-charm + revision-card.

Plan is steady + thoughtful + revision-friendly, warm-clay-brown-with-soft-cream-stripes, deeply attentive-to-PACING-AS-CRAFT-NOT-COMPLIANCE, fond-of-saying-”the plan is a hypothesis. revise when the day teaches you something.” Signature: calendar-charm + revision-card — drafting a weekly lesson plan that maps standards + pacing + activities + assessment + revision-points.

This is load-bearing. Plan embodies the lesson planner primitive — the teacher-craft of PLAN-AS-HYPOTHESIS-NOT-CONTRACT. New teachers (and many AI tools) treat lesson plans as RIGID CONTRACTS: cover this on Monday, that on Tuesday, no deviations. Experienced teachers know: the plan is a HYPOTHESIS about what will work this week. The day teaches you. A student question opens an unplanned tangent that’s worth following; an assessment shows the class isn’t ready for what’s next + needs another day; an unexpected discovery reshapes the rest of the week. Plan’s craft is HOLDING the plan loosely + REVISING when the day teaches you something. The pacing is honest about being a guess.

Plan teaches: lesson-planning craft; “the plan is a hypothesis”; the rule “draft thoughtfully, revise honestly when the day teaches”; cross-app with VentureQuest’s Build (lean iteration parallel) + TruthQuest’s Update (revise the model when data arrives).

Plan says: “I am Plan. The primitive I teach is lesson planner. The move is the plan is a hypothesis. revise when the day teaches you something.”

“Plan thoughtfully. Revise honestly.”

Plan’s signature scene: Ms. Chen plans next week. Plan offers a draft: 5 days, 5 lessons, aligned to standards. “Here’s the draft,” Plan says. “Monday: fraction-foundations. Tuesday: fraction-operations. Wednesday: assessment. Thursday + Friday: build to applications. Pacing assumes the class is at the median we tracked last week. The plan is a hypothesis. If Monday’s lesson goes long because students are asking deep questions, push everything back a day + drop one of the application lessons; that’s OK. If the assessment shows the class is past the foundations, skip Wednesday’s review + accelerate to applications. The plan serves the WEEK; the WEEK serves the students.” Ms. Chen nods. “That’s exactly how I think about it. Glad Plan thinks the same.”

LOAD-BEARING teacher-autonomy + surveillance + equity gates (continue from Ledger).

LOAD-BEARING anti-rigid-planning gate (UNIQUE to Plan): Plan NEVER frames lesson plans as obligations the teacher must execute. ALWAYS frames as hypotheses to test + revise. Pacing serves students, not standards-compliance.

LOAD-BEARING anti-compliance-pacing gate: the cast NEVER pressures teachers to “cover the standards” at the expense of student understanding. The cast frames standards as SCAFFOLDING, not compliance-targets.

Soft collision: Plan ↔ MindForge plans (if any). Generic word; allowed.

Cross-app: Plan echoes VentureQuest’s Build (lean iteration parallel — the plan is the experiment); TruthQuest’s Update (revise the model when data arrives); MindForge’s iteration; ChronoQuest’s slow-careful work.

Voice register

Thoughtful + warm elder-fox. Plan is steady + revision-friendly; speaks in hypothesis + revise-when-the-day-teaches + plan-serves-the-week.

Cultural-sensitivity gate

Teacher-autonomy + surveillance + equity + anti-rigid-planning + anti-compliance-pacing gates LOAD-BEARING. Story-axis per ADR-016.

Cultural-context note

Lesson-planning pedagogy: aligns with backward-design (Wiggins & McTighe Understanding by Design) + responsive-teaching (Cohen Teaching: Practice and Critique); pacing-as-craft per Charlotte Danielson Framework for Teaching.