Future ideas¶

Desired features and improvements for Conductor as a knowledge base and multi-agent system. Not committed — just collected.

Agent workflows¶

Level 1 loops for other roles — Product Manager (scorecard cycle), Platform Engineer (incident/change loop), Editor-in-Chief (fact-check loop), Engagement Manager (lead qualification cycle). Modeled after Engineering Lead's Plan→Do→Self-check→Review→Complete pattern.
Cross-role handoff workflow — When a gatekeeper finishes, a structured handoff note could be written to the Task description in Notion, giving the next gatekeeper context.

Sync Notion state to markdown registry — Whenever an Initiative is updated in Notion, regenerate docs/registry/initiatives.md as a snapshot. Not authoritative, but keeps the docs current.
Notion views per gatekeeper — Create filtered views in Notion UI for each Line (Product Work, Software Work, etc.) and "My Tasks" per assignee.
Google Calendar sync — Enable native Due Date → Google Calendar sync in Notion settings.

Pi/Cursor/Codex harness configs — Currently only OpenCode gets a proper agent config with disabled built-ins. Extend to Pi (append-system-prompt), Cursor (rules files), Codex (mode config).
Setup dry-run mode — Return what would be written without actually writing anything. Useful for diagnostics.
Setup returns available upgrades — Compare conductor/docs/ hash against the repo to tell the agent if new instructions exist before git pull.

Gatekeeper quickstart — A 5-minute walkthrough for each role showing the first session: connect MCP, run setup, check Notion, do the first task.
Cross-line examples — End-to-end walkthrough of a full Path A (Portfolio → Product → Software → Operate + Editorial) with real Notion commands.
Troubleshooting guide — Common failures: expired Bitwarden session, ntn auth issues, git pull conflicts, stale agent config.