PR architecture gate: catch undocumented change before merge
Arcobay · Architecture documentation · Aug 15 · Updated Aug 15
A PR architecture gate warns or blocks when a pull request changes system structure without updating the living diagram — like tests, but for the map.
A PR architecture gate is a check on the pull request that warns or blocks when the change alters system structure and the living diagram was not updated.
Unit tests catch broken functions. Nothing catches “we added a queue and forgot the map” until a client asks. Arcobay’s gate is that missing check: compare the PR to the documented architecture, then warn or block on Team and Agency.
How to use it
- Start in warn mode so the team sees the signal without stopping merges.
- Move to block on paths that define production topology (new services, new data stores).
- Pair it with decisions on the diagram so the PR can link to why, not only what.
This is a Team-plan feature — see pricing. It is also why Arcobay is not only a diagram generator; compare architecture tools that stop at a PNG.
FAQ
Need CI? Team/Agency include warn and block; wire it to your GitHub or GitLab flow.
UI-only PRs? The gate targets structural change, not every stylesheet edit.