Pending: Sequential (Phase 1) vs scaffolding architecture (Phase 2) — when to switch?
Pending: Google Calendar MCP server for calendar integration?
Pending: How to sync compiled briefing to Atlas (C:\Users\marij\Vaults\My Life Lab)?
User Tasks
Summary
Automated daily briefing that summarizes system status, pending tasks, and relevant updates.
Problem / Motivation
Without a daily summary, it’s easy to lose track of what the system has done, what needs attention, and what’s coming up. A briefing creates a daily rhythm.
Proposed Solution
A scheduled process that generates a daily briefing markdown file in the vault, summarizing feature status, recent changes, and action items.
Architecture: Sections Pattern (Phase 2+)
Multiple sub-agents work in parallel, each writing a section file to vault/30_daily/briefings/YYYY-MM-DD/sections/. A compiler agent then merges all sections into the final briefing.
30_daily/
└── briefings/
└── YYYY-MM-DD/
├── sections/ # Agent-written sections
│ ├── changes.md
│ ├── features.md
│ ├── inbox.md
│ ├── opus-activity.md # What Opus did autonomously
│ └── ... # Future: finances.md, health.md, calendar.md
└── briefing.md # Compiled main briefing → also synced to Atlas
Section agents (run in parallel):
Agent
Reads
Writes
changes-agent
Git log, recent vault changes
YYYY-MM-DD/sections/changes.md
features-agent
All FR files (status, next-step, current-phase)
YYYY-MM-DD/sections/features.md
inbox-agent
vault/90_inbox/, vault/10_features/02_new/
YYYY-MM-DD/sections/inbox.md
opus-activity-agent
Git log filtered to autonomous/non-session commits
YYYY-MM-DD/sections/opus-activity.md
agent-reports-agent
vault/00_system/logs/agent-reports/YYYY-MM-DD/
YYYY-MM-DD/sections/agent-reports.md
cron-tasks-agent
Cron/scheduler execution logs
YYYY-MM-DD/sections/cron-tasks.md
external-agent
Calendar, weather, news (Phase 3)
YYYY-MM-DD/sections/external.md
Note: Until autonomous actions are live (FR-066 or similar), changes.md covers Opus activity. Split into opus-activity.md when autonomous Opus actions are enabled.
Compiler agent (runs after all sections are ready):
Reads all vault/30_daily/briefings/YYYY-MM-DD/sections/*.md files
Applies the briefing template from _templates/briefing.md
Produces the final vault/30_daily/briefings/YYYY-MM-DD/briefing.md
This approach is faster (parallel), modular (easy to add new data sources), and testable (each section can be verified independently). Sections are kept for reference. Inspired by Sven’s scaffolding approach in Nexus.
Open Questions
No open questions.
Phase Overview
Phase
Description
Status
Phase 1
Basic briefing (sequential)
—
Phase 2
Sections architecture
—
Phase 3
Smart briefing (external data)
—
Phase 4
Delivery (phone, voice)
—
Phase 1: Basic Briefing (Sequential) —
Goal: Generate a simple daily briefing file from feature overview and recent changes. Includes a daily cron task that refreshes all dashboards first, then generates the briefing with open items.
File / Feature
Details
Owner
Status
Dashboard refresh cron
Daily task that syncs all dashboards (feature-dashboard, user-review-dashboard, ideas-dashboard, capabilities-dashboard, user-tasks-dashboard) with actual vault state
mv
—
Open items extraction
Collect items where Last Changed > User Review from user-review-dashboard
mv
—
Briefing template
Update _templates/briefing.md to match sections-based approach
opus
—
Generation script
Reads dashboards, feature overview, and recent changes
opus
—
Output file
vault/30_daily/briefings/YYYY-MM-DD/briefing.md — includes “Needs Your Review” section with open items
mv
—
Naming convention
YYYY-MM-DD/briefing.md inside briefings/
opus
—
Phase 2: Sections Architecture —
Goal: Implement parallel section agents and a compiler agent for modular briefing generation.
File / Feature
Details
Owner
Status
vault/30_daily/briefings/YYYY-MM-DD/sections/
Sections directory (per date-folder)
opus
—
changes-agent section
Git log + recent changes
opus
—
features-agent section
FR status summary
opus
—
inbox-agent section
Inbox items
opus
—
opus-activity-agent section
Git log filtered to autonomous/non-session commits → YYYY-MM-DD/sections/opus-activity.md
opus
—
agent-reports-agent section
Reads vault/00_system/logs/agent-reports/YYYY-MM-DD/, summarizes per-agent activity (what each role did, which FRs, pass/fail) → YYYY-MM-DD/sections/agent-reports.md