The model is the camera.

Days are engineering days for one engineer with an agent, verification included. "Holds under" says which Sprint 1 reads the item survives; the swaps are in section 5.

Rulings by noon and the Sprint 2 baseline column before any code (1 h)

Why. Every number in the sprint is read against a row that exists before code ships, and rulings 1 and 2 shape migration 0020, which is written on Day 1.

Done when. Day 1 by noon: rulings 1–12 answered or explicitly defaulted in docs/RETENTION.md (0.5 h). Day 1 morning with the agent: the 'Sprint 2 baseline' column in docs/RETENTION.md — Sprint 1's Day-14 row (pos-0 hold, reached-end, back taps, D1 with interval, n, by via) beside the loop's zeros (distinct non-founder uploaders 0, cards with fit 0, makers who saw a number 0, cards that waited on a bench 0, logged status flips 0) — and Sprint 1's carried-to-sprint-2 list read and its first chrome P0 named (0.5 h).

The core above holds under every read. On 22 September, the readout picks one of these and the plan swaps accordingly.

• a. Sprint 1's Day-14 row shows position-0 hold < 40% and reached-end < 50%: the first minute is the problem — card 0's phone fit and the chrome, not supply, not composition Add: Day 1, before any ruling: tools/fit-check.mjs run by hand against the live deck (Deepstate, chess, the Sprint 1 pages, the platform embeds) and the verdicts written into docs/RETENTION.md — card 0's phone fit read from data, not memory; Day 3 (ruling 9): if Deepstate's verdict is painted_3s < 60% or overflow_x, card_editorial re-ordered in the SQL editor so the deck opens on the best-fitting founder page by fit then card_rank(14) hold — an editorial act RANKING.md permits; nothing promoted on telemetry; Days 8–10, item 9 (1.5 d): migration 0023 card_zero rewriting card_editorial with MOCK_GAMES, feed.json and the e2e fixture in one commit; the one chrome P0 Sprint 1's carried list names first, failing test first; tests/e2e/first-minute.spec.ts (card 0 'running' under 1.5 s from a cold context, meta strip never over the surface, BLITZ and chevron hit areas disjoint); Deploy 6 with a phone verdict; Founder: 2 h re-reviewing every deck card for fit at 375x667 on the phone and hiding by hand what fails; the deck may shrink to six; The outcome is read as written, but position-0 hold on first visits >= 50% becomes the headline beside it, with complete loops reported. Drop: The review strip UI (item 6, 0.75 d) — card_set_status and bench_feed() in the SQL editor from the laptop each evening; the bench, the log and the 24-hour rule stay; The fix day's no-P0 filler (0.5 d) — item 9 is the filler; The hourly fit-check schedule (0.25 d) — workflow_dispatch after each bench pass; Founder: pages shrink from six to eight to four (two that remember); the makers-already-posting hunt shrinks to five and the Day-11 second send is skipped — no hour goes to supply until card 0 holds; the trust floor ('…' with Report / Remove it) waits for Sprint 3.
• b. Reached-end >= 50% but D1 < 5%: people finish and do not return — the deck is too short; supply through the founder's own uploads and the concierge, with the bench ruling in hand Add: Day 6, item 10 (0.75 d, riding migration 0021): actor.house and the audition pick over house uploads — the internal exclusion applies to voters not uploaders, one ticket per house card, md5(current_date || card_id) — so the founder's newest page gets 'New today' distribution at slot 2; tools/pg/check-audition.sql; the production check select card_id, slot from card_rank(28) where slot='explore' returns a house card the next UTC day or it is fixed before Deploy 4; Founder: ten to twelve pages through the brief instead of six to eight (+3 h); five known or already-posting makers DMed the brief by Day 6 instead of Day 8 (+2 h), each handed a /c/ link that opens playing on a phone once their card is live; The fix day's no-P0 filler is the trust floor (item 8's 0022: Report / Remove it, no auto-hide) if the half day remains. Drop: The hourly fit-check schedule (0.25 d) — workflow_dispatch after each bench pass; The fix day shrinks from 1 d to 0.5 d; Founder: the image and the clip (0.75 h) — pages are the supply the read asked for; the Day-11 second send folds into Day 8 (−1 h).
• c. D1 >= 10% at n≈100 with the four guard rails met: the bar holds provisionally — composition rescoped for a short deck (bet 4) plus supply (bet 6), still no launch post Add: Days 8–10, item 11 (1.75 d): composition-lite, two-sided — feed(n, seed, exclude) with slots 0–1 from card_rank and a seeded per-device order over the live tail under one hard rule (no two consecutive cards of the same kind: page, image, clip, site) in a plpgsql greedy with an explicit fallback; src/api/sequence.ts as the synchronous client twin; tests/fixtures/sequencer.json asserted by both tools/pg/check-sequencer.sql and tests/unit/sequence.test.ts; the end card's BLITZ re-reads minus the ids held this visit; the Day-10 SEQUENCER GATE on production before Deploy 6; demote-only untouched, no tier reads a rate; The readout adds the fork's own number: two seeds differ past slot 1 in production, no adjacent kinds, the end card's exclude working — reported, not targeted; Still no launch post, no community post, no seed cohort: the day-21 bar on >= 200 browser arrivals is not met by a 100-person pilot; D1 is read again on Sprint 3's cohort. Drop: The review strip UI (item 6, 0.75 d) — SQL editor; The fix day's no-P0 filler (0.5 d) — item 11 is the filler; The /stats loop panel (0.25 d of item 5) — loop_funnel and bench_summary read in the SQL editor; 'Your cards' and card_stats stay; The hourly fit-check schedule (0.25 d) — workflow_dispatch after each bench pass.
• d. D1 between 5% and 10% at n≈100 (the gray zone): one more founder-network wave, the day-21 read decides Add: Founder, Day 2 (Thu 24 Sep) after Deploy 1's phone check: wave 3 of ~50 through /feed?via=pilot&r=<uid> into Deploy 1's build, whose visitor path is behaviour-identical to the frozen Sprint 1 build (feed() still serves only live rows; the chrome is untouched; only the + sheet's copy and the landing line changed) — 2 h; Day 1, item 12 (0.25 d): the day-21 block in tools/sql/retention-readout.sql (D1 with its interval on pilot plus wave-3 browser arrivals, first sessions Sprint 1 Days 9–12 and Sprint 2 Days 2–3), rehearsed on Sprint 1's rows; Day 7: the read with n near 150 selects (a), (b) or (c) for Days 8–14; that fork's add and drop lists apply from Day 8 with what is left of the fix day; if D1 is still in the gray zone at n≈150, week 2 takes the (a) swap — another wave cannot narrow it and the first minute is the cheapest place to look. Drop: Nothing in week 1: the core ships as written through Deploy 2; Deploy 3 (the Make tab and the end card's count line, the first visible client change) waits until after the Day-7 read and ships that afternoon with Deploy 4; the fit-check workflow still runs from Day 6 because it changes nothing a visitor sees; The pilot-replier and makers-already-posting 'make one' send waits until Day 8, after the read, so the wave-3 cohort's first card is not changed under it.

