Open Source · Concepts

The vocabulary behind the boundary.

Authority Envelope

Bounds who/what may act, on which resources, under which delegation and constraint rules. It is not a bypass around policy.

Short-lived one-use authority bound to the reviewed action. A retry must obtain fresh authority rather than replaying a consumed lease.

Structured record of execution/effect observations. It is evidence, not automatically proof of the external postcondition.

Trusted, reviewable semantics for checking a specific operation/resource effect. Tool names alone never create these semantics.

Describes the strength and limitations of effect evidence. It prevents weak evidence from silently becoming a stronger conclusion.

Separates confirmed success, confirmed no-effect retry eligibility and unresolved/manual verification.

Redacted local evidence chain with verification, graph/timeline and offline-report surfaces.

Discovery and normalized capability history. Discovery metadata informs review but never grants execution authority.

Reproducible failure/retry/concurrency/staleness scenarios. Passing a fixture is not independent production certification.