Weekly Commander Report — HTML

Intent

Each Commander contributes to a single weekly HTML report (similar shape to the Virgin Media monthly review) covering "how I've lived the last week". Each Commander gets a section. Hinata writes a top-of-report summary. A progress score is rendered per Commander.

Open design decisions (Minato 2026-05-21)

1. Scoring model — 0-10 per Commander? % progress vs. weekly targets? Qualitative (On Track / At Risk / Off Track)? Whether the summary rolls into one global score or stays decomposed.
2. Data source — does each Commander already have a weekly log worth extracting from, or does each Commander run a questionnaire before render?
3. Cadence & trigger — Sunday 21:00 (aligned with Orochimaru's weekly scout)? On-demand? Auto-generated + Telegram-delivered?
4. Use case — reflection tool only, or also feeding into the next week's prioritisation?

Architecture sketch (TBD)

• Source: each Commander emits a structured weekly summary (JSON or YAML) every Sunday before 20:00.
• Renderer: Python script at /opt/jimmy-brain-ops/scripts/weekly-commander-report.py.
• Output: documentation/YYYY-MM/YYYY-WNN-commander-report.html + Telegram-deliverable PDF.
• Hinata's top-summary: synthesised by Claude from the 27 Commander emissions.

Why this exists

Lifted from inbox/pending-review/2026-05-21-telegram-45bdb30c.md (since destroyed). The design decisions above were posed by Minato but never answered — pickup work for Uncle Iroh when this project gets prioritised.

Related: orochimaru-weekly-scout, hinata-studio-dashboard.