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

RPF-WP-0018 T07: route findings F1-F5 and close the workplan
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
Details
CI Smoke / container-smoke (push) Successful in 2s
Details

Browse source 
Replies sent to policy-nexus (F1 substrate boundary, F2 ADR surface, F5
frontmatter corpus), rapp-postgres and net-kingdom (F3 rule/number split,
F4 provider-versus-consumer ladders), tenant-engine (placement policy
answering its three asks), adaptive-pricing (co-signature requested) and
railiance-master (bao.coulomb.social still open, second public name
proposed). Routed inbox marked read.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
codex 2026-08-17 21:57:56 +02:00
parent e7e4e33bb8
commit 1147406035
2 changed files with 7 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

5
SCOPE.md
View file

@ -89,6 +89,11 @@ policy, and lane governance.
declared, not deployed. OpenBao package boundary and PAT cutover are declared, not deployed. OpenBao package boundary and PAT cutover are
closed. Platform rapp declarations conform (`RAILIANCE-WP-0015`). closed. Platform rapp declarations conform (`RAILIANCE-WP-0015`).
Versioned consumer interfaces: `docs/s3-consumer-interfaces.md`. Versioned consumer interfaces: `docs/s3-consumer-interfaces.md`.
Tenancy posture and database placement policy are declared
(`docs/tenancy-posture.md`, `docs/placement-policy.md`, `RPF-WP-0018`).
Two open items they surfaced: `apps-pg` has no backup configured, and
both shared clusters owe a declared consumer ceiling before their third
consumer. Decisions are now recorded as ADRs in `docs/adr/` (ADR-0003).
- Known drift: State Hub attributes ~11 capabilities to this repo, including - Known drift: State Hub attributes ~11 capabilities to this repo, including
S1/S2/S4/S5 concerns it does not own. The four `capability` blocks in this S1/S2/S4/S5 concerns it does not own. The four `capability` blocks in this
file are authoritative; the hub carries stale pre-split attributions file are authoritative; the hub carries stale pre-split attributions

4
workplans/RPF-WP-0018-policy-surface-alignment.md
View file

@ -68,7 +68,7 @@ marker, and the marker is the honest answer until telemetry lands.
**Does not fit, and the policy should change.** Five findings, T07. **Does not fit, and the policy should change.** Five findings, T07.
## Findings against the policy (recommendations, not yet routed) ## Findings against the policy (routed 2026-08-17, T07)
**F1 — `POLICY-NEXUS-WP-0001` assigns S3 a concern S3 does not own.** **F1 — `POLICY-NEXUS-WP-0001` assigns S3 a concern S3 does not own.**
It states "`railiance-platform` owns the substrate — DNS, TLS, ingress, It states "`railiance-platform` owns the substrate — DNS, TLS, ingress,
@ -262,7 +262,7 @@ maximum declared across co-residents, so a shorter horizon is a P2 trigger.
```task ```task
id: RPF-WP-0018-T07 id: RPF-WP-0018-T07
status: progress status: done
priority: high priority: high
state_hub_task_id: "b021fda3-23bd-4843-8d1b-983b6ec582b5" state_hub_task_id: "b021fda3-23bd-4843-8d1b-983b6ec582b5"
``` ```