Discovery first.

Observed on the live site on 7 September, before the chrome fix (viewport between the bars, meta strip below the card) shipped that evening. The other findings stand.

Founder's positioning, 25 September — this is the headline, and everything else is read under it. Blitz is a feed of content, much of it made with AI: pictures, videos, graphics, web pages and games. AI-generated content is getting better every month and is about to explode — we are entering an AI renaissance — and Blitz is the feed built for it. Blitz is not a gaming platform, and "things you play" is not the headline anywhere: a game is one kind of card among many, beside the image, the clip, the graphic and the page.

What sets the feed apart is what it trusts. TikTok's ranking is built on a watch-time signal it can see end to end; Blitz cannot see inside a card that runs its own code and refuses to trust what a card says about itself, so its only currency is what a phone gives away honestly: whether you stayed, and whether you pressed the button. The next card is a different kind of thing, and one button is the whole interface. StumbleUpon was the existing web filtered by people, and it died when the web stopped fitting the frame; Blitz's supply is the part of the web that fits a thumb, plus a generator that makes more of it on demand, plus the people who made those things, who can be shown host-measured numbers nobody else will give them. Roblox is a place you install, join and learn; Blitz is one URL, no install, no sign-up, playing before the network answers. For the next twelve weeks the thesis is one sentence: cards 18 onward come from a generator the founder runs and a web the founder harvests with the maker's yes, not from creators who have not arrived, and none of them goes live faster than the feed can give it a verdict; and until a hundred networks a day are voting, the feed's job is composition, not ranking — a different kind of card every BLITZ, shuffled per visit from what this phone has already held, looping, never ending on a dead button, and remembering you when you come back. The thesis carries its own test, written in section 8: if seventeen cards under the new chrome and composition do not move position-0 hold and depth, no number of generated cards will, and that is a verdict on the feed, not on the catalogue.

This is the designed first session on a phone, cold, no account. Timings assume the measured numbers (85 KB bundle, hosted toys painting in 100–260 ms) with the boot no longer gated on Supabase.

1. 0.0 s — the shell

   Dark ground; the feed is dark-only (the light shell around dark cards goes; the landing keeps both themes). Top bar: the BLITZ mark left, the person icon right, and a thin progress line between them — the seventeen dots become a line because decks will soon be thirty cards long. Centre: the slide-thumb of card 0 (its thumbnail and title) drawn from the bundled catalogue, not a spinner. Bottom bar: a 36 px back chevron on the left, dim because there is nothing behind it yet; the violet BLITZ button, centred, with a 48 px hit area; nothing else. Under BLITZ, the word "next" in 10 px caps — shown until the first press ever on this device, then never again. That word plus the glowing button is the entire tutorial. No stats cells, no Developer-toolbar button, no "+", no coach marks.

2. ~0.5 s — card 0, Ripple Tap

   The iframe paints before anonymous sign-in and feed() return; the transport queues batches until the session exists. Ripple Tap's own ghost pointer is already rippling the grid. Any touch anywhere produces a ripple; nothing can be failed. The meta strip sits below the surface, never over it: "Ripple Tap · @blitzlabs · toy" on the left, Like and Share as two 40 px icons on the right, and a small "…" beside them that holds Report (and, later, Remix). Ripple Tap is the opener for every first visit. The Gravity Well comparison waits until after the retention bar: 100 first visits per arm is the whole seed cohort's card-0 signal, spent on a ±10-point answer, and the position-0 bar cannot be read across a split.

