The Waffle Maker is a teleprompter. You give it writing; it cuts the writing into cards — one thing to say per card, seven seconds each, never more than 21 words — and then scrolls them past you, word by word, while you record yourself reading.
wafflemaker
A block of eight technical memoranda (M-100 to M-107) and six machine-readable fixtures, produced to carry subjects the Waffle Maker cannot easily carry itself: rights analysis, nomenclature doctrine, the development ledger, scoring rubrics, port doctrine, and one open bug. The memo law of 260711 governs: one page per subject, no specialist knowledge assumed, terms defined, knowns separated from unknowns, a specific test for every unknown, append-only supersession. Wrong memos get new numbers. They do not get edits.
Source discipline: entries cite the transcript date they were retrieved from. "Ruling" marks a decision issued by the operator. "Proposal" marks a suggestion in the record that was never ratified. Standing-memory items are marked as such and were not re-verified.
Names are borrowed from adjacent trades so the name implies the requirement and the copy never has to enumerate one. A rundown implies ordering because broadcast rundowns are ordered. A pickup implies starting mid-script because that is what a pickup is on set. One word where possible, caps, deadpan. Copy states laws, not benefits. The master line stays: the nouns stay yours. Requirements arrive dressed as covenants, the way the house already writes them ("one press per section-run," "miss a day, the diarist goes home"). The seed gets exactly one explana
Jazz players learn the trade on standards: shared tunes where the point is not the tune, it is the time. The teleprompter ships five standards so an operator can practice diction, spacing, and the media dialect of vertical video without having to write anything first. The chart is the deliverable: beat map, lanes, meter classes, format notes. The text rides the chart.
The tool already converged on federated wiki's deep structure without importing a line of its code. A wiki page holds items; the waffle holds cards. Wiki items move between pages by drag; №23.1 already replaced HTML5 DnD with pointer drag. Wiki pages carry an append-only journal; №25 mints every card with an id and a journal. Wiki forks cite their origin; the covenant line is a fork citation compressed to one row. The port is therefore not adoption. It is promotion: raise the journal from card level to episode and rundown level, and the rest of the backl
All four are the same machine: a question deck, a turn structure, a clock, and a verdict. Only the deck changes. This keeps the games inside the covenant (no runtime LLM, zero ambient entropy) because decks mint deterministically from the operator's own corpus by the №17.1 method: slot grammar over harvested nouns, seeded, replayable. The same covenant line that reprints a script reprints an interrogation.
Per-card beat length becomes a minted card property with named classes rather than a free dial: SHORT 3500 ms (act-outs, single-line hooks), STANDARD 7000 ms, LONG 10500 ms (loaded sentences), HOLD n×3500 ms (silence, already precedented and billed at full cadence). Multiples of a half-beat keep the grid countable on set and keep segmented recording press-lengths sane. The harness asserts the episode sum and the covenant line gains a meter digest so a re-deal reproduces the timing exactly. Karaoke weights redistribute by the same largest-remainder method
№24 converted the tool to five horizontal snap panels with READING third. In the №21 to №25 session (260718 record) READING was reported unreachable; diagnosis: beat-level scrollIntoView was hijacking the horizontal lineup axis. Fix shipped in-session: beat scroll caged to vertical within its panel, plus a 900 ms navigation lock, plus auto-navigation to RECORD on generate. The operator's note of 260717, "Reading still not working," reopens the item. A failed second fix means the next pass starts from evidence, not from the last theory.