Why Tribal Knowledge Breaks Repos for AI Agents

Every repo has a little tribal knowledge. The command everyone knows not to run. The service that must be started before tests. The environment variable missing from .env.example. The setup step that only lives in someone’s memory. The CI behavior nobody explains because "that’s just how this repo works." For human teams, tribal knowledge is already expensive. For AI-native repos, it is worse. It is incompatible with the operating model. An AI-native repo is not just a repo where someone occasionally uses an AI coding tool. It is a repo where humans, CI, automation, and AI agents are all expected to reason about the same codebase and take useful action from the same operating truth. That model breaks if the repo’s real rules live outside the repo. This is one of the clearest reasons Ota exists. Ota is built around software execution governance for humans and AI agents. A repo should not depend on memory, Slack history, or maintainer intuition to explain how execution works