Skip to content

You are currently viewing documentation for0.1.0-alpha.1

Saved documentation for 0.1.0-alpha.1 (npm) / 0.1.0a0 (PyPI). Interactive tools use the current release. View latest documentation.

The guard loop

  1. 01Wrap
  2. 02Inspect
  3. 03Frozen-mode decision: ok / repaired / degraded / bypassed / blocked
  4. 04Audit artifact
  5. 05Optional feedback
Mode is fixed for both request and response phases before inspection starts; the decision names only what this call produced.

Wrap → inspect → decision → audit → feedback

Wrap the callable. Inspect bounded complete request and response evidence before dispatch and after a response. Supplied OpenAPI, schema or contract evidence and runtime failures are inputs; they are not themselves detection. Freeze the mode for both phases. Produce ok / repaired / degraded / bypassed / blocked. Export an audit artifact through an explicitly configured sink. Optional feedback informs later investigation; it cannot authorize replay or change a completed decision. Response inspection cannot undo a completed upstream write; availability faults bypass inspection even for writes.

Evidence classes

A finding describes drift evidence. A patch describes a proposed or verified selective change. An incident is a separately admitted accounting unit. A candidate is not an applied repair; an audit artifact is not automatically write-integrity proof. Incomplete captures are unavailable evidence, not malformed vendor bodies.

Rename authority versus meaning

A fictional mechanical rename (for example order_ref → order_id) may be considered only with authoritative migration facts, independent verification of the migration constraint, sufficient confidence and preservation of untouched caller fields. Schema acceptance and confidence alone are insufficient to establish intent or persisted write correctness. An ambiguous source ↔ payment_method mapping cannot establish intended meaning from matching names or types; it is not a verified real payment-provider migration. Observe records without changing the call; repair mode blocks unresolved semantic write drift. Human review is an explicit host integration — a review receipt does not execute or replay the write.

Byte identity

No-repair paths preserve original payload identity. Selective repair changes only verified drifted fields and records byte_identical: false. Numeric coercion is not a repair. The default guest supplies no selective repair output.

Specification

Read the published modes guide and the guard loop.