docs: align master with canon and policy publication

2026-08-18 17:00:07 +02:00 · 2026-08-18 17:00:07 +02:00 · 7d32673812
commit 7d32673812
parent 6e230be13a
12 changed files with 403 additions and 70 deletions
--- a/workplans/RMASTER-WP-0024-canon-and-policy-publication-alignment.md
+++ b/workplans/RMASTER-WP-0024-canon-and-policy-publication-alignment.md
@ -0,0 +1,138 @@
+---
+id: RMASTER-WP-0024
+type: workplan
+title: "Align railiance-master with InfoTechCanon and policy publication"
+domain: financials
+repo: railiance-master
+status: active
+owner: codex
+topic_slug: railiance
+created: "2026-08-18"
+updated: "2026-08-18"
+state_hub_workstream_id: "de6681cd-9f8b-4a17-89d8-d3e3ce506388"
+---
+
+# RMASTER-WP-0024 - Canon and policy publication alignment
+
+## Goal
+
+Adopt the useful parts of the InfoTechCanon consumer and repository-layout
+standards while preserving Railiance-specific authority, and make this repo's
+accepted ADRs consumable by `policy-nexus` without creating a second source of
+truth.
+
+## Boundaries
+
+- `info-tech-canon` owns the general semantic and layout standards; this repo
+  records consumer alignment and sends canon pressure back explicitly.
+- `railiance-master` owns Railiance framework ADR content and lifecycle.
+- `policy-nexus` owns publication addresses, rendering, history, and currency;
+  it reads this repo and never writes back.
+- This workplan does not publish workplans, evidence, runbooks, schemas, or
+  general documentation as policy.
+- Custodian ADR-001 workplan discovery remains controlling where the generic ITC
+  layout recommendation would break State Hub indexing.
+
+## T01 - Separate intent, current scope, canon authority, and publication
+
+```task
+id: RMASTER-WP-0024-T01
+status: done
+priority: high
+state_hub_task_id: "bc28546d-4184-40df-b9e5-5f1c1015ba1e"
+```
+
+Review `INTENT.md` and `SCOPE.md` against ITC-REPO-LAYOUT, the canon consumer
+review workflow, and the `policy-nexus` source/publication boundary. Record an
+honest layout conformance level, current omissions, authority relationships,
+and the SCOPE-to-INTENT gap.
+
+Completed 2026-08-18. `INTENT.md` now distinguishes semantic canon, Railiance
+content authority, and downstream publication. `SCOPE.md` describes current
+artifacts and active work, declares minimal ITC layout conformance, preserves
+the Custodian archive deviation, and records the policy-publication gap.
+
+## T02 - Make framework ADR source metadata publication-ready
+
+```task
+id: RMASTER-WP-0024-T02
+status: progress
+priority: high
+state_hub_task_id: "00e6bc8b-5ff1-4f12-9ea0-08fe2d8486ca"
+state_hub_task_id: "00e6bc8b-bb75-44a0-b6aa-5a4ce034ce99"
+```
+
+Add consistent source metadata to every accepted ADR under `docs/adr/`: title,
+status, owner, immutable semantic revision, and last-reviewed date. Review each
+date rather than copying file timestamps. Define how amendments advance a
+revision without rewriting an already-published immutable revision.
+
+Coordinate with `policy-nexus` for explicit stable and revision addresses and a
+review interval. The publication manifest remains downstream; the source
+metadata remains here.
+
+Done when all eight currently discovered ADRs move from `metadata-pending` to
+published or carry an explicit reviewed reason not to publish, and the
+`policy-nexus` source audit/build/currency checks pass against a clean
+`railiance-master` revision.
+
+2026-08-18: Source-side metadata is present on all eight ADRs using stable
+`RMASTER-ADR-NNNN` identities, `accepted-1` as their first immutable semantic
+revision, source ownership, evidence-based last-reviewed dates, and a six-month
+review interval. Remaining work is downstream explicit addressing, manifest
+registration, and clean-revision publication verification in `policy-nexus`.
+
+## T03 - Establish reviewed demand intake without demand-as-task
+
+```task
+id: RMASTER-WP-0024-T03
+status: todo
+priority: medium
+state_hub_task_id: "54e321e2-e603-4b72-9d76-7a36f6b30782"
+```
+
+Decide whether recurring cross-repo architecture proposals justify adopting
+the ITC `demand/` surface and `core` layout conformance. If adopted, define a
+small demand record that captures provenance, consumer purpose, purpose fit,
+scope pressure, review disposition, and the resulting workplan or rejection.
+
+Do not mirror the State Hub inbox wholesale and do not promote raw requests
+directly to tasks. Empty directories alone do not count as adoption.
+
+Done when the repo either has a used, documented demand intake with one worked
+example or records why `minimal` conformance remains the honest level.
+
+## T04 - Reconcile completed-work archival with State Hub discovery
+
+```task
+id: RMASTER-WP-0024-T04
+status: todo
+priority: medium
+state_hub_task_id: "27f1b916-d6fc-4cc4-8bd2-52eda8994666"
+```
+
+Review finished workplans still present in `workplans/`. Archive eligible files
+using the repository's Custodian convention
+`workplans/archived/YYMMDD-RMASTER-WP-...` and preserve frontmatter IDs and
+links. Keep `history/` for dated inactive architecture exploration rather than
+silently adopting the generic ITC finished-workplan placement.
+
+Done when active retrieval is uncluttered, archived records remain indexed, and
+`statehub fix-consistency` reports no task or workplan drift.
+
+## T05 - Produce a repeatable canon-consumer alignment packet
+
+```task
+id: RMASTER-WP-0024-T05
+status: todo
+priority: low
+state_hub_task_id: "ff70f0e3-32ba-4420-8ce5-983224d792a3"
+```
+
+Apply the InfoTechCanon consumer review kit using the smallest relevant surface
+set: Purpose/Demand, Intent-Scope-Purposes, Governance, Task, Information Space,
+Landscape, and ITC-REPO-LAYOUT. Record mappings, evidence, prioritized gaps,
+repo-local work, and any canon feedback without silently changing canon terms.
+
+Done when a future reviewer can repeat the assessment and distinguish a
+Railiance-specific gap from genuine pressure on InfoTechCanon.