Every request that reaches a business factory, from a person or from another role, first chooses its path. The path decides how much is written before doing, how much is reviewed and who has to step in. And it is chosen by what the request touches, never by its size.
Three paths
| Path | When | What is done |
|---|---|---|
| small | the request is understood, stays contained and can be resumed from the request and the change alone | it is explored, done, checked and verified for real; no document is needed |
| medium | the request needs to be organized, but crosses none of the limits of the large path | a short document with the original request quoted, numbered specifications, tasks and a record of what was done; proportionate checks; real verification |
| large | it touches any of the limits below, whatever its size | a full design, with its reviews, before doing |
What makes a request large
A request is large if it touches any of these things, even if it looks like a one-line change:
- more than one service, or a contract between services: a route, an event, a permission, a stored value that another service reads (a rename becomes a contract change as soon as the name crosses from one service to another);
- real data deleted, or written without a way back; anything irreversible;
- secrets, access, permissions or credentials;
- a decision that belongs to a person: a business concept, a new term, something that is published.
When in doubt, it is large. And a request that started as small or medium and along the way turns out to touch one of those limits stops, says so and moves to the large path.
Why it is not measured by size
The usual temptation is to measure a request by how much work it seems to be: one line of code, a paragraph, a configuration change. But the most dangerous requests tend to be small. Renaming a field is one line; if another service reads that field, it is a broken contract. Changing a permission is one line; if it opens access it should not, there is no going back.
What defines the risk is what the change touches, not how big it is. That is why the question that chooses the path is the same one that orders autonomy (chapter 10): if something crosses a limit, can break without anyone noticing or belongs to a person, it deserves more care, however small it is.
Example. At Ópticas Horizonte, fixing a typo in the skill «How to put together a quote» is a small request. Adding a new section on financing to the skill, which Administration has to validate, is medium. Renaming the field «price» to «list price» in the spreadsheet that the follow-up routine also reads is large, even though it is one word: it is a stored value that another piece reads, and therefore a contract.
Reviews, sized to the risk
The path also sets how much review a request gets. A small change is verified against reality, and that is enough. A medium one adds a couple of reviews chosen for the risk. A large one goes through several independent reviews, and if after a few rounds a serious problem remains unresolved, it is taken to the person who decides, with the problem in plain view, instead of going around in circles (chapter 18).
In short, each request chooses one of three paths according to what it touches, goes the large way when in doubt, and a request that discovers it has crossed a limit changes paths. The interlude that follows traces a request through the whole business factory.