Òtítọ́

Models generate the change. Otito proves whether it is safe to merge.

  ___ _____ ___ _____ ___
 / _ \_   _|_ _|_   _/ _ \
| | | || |  | |  | || | | |
| |_| || |  | |  | || |_| |
 \___/ |_| |___| |_| \___/

The generic agent loop (prompting, retries, tool routing, file editing) is becoming infrastructure. Frontier models already plan, search repositories, use tools, and recover from mistakes. Model vendors are packaging native harnesses with file tools and sandbox execution. Competing there is a losing bet.

What remains strategically important is the trust harness: accurate repository context, permission and sandbox boundaries, exact validation against the changed code, risk-sensitive policies, CODEOWNERS and human approval, reproducible receipts, and independent evidence the model cannot award itself. Stronger models increase that need, because teams will let them change more code with less supervision.

Òtítọ́ is that independent trust layer. It is local-first, deterministic, and model-agnostic: it discovers repositories, builds local indexes, generates task-aware context before an agent edits, scores how much a change actually touches, and gates merge readiness. It works the same way every time, with no server, no account, and no code leaving the machine. It does not compete with Codex, Claude Code, Gemini, Cursor, or future native harnesses. It integrates with them, and keeps working as models change underneath it.

Trusted agent workflow

New in v1.7.0: otito eval --gate-effectiveness proves the real staged gate against one valid control and six adversarial changes, each with an expected deterministic reason.

Request -> context -> scoped change -> exact validation -> review evidence -> human decision

Otito helps the agent understand and bound a task before editing, then gives the maintainer evidence to decide whether to trust the result. A passing local gate is never an automatic merge approval: hosted CI, GitHub review, CODEOWNERS, and the human release decision remain separate authorities.

It does not try to replace native agent harnesses, opensrc, code-structure, Daytona, or Harnss. It gives developers and coding agents a single CLI that can:

Deterministic merge gates are the differentiated core. This is the human-in-the-loop checkpoint that a model cannot grade for itself:

• score merge readiness for local changes and pull requests with one review_gate tool (gate on the CLI)
• execute a protected validation plan against the exact staged tree and retain a bounded receipt of its outcomes
• bind staged web, API, and shared-contract changes into one workspace receipt
• resolve CODEOWNERS to required reviewers and surface owner-decision warnings
• check branch-protection expectations and required checks before merge
• generate actionable PR review context from git diffs and optional GitHub comments
• continuously prove the local gate against a committed valid control and adversarial change corpus with otito eval --gate-effectiveness

Local-first context feeds the gates:

• inspect a repository
• discover and index local repositories
• maintain a local catalog and search across it
• generate task-aware context packets before an agent plans or edits
• generate AST-backed JSON-first code maps for agents
• generate a setup/validation/runtime harness for a repo
• produce Markdown or JSON reports

... View full README on GitHub