RISK-WP-0002: findings publish whole; method docs public except escalation
Operator ruled both. Findings publish as the file a reader gets — including RISK-F-0001's record that this register graded it critical while its fix notice sat unread. A summary would be a second document per finding kept in sync by hand, and drift is the failure this repo most distrusts; and a published register containing only other repos' defects reads as an accusation, while one containing its own reads as a record. Method docs public except escalation, which is restricted because it names spend thresholds and describes when the operator personally is interrupted — a map of where attention is scarce, needed by nobody judging a finding. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
parent
7dc8d01a63
commit
f0db7c83ca
10 changed files with 112 additions and 10 deletions
|
|
@ -43,7 +43,7 @@ batch — so the route wants to exist before it is needed, not during.
|
|||
|
||||
```task
|
||||
id: RISK-WP-0002-T01
|
||||
status: todo
|
||||
status: progress
|
||||
priority: high
|
||||
```
|
||||
|
||||
|
|
@ -56,11 +56,13 @@ or as a summary?** `RISK-F-0001` contains a full ruling, a re-grade, a review
|
|||
log and this register's own process defect. Some of that is register-internal
|
||||
work product. Decide once, here, and apply it to every later publication.
|
||||
|
||||
In progress 2026-08-20. Operator ruled: findings publish **whole**. Publication front-matter applied to `RISK-F-0001` and `RISK-F-0008` (`revision`, `last_reviewed`, `review_interval: 6m`) with proposed ids, paths and subtitles; both now read `publication: requested`. Handover request sent to `policy-nexus`. The open question the task named is answered and recorded in `docs/rulings/2026-08-20-publication.md` — including that `RISK-F-0001` publishes with the paragraph about this register grading it wrong.
|
||||
|
||||
### T02 — Rule on the method documents
|
||||
|
||||
```task
|
||||
id: RISK-WP-0002-T02
|
||||
status: todo
|
||||
status: done
|
||||
priority: medium
|
||||
```
|
||||
|
||||
|
|
@ -78,6 +80,8 @@ Suggested split, to be ruled on rather than assumed: severity and disclosure
|
|||
public, escalation and review internal. Escalation in particular describes when
|
||||
the operator is interrupted, which is not the estate's business to advertise.
|
||||
|
||||
Completed 2026-08-20. Public: `severity`, `disclosure`, `review`, `verification`, `dependencies` — the instruments a reader needs to judge whether a published finding means anything. Restricted: `escalation`, because it names the operator's spend thresholds and describes when the operator personally is interrupted, which is a map of where attention is scarce and is needed by nobody judging a finding. `check-procedure` stays internal by omission: an operating manual, not an instrument.
|
||||
|
||||
### T03 — The standing route
|
||||
|
||||
```task
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue