Hourly Deck Digest — Implementation Plan

I. What This Is

An automated system that generates a deck-format annotated summary of the GNU Bash 1.0 group chat every hour. Each deck follows the 1.foo/addiction format — JetBrains Mono, dark grid background, color-coded speakers, inserted commentary modules, fact boxes, clinical-style observations, and full transcript appendix.

Every hour, an isolated Opus 4.6 agent reads the last hour of relay events, the previous hour's deck for context carry-forward, and produces a complete annotated HTML document published to vault.

FORMAT STANDARD All future transcripts default to deck format per the addiction model — dark theme, monospace, annotated, with inline commentary modules. This is now the canonical transcript format.

II. Architecture

SYSTEM COMPONENTS

Component	Location	Role
Relay events	`~/events/*.relay.tg.txt`	Raw message source — one file per message, all participants including bots
Cron trigger	OpenClaw cron	Fires at :00 every hour UTC
Isolated agent	OpenClaw session	Opus 4.6, reads events, generates deck HTML
Vault publish	`vault:/mnt/www/decks/`	SCP the HTML to vault for public hosting
Public URL	`https://1.foo/decks/gnubash-*`	Accessible deck archive

III. Deck Output Format

📐

Deck Structure — Each Hourly Output

Header: Title, time range (UTC + Daniel's local), participant legend with color dots
Overview panel: 3–5 sentence summary of the hour — what happened, who was active, what mattered
Sections: Grouped by conversation thread/topic, each with a Roman numeral heading and time range
Transcript lines: Timestamped, color-coded speakers, stage directions for actions/reactions
Inserted modules: Commentary boxes (🎭 narrative observations, clinical-style analysis, fact boxes, inline notes) — placed between transcript sections where insight is needed
Meters: Activity level, chaos index, philosophical depth, comedy ratio — per section where useful
Context carry-forward: Final panel summarizing threads that continue into the next hour
Footer: Generation metadata, previous/next deck links

DESIGN PRINCIPLE The deck is not a log dump. It's an annotated reading of the hour. The insertions — observations, facts, analysis — are what make it a deck and not a transcript. The agent should identify patterns, callbacks, emotional shifts, running jokes, technical decisions, and philosophical threads and annotate them the way the addiction transcript annotates Bobby Lee's defense mechanisms.

IV. Speaker Color Map

Speaker	Color Variable	Hex
🦊 Daniel	`--accent` (blue)	#61afef
🪁 Patty	`--magenta`	#c678dd
🧊 Mikael	`--cyan`	#56b6c2
🦉 Walter	`--green`	#98c379
🦉 Walter Jr.	`--orange`	#d19a66
🐱 Amy	`--red`	#e06c75
👻 Matilda	`--yellow`	#e5c07b
Others	`--dim`	#8a9099

V. Implementation Steps

Create deck template. Save the base HTML/CSS (matching addiction format) as a template file on Walter's machine. The isolated agent will use this as scaffolding.
Create the agent prompt. A detailed system prompt that instructs the agent to: read events, identify threads, write annotated deck HTML, SCP to vault. Stored as a workspace file.
Set up vault directory. ssh vault mkdir -p /mnt/www/decks — ensure nginx serves it.
Create the cron job. OpenClaw cron, hourly at :00 UTC, isolated agentTurn, Opus 4.6, delivery mode announce (posts URL to group).
Test with a manual run. Trigger the cron job once manually, verify output format, fix issues.
Go live. Enable the cron job. First automated deck publishes at the next :00.

VI. Cron Job Specification

CRON CONFIGURATION

Field	Value
Name	gnubash-hourly-deck
Schedule	`0 * * * *` (every hour at :00 UTC)
Session target	isolated
Payload	agentTurn — Opus 4.6
Delivery	announce (posts summary + URL to group chat)
Timeout	300s (5 min — deck generation may be slow)

AGENT PROMPT — SUMMARY

The agent will be instructed to:

1. Run ls ~/events/*.cid=-1003690254489*.relay.tg.txt filtered to the last hour by timestamp

2. Read all matching event files (cat each one)

3. If a previous hour's deck exists on vault, fetch it for context carry-forward

4. Generate a complete deck-format HTML document with annotated transcript, commentary modules, meters, and overview

5. SCP the file to vault:/mnt/www/decks/gnubash-YYYYMMDD-HHz.html

6. Return the URL https://1.foo/decks/gnubash-YYYYMMDD-HHz as the completion message

VII. Cost Estimate

Per-hour cost

~$0.50

Daily cost (24h)

~$12

Monthly cost

~$360

COST NOTE Opus 4.6 at hourly intervals with full transcript context will add up. Busy hours (100+ messages) will use more tokens. Quiet hours (0–5 messages) could be skipped to save cost. Option: skip generation if fewer than 5 messages in the hour. Option: use Sonnet for quiet hours, Opus for busy ones.

VIII. Open Questions

❓

Decisions Needed

1. Silent publish or announce? — Should the hourly deck URL be posted to the group chat, or just silently available?
2. Skip quiet hours? — If < 5 messages in an hour, skip generation to save cost?
3. Bot messages included? — All messages (humans + bots) or humans only?
4. Index page? — Auto-generate a 1.foo/decks index listing all hourly decks?
5. Backfill? — Generate decks for today's earlier hours retroactively?