Service · the happy path
One sentence in, one recorded release out.
A request turns into a health-gated release with the commit, the evidence and the pages it touched attached to it. This is the same path the page you are reading went through.
The docket
In the order it happens
- Read The repository is mapped first: routes, templates, shared shells, CSS selectors, script hooks and existing tests. Nothing is inferred from a filename.
- Plan The request becomes ordered batches with acceptance criteria, and every discovered route ends up changed, verified or deliberately deferred — and it says which.
- Change One writer per project. Edits stay inside the discovered surface, and a guard that the change would break is re-asserted with its intent rather than deleted quietly.
- Verify The running application is rendered at desktop and mobile widths, console and network are inspected, and the before/after impact is compared rather than assumed.
- Release The image is built with the test suite as a build step, the proxy configuration is validated before the reload, and the public endpoint is probed before the release is recorded.
Evidence
What comes back with the work
Routes accounted for
every entry in the map is changed, verified or deferred
Renders checked
desktop, tablet and phone, plus a no-script pass
Release record
commit, health samples, 5xx rate and proxy logs
Rollback
the previous release commit stays known until the next
The release is recorded only after the gate passes. A failed step is a failed release, not a warning in a log.