1. Day 1Wed 23 Sep

   Rulings 1–12 by noon (defaults otherwise). Founder with the agent, before code: the Sprint 2 baseline column in docs/RETENTION.md (Sprint 1's Day-14 row plus the loop's zeros) and Sprint 1's carried-to-sprint-2 list read, its first chrome P0 named. Agent: migration 0020 written — the bench, the AFTER UPDATE trigger, card_set_status, submit_* re-created inserting 'bench' with p_meta (content_hash, made_with), card_set_fit, card_by_slug, my_cards, bench_feed, bench_summary, the ui_event kinds — and chained x3 with tools/pg/verify.sh + tools/pg/check-bench.sql; the fit tool's lint half (tools/fit-check.mjs lint, tests/unit/fit-lint.test.ts, the four fixtures). No deploy: the fork is read, not shipped, on Day 1. Fork (a): the fit tool's render half run by hand against the live deck by evening, verdicts into RETENTION.md. Fork (d): the day-21 block added to retention-readout.sql and rehearsed; the wave-3 message ready.

2. Day 2Thu 24 Sep

   0020's client side: cardBySlug and the /c/<slug> splice at index 0, myCards, uploadMedia's SHA-256 and the 'Made with' input, the 'Added under @handle … once it has been looked at on a phone' copy and toast, the landing line, link.spec, comments-upload.spec and pages.spec updated, share-link.spec.ts green; CI green. DEPLOY 1 (0020 + client). Migrate applies 0020; the card_rank assertion holds (deepstate 0, chess 1). Phone check within the hour: a page from a non-admin test account is absent from /feed in a fresh profile and opens at /c/<slug> for its creator; the founder's own upload lands on the bench too; select public.card_set_status(...) flips it and card_status_log has the row with via='rpc'; a direct update in the SQL editor leaves a via='sql' row. Agent: the fit tool's render half run by hand against the live deck (all forks) — verdicts into RETENTION.md for the Day-6 FIT GATE. Fork (d): WAVE 3 sent after the phone check. Agent starts the save channel.

