Blocker resolution

majordomus://rule/majordomus.blocker-resolution@1active blockersfinish

it references

depends_on majordomus.externalise-decisions@1

referenced by

governed_by long-running-work
exercises accept-or-refuse-finished-work
exercises block-acceptance-on-an-open-question
exercises carry-a-blocker-across-a-handover

Rationale

No task can be completed while any question on this branch is unresolved; it can still be finished as blocked, partial, no_match or failed.

Required behaviour

No task is accepted as completed while any question on the branch is unresolved.

Failure behaviour

A violation is a FAIL finding under the category blockers, and the command that found it exits 10. Under watch the same violation is reported as drift and the command exits 11.

Verification

mj_validate_blockers decides it, dispatched from check, finish. The behavioural case test/cases/17_doctrine_enforcement.sh proves it, and CI runs that case.

Where this comes from

canonical file: .ai/repo/rules/vendor/majordomus/rules/blocker-resolution.v1.md
identity: majordomus.blocker-resolution@1
also served as: MCP resource majordomus://rule/majordomus.blocker-resolution@1 · majordomus entity show rule/majordomus-blocker-resolution-1 · GET /api/v1/entity?uri=majordomus://rule/majordomus.blocker-resolution@1
in the Cockpit: /cockpit/objects/rule/majordomus-blocker-resolution-1

This page is generated from the file above by scripts/generate-site-data; editing the page changes nothing, editing the file changes every surface. The relations above are edges of docs/generated/graph.json, which the executable writes from the same index.