Vinaya is a series of deterministic checks and workflows that hold agentic and human development to the same discipline — an AI agent and a person answer to the identical rules before anything merges. Each ring below is read at build time from this repo’s own doctrine, not hand-written for this page.
The ActorsEvery human and AI agent that touches the repo — Planner, Brief-author, Developer, Reviewer, Security, Archivist, Tranche-archivist, Principal. One rulebook binds all of them.
What Actors DoThe contracts: the defined handoffs between actors — brief to developer, developer to reviewer, reviewer to archivist. Each handoff carries a fixed obligation.
HooksChecks on the agent’s own machine. An invalid commit or push is refused before it ever leaves the session; the agent reads the error and fixes it in place. Self-correcting — nobody downstream pays.
The ActionsThe canonical acts of work an agent or human performs — 10 in all; some cross into GitHub, some stay local.
GitHubThe forge where actions land — issues, branches, pull requests. The shared substrate everything writes to.
Branch RulesCI on every pull request. The same checks re-run on the forge; a violation turns CI red and the merge gate makes red unmergeable by agents. Catches writers the local hooks can’t reach — the web UI, humans, other tools.
AuditsContinuous sweeps across the whole forge, after merge. Drift surfaces as findings no matter who wrote it — even history that predates the gates. Scheduled clean-up, never a mid-work surprise.
main — ProtectedThe branch everything guards. It only ever advances through the rings above — reviewed, checked, green. A push that slips past by force doesn’t stay invisible — the Audits ring catches it after the fact.