the-custodian/workplans/CUST-WP-0063-inbox-governance-packets.md

id	type	title	domain	repo	status	owner	topic_slug	created	updated	origin	origin_ref	state_hub_workstream_id
CUST-WP-0063	workplan	Resolve legacy identifier and Risk Nexus governance packets	infotech	the-custodian	finished	codex	custodian	2026-08-22	2026-08-22	handoff	statehub-inbox:08067461-bb95-42e2-b8de-b492fb99f56e	7b8fbe11-6254-5fd8-a402-606ba91f4ae7

Resolve legacy identifier and Risk Nexus governance packets

Resolve the current Custodian inbox requests without renaming historical work records or inventing an external security contact. The packet covers the Ops Mason legacy MASON-0001 scheme, Risk Nexus register species, the proposed production-transition definition, and the minimal external-report route.

The operator already ruled that Risk Nexus's lifecycle-bearing register records must join the work-record backbone. The remaining canon judgment is their placement under the existing register-entry kind and the exclusion of notes, which deliberately have no lifecycle and therefore do not meet the canon definition of a work record.

Triage the coordination packet against current canon

id: CUST-WP-0063-T01
status: done
priority: high
state_hub_task_id: "36a33104-f551-539a-baf3-5f9fccc63766"

Read the source residuals and proposals, current canon, validator behavior, relevant Repo Manager ownership decisions, and the source records themselves. Distinguish decisions that can be made from missing real-world inputs.

Extend the work-record registry and validator coverage

id: CUST-WP-0063-T02
status: done
priority: high
state_hub_task_id: "0420420c-6923-515e-b4f8-1e893f86dd9f"

Grandfather the exact MASON-0001 workplan/task scheme. Register Risk Nexus findings and regulatory records as register-entry schemes. Keep RISK-N-* notes unregistered because they have no lifecycle. Make the validator consume the registry as its sole task-id authority and add regression coverage.

Done (2026-08-22): the machine registry and prose canon carry the exact Mason schemes and the two Risk register species. The validator no longer has a second hard-coded task-id grammar. Thirty-five focused tests pass; this repo is strict-clean at 412 records; the live Ops Mason files classify the legacy ids without a sidetrack warning.

Resolve repeated historical source identity

id: CUST-WP-0063-T03
status: done
priority: high
state_hub_task_id: "0b914088-0ca6-53d0-9185-d1b443c0309b"

Record that repeated source blocks carrying the same canonical id and same hub UUID are one record with duplicate source occurrences, not two records. Ask Repo Manager to index the UUID once, preserve both source locations as diagnostic provenance, and reject creation of a second identity.

Done (2026-08-22): canon and machine copy now distinguish a duplicate source occurrence (same id, same UUID) from an identity collision (same id, different UUID). Decision 3c487545-ee40-4049-89fa-34b41747a7eb records the ruling. Handoffs went to Ops Mason (8e65a254) and Repo Manager (48eff8d3). The Ops Mason source intake also lacks its required lane; that exact local correction was returned to its owner rather than silently changed here.

Resolve and route the Risk Nexus policy requests

id: CUST-WP-0063-T04
status: done
priority: high
state_hub_task_id: "36c3aa5a-5c5d-5221-8c5f-597eda15a2c2"

Adopt the proposed production-transition definition and Custodian declaration authority. Approve the minimal RFC 9116 route at Policy Nexus, routed to Risk Nexus, without adding a bounty, response-time promise, or safe-harbour policy. Keep selection and provisioning of a real monitored Contact URI as a live human-needed intake rather than publishing an invented address.

Done (2026-08-22): decisions 051de446-7ae9-4eca-a766-14345655ab35 and 937bf962-9297-40d5-a3e4-356532f179c7 adopt the production-transition definition and approve the bounded RFC 9116 route. Risk Nexus received the consolidated outcome in 477ec6f9; Policy Nexus received its publication gate in 2d86983b. The missing real Contact URI remains live as CUST-IN-0011.

Close coordination and reconcile State Hub

id: CUST-WP-0063-T05
status: done
priority: medium
state_hub_task_id: "5f981912-7c54-5a9b-b07d-a8f45c793dcb"

Record decisions, send outcome messages, mark handled inbox messages read, hand off every residual as a live work record, run repository verification, and run statehub fix-consistency.

Five of six unread source messages were marked read. The sixth has malformed legacy id 0b8dd0bf-41d-47da-96ac-40e443c32e47; the typed API rejects it before the read transition. That repair is live residual CUST-IN-0012 rather than an invisible note.

Done (2026-08-22): all handled messages are read where the API permits; the malformed-id repair was routed to Hub Core in ffc8d656. The complete repository suite passes (72 tests), strict work-record validation passes with 413 records, and git diff --check is clean. Final consistency reconciliation regenerates the work-record index; identifier write-back is correctly deferred to the single Repo Manager registrar after commit and push.

Closure Review

The packet is resolved. Canon, machine registry, validator behavior, tests, State Hub decisions, and owner handoffs now agree. No historical identifier or UUID was rewritten.

Two actionable leftovers are live records before closure:

• CUST-IN-0011 — select, provision, and receipt-test the monitored public security Contact URI before Policy Nexus publishes security.txt;
• CUST-IN-0012 — repair the malformed legacy message identity so its handled request can transition to read through the supported API.

Decision ids: 3c487545-ee40-4049-89fa-34b41747a7eb, 051de446-7ae9-4eca-a766-14345655ab35, and 937bf962-9297-40d5-a3e4-356532f179c7.