Conductor knowledge base workflow (archived)

The canonical execution-authorizing workflow has been archived to archive/compiler-v1/. Conductor is now a pure knowledge base — there is no consult_plan, no authorize, no complete_authorized_work, and no authorization lifecycle.

How it worked (historical)

The compiler workflow involved:

1. Constructing an exact plan-bundle.v1
2. Calling consult_plan for server-side supervisory review
3. Claiming a one-shot authorization via authorize
4. Executing work using production tools outside Conductor
5. Calling complete_authorized_work with evidence and writeback verification
6. Submitting reusable experiences through the learning pipeline

All of these steps and their associated MCP tools no longer exist. The compiler, plan bundles, authorization, and learning pipeline are archived.

See the stage contracts catalog for descriptive stage reference, and the connecting guide for current MCP transport documentation.