council-maintenancelisted

# Council Maintenance — Learning Hooks > The self-improvement surface for the Council's own rules. Sister to > `continuous-learning-mandate.md` (the loop these feed), > `rule-authoring-global-vs-project.md` (where a refinement lands), > `principal-level-mandate.md` (the depth a refinement must hold). ## Standards Cited - **ISO 9001:2015 §10.3** — *Continual improvement*: the organisation shall continually improve the suitability, adequacy and effectiveness of the system. These hooks are that mechanism for the rule corpus: each rule declares how its own effectiveness is observed. - **ISO/IEC 27001:2022 §10.1** — *Continual improvement*, paired with §10.2 *Nonconformity and corrective action*. A fired signal is a nonconformity; a refinement candidate is the bounded corrective action it may take. - **NIST SP 800-53 Rev. 5, CA-7** — *Continuous Monitoring*: define metrics and the frequency of assessment. Each rule's "signals to watch" is its metric set; the phase boundary is its assessment frequency. - **ISO/IEC/IEEE 12207:2017** — *Systems and software engineering — Software life cycle processes*, which places process improvement inside the life cycle rather than beside it. Same argument for why upkeep guidance is versioned with the rules it maintains. ## Purpose `continuous-learning-mandate.md` rule 6 requires every rule, skill and agent to carry a `learning_hooks` section naming **signals to watch** ("what observations matter for refining this artifact