Use the canon-registered id scheme for the workplan prefix

work-record-types_v0.1 pins workplan ids to ^[A-Z]+-WP-[0-9]{4}$ and tasks
to that plus -TNN; a hyphenated RISK-NEXUS prefix trips the sidetrack
detector. RISK-WP also matches the register's existing RISK-F finding
prefix. Renamed before the workplan was indexed anywhere.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
tegwick 2026-08-19 23:20:31 +02:00
parent 0cb5ec0c3c
commit e8ee138ad2
2 changed files with 29 additions and 10 deletions

19
WORK-RECORDS.md Normal file
View file

@ -0,0 +1,19 @@
# Work Records — risk-nexus
> Generated by `statehub fix-consistency` (CUST-WP-0061-T04, work-record
> stage 3). Do not edit by hand — edit the source file/block listed for
> each record and re-run fix-consistency to refresh this index. Archived
> workplans are omitted; closed decisions/intakes/engagements stay listed
> so recently-resolved work is still visible. [auto]
| Kind | ID | Status | Lane | Source |
| --- | --- | --- | --- | --- |
| workplan | RISK-NEXUS-WP-0001 | active | — | workplans/RISK-NEXUS-WP-0001-make-the-register-decidable.md |
| task | RISK-NEXUS-WP-0001-T01 | todo | — | workplans/RISK-NEXUS-WP-0001-make-the-register-decidable.md |
| task | RISK-NEXUS-WP-0001-T02 | todo | — | workplans/RISK-NEXUS-WP-0001-make-the-register-decidable.md |
| task | RISK-NEXUS-WP-0001-T03 | todo | — | workplans/RISK-NEXUS-WP-0001-make-the-register-decidable.md |
| task | RISK-NEXUS-WP-0001-T04 | todo | — | workplans/RISK-NEXUS-WP-0001-make-the-register-decidable.md |
| task | RISK-NEXUS-WP-0001-T05 | todo | — | workplans/RISK-NEXUS-WP-0001-make-the-register-decidable.md |
| task | RISK-NEXUS-WP-0001-T06 | todo | — | workplans/RISK-NEXUS-WP-0001-make-the-register-decidable.md |
| task | RISK-NEXUS-WP-0001-T07 | todo | — | workplans/RISK-NEXUS-WP-0001-make-the-register-decidable.md |
| task | RISK-NEXUS-WP-0001-T08 | todo | — | workplans/RISK-NEXUS-WP-0001-make-the-register-decidable.md |

View file

@ -1,5 +1,5 @@
---
id: RISK-NEXUS-WP-0001
id: RISK-WP-0001
type: workplan
title: "Make the register decidable: severity, disclosure, escalation, expiry"
domain: infotech
@ -11,7 +11,7 @@ created: "2026-08-19"
updated: "2026-08-19"
---
# RISK-NEXUS-WP-0001 — make the register decidable
# RISK-WP-0001 — make the register decidable
## Goal
@ -92,7 +92,7 @@ publishable through `policy-nexus` later; this workplan does not publish it.
### T01 — Severity scale
```task
id: RISK-NEXUS-WP-0001-T01
id: RISK-WP-0001-T01
status: todo
priority: high
```
@ -117,7 +117,7 @@ Constraints it has to satisfy, taken from the findings already here:
### T02 — Disclosure states
```task
id: RISK-NEXUS-WP-0001-T02
id: RISK-WP-0001-T02
status: todo
priority: high
```
@ -141,7 +141,7 @@ Whichever way it goes is a recorded decision, not a habit.
### T03 — The escalation rule
```task
id: RISK-NEXUS-WP-0001-T03
id: RISK-WP-0001-T03
status: todo
priority: high
```
@ -171,7 +171,7 @@ The custodian adopts the rule. Ask, do not assume.
### T04 — Review dates and expiry
```task
id: RISK-NEXUS-WP-0001-T04
id: RISK-WP-0001-T04
status: todo
priority: medium
```
@ -193,7 +193,7 @@ with `review_by` and `last_reviewed`.
### T05 — Register index
```task
id: RISK-NEXUS-WP-0001-T05
id: RISK-WP-0001-T05
status: todo
priority: medium
```
@ -213,7 +213,7 @@ generator relies on written down where a reporter will see it.
### T06 — Grade the three open findings
```task
id: RISK-NEXUS-WP-0001-T06
id: RISK-WP-0001-T06
status: todo
priority: high
```
@ -243,7 +243,7 @@ message to that repo, not as an edit in it.
### T07 — Rule on what is waiting outside the register
```task
id: RISK-NEXUS-WP-0001-T07
id: RISK-WP-0001-T07
status: todo
priority: medium
```
@ -270,7 +270,7 @@ one.
### T08 — Nag
```task
id: RISK-NEXUS-WP-0001-T08
id: RISK-WP-0001-T08
status: todo
priority: low
```