docs(RMASTER-WP-0024): finish canon publication alignment

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a025c2-407a-7a32-b40a-f37a52f03f62
This commit is contained in:
codex 2026-08-22 18:26:51 +02:00
parent 5078e5a487
commit 4fb07b5796

View file

@ -4,11 +4,11 @@ type: workplan
title: "Align railiance-master with InfoTechCanon and policy publication"
domain: financials
repo: railiance-master
status: blocked
status: archived
owner: codex
topic_slug: railiance
created: "2026-08-18"
updated: "2026-08-18"
updated: "2026-08-22"
state_hub_workstream_id: "de6681cd-9f8b-4a17-89d8-d3e3ce506388"
---
@ -56,7 +56,7 @@ the Custodian archive deviation, and records the policy-publication gap.
```task
id: RMASTER-WP-0024-T02
status: wait
status: done
priority: high
state_hub_task_id: "00e6bc8b-bb75-44a0-b6aa-5a4ce034ce99"
```
@ -89,6 +89,17 @@ eight explicit publication entries. The workplan is blocked only on that
downstream owner action; no local metadata, renderer, or clean-revision gate
remains.
Completed 2026-08-22. `policy-nexus@25dd59a` registered all eight ADRs with
stable `/adr/<document>/v1/` addresses and immutable
`/revisions/accepted-1/` addresses. Its generated publication manifest records
each entry as `current`, owned by `railiance-master`, and sourced from clean
revision `468a52a`; there are no ADR changes between that revision and current
`railiance-master@5078e5a`. Current downstream verification reports 17 policy
tests passing and all eight currency checks current. The fleet-wide source
inventory now also sees six newer, unrelated sources in other repositories;
that downstream review queue does not invalidate or reopen this completed
Railiance publication slice.
## T03 - Establish reviewed demand intake without demand-as-task
```task
@ -166,3 +177,11 @@ Rail/rapp/reef specialization remains local; the only canon pressure is whether
ITC-REPO-LAYOUT should explicitly permit task-system-compatible archive paths.
That question was routed to `info-tech-canon` in State Hub message
`446f5cf1-53f7-4ca0-ab5a-f7278eae6fd7`.
## Closeout
All five tasks are complete. Railiance authority remains in this repository;
InfoTechCanon remains the general semantic authority; and Policy Nexus now
publishes the accepted Railiance ADRs without becoming a write-back source.
No residual work from this workplan remains. Later policy-source discoveries
and future ADR revisions follow the standing downstream publication workflow.