A record's changed_files names the work, not the tool's exhaust

The changed_files block of a checkpoint, a handover or a closed session names what the episode produced. Paths a declaration already calls generated, projected or local are classified out, and the classification reads those declarations rather than a list of its own.

advisory A violation is reported and the command still succeeds.

The chain

A rule is enforced only when every link below holds. majordomus doctor resolves each one from the source on every run; this page shows what it resolved.

1 Declared majordomus.record-changed-files
2 Validator mj_validate_record_changed_files
3 Runs under doctor
4 On violation reported; the command still exits 0
5 Proved by test/cases/136_changed_files_classifier.sh
6 Run by CI .github/workflows/validate.yml

Where it runs

majordomus doctorIt checks governance only: is Majordomus itself healthy, and is every enforcement it declares actually wired here?

Read it here

read one rule

majordomus doctrine show majordomus.record-changed-files
majordomus check --rule majordomus.record-changed-files