Skip to content

Decision records

Decision records

majordomus://rule/majordomus.decision-records@1active recordsdecisions

it references

referenced by

Rationale

Every entry in decisions.md carries the task, the head and the reason, so a decision can be found by the worker who needs it.

Required behaviour

Every recorded decision carries the task, the head and the reason, so the worker who needs it can find it.

Failure behaviour

A violation is a WARN finding under the category records; the command continues and exits as it otherwise would. Under watch it is reported as drift and the command exits 11.

Verification

mj_validate_decisions decides it, dispatched from check, doctor, watch. The behavioural case test/cases/21_decision_question.sh proves it, and CI runs that case.

Where this comes from

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

Searches the titles and descriptions of every page this site publishes.