The Codex

Depends what kind. Funnel ticks (Outreached, Interested, Key Sent, Covered): fix them on that campaign's War Table - unticking is deliberate and row-by-row, because history is added in batches but erased one line at a time. Creator details (name, email, country, agency, tags, notes, platform links): open their character sheet - from any table, click their name - and edit right there.

Every fix is signed with your name in the Annals, so correcting data never needs permission - it leaves a trail instead. If something looks structurally wrong (duplicated rows, a campaign missing entirely), tell Jake - the Chronicler has repair tools for exactly that.

Subscriber and follower counts are API-owned: the Keep re-pulls them from YouTube and Twitch, so nobody ever "fixes" a number by typing over it. If the number is wrong, the cause is almost always a wrong link - the API is reading the wrong channel.

Fix: character sheet → Edit manual → correct the YouTube/Twitch URL → Refresh numbers. The right channel's numbers land immediately. TikTok, X, and Instagram have no API, so those numbers are hand-maintained in the same panel - if you know them, type them in.

A creator with no numbers at all usually arrived via an early coverage report (name and VOD link only) - since July 2026 coverage arrivals bring their size and region in from the report itself. Add a bare record's channel URL once and the APIs take over from there.

Not anymore. Open their character sheet (Edit manual), the Contribute workbench, or the Gatehouse's admit form, and under each empty platform field there's a dotted "Seek their Twitch →" (or YouTube, or TikTok). Press it and the Keep searches by the creator's name - Twitch and YouTube through their own official APIs, TikTok through Google's results - and offers what it finds as chips: name, follower count, a LIVE marker for Twitch. A count chip leads the row: "1 found - likely them" or "6 found - pick carefully".

You pick; nothing ever links itself. Telling Gronkh-the-streamer from gronkh_fanpage is a human's judgment, so clicking a chip only fills the field - your normal Save is still the write. Pressing again on the same creator within a day re-serves the cached answer and spends nothing, and the chips row shows the day's usage meter. TikTok follower counts stay hand-kept as always (TikTok has no public API - the link is the prize).

Yes, everywhere it matters. Export CSV on the War Table (the campaign table) and the Muster Roll (the current filtered view - so "Iridescent only" exports as the iri list). Client report on the War Table and Orb builds the client-facing XLSX in the house template - At a Glance stats plus Organic Twitch/YouTube tabs. All of it opens straight into Excel or Google Sheets.

Campaigns with a connected mapping doc also have Sync to Sheet, which rewrites the doc's live-status tab in place.

Both directions, differently. Reading: connect a campaign's coverage report sheet on the War Table, and Watchtower Earned reads it - everyone found gets ticked Covered, view counts and watch hours land on their rows, and Refresh numbers re-reads the sheet (D7 → D30 → …) and live-checks every count against the platform APIs. Writing: the Client report button generates the outgoing XLSX from the Keep's own data.

Report shapes differ per client - BHVR takes per-beat milestone snapshots, Capcom the full D30 with learnings, smaller clients whatever the campaign calls for - which is why the export asks for a free-text label instead of assuming. Sheet ticks flow back too: Pull from sheet on the War Table reads the mapping doc's ticks in - ticks flow in, unticks don't, so a stray sheet edit can never untick the Keep. Funnel truth lives here; sheets carry prose and keys.

The flip side of that rule (worth knowing, said plainly): un-doing a mistaken tick only counts in the Keep. Unticking a cell on the sheet does nothing here - the pull will just report that cell as sitting behind. If a tick was wrong, untick it in the War Table's own campaign table (row edit - deliberate, per-creator, signed) and the next push writes the correction back out to the sheet. The pull preview now names any sheet-unticked-but-Keep-ticked rows so this case is never silent.

No, and it isn't trying to. Discovery tools answer "who exists and who's growing?" - the Keep answers "what happened between us and the people we actually called?" Scout wherever you like, paste the list into the Herald - a whole Streamforge table works, links and counts ride along - and from that moment the Keep is the memory: who answered, who covered, who got keys, who got paid, across every campaign since.

What it does replace: the mastersheets. The colour-coded tabs, the "which doc has the DbD history" hunt, the hand-collated coverage totals - that era is over.

One sentence: work in the War Table, show the Orb. The War Table is the campaign happening - ticks, stages, bulk marks, documents. The Orb is the campaign described - the report-shaped read you'd put in front of a client. They draw from the same rows, so they can never disagree; one of them just has its sleeves rolled up.

A one-off game is one campaign: one War Table, done. A live-service title is an umbrella with beats under it - each update/chapter is its own campaign with its own War Table, and the title compiles them: lifetime stats on the umbrella's Chronicle So Far, and the Muster Roll showing every creator who ever answered that title's call, beat by beat. Retainer vs project changes the client relationship, not the mechanics.

Character sheet → ⚑ Set standing. Pick the standing and its scope: a specific game (tiers are usually a programme thing - Iridescent is a DbD word), a client, or Guillotine-wide (reserved for blacklists that should follow someone everywhere). It applies immediately, outranks per-title lists where scoped wider, and goes on the record with your name and reason. The 90-day standing sheets still upload through Watchtower → Standing Sync as the bulk path.

