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

Record all three rulings; RISK-WP-0003 finished

Browse source 
Escalation rule adopted as written. RISK-F-0008 accepted with the legal
policy set as the compensating control. Canon kinds packet sent to
the-custodian, with note offered lifecycle-free and verifications
deliberately withheld as an unsettled species.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
tegwick 2026-08-20 23:37:45 +02:00
parent 674bd41635
commit 02a17e601d
3 changed files with 57 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

10
workplans/RISK-WP-0003-regulatory-intake.md
View file

@ -4,7 +4,7 @@ type: workplan
title: "Make regulatory intake a working remit rather than one record"
domain: infotech
repo: risk-nexus
status: blocked
status: finished
owner: the-custodian
topic_slug: risk-nexus
created: "2026-08-20"
@ -51,7 +51,7 @@ From `RISK-REG-0001` and `RISK-F-0008`, both already written down:
```task
id: RISK-WP-0003-T01
status: wait
status: done
priority: high
```
@ -59,7 +59,11 @@ Custodian decision. Cheap, and it is what stops the estate either buying advice
it does not need or discovering it needed it. Until it is ruled, `RISK-F-0008`
stays escalated as `partially-answered`.
Waiting 2026-08-20, typed rather than open-ended (`docs/method/dependencies.md`): the custodian rules the trigger list, and if nothing arrives by 2026-11-17 the register records the assumption **as an assumption**, which is honest and is not an answer. Carried on `RISK-F-0008`.
Completed 2026-08-20. Ruled: **no external determination while building.** The three triggers survive, not as what starts a purchase but as what ends the acceptance — `RISK-F-0008` moves to `accepted` with a named accepter and an end condition rather than sitting `open` on an assumption.
The ruling came with a direction that turned a deferral into an asset: **define and keep a set of legal policies for reuse**, because work contexts will need specific positions in place and should retrieve them rather than research them. `docs/regulatory/policies/` — thirteen entries keyed by activation condition, with a retrieval table so a context pulls a slice.
Two entries turned out to be **already active and unowned**: commercial and tax retention (`RISK-POL-0009`) and the e-invoicing receiving obligation (`RISK-POL-0012`), live since 2025 with no system in the estate named as the receiving point. Finding a live obligation in the first hour of writing the catalogue is the argument for the catalogue.
### T02 — Retention periods per category