Aliases: UI; frontend; BFFE; API; worker; projection; DTO; observation; consumer contract.
Expose only the choices and obligations relevant to the selected commitment. When a story protects server-owned work, the backend owns its permitted progression, results and recovery. A browser presents those outcomes; its cached availability, local flags or earlier green badge do not grant server authority. This boundary does not mandate a backend for a genuinely local story.
Engines own their source facts and effects. Ports describe the contracts through which stories use them. Adapters remain responsible for truthful observations and actions; a trait implementation or mocked invocation is not proof of a real effect.
A serializable receipt, refusal code or validated value is data under its stated contract. It is not a deserialized current permission. Keep known settlement separate from availability of a current projection. Presentation patterns such as MVVM and intentional dynamic dispatch are useful when they preserve these boundaries; their names decide no business policy.
Your Reflection
Saved in this browser. Export a copy before changing devices.