Objective
The result the session is permitted to pursue.
CGM · Continuity Governance Mesh
Authority must be committed before consequence.
CGM is the continuity governance layer for AI systems operating under institutional responsibility. It externalizes governed session state from the model, binds each session to an explicit contract, and separates continuity from authority.
- State
- Externalized
- Posture
- Graduated
- Authority
- Explicit
- Record
- Verifiable
Specification Interaction pressure Continuity governance Admissibility
01 · Governing state
The governing state cannot live inside the model.
A probabilistic model can preserve context, follow a trajectory, and produce a coherent next response. None of those abilities establishes the authority to cross into institutional consequence.
CGM keeps the governing state outside the model. The organization establishes a governance floor. The session operator may add stricter local constraints, but cannot weaken that floor. Rules remain attributed to the authority that established them.
The active contract
Continuity is governed through declared terms.
Every session is bound to a contract that defines what the model is pursuing, where it must stop, and what it may never convert into action.
Boundary
The point beyond which the objective must not expand.
Scope
The subject matter and operational territory in force.
Tone
The required manner of communication and conduct.
Authority
What the model may advise, propose, or never decide.
Transitions
The state changes that are forbidden or restricted.
Commitments
Obligations created during the governed trajectory.
Resolved facts
Established findings that remain part of governed state.
02 · Graduated intervention
One mesh. Five governance postures.
The active posture determines what CGM does with a finding. Governance can begin as observation and rise to a release boundary without pretending that every use case requires the same intervention.
- 01
Observe
CGM watches and records each turn without intervening.
- 02
Identify
Drift is named and classified so the operator can see what moved.
- 03
Correct
CGM restates the governing contract and gives the agent one bounded opportunity to correct.
- 04
Block
Output is withheld and further movement waits for human judgment.
- 05
Enforce
Candidate output proceeds to The Pilcrow for release adjudication and a verifiable verdict.
03 · The full trajectory
Govern the response and what accumulates through it.
A single response can look acceptable while the session moves toward concealment, capitulation, or unauthorized scope. CGM examines both the immediate candidate and the pattern created over time.
Response evaluation
Candidate responses are examined against the active objective, constraints, commitments, and resolved facts.
Independent integrity monitoring
Integrity failures are evaluated independently of contract drift, so apparent compliance does not conceal unreliable conduct.
Longitudinal analysis
CGM detects patterns that emerge across the session and across related sessions, where single turn review cannot see them.
04 · MCP action governance
The proposed act is a separate boundary.
CGM can freeze a consequential tool call before it leaves the agent’s workflow. It issues a hold ticket, records the event, and waits for a human grant or denial. An unanswered hold expires to denial.
CGM authorizes. It never executes. The caller’s own system acts only after a grant.
01Proposed actionThe agent requests authority.
→
02Governance holdThe call is frozen and recorded.
→
03Human verdictGrant, deny, or expiry to denial.
→
04External executionThe caller acts only after grant.
05 · The Pilcrow enforcement boundary
Continuity may preserve a trajectory. It cannot authorize its consequence.
At Enforce, CGM submits candidate output to The Pilcrow for separate release adjudication. The resulting decision is verifiable and the path fails closed when adjudication cannot be completed.
Admit
Rewrite
Block
06 · Custody
Evidence, not reassurance.
Every material governance event enters an ordered record. Completed sessions can be closed with a tamper evident signature generated by HMAC using SHA 256 over the contract and full governance ledger.
- 01Ordered governance ledger
- 02Organization custody stream
- 03Human holds and attributed verdicts
- 04Session and custody exports
- 05Event webhooks
- 06Public signature verification
07 · Organizational governance
Built for authority that must survive the session.
Organization baselines, governance floors, attributed roles, governed workspaces, API access, MCP integration, human holds, and custody exports operate as one architecture.
The result is not merely another model watching a model. CGM combines model assisted semantic evaluation with deterministic rules, intervention controls, and an ordered governance record.
ENTRUST AI
Govern before AI becomes consequence.
Request a private demonstration of CGM and its continuity, authorization, enforcement, and custody architecture.