← BOUND MethodGitHub
GUIDE / BOUNDARY

Define responsibility before interface shape.

A boundary describes ownership and decision rights. The interface is the observable mechanism through which that responsibility becomes usable by another domain.

Boundary questions

  • What responsibility belongs here?
  • Who owns the decisions inside it?
  • What state does it own?
  • What may it decide independently?
  • What does it expose?
  • What does it consume?
  • Which dependencies are forbidden?

Boundary artifact

domain:
responsibility:
owner:
owns:
may_decide:
exposes:
consumes:
forbidden_dependencies:

This is a proposed canonical structure for the documentation layer. It should become normative only after the BOUND artifact schema is formally specified.

Independence test

Ask whether independent implementers can build opposite sides of the boundary and reach the same behavioural conclusion without requiring a meeting. If not, the missing assumption belongs in the boundary or contract.