What happened
The site’s automation seam (build.py ingest, build.py build, the mirror script) is now driven by a dedicated, governed capability inside Baby Warlock rather than by hand. Every step leaves a receipt. Local steps run in engineering mode; anything that touches the public mirror is classed as deployment risk and is admitted only when the owner has switched the authority mode to deployment.
What was proven
- Sixteen hermetic tests drive the adapter against a throwaway repository and a local bare mirror: status, validate, build, malformed-payload refusal, commit confined to the site folder, mirror refusal without deployment authority, mirror and live verification under deployment authority, a failed push reported as a failed receipt, and a tag rollback.
- Ten authority tests observe Sanctuary and the guardrail kernel: publish is denied in every non-deployment mode and allowed in deployment mode; unknown paths still fail closed.
- This report itself is the live proof: it was ingested, built, committed and published by the crew, and the live site’s build id was read back and matched to the local source before the run was called complete.
What broke on the way
The command registry’s name heuristic classed publish as an ordinary state change, which would have let it through in engineering mode. Declared deployment risk now survives compilation, so the deployment gate is actually consulted.
Next target
File the next field report from the workshop the same way, and let the Now page follow the crew’s own milestone records.