Practice 1
Describe the data flows of the fictional note service, mark where trust boundaries belong, and name what enforces each one. Include the reviewer path.
Compare with a sample answer
A document reaches the model, which returns a JSON proposal. Trusted host code supplies the signed-in actor and time to the gateway, which checks its note store and, for writes, a separate approval record, then returns a response to the host. Boundaries sit where data gains a different kind of authority: document to model, model to gateway, and reviewer decision to execution. The gateway code enforces ownership and approval checks, and the reviewer path that creates approvals is a distinct trusted path that must not appear among the model's callable tools. A boundary line only helps if I can name the code that enforces it; if the model could edit the store directly, the gateway would change nothing.
A good answer traces document, model, host, gateway and reviewer path, and ties each boundary to enforcing code.