docs: reef attribute refs and resource object workplan
Publish the operational reference convention (reef: and secret: handles). Add a resource-control view of reef-railiance that excludes S3. Open RESOURCE-WP-0006 for the five-facet inventory model.
This commit is contained in:
parent
4b8fc909e6
commit
5b2435cb58
10 changed files with 395 additions and 1 deletions
|
|
@ -69,6 +69,13 @@ This workplan owns requirements, comparison, procurement evidence, resource
|
|||
registration, cost/utilization monitoring, and proof that the purchased
|
||||
resource works.
|
||||
|
||||
The purchased object is a five-facet resource (`RESOURCE-WP-0006`):
|
||||
description, decision, `reef:` attribute refs, `secret:` handles, and
|
||||
potential vs actual consumers. Non-secret operating attributes (endpoint,
|
||||
bucket, region) will be owned by `reef-storage` (`RMASTER-WP-0022`), not
|
||||
inlined here and not placed on `reef-railiance`. See
|
||||
`docs/operational-reference-convention.md`.
|
||||
|
||||
- Human financial authority approves purchase and accepts contractual terms.
|
||||
- `railiance-platform` owns provider credential custody and the approved
|
||||
Kubernetes Secret/credential-broker delivery.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue