How Chock works
Architecture
How the chock repositories fit together, and the path one policy takes from the catalog to your agent's hook.
These diagrams show how chock blocks your coding agent's wrong moves before they land. Each box cites the file that does the work, at a pinned commit, and each has a card. Select a box to read its card, or read the cards in order below each diagram.
Diagrams
- The whole train: Every repository in the chock train and how a policy travels from chock-catalog through chock to the hook your agent's client runs.
- The life of a policy: One policy from its manifest in chock-catalog, through chock compile and an install, to a tool call, its verdict and the decision log.
- Lifecycle in a repository: The repo path from end to end. You author a policy, check it and sync it into hook files. Then each tool call, commit, push and CI run goes through the hook to a verdict and one log line.
- Emitters and hook points: Which emitter of chock compile writes each hook point, and the file chock sync installs for it.
- Stop and resume: A person's stop on agents. It shows the files chock stop and chock stop --everywhere write, the hooks that read them, and the log lines a stop leaves.
Kinds of box
Each box's outline colour says what kind of thing it is:
- Repository: a repository in the chock train.
- Engine code: engine code that runs as a command or inside a hook.
- Generated file: a file chock writes or a policy carries. Its outline is dashed.
- The agent's client: the agent's client, and what passes between it and the hook.
- Local log: a file the hook writes on your machine.
Built from engine 5a4b6287a46e and catalog 1e60d211c1bb.