Start with one behavior.

You do not need to reorganize your repository to try the model. Choose one observable promise, then connect the evidence around it.

1. Write the promise

Describe the actor, trigger, successful result, and meaningful failure response. Give the behavior a stable ID. If two parts can be released or owned independently, consider separate behaviors.

2. State the constraints

Add rules and concrete scenarios. Reuse a shared rule through a link rather than copying its wording into every behavior.

3. Find the owner

Identify the slice accountable for delivering the behavior. Record its public contract and implementation paths, including backend resources that live elsewhere.

4. Connect the checks

Name the verification procedure and its stable selector. A linked test is useful, but a current passing run is a separate claim. Keep that distinction visible.

5. Review the explanation

Write audience-safe guidance for an exact release. Keep internal decisions and implementation details out of the customer projection unless they help the customer act.

Open the worked example Read the Core specification