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

workplan: RMASTER-WP-0022 establish reef-storage

Browse source 
Plan a storage reef for Scaleway object storage, distinct from
reef-railiance. Backup attributes will live there; the reef schema
must allow a substrate with no compute rail.
This commit is contained in:
codex 2026-08-14 15:44:44 +02:00
parent 4864b7852d
commit 82b7b7295d
3 changed files with 133 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

6
docs/repo-family-bootstrap-contract.md
View file

@ -96,8 +96,10 @@ reefs it is placed on; that field is the source of a reef's `bound_rapps`.
`runtime_dependencies` names capabilities, not the resources that satisfy
them. Who provisions a capability (for example the postgres backup object
store) is owned outside the rapp: the bucket by `resource-control`, the
credential by `railiance-platform`. The rapp consumes a reviewed destination.
store) is owned outside the rapp: procurement and cost by
`resource-control`, operation and non-secret attributes by the reef
(`reef-storage` for S3, not `reef-railiance`), the credential by
`railiance-platform`. The rapp consumes a reviewed destination.
### `reef-*`