otaExecution governance for humans and AI agents.
Get startedGitHub

Module 01

Foundations

Understand the core mental model behind Ota: contract, execution, admission, evidence, and acceptance. Learn the critical difference between declared, observed, and proved — and why honest boundaries matter.

Foundation4 lessons · ~26 min
Start with first lesson

Module curriculum

Lessons in Foundations

Follow the sequence to build the model, then use the exercises to test the boundary.

Lesson 016 min read

What Ota governs

Ota governs declared repository execution: readiness, admission, selected work, and bounded evidence for humans, CI, and agents.

  • Explain the scope of Ota governance in one sentence
  • Distinguish repo readiness from code correctness
FoundationOpen lesson
Lesson 028 min read

Contract, execution, admission, and evidence

The four pillars of Ota: a declared contract, deterministic execution, admission gates, and receipts that prove what actually ran.

  • Name the four pillars and state what each covers
  • Explain why evidence must be separate from execution
FoundationOpen lesson
Lesson 037 min read

Declared, observed, and proved

Declared truth is contract intent, observed truth is a bounded witness, and proved truth requires Ota to reconcile the relevant identities and evidence.

  • Define all three truth levels with an example
  • Explain why Ota refuses to treat declared as proved
FoundationOpen lesson
Lesson 045 min read

Honest boundaries and not_proved

When Ota cannot verify a claim, it must say so explicitly. not_proved is a first-class result, not a failure.

  • Explain what not_proved means in a receipt
  • Describe when Ota emits a not_proved boundary
FoundationOpen lesson