Coding Agent Workstation
A plan-first coding agent node — approved tasks become controlled coding sessions with docs-as-code governance.
Problem
Coding agents are most useful and most dangerous in the same moment — unsupervised, they drift from the plan; supervised manually, they don't scale.
Solution
A dedicated workstation node where coding work follows a plan-first approval workflow — task plans are recorded, approved, then executed in controlled sessions — governed by a docs-as-code role manual.
Architecture
The coding workstation is where the portfolio’s governance philosophy meets software development itself: the same plan → approve → execute → audit loop that gates desktop actions is being applied to code changes. Its role manual is written as docs-as-code — the manual is the spec the agent operates under.
Repo evidence
- 13 MCP tools including the intake/memory trio (update_task_plan, create_session, end_session) shipped in Milestone 2 Slice A
- Coding Agent Role Manual maintained as docs-as-code (MDX source, manifest for a future dashboard)
- Milestone 1 complete and verified cold; audit-log fix landed with the M2 tools
- Runs the shared workstation engine with a coding-specific layer — one deploy path across the fleet