Guide
This guide is for engineers who contribute to product flows: you write a change, and the change then travels through build, review, deploy, exposure, and measurement systems that you do not own but are accountable for.
It answers three questions that people usually learn the slow way:
- Where is my change right now? Every stage is a named state with an owner and an exit condition.
- Why is it stuck? Each gate blocks on something specific. The pages name it.
- What happens after it ships? Merging is the middle of the story, not the end.
How to read it
Each page is anchored by one interactive diagram. The diagrams are standalone documents — you can pan, zoom, search, trace a relationship, switch themes, and export them. Open one full screen when you want to follow a single path through it.
| Page | Diagram | Answers |
|---|---|---|
| Delivery Platform | Architecture | Which systems exist and who owns them |
| Pull Request to Production | Workflow | Which gate you are waiting on |
| Deploy Request | Sequence | What a rollout does, call by call |
| Product Events | Data flow | Where the data you emit ends up |
| Feature Rollout | Lifecycle | How exposure widens after merge |
| Your First Change | — | The whole path as one checklist |
A note on accuracy
The diagrams describe a conventional delivery platform, not one specific company’s stack. Where your organisation differs, the shape usually survives even when the tool names change: something builds an artifact, something signs it, something promotes it, something watches it, and something can put it back. Replace the labels, keep the gates.
The diagram sources live in diagrams/
as small JSON specifications, so a correction is a pull request rather than a redraw.