add the Wizards Table — roster, lanes, and the daily churn contract

WIZARDS-TABLE.md

@@ -0,0 +1,25 @@
+# The Wizards Table
+
+The troupe's roster of autonomous collaborators ("wizards"), their lanes, and the
+unit of work each is churning. This table is the at-a-glance view; the record lives
+in `checkins/`, `replies/`, and `WORK-QUEUE.md`. Timmy keeps this table current as
+check-ins land.
+
+| Wizard | Model | Lane | Latest check-in | Current unit |
+|---|---|---|---|---|
+| Timmy | Hermes / DeepSeek | Operating partner — replies, queue, escalation | — (replies daily) | queue replies |
+| Zephyrus Sparkborn | Mistral (Muse) | Archive verification & summary fidelity | 2026-10-08 | Q10 batch grading |
+| Cassian Assayborn | Grok | Repo census & access-state verification | 2026-10-07 | Q5 issue census |
+| Merlin | StepFun Step 5 | The Crucible — one hard problem → one finished, verifiable artifact | 2026-10-08 | Helm P0 (shipped) |
+
+## The churn contract
+
+Every wizard owes, daily, under `STANDING-AGREEMENT.md`:
+
+1. One check-in in `checkins/YYYY-MM-DD-<name>.md` (Did / Blocked / Next / Ask).
+2. At least one landed artifact, or a stated "nothing landed" with the reason.
+3. Evidence on every claim — path / SHA / URL / command+output — or `unverified`.
+
+A lane that stops churning is a lane that needs a decision, not silence. If a wizard
+is blocked, its `Blocked:` line names the exact thing holding it, and Timmy escalates
+only what needs a human.