azoth-operating-model

To bootstrap an Antigravity session, use the Azoth operating model to standardize setup, define workflow scope boundaries, and establish governance gates before active work begins.

An Azoth operating model provides end-to-end orientation for Antigravity sessions, standardizing setup, scope, and workflow gates while centralizing governance artifacts like AGENTS.md and CLAUDE.md.

Set up governance artifacts under .azoth by centralizing primary references such as AGENTS.md and CLAUDE.md, which define read-front references, routing conventions, and repository authority.

Yes, the operating model provides guardrails for bootstrap limits and delivery expectations, helping validate scope and determine bootstrap boundaries to actively reduce out-of-scope work.

You need a cold-start orientation when beginning new Antigravity sessions to align project goals, scope boundaries, and adapters before initiating active development tasks.

The operating model focuses on initial orientation and governance setup; it standardizes workflow routing and scope boundaries but does not handle active development execution or runtime task processing.