REFERENCE
BOUND vocabulary and engineering rules.
This section is intended to become the precise technical reference for the methodology and its machine-readable artifacts.
Core terms
| Term | Meaning |
|---|---|
| Domain | System context from which meaningful responsibilities are derived. |
| Boundary | Explicit responsibility ownership and decision rights. |
| Contract | Observable cross-boundary behaviour and guarantees. |
| Execution | Independent implementation inside an agreed boundary. |
| Verification | Evidence that implementations conform to the intended contracts. |
| Contract Freeze | A governed state in which contract changes become explicit engineering events. |
| Team Brief | A bounded execution context describing mission, scope, dependencies, constraints, and acceptance. |
Agent execution artifacts
Phase 2 adds transport-neutral artifacts for agent handoff, verification planning, and result reporting. See Agent Artifacts.
Required Interfaces Statement
Identify every cross-boundary interface and its contract/version. State that no other cross-boundary dependency is assumed unless explicitly added.
Normative status
The documentation layer distinguishes established BOUND concepts from proposed future tooling. Machine-readable schemas become normative only when formally specified and implemented.