Profile requirements

majordomus://rule/majordomus.profile-requirements@1active profilesfinish

it references

depends_on majordomus.justified-escalation@1

referenced by

exercises accept-or-refuse-finished-work
exercises read-only-the-context-that-fits
exercises trust-the-policy-before-reading-it

Rationale

A profile may demand more than the shared contract — a regression test, a decision record — and finish refuses without it.

Required behaviour

A profile may require more than the shared contract, and finish refuses a completed outcome that lacks it.

Failure behaviour

A violation is a FAIL finding under the category regression, 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_profile_requirements decides it, dispatched from finish. The behavioural case test/cases/16_profiles.sh proves it, and CI runs that case.

Where this comes from

canonical file: .ai/repo/rules/vendor/majordomus/rules/profile-requirements.v1.md
identity: majordomus.profile-requirements@1
also served as: MCP resource majordomus://rule/majordomus.profile-requirements@1 · majordomus entity show rule/majordomus-profile-requirements-1 · GET /api/v1/entity?uri=majordomus://rule/majordomus.profile-requirements@1
in the Cockpit: /cockpit/objects/rule/majordomus-profile-requirements-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.