railiance-platform/registry/capabilities/capability.railiance.platform-services.md
codex a86dfe2220
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 3s
docs(reuse): establish reviewed NetKingdom security capabilities
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a137ca-5c77-7a71-b9ae-23ad9b0b5684
2026-10-14 06:42:43 +02:00

135 lines
4.8 KiB
Markdown

---
id: capability.railiance.platform-services
name: Secret custody and platform data services
summary: OpenBao policy/custody, consumer grants, secret delivery and database/backup
contracts.
owner: railiance-platform
status: draft
domain: financials
tags:
- railiance
- platform
- secrets
- postgres
- security
- netkingdom
- framework-reuse
maturity:
discovery:
current: D3
target: D4
confidence: medium
rationale: SCOPE.md places this repo precisely at S3 in the Railiance OAS Stack,
scoped to shared cluster services (PostgreSQL HA, Valkey, secrets, identity
integration, object storage).
availability:
current: A2
target: A3
confidence: medium
rationale: 'Source interface assessed 2026-10-14: OpenBao policy/custody, consumer
grants, secret delivery and database/backup contracts. Availability describes
the delivery form, not production acceptance. Package ownership is split to
rapp repos; caches and object services are demand-led.'
external_evidence:
completeness:
level: C1
confidence: low
basis: scope_vs_intent_and_consumer_expectations
satisfied_expectations:
- OpenBao/Vault secret-management apply/verify scripting
- credential-change tooling
broken_expectations: []
out_of_scope_expectations: []
reliability:
level: R0
confidence: low
basis: consumer_quality_signals
known_reliability_risks:
- no top-level packaging; scripts/tools have no unified install path
discovery:
intent: OpenBao policy/custody, consumer grants, secret delivery and database/backup
contracts
includes:
- OpenBao policy/custody, consumer grants, secret delivery and database/backup contracts
excludes:
- Package ownership is split to rapp repos; caches and object services are demand-led
assumptions: []
use_cases:
- 'U04: Protected operation obtains and consumes exact human approval before its
side effect'
- 'U05: Operator provisions and delivers a scoped workload credential through the
approved owner lane'
- 'U07: Owner inventories, rotates, revokes and detects exposure of credentials'
- 'U10: Operator recovers identity, custody or data with independently held recovery
material'
- 'U13: Platform owner deploys and rolls back a workload with explicit substrate
and custody bindings'
research_memos: []
availability:
current_level: A2
target_level: A3
current_artifacts:
- SCOPE.md
- docs/openbao.md
target_artifacts: []
consumption_modes:
- CLI
- source
relations:
depends_on: []
supports: []
related_to:
- capability.railiance.openbao-package
- capability.railiance.postgres-isolation-recovery
- capability.iam.key-cape
- capability.security.credential-lifecycle
evidence:
documentation:
- SCOPE.md
- docs/openbao.md
tests:
- tests/
consumer_feedback: []
bug_reports: []
incidents: []
consumer_guidance:
recommended_for:
- Protected operation obtains and consumes exact human approval before its side
effect
- Operator provisions and delivers a scoped workload credential through the approved
owner lane
- Owner inventories, rotates, revokes and detects exposure of credentials
- Operator recovers identity, custody or data with independently held recovery material
- Platform owner deploys and rolls back a workload with explicit substrate and custody
bindings
not_recommended_for:
- Package ownership is split to rapp repos; caches and object services are demand-led
known_limitations:
- Package ownership is split to rapp repos; caches and object services are demand-led
- 2026-10-14 architecture review estimates operational maturity separately; a registry
entry does not authorize execution or establish deployment.
promotion_history: []
---
# Secret custody and platform data services
OpenBao policy/custody, consumer grants, secret delivery and database/backup contracts.
## Reuse boundary
Package ownership is split to rapp repos; caches and object services are demand-led.
## Supported use cases
- U04: Protected operation obtains and consumes exact human approval before its side effect
- U05: Operator provisions and delivers a scoped workload credential through the approved owner lane
- U07: Owner inventories, rotates, revokes and detects exposure of credentials
- U10: Operator recovers identity, custody or data with independently held recovery material
- U13: Platform owner deploys and rolls back a workload with explicit substrate and custody bindings
## Evidence and integration
- [SCOPE.md](../../SCOPE.md)
- [docs/openbao.md](../../docs/openbao.md)
Assessment: CUST-WP-0081, 2026-10-14. Relations identify interfaces to compose; they do not certify native integration. Existing external evidence levels are retained where present. New entries use conservative C1/R0 until consumer assessment exists.