coulomb/risk-nexus
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
A risk management service.
32 commits 1 branch 0 tags 849 KiB
Find a file
tegwick ff74a60af4 Classify with the canon governance_and_control tags 
'security' warned as an unrecognised family tag; risk, governance,
compliance and audit are the canonical ones and are closer to what this
repo does anyway — it holds risk and judges compliance, it does not
build security.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-20 08:08:07 +02:00
docs Record the 2026-08-20 ruling: OpenBao layer, id collision, silent-drop defect 2026-08-20 07:44:21 +02:00
findings Adaptive check cadence: the interval is earned, not assigned 2026-08-20 07:43:51 +02:00
notes RISK-N-0004: route the zone-lookup requirement to zone-engine as a note 2026-08-20 07:24:33 +02:00
tools Ad hoc: make the ladder executable, and make the collision class loud 2026-08-20 08:05:42 +02:00
workplans Draft RISK-WP-0002, RISK-WP-0003, RISK-WP-0004 2026-08-20 08:07:06 +02:00
.custodian-brief.md chore(consistency): sync task status from DB [auto] 2026-08-19 23:41:18 +02:00
.repo-classification.yaml Classify with the canon governance_and_control tags 2026-08-20 08:08:07 +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
Makefile Ad hoc: make the ladder executable, and make the collision class loud 2026-08-20 08:05:42 +02:00
README.md Close out RISK-WP-0001: task notes, README, repo classification 2026-08-19 23:34:34 +02:00
REGISTER.md Adaptive check cadence: the interval is earned, not assigned 2026-08-20 07:43:51 +02:00
WORK-RECORDS.md Classify with the canon governance_and_control tags 2026-08-20 08:08:07 +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.

Where things are

  • REGISTER.md — the whole register, one screen. Generated; do not edit.
  • findings/ — one file per finding. findings/README.md is the filing contract for reporting repos.
  • notes/ — seen, deliberately below the floor. Not graded, not reviewed.
  • docs/method/ — how this repo decides: severity, disclosure, escalation, review and expiry.
  • docs/rulings/ — the reasoning behind each grading, dated.
  • workplans/ — the work.

Using it

make register   # rebuild REGISTER.md from findings/
make check      # verify the index, then report what is going quiet

make check reports ungraded findings, overdue reviews, stalled remediation, embargoes due for re-decision, escalations awaiting the operator, and what is owed at the production transition. It changes nothing.

  • Intent: INTENT.md