Current Workflow

Current workflow status: candidate.

Active Shape

• The source SaaS repo is implementation history.
• The board repo is the memory, automation, and export layer.
• Generated board docs are regenerated from source history.
• NotebookLM packs are generated from the board and used only for analysis.

Agent Roles

• User: final approval, merge authority, and sensitive-action gate.
• Codex: implementation agent for bounded tasks.
• Claude Code: pre-review and post-review agent.
• GPT or coordinator: task instruction writer and Adopt/Adapt/Reject reviewer.
• External agents: sandbox or study-only unless explicitly promoted.

Approval Gates

• Do not modify the SaaS repo from board automation.
• Do not run live provider calls unless a future approved task requires them.
• Do not expose secrets, raw customer messages, or PII in board summaries.
• Do not treat draft harness ideas as active rules.

Routing Principles

• Source implementation belongs in foryoutune-dev.
• Board automation belongs in foryoutune-board.
• Export packs belong under exports/notebooklm.
• Incidents and lessons should remain searchable for future reuse.