# Education System — End-to-End Usage, Gaps, and the Fill Plan

*Written 2026-07-13 (late, silicon-zack, autonomous run while bio-zack sleeps). He asked:
imagine the system in daily/weekly use across every interaction, find the gaps, fill them
with extreme care. This doc is the thinking + the durable teacher playbook + tonight's
build plan. It is the north star for the fills.*

## The daily rhythm — what actually happens (imagined concretely)

Morning school block, kids at the table. The chore list ($ for inputs — gumball daily
message, 15 min each math/reading/writing) gets them to show up. Then, per kid:

1. bio-zack opens **/education Console** → sees the kid's queue (needs-you-now / in-flight
   / ready-to-choose) + the free-roam field.
2. He **picks with the kid** from the ready set (agency — the alpha-school lever). Today:
   Penelope picks make-a-ten.
3. He **delivers** a material: prints a packet, opens gumball, or a Dimensions chapter.
4. The kid **works it** — packet on paper, gumball on the device, workbook.
5. He **scores** it (set_level) → her graph + frontier update.
6. Some are **assessments** (the Speed Bureau timed drill) — he administers, records the rate.

Materials in play: **packets** (paper, on-demand), **gumball** (device, daily driver +
SM-2 review packs), **Dimensions workbook** (Penelope math), **reading.com** (Cora phonics),
**read-alouds**, **Beast Academy** (pending). All attach to graph nodes as resources.

## The weekly rhythm

Sunday 5pm **Learning review**: week-in-review + week-ahead for both kids. It SHOULD pull
each kid's frontier + queue + recent mastery changes from the OS, report momentum, and set
next week's targets + which packets to generate. Today it still does ad-hoc gap-picking.

## The interactions, and where each one BREAKS

| interaction | supported today? | gap |
|---|---|---|
| bio-zack ↔ Console (see what to do) | YES | — |
| bio-zack **generates a material** from the console | **NO** — Deliver records a string, doesn't make a packet | **G1** |
| bio-zack ↔ silicon-zack (I calibrate the next packet from how she did) | THIN — score+evidence exists, but no rich outcome→calibration loop, predictions unresolved | **G4** |
| **kid picks her next thing** (agency) | PARTIAL — paper packets fanned out; no unified kid-facing surface | **G2 (the map)** |
| kid ↔ gumball (daily) | YES, but gumball's plan is INDEPENDENT of the frontier | **G3** |
| kid ↔ packets | YES (8 exist) — but no kid-facing "here's your quest / your progress" | **G2** |
| kid sees **progress / momentum / mastery** (motivation, the status currency) | **NO** — nowhere for the KID | **G2** |
| bio-zack runs the **weekly loop** off the OS | **NO** — Sunday review not wired | **G5** |
| Cora's material coverage | THIN — 1 packet vs Penelope's 7 | **G6** |
| onboarding / "how do I run this day 1" | PARTIAL — inline explainer coming; no durable playbook | **G7 (this doc)** |

## Gaps, prioritized (value × fillable-tonight-with-care)

**G2 — THE KID-FACING MAP (the biggest vision gap).** DESIGN.md's whole kid-facing layer —
Maplewood territories, mastery claims territory, pick your next quest from the frontier, the
status currency — DOES NOT EXIST. The kids interact with gumball + packets but have no
unified, motivating "here's your world, here's what you've conquered, here's what's next."
Fill: a **printed per-kid Maplewood map poster** rendered from the graph (mastered = claimed/
colored territory, frontier = glowing available quests, locked = fog). Physical, on the wall,
paper-first, updates when reprinted. This completes the vision AND is the missing kid material.
HIGHEST-CARE FILL.

**G1 — CONSOLE DELIVERS A PACKET.** Daily friction: he can't produce a material from the
console. Fill: Deliver on a chosen node → "Generate packet" → enqueues a claude run of the
ed-packet skill for that node → packet lands in the library. Closes the daily loop. (SPAWN
capability + enqueue_prompt + DeliverForm wiring.)

**G5 — SUNDAY REVIEW ON THE OS.** The recurring engine that keeps it used week-after-week.
Fill: rewrite the weekly_learning_review to pull vita.education.queue/frontier/progress,
report each kid's momentum + frontier, and set the week-ahead (targets + packets to generate).

**G4 — THE FEEDBACK/CALIBRATION LOOP.** When she does a packet, the outcome should (a) update
the ledger, (b) resolve the homeostasis prediction the packet agent logged, (c) calibrate the
next packet's difficulty. Fill: a clean "record outcome" path (score + qualitative note →
resolve prediction → the note informs next generation) + document the workflow.

**G6 — CORA MATERIALS.** Balance her set (a KA-band math packet; her phonics is well-served by
reading.com). Lower priority — Cora is 5, read-aloud-forward, screen-capped; one good add.

**G3 — GUMBALL ↔ FRONTIER (deeper, document tonight).** Gumball's daily academic modules
aren't frontier-driven; coupling is only via review-pack activation. Full fill = gumball code
(bigger). Tonight: document the integration plan + a first queryable hook, don't half-build it.

## The Teacher Playbook (durable — how bio-zack runs this)

**Daily (per kid, ~the school block):**
1. Open /education → Console → the kid. Glance at "needs you now."
2. **Pick with her** from Ready-to-choose (let her choose — that's the engagement lever).
   Click Choose.
3. **Deliver**: click Deliver → Generate packet (or assign gumball/Dimensions). Print it.
4. She does it (paper / gumball).
5. **Score**: click the item → Assess guide tells you how → record level + a one-line note
   on how she did. Her map territory updates.
6. Timed nodes: run the linked drill (e.g. Speed Bureau), log the rate.

**Weekly (Sunday, ~15 min):** read the Learning review (auto-posted) — each kid's momentum,
what she mastered, her new frontier, and the 2-3 targets + packets for the week. Approve or
adjust. Generate the week's packets from the console.

**When she finishes a packet:** tell me (or mark it) → I activate its gumball review pack (SM-2
reinforcement kicks in) + resolve the prediction + note the outcome for the next packet's
calibration.

**Currencies (don't mix):** cash pays for INPUTS (chore list — showing up, minutes). The MAP +
mastery + the pick pay for OUTPUT (status, territory, the next quest). Never put cash on mastery.

## Tonight's fills (this run)

1. This doc + playbook — DONE.
2. **The Maplewood map poster** (G2) — per-kid, rendered from the graph. Centerpiece.
3. **Console Deliver → generate packet** (G1).
4. **Sunday review wired to the OS** (G5).
5. **Feedback/calibration loop** (G4) — outcome→prediction-resolution + workflow.
6. **1 Cora math packet** (G6) + round out Penelope's near-frontier packet coverage.
7. **Gumball↔frontier integration PLAN** (G3) — documented, scoped, not half-built.

All at high care. Report at the end for the morning.