Manual FDE workflow → MC-1 Forward

What changes

Keep the existing client behavior stable first. Introduce the MC-1 base URL, logical model, and server-side credential, then add control-plane constraints only after compatibility passes.

Feature mapping

• Map discovery notes to approved read-only connectors and provenance.
• Normalize systems, workflows, constraints, and opportunities into the Intelligence Graph.
• Move plans through sandbox, approval, deployment, and outcome evidence gates.

Migration sequence

• Inventory endpoints, models, streaming, tools, retries, and error handling.
• Create a scoped MC-1 project and test key.
• Run an owned non-production fixture through both paths.
• Compare outputs, tool continuation, latency, usage, and failures.
• Canary a reversible workload before broader promotion.

Compatibility example

export MC1_API_KEY="..."
export MC1_BASE_URL="https://api.colomboai.com/v1"
# Keep the client OpenAI-compatible and use model colomboai/mc-1.

Source-specific caveats

• Do not import unapproved customer data or treat inferred relationships as facts.
• Consequential mutations remain operator-gated where no public write API is exposed.

Rollback

• Retain the previous route until acceptance passes.
• Do not translate unsupported provider-specific features silently.
• Record the exact client and integration versions used for validation.