How the system works
What the platform is made of, what it does by itself, what it never does without a person, and every outside service it talks to. Companion to user-flows.html (what people do) and PLAN.md sections 6, 10, 13 and 14. Read each flow left to right; a box sits in the row of the part that does that step.
1. The whole system
Four layers. People only ever touch the top one. Outside services only ever touch the bottom one. Everything that matters is decided in the middle, on the server.
2. The one path every change takes
Whatever a person does (send a quote, approve a payment, mark a delivery), it goes through the same steps. This is what makes the rest safe.
3. System flows
Each of the things the system does, end to end.
4. The stages a record moves through
Each kind of record has fixed stages and fixed ways to move between them. A record cannot skip a stage, and each move is recorded with who and when.
5. What the system does by itself
Every automatic step: what starts it, what it does, who is told, and where a person must still decide. Each has its own switch.
6. Outside services and how each is used
Every connection: which way data flows, what it is for, what happens when it fails, and when it is built. No connection is ever the only way to do something.
9. Where AI helps, and which tool does it
Jev makes typed choices only: it does not write, read documents or do sums. Each row names the tool, what the person sees, and what stays with a person. Full plan in AI.md.