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

feat: inventory schema 0.3 and close WP-0006 T01 T02 T04

Browse source 
v0.2 records stay valid. v0.3 requires the five facets. Validators
reject inline Scaleway endpoints and secret-looking strings. The
backup record is the first 0.3 object. Reef views already met T02.
This commit is contained in:
tegwick 2026-08-15 02:40:43 +02:00
parent a9830f3109
commit 34a014a896
8 changed files with 140 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

6
workplans/RESOURCE-WP-0002-procure-postgres-backup-storage.md
View file

@ -32,6 +32,12 @@ The candidate provider baseline is:
This workplan chooses on evidence. It does not presume that keeping compute and
backup at one provider is cheaper or safer.
Inventory output follows `docs/operational-reference-convention.md`
(`RESOURCE-WP-0006`). Operating attributes are `reef:storage/…` references.
Credentials are `secret:railiance-platform/backup`. Do not write a Scaleway
endpoint or key into `data/resources/`. `rapp-postgres` consumes the
reviewed destination; it does not procure it.
## Context and current evidence
`rapp-postgres` has deployed `platform-pg` on reef-railiance at Host Europe.

22
workplans/RESOURCE-WP-0006-resource-object-and-reef-refs.md
View file

@ -8,7 +8,7 @@ status: active
owner: grok
topic_slug: railiance
created: "2026-08-14"
updated: "2026-08-14"
updated: "2026-08-15"
related:
- RESOURCE-WP-0002
- RESOURCE-WP-0003
@ -51,7 +51,7 @@ object storage and own the non-secret attributes this repo will cite.
```task
id: RESOURCE-WP-0006-T01
status: todo
status: done
priority: high
state_hub_task_id: "55d3ebc2-51b7-49d1-8d0d-57ccc6379ae7"
```
@ -67,11 +67,16 @@ an inline secret or endpoint that should be a `reef:` / `secret:` ref, and
accept the proposed backup record with an explicit attribute-ref gap until
`reef-storage` exists.
Done 2026-08-15: schema accepts `0.2` and `0.3`. v0.3 requires the five
facets. `portfolio.validate_record` rejects inline `s3://` / Scaleway
endpoints and secret-looking strings. The live backup record is `0.3`.
Other inventory stays `0.2` until T03.
## T02 — Reef views and the reef-railiance projection
```task
id: RESOURCE-WP-0006-T02
status: progress
status: done
priority: high
state_hub_task_id: "f2b38140-3d73-45a2-a2ff-fea12733e7b0"
```
@ -87,6 +92,11 @@ is out of `reef-railiance`.
Started 2026-08-14: convention published; first reef-railiance view committed.
Done 2026-08-15: `data/reefs/reef-railiance.json` and `reef-storage.json`
validate. Every cited `resource_id` exists in inventory. railiance view
states S3 backup is out of that reef. `reef-storage` view exists now that
the repo does.
## T03 — Migrate live inventory to the five facets
```task
@ -110,7 +120,7 @@ only consumer list.
```task
id: RESOURCE-WP-0006-T04
status: todo
status: done
priority: medium
state_hub_task_id: "a34fa806-ee34-4d3b-a823-2797fe260bbc"
```
@ -122,3 +132,7 @@ remains a consumer, not the procurer.
Done when WP-0002 cites this convention and will not accept an inventory
update that inlines Scaleway endpoint or keys.
Done 2026-08-15: WP-0002 goal cites the convention. The live inventory
record is v0.3 with reef/secret refs; validators reject an inline
Scaleway endpoint on that record.