coulomb/risk-nexus
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
A risk management service.
68 commits 1 branch 0 tags 849 KiB
Find a file
custodian-sync dceb5ba008 chore(consistency): sync task status from DB [auto] 
Updated by fix-consistency on 2026-09-01:
  - update .custodian-brief.md for risk-nexus

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a058f3-8ba0-7692-a042-9a870fc3d663
2026-09-01 02:44:31 +02:00
activity-definitions Drop dedupe_key_strategy from the inbox watch and say what actually happens 2026-08-20 12:02:14 +02:00
docs Sweep risk inbox and reconcile findings 2026-09-01 02:41:32 +02:00
findings Sweep risk inbox and reconcile findings 2026-09-01 02:41:32 +02:00
history Persist the gap analysis to history/, open RISK-WP-0005 2026-08-21 08:19:57 +02:00
notes RISK-WP-0005 finished: the seven gaps closed 2026-08-21 08:34:30 +02:00
tools Match the record to what the owners were told, and stop the tracker hiding ids 2026-08-21 09:34:57 +02:00
workplans risk: complete Policy Nexus publication handover 2026-09-01 01:54:09 +02:00
.custodian-brief.md chore(consistency): sync task status from DB [auto] 2026-09-01 02:44:31 +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 RISK-WP-0005 finished: the seven gaps closed 2026-08-21 08:34:30 +02:00
README.md risk: complete Policy Nexus publication handover 2026-09-01 01:54:09 +02:00
REGISTER.md Sweep risk inbox and reconcile findings 2026-09-01 02:41:32 +02:00
STATE.md risk: complete Policy Nexus publication handover 2026-09-01 01:54:09 +02:00
WORK-RECORDS.md chore(registrar): project RISK-WP-0002 closure 2026-09-01 01:56:32 +02:00

README.md

risk-nexus

Risk register and regulatory intake for the estate. Owned by the-custodian.

It does not serve its own site. INTENT.md names risk.coulomb.social as the eventual surface; today public findings and method instruments have permanent addresses through policy-nexus. The source stays here and the published page records its exact source revision.

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