Confidence Engine

Evaluate, raise, and enforce confidence until ok before mutating commits.

What you will learn

• confidence_evaluate
• confidence_raise
• confidence_enforce ok

Prerequisites

• Enforcement sessions

Surface

What this feature does

Confidence is a checklist gate: schemas consulted, risks named, evidence present. Raise until enforce returns ok (or mayAskUser).

How to call it

Call these MCP tools through your AGS / tower-gov host — confidence_evaluate, confidence_get, confidence_raise, confidence_enforce.. Prefer scan/get before validate/diff, and enforce only when the change set is ready.

1. confidence_evaluate
2. Close gaps (schema_enforce, testing_plan, …)
3. confidence_raise
4. confidence_enforce

{ "intent": "add session refresh helper", "paths": ["src/auth/session.ts"] }

What success looks like

confidence_enforce ok:true

Recorded in enforcement session

Common failure modes

Enforce once and ignore gaps

Raise without evidence

Skip confidence → enforcement_check fails

Related reference

• Architecture
• API surface