Rules and instructions

What a workload is told is never a black box. The stage panel's instructions row and the pre-flight show the exact layers, in the order the model receives them:

1. The contract — CLAUDE.md, the company's operating rules. Changed through a pull request only.
2. The agent's persona — the agent manifest's system. Edit from the panel.
3. Craft — the skills attached to the agent. The Craft row says which skills reach a run, which reach only a worker, and which reach nobody.
4. Standing rules — rule sets bound to the company, a pipeline or a stage (Settings › Rules). Binding rules are enforced; advisory ones are read.
5. The workload — the workload's opening prompt.
6. Direction — words a person typed for this one run, when they did.
7. The stage — the pipeline file's own wording for the stage: what it asks, what evidence it expects, what it must produce.

History. Every layer is a file under git, so the History button lists every commit that changed what a run is told, and a diff shows exactly which lines differ from what runs today.

Read the whole sheet renders the assembled prompt server-side by the same code the run uses, so what you read is what the model gets.