coulomb/reef-storage
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Activate storage reef after verified restore and close workplan

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0e424-7d4f-7ca0-a5ac-31f8df7458d8
This commit is contained in:
tegwick 2026-09-27 20:35:21 +02:00
parent 30fdb7c336
commit 91b4c2e145
3 changed files with 20 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

4
declarations/reef.yaml
View file

@ -3,7 +3,7 @@ reef_id: reef-storage
repo: reef-storage
ownership_repo: railiance-platform
substrate_kind: object-storage
lifecycle_state: planned
lifecycle_state: active
criticality: high
current_members:
- railiance-platform-pg-backup
@ -14,6 +14,8 @@ source_documents:
path: workplans/RMASTER-WP-0022-establish-reef-storage.md
- repo: resource-control
path: docs/operational-reference-convention.md
- repo: resource-control
path: docs/evidence/RESOURCE-WP-0002-T05-restore-2026-08-14.json
compatibility_notes:
- "S3-compatible capability is delegated to Scaleway. This reef does not host a rail and does not operate the object store internals."
- "Non-secret attributes (endpoint, bucket, region, prefix, lifecycle) live under substrate/object-stores/."