3. Day 3Fri 25 Sep

   Save channel: the viewer's load/state/save relay and the probe's window.blitz, WebCardHost + src/lib/cardState.ts, public/cards/e2e/remember.html, cardState.test.ts and save-channel.spec.ts green with web-card-sleep.spec.ts unchanged -> main. DEPLOY 2 if green by evening, else it rides Deploy 3 on Day 6. Phone check: the counter fixture (uploaded from the founder's account as the first 'page that remembers') keeps its count across BLITZ and the chevron; localStorage holds only blitz:state:* keys. Fork (a): card_editorial re-ordered in the SQL editor from Day 1's verdicts if ruling 9's condition holds.

4. Day 4Sat 26 Sep

   No deploy. Agent draft only, to be verified Monday: src/lib/brief.ts and brief.test.ts (the CSP-list equality), the Make tab in LinkSite.tsx with fence-stripping and 'Made with', ?make=1 and 'make_open', the end card's 'You played N of M' line, make-one.spec.ts; fit-check.yml (workflow_dispatch + hourly with the early exit) and the CI fixtures step; tests/unit/workflows.test.ts. Founder (3 h): the first two pages by hand — the brief pasted from src/lib/brief.ts into a model, the answer pasted into the Upload tab, added, reviewed on the phone with a verdict line; one uses window.blitz.save per the docs sentence; brief edits noted.

5. Day 5Sun 27 Sep

   No engineering. Founder (3.5 h): two more pages, one image and one clip through the same door with the brief's variants; the bench reviewed with bench_feed() and card_set_status in the SQL editor and emptied; the two or three known makers DMed the brief itself; the hunt for ten makers already posting AI-made pages begun in concierge.csv. Fork (b): five makers' DMs drafted for Day 6.

6. Day 6Mon 28 Sep

   Morning: the FIT GATE — Day 2's tool verdicts on the live deck against the Sprint 1 phone verdicts; on pass, fit-check.yml dispatched by hand and its hourly schedule left on; on fail the tool is fixed first. Saturday's drafts verified (typecheck, vitest, e2e); migration 0021 (card_stats, loop_funnel) chained x3 with check-stats.sql. DEPLOY 3 (Make one + 0021 + the save channel if it slipped). Phone check: the Make tab shows the brief, copy works and 'brief_copy' lands, a pasted answer adds and is next in the founder's feed, the 900 px fixture from a test account gets 'wider than a phone' within the hour, card_stats returns for a card the pilot played. Fork (b): actor.house and the audition pick ride 0021, check-audition.sql green. Fork (d): Deploy 3 waits for tomorrow's read; only the fit workflow starts.

7. Day 7Tue 29 Sep

   MID-READ first (1 h): loop_funnel(7) and bench_summary() into docs/RETENTION.md, and Sprint 1's day-21 D1 with its interval — under fork (d) this selects week 2 and that fork's add/drop lists apply from Day 8. Then 'Your cards' on the profile with stats_open, the /stats loop panel and bench_summary, the ReviewStrip under /feed?bench=1 (b, d) -> main. DEPLOY 4 (under (d), Deploy 3's items ship here too). Phone check: the profile shows the founder's numbers and a test account's bench state and fit line; the strip flips a bench card Live in one tap and the next comes up; a Hide needs a reason; select * from loop_funnel(14) returns every column for @rand and 42501 otherwise. Fork (b): select card_id, slot from card_rank(28) where slot='explore' returns a house card or 0021's audition block is fixed before this deploy.

8. Day 8Wed 30 Sep

   The makers' build gate: tools/column-check.sql clean (fit on every hosted web card older than 24 h, zero to_status='live' rows with via='sql', 0019's stamps still zero missing on a headless tour), fit-check.yml green on its last three real runs, the cold walk in a fresh phone profile (landing -> feed -> + -> Make one -> brief -> paste -> the account door; /feed?make=1 opens on the tab). DEPLOY 5 only if anything changed; else Deploy 4 is the makers' build. Founder (2.5 h): the 'make one' message to the ten makers already posting and the pilot's ~30 repliers, one to one, via /feed?via=make&r=<uid>&make=1. Deck >= 12 live (Sprint 1's deck plus the founder's pages), every one flipped from a phone. Fork (a): item 9 starts (card_zero, first-minute.spec, the chrome P0). Fork (c): item 11 starts (feed_seed, the client twin, the fixture on both sides).

9. Day 9Thu 1 Oct

   Makers arrive. No deploy. The bench opened morning and evening on the phone; fit verdicts read on the strip; every Live tap on a phone; takedowns the same day. Agent on standby: fit-check runs and their verdicts, ingest_batch accepted/rejected, card_status_log (no via='sql' to live), localStorage keys audited on the founder's phone (blitz:state:* only, none over 4 KB), the maker replies' failure modes collected for tomorrow. Forks (a) and (c): the swap item continues.

10. Day 10Fri 2 Oct

    FIX DAY, P0 only: the Day-10 loop row written first (brief copies, make_open, uploads by class, fit pass rate, hours bench->live, live non-founder cards, stats opens, n); fixes with a failing test first -> DEPLOY 6, phone-checked within the hour. With no P0 the day goes to the swap-in — (a) item 9 with first-minute.spec green and a phone verdict; (c) item 11 after the SEQUENCER GATE on production (two seeds: same card 0, different past it, no adjacent kinds); (b), (d) the trust floor (0022 Report / Remove it, no auto-hide, rows on the strip). Freeze gate in the evening: column-check clean, fit-check green, no bench card older than 24 h, no open P0.

11. Day 11Sat 3 Oct

    Founder: the second send to the rest of the pilot list, only if the gate passed (1 h); the bench emptied; replies answered. FREEZE after the last send: the client bundle does not change again this sprint except by rollback, so the loop's numbers are one build; status flips are RPC calls and continue; the fit workflow keeps writing verdicts.

12. Day 12Sun 4 Oct

    Nothing ships. Founder (1 h): answers makers, hands numbers to anyone who asks (the panel does it; the SQL editor if the panel was cut), empties the bench, honours any takedown. Last arrival day whose next day is complete inside the window for the D1 diagnostic by via.

13. Day 13Mon 5 Oct

    Docs-only commits, the bundle byte-identical: docs/CREATING.md, EMBEDDING-A-SITE.md's 'Make your page remember', RANKING.md's never-ranks line, CONTENT.md's numbers table, ACCOUNTS.md's 'Your cards', STRATEGY section 5's two-line amendment. tools/sql/loop-readout.sql rehearsed against real rows with the interval formula; tools/column-check.sql's fit and status-log assertions pass; anything unfixed listed as carried to sprint 3; the concierge.csv tally and the per-page review table closed.

14. Day 14Tue 6 Oct

    READOUT, no deploy: /stats -> loop_funnel(14) and bench_summary() beside retention_daily(14,'make'), (14,'pilot') and (14,null); tools/sql/loop-readout.sql's block; the row into docs/RETENTION.md with n at every funnel step and the interval on every rate; the rule read first (zero unreviewed cards in feed(), zero via='sql' flips to live), then the funnel, the fit pass rate by brief version, the bench latency, the guard rails, the diagnostics; the kill criteria answered one by one; Sprint 3 named with both headlines written (ruling 10); the brief's version history written beside the pass rate.

In this order, when the hours run out:

• The hourly fit-check schedule (item 4, 0.25 d) — workflow_dispatch after each day's bench pass, or npm run fit:check by hand on the founder's machine with the verdicts pasted through card_set_fit over the DB URL; the tool itself is never cut
• The review strip (item 6, 0.75 d) — bench_feed() and card_set_status in the SQL editor from the laptop each evening; the bench, the trigger, the log and the 24-hour rule stay
• The /stats loop panel and bench_summary on the page (0.25 d of item 5) — both RPCs stay and are read in the SQL editor
• 'Your cards' on the profile (0.5 d of item 5) — card_stats and loop_funnel stay; makers who ask are handed their numbers by hand; stats_open then cannot be logged and the loop's last step is reported as n/a, not as 0
• The 'Made with' input and the end card's count line (0.2 d across items 1 and 3) — generation stays a column; the readout splits by brief_version only
• The trust floor on the fix day (item 8's 0022) — a takedown stays a same-day Hide with reason 'takedown' by hand, which is what the DM already promises
• The founder's one image and one clip (0.75 h) — pages first
• The second send on Day 11 — only if the freeze gate fails; the sprint then reports fewer than twenty stranger uploads honestly
• Never cut: migration 0020 with the trigger and card_set_status (the bench is the constraint that lets strangers' pages in at all, and the share link that resolves them), the save channel's host and viewer path with its e2e, the brief in src/lib/brief.ts with the CSP-list test, tools/fit-check.mjs runnable by hand and the Day-6 FIT GATE, the phone review of every deploy and of every bench card before Live, the Day-1 baseline column, the Day-7 mid-read, the Day-14 read

Day 14, Tue 6 Oct, from /stats (loop_funnel(14) and bench_summary() beside retention_daily(14,'make'), (14,'pilot') and (14,null)) and tools/sql/loop-readout.sql, written into docs/RETENTION.md beside the Sprint 2 baseline column and the Day-10 row, n at every funnel step and a binomial interval on every rate. Read in this order: (1) the rule — select count(*) from public.card c where c.status='live' and c.creator_id is not null and c.creator_id <> @rand's actor and not exists (select 1 from card_status_log l join actor a on a.actor_id = l.actor_id where l.card_id = c.card_id and l.to_status='live' and l.via='rpc' and a.is_admin) must be 0, and select count(*) from card_status_log where to_status='live' and via='sql' must be 0; the trigger makes both facts rather than conventions, and they are read before any number; (2) the funnel: brief copies -> make_open -> uploads -> fit ok -> live -> 10 sessions from 3 networks -> stats opened, by non-founder actors, complete loops against the >= 3 target (stretch 5) and non-founder uploads against >= 20; (3) fit pass rate on stranger pages, split by brief_version present versus absent and by made_with; (4) median hours bench->live and the oldest bench card at each day's end from card_status_log and bench_summary, with the cap reported beside the live count; (5) the guard rails carried from Sprint 1 on the same via filters — position-0 hold, reached-end, back taps — not below the Sprint 1 Day-14 row by more than the interval, with D1 by via reported with its interval and not targeted this sprint; (6) diagnostics, reported never targeted: save-channel keys on the founder's phone, uploads per brief copy, Hide reasons by kind, card_stats reads per maker, the fork's own number (a: card 0's hold from first-minute.spec and card_rank; b: whether the audition slot showed a house card each day; c: two seeds differing in production and the end card's exclude working; d: the Day-7 D1 with its interval), DAU with internal excluded, card_rank(14) for the deck (whether any founder page has 20 votes yet). Not read: any ranking number as a verdict under 20 votes, any promotion, any A/B, D7, anything a card self-reported. Demote-only stays exactly as written; the only thing this readout decides is where Sprint 3's engineering days and content hours go, and there is still no launch post until D1 holds on >= 200 browser arrivals at a day-21 read.

• Any non-founder card live in feed() without an admin card_set_status log row, or any card_status_log row with to_status='live' and via='sql', or any status change by anything but card_set_status or a hand Hide: the section-9 rule broke in code — nothing else ships until the path that skipped it is closed, and Sprint 3 starts there
• The FIT GATE fails on Day 6 (the tool disagrees with the founder's phone on two or more deck cards): the workflow does not write card.fit until it matches; the strip and my_cards say 'not checked yet' honestly and the founder's review is the only fit verdict that fortnight
• Fewer than 20 brief copies by Day 14 with both sends made: the door was never seen — the end-card 'Make one' door returns first in Sprint 3, and the sprint opens with where makers actually are, not with more supply tooling
• Twenty or more brief copies and zero complete loops: the loop is too long for a stranger — read where it drops (copy -> upload: the model's answers do not paste; upload -> fit ok: the brief is wrong; fit ok -> live: the founder's review hours; live -> 10 sessions: the deck has no traffic, a Sprint 1 problem again; 10 -> stats opened: the numbers are not found) and Sprint 3 fixes the single largest drop, nothing else
• Fit pass rate on stranger pages under 30%: the brief is wrong, not the makers — it is rewritten before another DM goes out, and BRIEF_VERSION 2's pass rate is read separately
• Median bench->live over 24 h or any bench card older than 48 h: the founder cannot review at this rate; the cap is real and honest, and Sprint 3 adds no supply channel until review hours exist — no content team, so the cap is the answer, not a hire
• A saved-state page fails to restore on the phone after BLITZ-away-and-back, or save-channel.spec.ts flakes twice: the channel ships dark the same day — the host path kept, window.blitz and the brief's save lines pulled — rather than half-remembering; a key over 4 KB accepted, or one card's state readable by another (audited on the phone and in the spec): the viewer is rolled back to Deploy 1 the same day
• Position-0 hold or reached-end below Sprint 1's Day-14 row by more than the interval, on the same via filter, after the founder's pages entered the deck: the pages the loop produces are worse than the linked sites for a stranger's first minute — the three questions become hard lines in the brief and card 0 is re-decided from card_rank, an editorial act
• The founder's own pages take over 45 minutes each through the loop: the brief is too long for a person; it is cut to a screen before the Day-8 send
• Fewer than 20 non-founder uploads with both sends made: the D1-style n problem — the loop is reported on the makers there were, the funnel with n, and no rate is spun into a verdict
• Fork (d): D1 still in the gray zone at the Day-7 read on ~150 browser arrivals — week 2 goes to the first minute (the (a) swap), because another founder wave cannot narrow it; no seed cohort, no post
• A takedown not honoured the same day, or a stranger's page found live that was never opened on a phone: the trust floor (Report / Remove it) becomes Sprint 3's first item regardless of the numbers

• Any generation endpoint, any model call from our side, any 'make anything' prompt box, any auto-flip to live on a fit verdict — never for anonymous visitors, and not for accounts this sprint: the brief is the creation path; a person admits what executes in front of strangers
• The in-sheet 375x667 preview — it needs a preview mode in the viewer (a srcdoc frame inside the feed inherits the feed's CSP, not the viewer's) and a scaled frame in a sheet on a 375-wide phone; the card itself, next in the maker's own feed and unlisted, is the preview, and the fit verdict on the profile is the check
• The end card's 'Make one' door and the image/clip aspect line — ?make=1 and the + sheet's third tab are the door this fortnight; the media viewer letterboxes; both return in an hour if the brief-copies kill criterion fires
• Composition outside fork (c): feed(n, seed, exclude) as a core item, the on-device returning order and held record, tier-drop demotion, verb families, 'N new since <day>', the rewrite of every e2e spec off the slots-0-to-4 contract — over an eight-card deck the shuffle is inert and Sprint 1's fork (a) says not composition
• Add-to-home-screen on the end card, web push, D7, the return-read columns (unseen_at_0, return_pos0_hold, card_exposure) — second-visit mechanics for a cohort that does not exist yet; unreadable at five to ten return visits
• The sixty-candidate platform harvest and tools/harvest/check.mjs — human-made platform embeds are the comparison, not the thesis; tools/fit-check.mjs runs on a URL by hand for the one or two the founder links through the + sheet
• bench_cap() enforcement with an 'override:' path — at pilot traffic the formula's floor binds and would throttle AI-page supply exactly when fork (b) says the deck is too short; the cap is reported by bench_summary() and the founder's daily phone pass is the cap
• The blocked_term filter and pageSummary as an admission gate — a client-computed string refusing an upload is theatre and contradicts 'hint, never the gate'; the phone review is the gate and content_hash is the part worth keeping
• Auto-hide on removal requests or on three reports from three networks — three phones would then remove any card, a bigger lever than demote-only ever gave a forger; if the trust floor ships it is a queue the founder clears the same day
• The claim flow (claim_card, ?claim= tokens, 'This is mine'), 'Open in browser' and source_url — nothing harvested means nothing to claim; a DM yes is relabelled by hand and the trigger logs it
• The nightly recheck_external_cards() under pg_cron and the pg_cron dashboard step — two or three external cards; a weekly hand run of embed_check until the deck has more than a handful
• The card_rank house-ticket rewrite outside fork (b) — elsewhere it touches the fabrication-proof ranker for no reader
• Per-account server-side saved state (Supabase rows for window.blitz.save) — the localStorage relay is per device; accounts get rows when a maker's page needs to remember across devices, not before
• Remix-by-pack (STRATEGY bet 7) — it was for the eleven hosted toys, which are hidden; one possible later creation path, not this sprint's
• Promotion on telemetry, per-actor affinity, any change to card_rank beyond the exclusions already in it (and (b)'s audition tickets), anything a card or client reports entering any rank — fit, saved state, likes, made_with, card_stats included
• The launch post, Show HN, any community post, the 200–300 seed cohort, paid dollars — no launch post before the day-21 D1 bar on >= 200 browser arrivals
• A topic taxonomy, an onboarding screen, a pick-your-interests step, coach marks — the brief is the only text a maker reads and the first card is the only onboarding a visitor gets
• A content team or paid generation spend — the founder's ~15 h/week inside the loop is the supply; hiring for content is the signal the loop failed
• The hosted-card 'Still there? Tap to continue' restyle and the wasm idle redesign — no wasm card is served; the html viewer's probe keeps touched pages alive
• Mirror mode for anyone outside mirror_host — consent only, as 0016 wrote it
• Merging actors across devices (ACCOUNTS.md's known limitation) — card_stats excludes the creator's own actor on this device only; the limitation is written under the number
• growth_weekly, sprint_readout, a chart on /stats — one admin RPC (loop_funnel) beside retention_daily, tables not charts

Each with the default the sprint runs on if nothing is said.

• 1. Bench visibility (the one place section 9 bends): a bench card reachable at its /c/<slug> link for anyone versus creator-or-admin only — default: creator-or-admin only until the fit tool has written fit_ok = true, then anyone with the link (unlisted: absent from feed(), cards_by(), the end card's re-read and the audition), so no unreviewed stranger page executes for a third party before a verdict exists; hidden and blocked never resolve; the founder can widen or tighten card_by_slug with one line
• 2. Who skips the bench: nobody (the founder's own uploads wait too and are flipped from the strip in one tap — one code path, the rule kept literally, the strip dogfooded) versus admin uploads live directly — default: nobody skips
• 3. What a failed fit does: accept to the bench with the verdict visible to the maker and the reviewer (never auto-hide, never refuse) versus refuse the upload with the reason — default: accept to the bench; a person decides, and a page that paints 40% might be a page whose first touch does everything
• 4. The save channel's scope: this device only (localStorage on the feed's origin, keyed by card id, 4 KB, one write a second) versus per-account rows now — default: this device only; the founder can name the first page that needs cross-device memory
• 5. The brief's external allowance: the html viewer's CSP list as it stands (cdnjs, jsDelivr, unpkg, esm.sh, skypack, jspm, Google Fonts) versus inline-only — default: the list as it stands, because the viewer already permits it and a model asked for p5 will reach for a CDN; brief.test.ts keeps the two identical
• 6. Make one for anonymous visitors: the brief readable by anyone with the account door on Add (default) versus the whole tab behind the door — default: readable; a brief is text, and the person has to leave for minutes to ask a model before they could possibly need an account
• 7. The maker ask, in order: the two or three known makers (Day 5), then ten makers already posting AI-made pages on r/vibecoding, r/ClaudeAI 'I built', Bolt and Lovable showcases, X or Bluesky together with the pilot's repliers (Day 8), then the rest of the pilot list (Day 11), by DM only, never a post, never where a community forbids it, nobody's page linked before a yes — default: that order; under (d) the Day-8 send waits for the Day-7 read
• 8. What a maker sees: 14-day counts with the creator's own sessions on this device excluded, impressions as distinct sessions and viewers as distinct actors, shown from the first impression with no minimum n hidden behind a dash, and the cross-device limitation written under the table — default: yes; a maker who sees '3 people, 2 stayed' has been told the truth
• 9. Under fork (a), whether card 0 is re-decided by editorial act on Day 3 from the fit verdicts and card_rank(14), or Deepstate stays until outvoted at 20 votes as Sprint 1's ruling said — default: re-decided on Day 3 only if the fit tool says Deepstate does not fit 375x667 (painted_3s < 60% or overflow_x); otherwise the Sprint 1 ruling stands and 0023 card_zero on Days 8–10 writes whatever the ruling is with the fixtures in one commit
• 10. Sprint 3's headline, chosen now so the readout cannot be spun: complete loops by strangers (this sprint's number) or D1 on browser arrivals at day 21 (STRATEGY section 7's bar) — default: both are written, D1 is the bar for any launch post, loops are the bar for the creation path, and neither substitutes for the other
• 11. The fit-check cadence on a private repo's metered Actions minutes: hourly with an early exit when nothing is unchecked (a checkout and a psql per empty hour) plus workflow_dispatch, versus dispatch only after each bench pass, versus by hand — default: hourly with the early exit; if the minutes bill by Day 5 says otherwise, dispatch after each bench pass, and the column-check assertion stays at 24 h either way
• 12. 'Made with' as an optional self-declared field on the Upload and Make tabs stored in card.generation, shown on the review strip and the maker's own profile only, never verified, never in the visitor strip — default: yes, optional; the model name is the maker's word and the readout splits the fit pass rate by it
• 13. Under fork (c), whether composition-lite ships this sprint (if Deploy 3 is live by Day 6 and the Day-10 sequencer gate passes) or waits for Sprint 3 — default: ships, because a deck that differs per device is the first thing a second visit needs and it reads no rate; it is the first thing dropped if the fix day has a P0