# Trust-boundary map

DA-MODEL-002 / Beacon Bench

Two aligned documents for the same invented bench. Identifiers link a trust boundary, a gap, required evidence and a closure criterion.

| Boundary | What crosses it | Trust basis / limitation |
| --- | --- | --- |
| TB-01 · Client → receiver | A command and its identifier. | A receipt establishes acceptance; it is not evidence of indicator state. |
| TB-02 · Receiver → environment | An intention to change external state. | Execution and observation are separate; an effect can occur without confirmation. |
| TB-03 · Observer → assessment | An observation bound to the command. | Source authenticity and measurement accuracy are assumed here. A real system needs separate evidence. |
| TB-04 · Assessment → interface | A status and observation time. | Display “observed”, time and scope; do not turn a past observation into a current-state guarantee. |

All gaps remain open when moving from the model to a real bench. This demonstrates a deliverable format; it is not a client-system review.

© 2026 Andriy Ivanov. Permission to edit and reuse these fictional review templates for evaluation; no licence to research programmes.