Five gates: paste a scouting list into the Herald (names alone, or a whole table - their links and counts ride along), creators petition through each campaign's public request form and get judged at the Gatehouse, coverage reports add the known faces they find (strangers wait in the Annex - see the next question), members graduate out of the Annex once they've earned it, and the Chronicler imports the historical archives. Duplicate protection is on at every gate - re-importing a sheet can't double anyone up, and every "new" name is re-checked against the live roster at the moment of writing.

No - and that's deliberate. When a report is sealed, people already on the roster get campaign rows stamped "Found via Coverage". Everyone else goes to the Annex: held outside the roster with their channel size and region kept from the report, recognised by the Gatehouse if they ever petition, but never cluttering a search, a match, or a duplicate scan. A one-shot creator who covered one game once is not a warm relationship, and pretending otherwise would poison the data everyone scouts from.

The door out is earned: cover a second of our games and they surface on the Annex's "Ready for the roster" shelf - one click raises them with everything the Annex knows, and their coverage history walks in with them. A clearly big channel can also be starred straight to the roster at seal time. Either way, joining the roster is a human decision, never a side effect of an upload.

No - and if it ever did, the Alchemist can fix it. The house rule (July 2026): a person is a roster record; a channel is an Annex row. When a coverage report carries a second channel we recognise - "lobosjrvods" when we already know LobosJr - the seal offers a fourth verdict for that stranger: alt of…. Confirm it and the channel is lodged in the Annex under "Secondary Channels", linked to its person - and the person gets the Covered credit on that campaign, so the coverage never falls between two names or counts twice.

Already ended up with two records for one human? The Alchemist's census now flags likely alt pairs and can fold the second record into the first the same way - history re-homed, the channel held in the Annex, one person, one sheet. Their character sheet lists every linked channel, so the whole picture lives in one place.

That's the Steam Whisperer. When a campaign's game is linked to its Steam page (a Connect Steam button in the Architect at founding, or on the War Table beside the document connects), the Keep reads the game's community tags from Steam - the real ones, like "Psychological Horror" and "Roguelike" - and starts whispering. The Gatehouse's admit form suggests the game's tags for new petitioners; Contribute and the character sheet recommend a tag once a creator has covered three or more of our games carrying it ("✦ Horror ×3" - hover to see which games).

Two laws keep it honest. Nothing auto-applies - every suggestion is a chip a human clicks, and the click rides the same signed write as typing the tag by hand. The vocabulary is ours, not Steam's - only tags that already exist in the Genres table are ever offered; a strong Steam tag the Keep doesn't speak just whispers "no Keep tag yet", and creating one stays its own deliberate act. A game with no Steam link costs nothing and suggests nothing.

Because the funnel only counts tracked relationships - people we actually targeted or admitted - so Covered can never exceed the outreach pool and the response-rate maths stays honest. The rest of the report's reach isn't lost: the line under the funnel reads "+N more covered via the Annex" with a door to the ledger. Total reach is both numbers together; the funnel is the one you can defend in a client meeting.

Around two dozen historical coverage reports are being sealed in. Expect campaigns to gain "Found via Coverage" rows, big "via the Annex" counts on older titles, and the Annex ledger to grow into the thousands - that's the design working, not a mess to clean. Don't hand-enrich annexed strangers: they hold their own size/region already, and the genre-tagging and detail work in Contribute to the Keep only applies to people who actually join the roster. The manual workload scales with who we choose, not with who happened to stream a game once.

Yes: the Keep now keeps a read-only copy of the base in its own database, refreshed on a timer, and the heaviest reads (the Scrying Pool's index, the homepage cards) read the copy instead of asking Airtable 150 questions per rebuild - a ~50-second rebuild became ~2 seconds. The rules that make it safe: Airtable stays the single source of truth, forever - every write still lands there instantly, the copy is never written to - and any read that can't trust the copy falls back to live Airtable on its own. Worst case is a list page a few minutes behind; never a wrong number written anywhere.

Only @guillotine.agency accounts get in, and every write - a tick, a note, an import, an export - is signed to the Annals with a name and timestamp. There is no anonymous edit. Clients never see the Keep itself; they see what we export from it.

Airtable holds the data; the Keep is how humans touch it. Every edit in the Keep lands in Airtable instantly - same records, same fields. If you're comfortable in Airtable nothing stops you working there, but the Keep exists so nobody has to be: it adds the guardrails (signed writes, duplicate guards, API-owned numbers) that raw table editing doesn't have.

The Keep does - never you. Copy the house External template into the client's folder, connect it in the War Chest's treasury, and press Raise the approval sheet. The Keep writes the styled Approval Sheet tab itself and keeps it current after every edit (about 2 seconds). Never hand-build an approval tab, and never name any tab "Approval…" or "All Platforms" - the Keep finds its tab by name, and a look-alike tab can shadow the real one.

What stays yours on that tab, always: the Status and Client Comments columns and any rows the client adds - the Keep reads those back (Pull verdicts) and never overwrites them. Everything else on the tab is the Keep's: hand-edits to its cells are rewritten on the next sync. The hand-filled tabs (Run of Show, Viewership Report, Social Posts) are entirely yours - the Keep never touches them; the Viewership Report reaches the Vault only when a human uploads it as a CSV at campaign wrap. One more habit: the template's worked example row is skipped automatically (any status containing "example" or "delete me"), but delete it before the client sees the doc anyway.