coulomb/risk-nexus
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
A risk management service.
7 commits 1 branch 0 tags 849 KiB
Find a file
tegwick 63dde5fa38 RISK-NEXUS-WP-0001 — make the register decidable 
The three open findings all leave severity, disclosure and escalation
unset, correctly: those are this repo's to set and the instruments to set
them with do not exist yet. The workplan writes the severity scale, the
disclosure states (re-taking the deferral with RISK-F-0001 in hand), the
escalation rule INTENT.md says is unwritten, and the review/expiry rule —
then grades the three findings and rules on what is waiting outside the
register.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-19 23:19:16 +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 RISK-NEXUS-WP-0001 — make the register decidable 2026-08-19 23:19:16 +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

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