coulomb/risk-nexus
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Audit blocked work and reconcile owner dependency requirements

Browse source 
Assistant: codex
Assistant-Model: gpt-6.1-sol
Assistant-Session: 01a1046e-3b46-7cb0-883c-bbb4739ab936
This commit is contained in:
tegwick 2026-10-04 11:31:48 +02:00
parent e1f006b067
commit 7095f328e6
7 changed files with 123 additions and 21 deletions
Download patch file Download diff file Expand all files Collapse all files

20
docs/method/intake.md
View file

@ -49,7 +49,7 @@ the loss is occurring, while the record is being written.
becoming aware. **`first_observed` is what starts that clock**, and this is
the one place the register puts a hard deadline on itself. Escalation is
immediate under trigger 1 or 2 — not batched, notwithstanding the batching
rule, because batching exists to protect the operator's attention and a
rule, because batching exists to protect the founder's attention and a
72-hour clock outranks that.
- **Severity is scored on what is happening, not what could.** The `L4`
likelihood band — "already happening" — exists for exactly this and is
@ -66,7 +66,7 @@ stopwatch.
Someone outside the estate finding something and having somewhere to send it.
**No such place exists.** There is no `security.txt` anywhere in the estate, no
**At proposal time (2026-08-21), no such place was recorded.** There was no `security.txt` in the reviewed records, no
published address, and no route from an outsider to this register. If someone
found a flaw in a coulomb.social surface tomorrow, their options would be to
guess an email address or say nothing.
@ -86,6 +86,22 @@ approve. Routed on 2026-08-21 with a proposal:
Until that exists, this register's claim to accept external reports is
aspirational and `STATE.md` says so.
### Owner disposition reconciled — 2026-10-04
The custodian's committed `CUST-WP-0063-T04` records approval of the bounded
RFC 9116 route on 2026-08-22, decision
`051de446-7ae9-4eca-a766-14345655ab35`. The decision-API lookup returned
404; this is an owner-file reconciliation. `the-custodian/intakes.md`
records `CUST-IN-0011` as `routed`, owned by `policy-nexus`, with selected
Contact URI `https://security.coulomb.social/` on 2026-08-23. Selection is
complete; provisioning and monitored delivery are not established here.
Required owner return: the production host grant, certificate/ingress,
monitored private receipt mechanism and an end-to-end report-to-risk-nexus
receipt, followed by the published `security.txt` location and expiry.
The intake's 2026-08-23 DNS/TLS observation is historical, not a fresh probe.
Risk-nexus does not provision the endpoint or publish an untested contact.
## What all four share
The reporter says what is true and how they know. This register says how bad it

17
docs/method/production-transition.md
View file

@ -2,10 +2,12 @@
id: RISK-METHOD-PRODUCTION
type: method
title: "The production transition: what expires, and who says when"
status: proposed
status: adopted
owner: the-custodian
drafted_by: risk-nexus
drafted: "2026-08-21"
adopted: "2026-08-22"
decision: "937bf962-9297-40d5-a3e4-356532f179c7"
workplan: RISK-WP-0005-T03
review_interval: 6m
---
@ -18,10 +20,15 @@ the event, named who declares it, or told the repos that carry the obligations.
An acceptance that expires on an undefined event expires on nobody's calendar.
**Status: `proposed`.** The definition is the custodian's; the plumbing is
this repo's.
**Status: `adopted`.** The custodian records adoption on 2026-08-22 in
`the-custodian/workplans/CUST-WP-0063-inbox-governance-packets.md`, T04,
decision `937bf962-9297-40d5-a3e4-356532f179c7`. Risk-nexus reconciled that
owner record on 2026-10-04, at commit
`01e7c7b4e46c360c60ed1cd9677cc4a455cbb332`. The State Hub decision lookup
returned 404; adoption is attributed to the committed owner record, not a
successful decision-API read. This does not declare that the transition occurred.
## Proposed definition
## Adopted definition
> **The production transition is the first moment any system in the estate
> holds, processes or decides about the data of a real external person or
@ -44,7 +51,7 @@ usable:
## Who declares it
The operator, through `the-custodian`. Not this register: `INTENT.md` keeps
The founder, exercising `GOVERN @ estate`, through `the-custodian`. Not this register: `INTENT.md` keeps
"deciding what canon says" and estate-level facts with the custodian, and a
risk register that unilaterally declares the estate to be in production has
appointed itself.