How our software lifecycle now works: Claude writes each artifact, a named person accepts it, and rules are enforced automatically while the work happens. Pick the way you would like to understand it.
A 3D simulation of one change going round the loop: files travel, people decide at the gates, hooks block what the rules forbid.
What this is in plain words, what changes for you and what does not, and a pointer to your role's page.
The claims-status example with the actual files and messages at every stage, from the idea to the incident that closes the loop.