Key features

Vinculum / Capabilities

Clear responsibilities. Deliberate boundaries.

Express the entities, rules and invariants that matter before changing an implementation.

Example in practice

For a release workflow, name the draft, checked and published states. State the invariant that publishing requires checks for the current candidate.

Make authority and policy explicit, so a workflow has clear boundaries.

Example in practice

Separate permission to propose a change from permission to approve it. A label or a comment is not itself authority to deploy.

Bind changes to the contract and candidate they were checked against.

Example in practice

When a specification or implementation changes, invalidate evidence bound to the previous version instead of carrying its green status forward.

Keep approvals, evidence and implementation state connected.

Example in practice

Retain the candidate identity, check results and approval basis together so a reviewer can explain why the transition was permitted.

Products