canon: resolve work-record governance packets
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
Python Tests / pytest (push) Successful in 21s

This commit is contained in:
codex 2026-08-22 22:35:37 +02:00
parent 3db3570b93
commit 8bda6e28b4
7 changed files with 255 additions and 11 deletions

32
intakes.md Normal file
View file

@ -0,0 +1,32 @@
# Custodian intake records
## CUST-IN-0011 — Provision a monitored external security-report Contact URI
```yaml
id: CUST-IN-0011
kind: intake
title: "Provision a monitored external security-report Contact URI"
status: open
lane: red
priority: high
owner: the-custodian
tags: [needs-human, compliance-relevant]
origin: residual
origin_ref: CUST-WP-0063
notes: "The minimal RFC 9116 security.txt route is approved for policy.coulomb.social/.well-known/security.txt, with reports routed privately to risk-nexus and no bounty, response-time, or safe-harbour promise. Completion requires the operator to select and provision a real monitored Contact URI; no address may be invented or published before its receiving path is verified."
```
## CUST-IN-0012 — Repair the malformed legacy inbox message identity
```yaml
id: CUST-IN-0012
kind: intake
title: "Repair the malformed legacy inbox message identity"
status: open
lane: green
priority: low
owner: hub-core
origin: residual
origin_ref: CUST-WP-0063
notes: "State Hub returns unread risk-nexus message id 0b8dd0bf-41d-47da-96ac-40e443c32e47, whose second UUID group has only three characters. PATCH /messages/{id}/read rejects it during UUID path parsing, so the already-handled superseded request cannot be marked read through the supported API. Repair must preserve the message body and chronology, assign or map a valid stable identity, and then apply the read transition without direct ad hoc database mutation from this repo."
```