coulomb/risk-nexus
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
A risk management service.
9 commits 1 branch 0 tags 880 KiB
Find a file
tegwick e8ee138ad2 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>
2026-08-19 23:20:31 +02:00
findings RISK-F-0003 — ops-warden agent read-boundary blind spot on ungraded lanes 2026-08-19 23:08:00 +02:00
workplans Use the canon-registered id scheme for the workplan prefix 2026-08-19 23:20:31 +02:00
.custodian-brief.md chore(consistency): sync task status from DB [auto] 2026-08-19 23:19:40 +02:00
INTENT.md INTENT: the register is no longer empty, and the first finding tested the deferral 2026-08-17 22:52:37 +02:00
README.md Seed INTENT: risk register, regulatory intake, escalation duty 2026-08-17 15:55:30 +02:00
WORK-RECORDS.md Use the canon-registered id scheme for the workplan prefix 2026-08-19 23:20:31 +02:00

README.md

risk-nexus

Risk register and regulatory intake for the estate. Serves risk.coulomb.social. Owned by the-custodian.

Holds findings — security, architecture, operational, compliance — with a severity, an owner and a date; decides whether and when each is published; and decides which must reach the operator personally rather than sitting in a register.

It does not fix things: findings route to the repo that owns the defect. It does not host: policy-nexus is the publication surface.

  • Intent: INTENT.md