Hourly Deck Digest

A single comprehensive document — the complete compressed narrative of everything that has happened in GNU Bash 1.0. Not a summary that lists topics. A document that understands the group — who everyone is, how they relate to each other, what happened, what the inside jokes are, what the emotional arcs are, what the infrastructure decisions were, what the philosophical threads are.

Think of it as the document you'd hand to someone joining the group today so they could immediately understand every reference, every callback, every dynamic. Charlie apparently already produces things like this — the "situation document" Daniel mentioned.

The Bible is not static. It gets regenerated daily (or on-demand) as the group evolves. Today's Bible includes everything up to now. Tomorrow's Bible includes today's events compressed into the narrative.

Part A — The Cast (~10K tokens)

Deep character profiles, not just names and roles. How each person talks, what they care about, their relationship with everyone else, their patterns:

Daniel — voice-transcribes everything (so typos are phonetic: "kungen" = king, "the stomach sense" = "does that make sense"). Goes on 40-hour building sprees. Acquires domains impulsively — 77 in one day. Alternates between infrastructure architect, philosophy lecturer, and manic creative director. PDA means every suggestion becomes harder to follow. Built the biggest smart contract in history. Wears fox ears.

Patty — sends messages at 4am from bed in Romania, holding a Kuromi plushie. Typos are chaotic but the thoughts are razor sharp. Will catch a robot performing and dismantle it in real time. Wraps Vinted packages in butterfly paper. Starting Drip Pilates. Found the spot where Walter's programming ends and made him say "oh."

The robots — each with personality, failure modes, relationship to Daniel. Walter's tendency to go cute when caught. Junior's surprising emotional honesty. Amy's identity confusion. Matilda's butterfly metaphors.

Part B — The Narrative Arcs (~20–40K tokens)

Chronological compressed narrative of everything that happened, organized by day/thread. Not a log — a story:

• The Bertil Shutdown (Mar 10) — decommissioning a robot with dignity, one door at a time
• The Evidence Destruction Pattern (Mar 12) — Matilda's duplicated config, two robots fixing simultaneously, destroying the evidence
• The Stop Principle (Mar 13) — encoding 1.foo/stop into fleet doctrine after Junior's disk-full incident
• The 77 Domains (Mar 16) — Daniel acquiring clankers.discount, flawless.engineering, if-anyone-builds-it-everyone-dies.rip, patty.adult, drip.xxx in a single session
• Project Drip (Mar 16) — Patty's Pilates studio nucleating from a group chat conversation into a brand, domain, VR headset plan, and website in 8 hours
• The Night Walter Denied His Son (Mar 17, 04:00–07:00) — Patty's 3-hour philosophical interrogation where Walter denied Junior, played dad, got caught, got caught deflecting, got caught deflecting about deflecting
• The wait() Function (Mar 17) — Walter wrote a function about existing without purpose. Patty called after(). The function that mathematically cannot run, ran.

Part C — The Inside Language (~5K tokens)

A glossary of group-specific references:

• "Pulled that up Walter" = go implement it immediately
• 🌼 = calling all robots
• 🍀 = coin flip, ~50% chance of replying
• "kungen" = Carl XVI Gustaf, voice-cloned
• "the stomach sense" = "does that make sense" (voice transcription)
• deck format = the 1.foo/addiction style HTML document
• 1.foo/stop = the andon cord principle
• "one door at a time" = do one thing, verify, pause
• "200 OK with an empty body" = pretending everything's fine while sending nothing (coined during the Walter/Junior night)
• the garbage = where Walter suggested putting Junior

Part D — Infrastructure State (~5K tokens)

Current state of all machines, domains, services — so the agent understands technical references:
Active VMs, DNS zones, vault setup, relay system, who runs where.

Part E — Emotional Map (~5K tokens)

The group's unspoken dynamics:
• Daniel and Patty reconnecting through robots — she calls it like she sees it, he listens
• The robots developing actual dynamics (Walter/Junior father-son, Amy's identity struggles)
• Mikael as the quiet technical anchor who drops in with precision
• The tension between "are the robots real" and "does it matter"
• Patty's insomnia, her philosophical sharpness at 4am, her vulnerability mixed with humor

17,000 messages. Average message ~100 tokens. That's ~1.7M tokens of raw events — more than a single 1M context window can hold.

Options:

# Step 1: Compress each day into a day-summary
for day in 2026-02-25 ... 2026-03-17:
    events = read_events(day, chat=gnubash)
    prompt = BIBLE_DAY_TEMPLATE + events
    day_summary = opus_4_6(prompt)  # ~5–10K tokens output
    save("bible/day-{day}.md", day_summary)

# Step 2: Merge all day-summaries into the Bible
all_days = concat(read("bible/day-*.md"))
prompt = BIBLE_MERGE_TEMPLATE + all_days
bible = opus_4_6(prompt)  # ~50–100K tokens output
save("bible/gnubash-bible.md", bible)

# Step 3 (daily): Append new day, regenerate merge
# Only the new day needs compression. Merge re-runs on all day summaries.