coulomb/risk-nexus
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Waits attach to any record, not just findings

Browse source 
Adopting a rule is nobody's finding; neither is registering a canon kind
or publishing a document. Each obligation that lived outside the
mechanism was invisible to it. RISK-WP-0001 now carries both of its
custodian waits, and the escalation-rule one has the register's most
uncomfortable default pointed inward: unadopted by 2026-09-17 means
recorded as de facto in force but unratified, said on the face of every
escalation sent under it. A draft that quietly governs is exactly what
this register exists to notice.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
tegwick 2026-08-20 23:18:52 +02:00
parent 9a22a2adc5
commit 3a0ba5d427
6 changed files with 54 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

19
docs/method/dependencies.md
View file

@ -112,6 +112,25 @@ So the waiting list is built from **every** finding, not from the watched ones.
A closed record with an open obligation is precisely the thing that goes quiet,
because nothing is prompting anyone to look at it any more.
## A wait is not a findings-only idea
Adopting a rule is nobody's finding. Registering a canon kind is nobody's
finding. Publishing a document is nobody's finding. All three are obligations
someone owes, and each one that lived outside the mechanism was invisible to it.
So waits attach to **any** record this repo keeps — findings, regulatory
records, workplans — and `make check` reports them together. `RISK-WP-0001`
carries two: the escalation rule that is producing decisions while still
`status: proposed`, and the canon question about what kind of thing a finding
is.
The first of those has the most uncomfortable default in the register, and it
points inward: **if the rule is not adopted by 2026-09-17, it is recorded as de
facto in force but unratified, and every escalation sent under it says so on
its face.** That is worse than either adopting or rejecting it, which is the
point — a draft that quietly governs is the thing this register was built to
notice.
## Where the waits are visible
`make check` reports every open wait with its age, its owner and its default