3. ~6 s — first BLITZ

   320 ms slide; card 1 is already running because N+1 is preloaded. Stack Drop: a game with a score, ten-second rounds, instant restart. The word in the strip is "game". The first tap drops a block; the result is visible. The back chevron is now live. Pressing it returns to Ripple Tap, still running. The chevron is the way back and the only one: browser history stays one entry (replaceState, for the reason share.ts documents), because hardware Back and the iOS edge-swipe arrive as the same popstate and cannot be told apart, so history-as-deck would let an OS gesture move the feed and end sessions mid-drag on cards that own the left edge (Bloom's wind, Colour Split, Echo Lines). Whether one sentinel history entry so that Back steps one card is wanted, knowing it must also answer the edge-swipe, is a one-sentence ruling the founder gives before bet 1 ships; the default is no.

4. ~15 s — second BLITZ, the daily slot

   Slot 2 is "New today": the day's audition pick — a factory toy, a remix, or a harvested sketch under 30 lifetime votes — with the word "new" in the strip, drawn by a lottery that rotates by provenance from day to day, which the ranker as written cannot do (section 6). When nothing qualifies it is Gravity Well. This is the one slot every visitor shares, and the reason tomorrow is different from today.

5. 15–60 s — slots 3 to 8

   A shuffle seeded by this device and today's date, under one hard rule: no two consecutive cards share a verb family (timing, ambient, tap, drag, plan — a normalised map, not the raw verbs), with same source and same template as penalties the sequencer avoids when it can and drops when it cannot, because eleven of seventeen cards are hosted and a rule that forbids hosted adjacency cannot be satisfied on the catalogue it runs on. Tide Pool (ambient) then Orbit Cut (timing) then a sketch harvested from its platform's embed page (site, by its platform, with a permanent "Open" at the right of the strip) then Colour Split (this-or-that) then Echo Lines then Pulse Lock. The five wasm test games appear no earlier than slot 8, as variety rather than first impression, unchanged except that their idle pause is a dim of the surface plus one line, "Still there? Tap to continue", and a tap within 60 s continues the same session — a pause at 20 s and an exit at 80 s under one session id, which is a change to the host, the worker and the agent, not a flag. Hosted toys never pause: each carries the snippet and the host sees every touch. A linked site has no timer at all and no alarm either: from outside the frame the host cannot tell a working page from a blank one, so blankness is decided once, at admission, on a phone-sized render, re-checked nightly, and the strip's "Open" is there all the time.

6. ~60 s

   The visitor has seen eight to ten different kinds of thing. A Like on Gravity Well was recorded. A Share from Tide Pool said "Play this." (not "See if you can beat it", which is now reserved for cards that have reported a score); when the OS sheet closes, one line offers "Want credit when they play it? Claim a handle" — the only account ask in the first minute, and only after intent.

7. The end of the deck

   After the last card, a hosted end card, not a dimmed button: "That was all 24. You've seen 24. New card tomorrow." with Again (a fresh shuffle minus what you held), Share Blitz, and Link something for accounts or Claim a handle for guests. BLITZ on it fetches a new deck minus what you held; the button never dims and aria-label "End of feed" goes away. If the visit arrived inside an in-app webview — Reddit's, Discord's — the end card's first line is "Open in your browser", with the address to copy, because a webview's storage is not Safari's or Chrome's and a return from the home screen would be a stranger to us.

8. The second visit

   Nothing in the frame can remember you: hosted cards run in an opaque origin under a CSP with no connect-src, so localStorage throws and there is no server. The host remembers instead. blitz-card.js carries a save channel, and Stack Drop's strip on a return reads "your best: 14" from state the host kept for that card on this device; a drawing tool keeps the drawing, a puzzle keeps its progress. A returning device opens on "New today", then the card it held longest, then the unseen interleaved one-to-two with what it held, weighted towards the verb families it stayed for — all from this phone's own record, which the server never reads. After the second held session ever on this device, one card in the deck is an add-to-home-screen card (beforeinstallprompt where it exists, the two-step iOS instruction where it does not), shown once. Accounts get one web push a day, "New card: <title>", from week 3.

9. Removed from the screen

   , named: the five bottom-bar stat cells and their shrink rules; the Developer-toolbar button (the toolbar stays behind ?dev=1); the MIG verb chips (verbs stay in the data; one plain word — toy, game, puzzle, site, new — renders); the Tip button and its "Active Mechanical Seconds ledger" toast; the "Ready — compiled and paused at tick 0" badge on the incoming slide; the "Compiling…" spinner card; the <code> crash string (visitor copy: "This one did not load. BLITZ for the next."); the light feed theme; the "+" for anonymous visitors; the white Paused modal; the dimmed BLITZ at the tail; the floating rail over the card surface; on the landing page, "Create account" as the primary CTA, the "Dev tools" footer link, the "<1s to first play" fact, and the Cannae, data-explorer and quiz promises; in Supabase, email confirmation — after the concierge makers' handles are reserved, because an unverified account is free and a handle is the only thing in it worth squatting.

Ordered by expected retention impact per week of work. Every bet is startable today by one engineer with an agent; none needs a second engineer to begin. Costs: days means under one working week; weeks means two to four; months means a pipeline built in days that runs for the quarter.

To a catalogue with a verdict, not to a number. Three sources, one review, one bench. In the first quarter: sixty probe cards from the factory (twelve families, five each), the harvested cards that pass the phone-fit check from platforms built for embedding and from makers who said yes, and the cards other people make — claimed harvests, concierge makers' second cards, remixes. Every one of them is opened once on a phone by a person before it leaves the bench, and reviewed against three questions only: does it respond to the first touch, does it fit 375x667, would you show it to someone. Admitted cards wait on the bench and go live only as fast as the feed can judge them — the live fresh set is capped at what 28 days of votes can carry to 20, about fifteen cards at today's traffic and fifty at the target — oldest-reviewed first, rotating by provenance. Live cards enter at the tail; the daily slot is their only distribution until they have votes, and the lottery rotates by provenance from day to day so "New today" alternates among the factory, the harvest and the remixes rather than by anyone's taste. The number of live cards at week 12 is whatever graduated; the target is that every one of them has a verdict.

To 5,000. The same three sources, with the gate on review moved, not removed, and the cap on the live fresh set raised only by traffic. Remix-by-pack scales without review because packs are inert and their strings are filtered. Full-code generation opens to accounts, not anonymous visitors, and only after a per-creator track record: three graduated cards holding within 10 points of the pool. Review becomes sampled — every card from a creator with fewer than three graduated cards, one in five otherwise — once the lint and smoke have 500 graduated cards of precision data behind them. Families expand from five cards to twenty-five only on pooled deep hold and share taps. Harvest scales by platform, driven only by per-platform numbers. The end-of-feed "Make one" entry opens when the factory's first-try pass rate is above 60% and the first 500 have been played, because a generation path that fails four times in ten in front of a stranger is a bounce, not a feature.

What is automated. Generation from the family spec; the lint; the smoke; the screenshot and thumbnail; duplicate refusal at admission; insertion on the bench; bench-to-live within the cap; the audition lottery; the nightly header re-check and the weekly pixel check on external cards; auto-hide (never auto-block), by card_set_status under pg_cron with a card_status_log row for every flip, on host-detected crash rate above 25% over eight or more votes, on a snippet heartbeat that stops while dwell continues, on a re-check failing, or on reports above 3 per 100 impressions over 50 or more impressions; the string filter in submit_pack; the daily and weekly readouts.

What is deliberately not. The grid — which families exist and how many of each — is decided by a person against the per-family deep-hold and share numbers, never by what the generator finds easiest and never by 5-second hold, which a screensaver satisfies. The yes/no on a phone. The flip from hidden to blocked, or back to live. A takedown. Promotion of any card into the top three. The DM to a maker. No model ever decides what executes in front of strangers; the model makes, the lint refuses, a person admits, the bench waits. The Deepstate lesson stands: framing permission is not fit, and only a phone-sized render can tell.

The founder's week. One person ships bets 1 to 8 and runs the content. The standing hours, per week, once the pipeline exists: phone review, about three minutes a card, three hours for the sixty-card probe spread over three weeks; harvest triage, about three hours per hundred URLs; the concierge, five hours; generation spend at a 60% first-try pass, cents a card; Netlify bandwidth trivial with cards committed rather than proxied. Around fifteen hours a week on content against a full engineering week, which is why the probe is sixty and not three hundred. When the hours run out the order of what stops is: the concierge, then harvest triage, then generation beyond the first six families; the measurement, the pilot and the phone review of anything that goes live are never cut. Hiring for content stays the signal the loop failed.

Today, per docs/RANKING.md and card_rank: editorial order is the ranking; a card needs 20 real votes before it can be demoted, only from positions ≥ 2, one slot per 0.10 of hold-rate deficit against the pool, capped at three, never out of the top two; a 40-pseudo-vote prior, a one-sided 90% upper bound, a 28-day window with a 14-day half-life; one network one vote per card per day, at most 20 votes per card per day; first-ever sessions, pure-bounce actor-days, internal actors and a card's own uploader never vote; one upload a day auditions at slot 2 until it has 30 lifetime votes or is 30 days old. RANKING.md says promotion opens "when there are enough distinct networks voting per day that one-network-one-vote makes fabrication expensive" and leaves the number open. This plan sets it.

Gate 0, now: composition, not ranking. Everything in bet 4 reads tiers that are editorial data — anchor is card_editorial, fresh is age under 14 days or votes under 20, tail is the rest — and interleaves by verb family, with source and template as penalties. It never reads a hold rate, directly or through an indirection, so a forger gains nothing from it. Demote-only stays exactly as written in SQL and, because a one-slot move inside a shuffled tier would be invisible, gains a v1.5 rule that makes it bite in the feed: a card demoted two or more slots drops a tier. And the audition slot is rewritten, because as written it does not reach the cards this plan makes: explore_pool draws one ticket per uploader actor, requires the uploader not to be internal, and distinct on (uploader_actor_id) … order by created_at shows that uploader's oldest card until it clears 30 votes — so sixty factory cards and every harvested card under the founder's account would share one ticket and show the same oldest card for a month, and zero tickets the moment the founder's account is marked internal, which it must be before the first seed link or every test tour votes on every editorial card. The change, shipped with bet 4: a house flag on actor; for house uploads the pick is md5(current_date || card_id) over eligible live cards bucketed by provenance, with the bucket rotating by day; the internal exclusion applies to voters, not uploaders; the three-held-cards test stays for outside uploaders. Before day 3 the three-line SQL that shows today's pick against a seeded house card runs; if it returns Gravity Well, nothing about "New today" is true.

Gate 1, position-adjusted promotion within tier. Opens when distinct voting networks per day (count distinct ip_hash in card_event) has been at or above 100 for 7 consecutive days and at least 20 cards carry 20 or more votes — a condition the bench cap of bet 5 is what makes reachable at all. Why 100: the daily sample per card is capped at 20 votes drawn from the day's networks, so at 100 networks a forger who wants to own a card's sample needs dozens of distinct addresses every day for the 14-day half-life to move it five slots — more than the slots are worth. Mechanics: hold is regressed on the feed_position bucket the client has been stamping since v1, sessions with visit_ordinal 1 are excluded as orientation, one-network-one-vote and the 20-vote cap stay, and a card may rise at most 5 slots a day within its tier. The editorial top three and the audition slot are untouched.

Gate 2, per-actor verb affinity. Opens when at least 30% of actors in the 28-day window have sessions on two or more distinct days, and there are at least 500 such actors. Per actor, held versus bounced by primary verb over 28 days is the whole interest vector — for a playable card, interest is not a topic; it is how you like to touch (tap, drag, time, plan), the tempo (calm or twitch) and the goal shape (score, finish, toy, social object). The next-card picker draws from the actor's top two verb families three times in four and from a family they have not played once in four. Actors with hash mod 10 = 0 are a permanent no-personalisation holdout, and the gate stays open only while personalised actors beat the holdout on cards per visit and D7. The on-device ordering in bet 4 is not this gate: it reorders one phone's deck from that phone's own record, the server never reads it, and it opens no fabrication surface; this gate is the server learning across phones, and it waits.

Gate 3, promotion into the editorial block. "Goes viral, ranks first" opens at 1,000 distinct networks per day sustained for 14 days, still one vote per network, still capped, still only on held and bounced. Until then, moving a card into the top three is an editorial act, as it is today.

Nothing a card or a client reports ever enters any gate: not Like, score, touches, beats, saved state, remix counts, reports or share taps. They are diagnostics, and they stay in their own columns.

Blitz can only grow through sent cards and through makers, because the product is a URL and the makers are the only acquisition channel that also fixes supply. The channels, in order:

1. Founder-controlled links, in two steps — a 100-visit personal pilot the day bets 1 and 2 are live, ?via=pilot, read for two days; then the seed cohort of bet 3, 200–300 visits from the personal network, r/WebGames and one generative-art Discord, every link ?via= tagged, sent only after composition is live, because it is the one denominator this plan gets for months and it is not spent on a fixed-order feed. Reddit's and Discord's in-app webviews keep their own storage, so a person who comes back from Safari is a new actor to us; ua_class is recorded on arrival, retention is read on browser arrivals only, and the end card tells webview visitors to open Blitz in their browser.
2. The creator concierge — three makers a day from day 10, each DMed a link that opens their thing playing on a phone with an OG image, the feed as the bonus, the claim as one tap, the numbers only when there are enough of them to mean something. Every claimed creator is a channel with a face and an audience that already likes their thing.
3. After the gates only: Show HN "the feed for what people make with AI", r/InternetIsBeautiful, and three 15-second vertical recordings (Gravity Well, Tide Pool, Bloom) on TikTok and Shorts with the card's /c/ link in bio, each with its own ?via=. The source with the best D1 × depth gets the next month's founder hours.

The retention bar, read from growth_weekly before any broader post, in three reads. Day 14, on the pilot and the first days of the cohort: position-0 hold ≥ 50%; median cards per visit ≥ 8; IDLE_TIMEOUT share of hosted-card exits < 10%; share-to-arrival ≥ 30% (new actors with entry_surface='share' divided by share taps); arrival hook ≥ 50% (share arrivals with visit_ordinal ≥ 2). Day 21: D1 ≥ 10% on browser arrivals from the cohort, with its interval written next to it. Day 28: D7 on the same. D1 is only worth gating on once there is a way back — the host-held state and the add-to-home-screen card ship in the fortnight, the daily push for accounts (VAPID plus a Supabase cron, about a day) in week 3 — and until day 21 the plan says plainly that it has measured first sessions. If the day-14 bar is not met, weeks 3 and 4 go to the first minute and composition, not to supply and not to posting. Paid channels stay off until D1 ≥ 20% on ≥ 1,000 organic new actors. There is one first launch, and sending a Show HN crowd into a feed that dead-ends in two minutes spends it on the wrong build.

The critical path is chrome and snippet, deploy, pilot, fix, composition, cohort. Everything else runs beside it and is what gets dropped when hours run out, in this order: concierge, harvest, factory beyond six families, landing. The pilot is never dropped and the readout is never moved.

1. Day 1

   The baseline row first: from the 61-batch tours and one fresh headless tour, today's position-0 hold, median depth, IDLE_TIMEOUT share on hosted cards, SWIPE_UP-within-3-s at position 0 and boot_ms, written next to every target in this document before any code. Confirm the live build is 6e5c69d; screenshots of Tile Flip and Colour Split. The CSP line for /cards/* in public/_headers and netlify.toml; verify-cards green. blitz-card.js written with the save channel and inlined into all eleven toys. The internal-flag function run for the founder's, the checker's and the smoke's actors. Push to main; Netlify builds. Measured next morning: IDLE_TIMEOUT share of hosted-card exits.

2. Day 2

   The migration: ui_event and log_ui with report; liked, boot_ms, the diagnostic counters and the SWIPE_DOWN exit as ingest_batch columns; entry_source from ?via= and ua_class; bench, provenance, template_id, parent_card_id, content_hash, platform, platform_terms, pack, generation on card; house on actor; card_status_log and card_set_status; ingest_batch joins lineage from card; the explore_pick rewrite and the SQL check that today's pick is a house card; growth_weekly v0. captureEntry reads ?via=. The card_editorial rewrite with MOCK_GAMES, feed.json, tools/seed-cards.mjs and the e2e fixture in one commit.

3. Days 2–5

   Consumer chrome behind ?dev=1; one plain word per card; Like, Share and the "…" with Report in the strip, Tip gone, share text per class; the back chevron on goTo(i-1), the founder's ruling on the sentinel; idle policy (external no timer and a permanent "Open", wasm pause at 20 s and exit at 80 s under one session id with the e2e contract rewritten); card 0 from the bundle, session before feed(), reconcile behind the active index; /c/<slug> resolved and spliced at 0; boot_ms; the end card with the webview line; the add-to-home-screen card; Stack Drop's "your best". Deploy on day 5.

4. Days 3–6

   Landing front door: "Open the feed" primary to /c/ripple-tap?via=landing, "Create account" to the creators section, three real card names, measured or no "<1s" fact, no "Dev tools" link; "+" hidden for anonymous visitors; the concierge makers' handles into reserved_handle, then Supabase Confirm-email off.

5. Days 5–7

   The pilot: 100 visits through the founder's own network, ?via=pilot; position-0 hold, depth and IDLE_TIMEOUT share read against the baseline row on day 7; what it shows is fixed before composition ships.

6. Days 6–9

   Composition v0: feed(n, seed, exclude), editorial tiers with tier-drop demotion, slot 2 as "New today" from the rewritten lottery, wasm games at 8 or later, seeded shuffle on verb families with the sequencer test green on both sides, fresh slots one in two, the on-device order for returning devices, BLITZ on the end card re-fetches minus held; client seed and bundled mirror. Ripple Tap is the opener for everyone. Deploy on day 9.

7. Days 5–10

   The factory: template with the pack block and the inlined snippet; lint with the meta CSP and the save-channel rule; dedupe; smoke; WebP thumbnail; the phone review page; the commit-a-day path with verify-cards in CI; the first thirty probe cards across six families — word toys, quizzes with a score, this-or-that, sound, drawing, micro-story — five each, onto the bench; the cap computed from the pilot's numbers and the first bench cards let through it.

8. Days 8–12

   The checker script (no RPC); 100 candidate URLs from Shadertoy, Scratch, OpenProcessing and p5.js embed pages and itch.io HTML5; the 25 that pass reviewed on a phone and inserted on the bench with developer = domain, platform and platform_terms set; the nightly re-check under pg_cron. Concierge from day 10: three makers a day, DMed a phone link that opens straight to their work, with a claim token.

9. Days 10–12

   Seed cohort: 200–300 visits through founder-controlled links, ?via= and ?r= on every one, into the composed feed.

10. Day 14

    The readout from growth_weekly, with cohort sizes and the baseline row beside it: position-0 hold, depth, IDLE_TIMEOUT share, share-to-arrival, arrival hook. Not D1 — nobody who arrived on day 12 has a day-21 yet — and not D7. Result: about 70 cards admitted (17 plus 30 probe cards plus 25 harvested plus the makers'), of which as many live as the cap allows, a feed that differs per visit, remembers the device and never ends, web cards that can be measured, and a cohort large enough to read the first bar. Day 21: D1 on browser arrivals. Day 28: D7, and the go or no-go on the launch post.

Kill criteria

• If IDLE_TIMEOUT share on hosted cards is not under 10% by day 4, the snippet is not reaching the host; nothing else ships until it does, because it is the measurement.
• There is no opener A/B in the fortnight; Ripple Tap opens for everyone, and the Gravity Well comparison runs after the bar at 200 first visits per arm or not at all.
• A factory family whose five cards, at 50 pooled votes, sit more than 10 points below the original eleven on deep hold or share taps gets its spec rewritten before another card is made; a second rewrite drops the family. If median days-to-graduate exceeds 28, generation stops until it does not.
• A harvest platform more than 10 points below the hosted toys on the same two numbers is dropped; checker pass rate under 30% on approached URLs means the hunting ground is wrong.
• If median depth over the cohort does not rise against the pilot, the shuffle goes; the editorial top three and the on-device order for returning devices stay.
• If the day-14 bar (section 7) is not met, no launch post; weeks 3 and 4 return to the first minute.
• And one for the thesis, not a bet. If, with seventeen cards under the new chrome and composition, position-0 hold and median depth do not move against the baseline row across the pilot and the cohort — hold still under 40% and depth still under 5 on day 14, with no upward trend between the two reads — that is the verdict on the feed, not on the catalogue. Then the factory stops at the probe, no cohort is spent on supply, and the founder's next fortnight goes to the question of whether Blitz is a feed people return to at all.

• No wasm or C SDK ecosystem, no porting games for supply.The five wasm cards cost far more than the eleven toys, read as test fixtures, and were the worst first impression the feed had. The ABI stays as it is until a creator asks for it.
• No promotion on telemetry and no personalisation before the gates in section 6, including through a tier boundary.At tens of sessions a day any promotion path is a ranking by willingness to fabricate, and a tier whose membership reads a rate is a promotion path with one more step. Demote-only is the rule until the numbers say otherwise.
• Nothing a card or client reports ever ranks.Like, score, touches, beats, saved state, remix counts, share taps — recorded as diagnostics, never as votes.
• No open-prompt "make anything" for anonymous visitors in the first 500 cards, no ungated generation endpoint, and no model ever flips a card to live.Remix-by-pack is the only in-product generation path until the lint and review have a track record, its prompt box is for accounts with a handle behind its own bucket, and a person admits what executes in front of strangers.
• No card goes live unreviewed on a phone, no card goes live faster than the feed can judge it, and no harvesting of desktop layouts.Framing permission is not fit; the feed cannot see a blank or squeezed frame from outside, and Deepstate is the proof. A catalogue that outruns its signal is Instant Games, and the bench is the refusal.
• No framing a person's work before asking.Platform embed endpoints built for third parties are fair; a maker's own page is asked first, every harvested card carries "Remove it" next to "Claim it", and a takedown is honoured the same day.
• No swipe or gesture feed navigation.The founder's rule stands, and discovery does not need it — composition is what makes the next press worth taking. That includes history-as-deck: the chevron is the way back, and a sentinel entry so that hardware Back steps a card, which cannot be told from the iOS edge-swipe, ships only on the founder's explicit ruling.
• No spend on tips, the ledger or payouts.The Tip button is gone; the rate stays at zero; the creator payoff for the first year is a phone link that opens straight to their work, host-measured numbers and feed position.
• No topic taxonomy, no pick-your-interests step, no onboarding screen, no coach marks.The verbs plus held/bounced per verb are the interest model — on the device now, on the server after Gate 2 — and any question asked before the first play costs the first play. The first card is the onboarding.
• No longer idle timer as the fix for hosted cards.The snippet is the fix. External cards get no timer at all, which is a different thing: their session ends on exits the host can actually see.
• No RPC that fetches a URL for an anonymous caller.embed_check was revoked from clients for a reason; the checker runs on the founder's machine and submit_link checks on insert.
• No launch post, press or paid dollar before the retention bar, and no opener A/B on the cohort that has to answer it.There is one first launch and it is not spent on a two-minute feed.
• No content team.Cards 18 onward come from the generator, the harvest and the makers they surface, inside the founder's fifteen content hours a week; when the hours run out the concierge and the harvest stop before the measurement does, and hiring for content is the signal the loop failed.