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

Publish S3 platform-service rapp pattern; route family proposals
Some checks failed
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Has been cancelled
Details

Browse source 
T01: docs/rapp-platform-service-pattern.md generalizes the ownership split
already drawn in the rapp-openbao and rapp-postgres boundary docs into a
reusable four-question test, a reference rapp.yaml for platform services, the
grouped-rapp member rule, and the credential-lane position. It deliberately
does not restate the four-axis model, which railiance-master owns.

T03/T04/T05: proposals routed to the repos that own the model rather than
authored here - reef-railiance (bound_rapps lists 1 of 3 live rapps, and should
be derived rather than hand-listed), railiance-master (rapp.schema.json plus a
family declaration validator, grouped-rapp members field, wave-2 candidate
refresh), the-custodian (canon promotion of the four-axis model, which also
closes the open C-31 multi-segment prefix failures).

T02 is held until the schema settles so the platform rapps and the schema do
not converge on different answers.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
codex 2026-08-11 11:11:57 +02:00
parent 20d9a599f5
commit b17a9f8bff
3 changed files with 172 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

21
workplans/RAILIANCE-WP-0015-platform-rapp-consistency.md
View file

@ -15,6 +15,7 @@ related_repos:
- reef-railiance
- rapp-openbao
- rapp-postgres
state_hub_workstream_id: "a14fd4d3-2e30-474f-aeea-af560c622394"
---
# RAILIANCE-WP-0015 - Platform rapp consistency and deployment-management contract
@ -104,8 +105,9 @@ It must not:
```task
id: RAILIANCE-WP-0015-T01
status: todo
status: done
priority: high
state_hub_task_id: "53f6a28f-ee10-4695-ab7f-6781b3d35c76"
```
Publish the S3 platform-service rapp pattern as `docs/rapp-platform-service-pattern.md`:
@ -119,6 +121,7 @@ inventing a third boundary vocabulary.
id: RAILIANCE-WP-0015-T02
status: todo
priority: high
state_hub_task_id: "eada3a6f-9f4e-47bc-bfe5-2ec585f5d312"
```
Bring `rapp-openbao/declarations/rapp.yaml` and
@ -132,8 +135,9 @@ not converge on different answers.
```task
id: RAILIANCE-WP-0015-T03
status: todo
status: done
priority: medium
state_hub_task_id: "493d0ab0-595c-4a14-b3d6-8c396bd7747b"
```
Correct the reef binding registry: propose to `reef-railiance` that
@ -144,8 +148,9 @@ since a hand-listed registry is what went stale.
```task
id: RAILIANCE-WP-0015-T04
status: todo
status: done
priority: high
state_hub_task_id: "30cb0cb2-2ce2-4d27-8d43-c29dc32904a8"
```
Route the schema and validator proposal to `railiance-master`: a
@ -156,8 +161,9 @@ was actually built and the grouped-context wave-2 inventory.
```task
id: RAILIANCE-WP-0015-T05
status: todo
status: done
priority: medium
state_hub_task_id: "ca661530-5ebd-422b-854d-7b6986f0b3fe"
```
Route the canon promotion proposal to `the-custodian`: a
@ -170,6 +176,7 @@ the open C-31 failures on multi-segment `RAPP-*-WP-` ids.
id: RAILIANCE-WP-0015-T06
status: todo
priority: medium
state_hub_task_id: "9ea10522-47a9-4cce-b0d8-cb6f9c7813b8"
```
Define how a rapp binds to its credential lane: the relationship between
@ -181,4 +188,8 @@ the existing lane, it does not build a parallel one.
## Outcome
Pending.
Session of 2026-08-11: T01 published the S3 platform-service pattern; T03, T04
and T05 routed their proposals to the owning repos (reef-railiance
f0f44ce0, railiance-master 04c776c4, the-custodian cc64764a). T02 is
deliberately held until railiance-master settles the schema, so the platform
rapps and the schema do not converge on different answers. T06 is open.