Feature note
Feature notes on repo readiness, contract design, and AI agent operations.
These notes explain what shipped, why it matters, and how new contract or execution surfaces change repo readiness for humans, CI, and agents.
Why Heavier Repository Execution Needs Audited Boundary Crossings
Why publishing, migrations, deployments, and other non-routine repository tasks need explicit crossing evidence, and how Ota separates per-run evidence from reusable authority.
Testing the Proof System: Negative Controls and Dependency Evidence in Ota
How Ota separates dependency reachability, transaction-bound seam exercise, and validated negative controls without turning any red exit into causal proof.
Ota 1.6.24: Replayable Proof for Real Repository Execution
How Ota uses archived receipts, scoped baselines, input identity, and witnessed observations to distinguish a replay from a fresh derivation.
Why ok: true Is Not Enough for AI Agent Execution
How agents and CI should read Ota execution status, proof verdicts, scope, and not-proved boundaries without turning a narrow green into broad authorization.
Turning Ota Contracts into Merge-Gate Truth
How Ota turns contract-owned verification lanes into stable merge-check identities, CI drift findings, and an opt-in GitHub pull-request gate.
How Ota Turns Execution Logs Into Governance Verdicts
How Ota turns CI and AI agent logs into machine-readable governance verdicts for admission, execution, receipts, proof, and unresolved evidence.
npm test passed. Ota still caught missing repo setup truth.
A passing `npm test` run does not prove a repo is ready. This technical demo shows how Ota catches missing env, service, generated-file, and workflow setup truth that unit tests alone never prove.
How Ota Explains Contract Drift Against New Failures
Ota can now archive semantic contract truth, diff normalized assumptions, and explain whether new blockers are likely related to contract drift without pretending every failure has one certain cause.