Non-Goals

A contract that only says what a capability does is half finished. Non-goals are the other half, an explicit list of what the capability deliberately does not handle, written down so the next person doesn't expand it by accident.

Leaving non_goals blank because the scope feels obvious is one of the toolkit's named anti-patterns. It feels harmless in the moment and turns into a real problem the first time someone extends a capability into territory it was never meant to cover, and review has no boundary left to point at.

Non-goals pair with inputs and outputs to define a capability's edges. Together they're what makes acontract something you can trust instead of something you have to reverse-engineer.