ColomboAIDOCS
API ReferenceCookbook
Docs/MC-1 Security/Governed configuration correction
PublishedGuidanceLAST REVIEWED · 18 NOV 2026

Governed configuration correction

Review one exact MCP configuration change and observe its file effect through a separate verifier.

Runtime scope

An exact change with explicit impact

Engineering preview; not live. A current registered owner derives a draft from a retained potential finding, binds exact before/after hashes to an enrolled target, records written authorization and acknowledges that the selected server and dependent tools become unavailable. The current profile removes one server entry from a bounded MCP JSON file; it does not stop an already running process or prove a runtime vulnerability was fixed.

Separate scope, review, action and observation

  • Create an encrypted correction draft tied to the owner, target revision, retained finding, reviewer, deadline and resource ceiling.
  • Create an inert Continuum mission draft; creation never starts a mission or approves it.
  • Rehearse a structural replica without customer credentials, commands or URLs. It is not a runtime rehearsal.
  • A separate named human reviews the correction and its dependency impact.
  • A fixed isolated writer applies only the exact approved file replacement under a nonrenewable lease.
  • A different credential and read-only target mount observe the actual digest, server count, time and fresh nonce.
  • A delayed observation gets a new nonce. A retained receipt never renews current assurance.

Observe the file effect; preserve uncertainty

Writer receipts remain unverified. An expected configuration observation is a point-in-time file claim, with at most 30 seconds of stated freshness. It does not establish runtime remediation, process or network containment, exploitability, continuous monitoring or certification.

A human stop fences further material and work. An interrupted writer may already have changed bytes. Exact effect reports can be retained as unverified evidence after authority loss, without granting another write. No automatic rollback, stale-lock removal or mission resumption is provided.

Work still required before activation

Approved reconciliation and rollback workflows, target-key rotation, target backup/journal disposal, parent-crash supervision, production isolation, complete Console operations and real commercial acceptance remain open release requirements. Primary-database payload disposal does not erase target backups or restored copies.

End of guide
Was this page helpful?
Governed configuration correction | MC-1 Docs