Skip to content

Enforcement wiring

Enforcement wiring

majordomus://rule/majordomus.enforcement-wiring@1active wiring

Rationale

Every enforcement the policy declares is invoked by the hook it names, from a file the dispatcher will actually execute, without swallowing the exit code.

Required behaviour

Every enforcement the policy declares is invoked by the hook it names, from a file the dispatcher executes, without a swallowed exit code.

Failure behaviour

A violation is a FAIL finding under the category wiring, 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_wiring decides it, dispatched from doctor. The behavioural case test/cases/14_wiring_dispatcher.sh proves it, and CI runs that case.

Where this comes from

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