docs: complete canon alignment housekeeping

This commit is contained in:
codex 2026-08-18 18:12:32 +02:00
parent 490c2d97b1
commit debbc13b40
14 changed files with 397 additions and 81 deletions

View file

@ -4,7 +4,7 @@ type: workplan
title: "Align railiance-master with InfoTechCanon and policy publication"
domain: financials
repo: railiance-master
status: active
status: blocked
owner: codex
topic_slug: railiance
created: "2026-08-18"
@ -56,7 +56,7 @@ the Custodian archive deviation, and records the policy-publication gap.
```task
id: RMASTER-WP-0024-T02
status: progress
status: wait
priority: high
state_hub_task_id: "00e6bc8b-bb75-44a0-b6aa-5a4ce034ce99"
```
@ -83,11 +83,17 @@ registration, and clean-revision publication verification in `policy-nexus`.
That handoff is State Hub message
`3f27c5a1-3ff8-4d9d-9310-799f303f526a`.
2026-08-18 closeout: all source-side and repo-local work is complete. T02 is
`wait` because `policy-nexus` has not yet claimed the message or registered the
eight explicit publication entries. The workplan is blocked only on that
downstream owner action; no local metadata, renderer, or clean-revision gate
remains.
## T03 - Establish reviewed demand intake without demand-as-task
```task
id: RMASTER-WP-0024-T03
status: todo
status: done
priority: medium
state_hub_task_id: "54e321e2-e603-4b72-9d76-7a36f6b30782"
```
@ -103,11 +109,18 @@ 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.
Completed 2026-08-18. `demand/README.md` defines an unreviewed DemandSignal
surface, required purpose/scope review, four explicit dispositions, and the
rule that resolved records leave intake for dated history. The operator request
that created this workplan is the worked example at
`history/260818-demand-canon-policy-alignment.md`. `SCOPE.md` now declares
honest `core` conformance; no empty optional directories were created.
## T04 - Reconcile completed-work archival with State Hub discovery
```task
id: RMASTER-WP-0024-T04
status: todo
status: done
priority: medium
state_hub_task_id: "27f1b916-d6fc-4cc4-8bd2-52eda8994666"
```
@ -121,11 +134,18 @@ 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.
Completed 2026-08-18. Seven finished records (`ADHOC-2026-07-30` and
`RMASTER-WP-0017`, `0018`, `0019`, `0021`, `0022`, `0023`) moved to
`workplans/archived/260818-...`, retained their stable IDs and State Hub task
bindings, and changed to `status: archived`. `history/` remains the home for
inactive architecture exploration and reviewed demand rather than workplan
state.
## T05 - Produce a repeatable canon-consumer alignment packet
```task
id: RMASTER-WP-0024-T05
status: todo
status: done
priority: low
state_hub_task_id: "ff70f0e3-32ba-4420-8ce5-983224d792a3"
```
@ -137,3 +157,12 @@ 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.
Completed 2026-08-18. The structured review packet is
`docs/evidence/infotech-canon-alignment-review-2026-08-18.yaml`. It records the
repository context, seven selected canon surfaces, ten source-linked mappings,
the full scorecard, the existing repo-local workplan, and two feedback items.
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`.

View file

@ -4,11 +4,11 @@ type: workplan
title: "Ad-hoc Railiance framework maintenance on 2026-07-30"
domain: financials
repo: railiance-master
status: finished
status: archived
owner: codex
topic_slug: railiance
created: "2026-07-30"
updated: "2026-07-30"
updated: "2026-08-18"
state_hub_workstream_id: "1cc4d75f-9bd8-4843-8b18-5ce9637edd60"
---

View file

@ -4,13 +4,13 @@ type: workplan
title: "Rail, Rapp, and Reef Repo Separation"
domain: financials
repo: railiance-master
status: finished
status: archived
owner: codex
topic_slug: railiance
planning_priority: high
planning_order: 17
created: "2026-07-25"
updated: "2026-07-25"
updated: "2026-08-18"
related_repos:
- railiance-master
- railiance-cluster

View file

@ -4,13 +4,13 @@ type: workplan
title: "First-Wave Repo Family Materialization"
domain: financials
repo: railiance-master
status: finished
status: archived
owner: codex
topic_slug: railiance
planning_priority: high
planning_order: 18
created: "2026-07-25"
updated: "2026-07-26"
updated: "2026-08-18"
related_repos:
- railiance-master
- railiance-cluster

View file

@ -4,13 +4,13 @@ type: workplan
title: "Knative Qonto Runtime on reef-railiance"
domain: financials
repo: railiance-master
status: finished
status: archived
owner: codex
topic_slug: railiance
planning_priority: high
planning_order: 19
created: "2026-07-26"
updated: "2026-07-29"
updated: "2026-08-18"
related_repos:
- railiance-master
- qonto-assistant

View file

@ -4,13 +4,13 @@ type: workplan
title: "Rapp Declaration Schema and Family Declaration Validator"
domain: financials
repo: railiance-master
status: finished
status: archived
owner: codex
topic_slug: railiance
planning_priority: high
planning_order: 21
created: "2026-08-11"
updated: "2026-08-13"
updated: "2026-08-18"
related_repos:
- railiance-master
- railiance-platform

View file

@ -4,11 +4,11 @@ type: workplan
title: "Establish reef-storage for Scaleway object storage"
domain: financials
repo: railiance-master
status: finished
status: archived
owner: grok
topic_slug: railiance
created: "2026-08-14"
updated: "2026-08-14"
updated: "2026-08-18"
related:
- RMASTER-WP-0017
- RMASTER-WP-0021

View file

@ -4,13 +4,13 @@ type: workplan
title: "Private-by-default exposure until production admission"
domain: financials
repo: railiance-master
status: finished
status: archived
owner: grok
topic_slug: railiance
planning_priority: high
planning_order: 23
created: "2026-08-15"
updated: "2026-08-15"
updated: "2026-08-18"
related:
- ADR-0006
- ADR-0008
@ -97,7 +97,7 @@ It does **not** belong as the system owner in:
## Decision (T01, accepted 2026-08-15)
Ratified as written. Recorded in
[`docs/adr/ADR-0008-private-by-default-exposure.md`](../docs/adr/ADR-0008-private-by-default-exposure.md).
[`docs/adr/ADR-0008-private-by-default-exposure.md`](../../docs/adr/ADR-0008-private-by-default-exposure.md).
| Posture | Meaning | Who may reach it |
| --- | --- | --- |