Grouping procedures by shared maintenance operations may ease audits

Type: types/note.md

Conjecture: keeping procedures that need the same maintenance checks in a persistent group may reduce audit effort compared with assembling that group on demand.

Concrete example

Commonplace groups reusable procedures such as writing and connection discovery under kb/instructions/. A maintenance pass could inspect that group for procedures that have drifted from their supporting theory or duplicate one another. If those procedures were scattered among theory notes, the pass would first have to distinguish executable procedures from explanations. This illustrates the proposed saving; no comparison has measured it.

Open Questions