Release essay
Release essays on repo readiness, execution governance, and AI agent tooling.
These essays connect release-level changes to the broader operating model: how repo contracts, proof surfaces, and execution rules evolve over time.
Ota v1.6.27 Now Available: Effect-Bound Refusal Assurance
Ota v1.6.27 closes V12 with typed effect declarations, pre-execution refusal, private evidence reconciliation, and bounded Linux/macOS pressure.
Ota v1.6.26 Now Available: Protected Execution Foundations and Receipt History
Ota v1.6.26 closes the bounded V11.7 OSS audited-crossing slice through protected systemd-launcher execution, immutable receipt history, recovery evidence, and refined service-listener admission.
Ota v1.6.25 Now Available: Governed CI, Trusted Replay, and Lifecycle Proof
Ota v1.6.25 adds governed CI projection, runner-authored freshness evidence, promoted replay authority, and transaction-bound lifecycle proof.
Ota v1.6.24 Now Available: Runtime Proof, Replay Trust, and Typed Execution
Ota v1.6.24 strengthens runtime proof with transaction-bound seam evidence and negative controls, adds replay-grade input provenance, and expands typed image, hydration, runtime, and artifact ownership.
Ota v1.6.23 Now Available: Machine-Readable Execution Governance
Ota v1.6.23 strengthens machine-readable execution governance with explicit merge gates, stage-family output, crossing evidence, agent-safe enforcement, and broader first-class setup/orchestrator ownership.
Ota v1.6.22 Now available
Ota v1.6.22 expands execution governance across workspace orchestration, structured setup, Compose ownership, workflow instances, and semantic contract evidence.
Ota v1.6.21 Now available
Ota v1.6.21 turns more install, tool, Helm, and working-directory behavior into declared contract truth, so repos can stop hiding execution ownership inside shell glue and CI folklore.
Ota v1.6.20 Now available
Ota v1.6.20 turns more of execution truth into governed public surface: published contract schemas, stable doctor finding identity, first-class environment ownership, structured dependency hydration, orchestration-aware execution, and stronger service topology modeling.