coulomb/railiance-platform
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Finish architecture-cleanup RAILIANCE-WP-0016 T05
Some checks failed
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Has been cancelled
Details

Browse source 
Item 13 is the restore RESOURCE-WP-0002 already proved. Item 14 retires
the dead Bitnami postgresql-ha deploy path and gates Valkey until a
consumer exists. Item 17 publishes the versioned S3 consumer-interface
index.
This commit is contained in:
codex 2026-08-15 14:43:44 +02:00
parent 2af19627e1
commit 1eb5fa51ed
8 changed files with 156 additions and 69 deletions
Download patch file Download diff file Expand all files Collapse all files

31
workplans/RAILIANCE-WP-0016-architecture-cleanup-backlog.md
View file

@ -4,11 +4,11 @@ type: workplan
title: "Architecture cleanup backlog, WSJF-prioritized"
domain: financials
repo: railiance-platform
status: active
status: finished
owner: codex
topic_slug: railiance
created: "2026-08-12"
updated: "2026-08-12"
updated: "2026-08-15"
related_repos:
- railiance-master
- railiance-infra
@ -67,11 +67,11 @@ reliable numbers here, because nobody has scoped them yet.
| 10b | Schedule verification; route failures where they are seen | `railiance-infra` / Q7 owner | 7 | 6 | 8 | 3 | **7.0** |
| 11 | Consolidate the bootstrap path; sort inherited S2 content | `railiance-bootstrap` | 5 | 3 | 4 | 4 | **3.0** |
| 12 | Forge migration: `rapp-forgejo` + S4 layer transfer | `railiance-forge` / S4 | 6 | 4 | 4 | 5 | **2.8** |
| 13 | Prove a restore end to end | `railiance-platform` | 9 | 5 | 9 | 8 | **2.9** |
| 14 | Valkey extraction + legacy postgresql-ha retirement | `railiance-platform` | 5 | 4 | 4 | 5 | **2.6** |
| ~~13~~ | ~~Prove a restore end to end~~ **DONE 2026-08-15** | `railiance-platform` | 9 | 5 | 9 | 8 | **2.9** |
| ~~14~~ | ~~Valkey extraction + legacy postgresql-ha retirement~~ **DONE 2026-08-15** | `railiance-platform` | 5 | 4 | 4 | 5 | **2.6** |
| 15 | Sweep remaining Gitea prose (~31 files each) | `railiance-forge`, `railiance-apps` | 3 | 2 | 2 | 3 | **2.3** |
| 16 | Declare the Q6 cost boundary with `resource-control`/`fin-hub` | `railiance-master` | 4 | 3 | 3 | 4 | **2.5** |
| 17 | Version S3 consumer service interfaces | `railiance-platform` | 6 | 3 | 5 | 6 | **2.3** |
| ~~17~~ | ~~Version S3 consumer service interfaces~~ **DONE 2026-08-15** | `railiance-platform` | 6 | 3 | 5 | 6 | **2.3** |
| 18 | Resolve the C4 ecosystem-modelling overlap | `railiance-master` / `railiance-fabric` | 4 | 3 | 4 | 5 | **2.2** |
| 19 | S4 build-out: pipeline templates, SDKs, portal | `railiance-enablement` | 7 | 3 | 4 | 9 | **1.6** |
@ -94,9 +94,10 @@ conformance checker already exists in `railiance-infra` and has simply not run
since 2026-03-09. **Slice 10a is now the highest-value item after the
ratifications** at WSJF 12.0.
**Item 13 is blocked, not deprioritized.** Proving a restore needs the object
storage decision (`9c21c0e0`), which is escalated and awaiting human approval on
commercial terms. Its WSJF understates it; treat the blocker as the real item.
**Item 13 is done, not blocked.** `RESOURCE-WP-0002` finished 2026-08-15.
Barman is live on `platform-pg`; T05 recorded full restore and PITR on
2026-08-14; daily backups have completed since. Pointer:
`docs/evidence/RAILIANCE-WP-0016-item13-restore-2026-08-15.md`.
**Item 19 is last and that is deliberate.** S4 build-out is the widest gap in
the family, but it is large, and item 12 gives S4 a smaller first
@ -270,7 +271,7 @@ it.
```task
id: RAILIANCE-WP-0016-T05
status: todo
status: done
priority: medium
state_hub_task_id: "a40faaf1-77db-43f5-a774-6ab3866d8e1d"
```
@ -278,7 +279,15 @@ state_hub_task_id: "a40faaf1-77db-43f5-a774-6ab3866d8e1d"
Execute the S3-owned items in WSJF order — 13 (blocked on `9c21c0e0`), 14, 17 —
and keep this table current as items complete or their sizes become known.
**Done 2026-08-15.** Item 13 unblocked by `RESOURCE-WP-0002` finish: restore
already proven as T05 there; live `platform-pg-daily` backups completing.
Item 14: Bitnami postgresql-ha deploy path fail-closed (never live on
railiance01); Valkey has no S2 instance to extract and no consumer, so
deploy is gated. Item 17: `docs/s3-consumer-interfaces.md` v1.0.0.
## Outcome
Pending. T01-T03 delivered; routed to `railiance-master` for adoption
(message `ac73b172`). T04 rescoping and T05 S3-owned execution remain.
T01–T05 done. Routed to `railiance-master` (message `ac73b172`); master
took items 6 and 8 as WP-0021 and declined the rest. S3-owned items 13,
14 and 17 executed 2026-08-15 after the object-store purchase landed.
Workplan finished. Remaining backlog rows belong to other repos.