Zephr Docs

Governance & defect

Governance and defect are the two accountability bands around the belief circuit. They are kept deliberately separate in the baseline (governance prevents before the act; defect immunises after a failure), and each page covers both so the lifecycle pairing is visible without restating shared architecture — see Architecture and Trust for the review-state machine provenance lives in.

Capability status

CapabilityStatusEvidence
governancePartialConstraint store, ladder, waivers, zephr_constraint, enforced gate
defectPartialHTTP create + immunity/decay monitor

governance

governance owns invariant mining, constraint authoring, the constraint ladder, waivers, the zephr_constraint MCP tool, and the enforced admission gate (evaluateGovernanceAdmission + transport block + POST /api/cloud/guard/governance/enforce). The constraint store, the ladder, waivers, and the enforced admission gate ship; invariant mining and the full enforcement-point matrix are designed-not-built. Governance admission is fail-closed and cannot weaken the enforcement posture supplied by its caller (see Trust).

defect

defect owns defect records, immunity artifacts, and the decay monitor. The HTTP create slice, immunity attach/decay, and the decay-monitor hook (POST /api/cloud/guard/defects/decay-monitor) ship; derivation triggers and the full incident loop are designed-not-built. Immunity artifacts attach to code anchors and decay independently; they do not alter the belief review state owned by trust.

Availability

SurfaceTierResidencyNotes
zephr_constraint (MCP)coredeferredConstraint authoring and ladder inspection
POST /api/cloud/guard/governance/enforce—cloudAdmission gate; blocks out-of-policy writes
POST /api/cloud/guard/defects—cloudSix-face defect create slice
POST /api/cloud/guard/defects/decay-monitor—cloudImmunity attach/decay + decay-monitor hook
zephr constraint create|promote|shadow|smoke (CLI)—localLocal constraint lifecycle

Limits and failures

  • Governance constraints never broaden recall: a passing admission does not promote a belief through review-intel; only a human review path can (see Review, progress & Pulse).
  • A defect record is not a ticket: derivation triggers and the incident loop are designed-not-built, and immunity decay does not mutate belief review state or open a tracker issue.
  • Admission evaluation reads the canonical constraint version; shadow-mode constraints (zephr_constraint shadow) report without blocking, but production admission is never shadow.

constitution (machine-checked project constraints) and trust (review-state ownership) bound this family; progress records the change graph this band annotates.