diff --git a/registry/capabilities/capability.railiance.platform-services.md b/registry/capabilities/capability.railiance.platform-services.md index 905bdbe..f0d04ad 100644 --- a/registry/capabilities/capability.railiance.platform-services.md +++ b/registry/capabilities/capability.railiance.platform-services.md @@ -1,8 +1,8 @@ --- id: capability.railiance.platform-services -name: Railiance Platform Services -summary: 'S3 Platform Services layer of the Railiance OAS Stack — shared cluster services: PostgreSQL - HA, Valkey cache, secret management, identity integration, and object storage.' +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 @@ -11,19 +11,25 @@ tags: - 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). + 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: No top-level package manifest, but ships real scripts/ (OpenBao/Vault apply/verify, credential-change - Python tooling) and tools/; has `.forgejo/` CI already in place. + 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 @@ -41,35 +47,46 @@ external_evidence: known_reliability_risks: - no top-level packaging; scripts/tools have no unified install path discovery: - intent: Own the shared platform services layer (Postgres HA, Valkey, secrets, identity integration, - object storage) that application and enablement layers depend on, without owning the underlying host/cluster - substrate. + intent: OpenBao policy/custody, consumer grants, secret delivery and database/backup + contracts includes: - - PostgreSQL HA and Valkey cache service management - - secret management (OpenBao/Vault) apply/verify tooling - - identity integration and object storage + - OpenBao policy/custody, consumer grants, secret delivery and database/backup contracts excludes: - - host/cluster substrate provisioning (see railiance-infra, railiance-cluster) - - application workload deployment (see railiance-apps) + - Package ownership is split to rapp repos; caches and object services are demand-led assumptions: [] - use_cases: [] + 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: - - scripts/ (OpenBao/Vault, credential-change tooling) - - tools/ + - SCOPE.md + - docs/openbao.md target_artifacts: [] consumption_modes: - - cli (shell/python scripts) + - CLI + - source relations: depends_on: [] supports: [] - related_to: [] + 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: [] @@ -77,46 +94,42 @@ evidence: incidents: [] consumer_guidance: recommended_for: - - Railiance operators managing shared platform services (Postgres, Valkey, secrets, identity, storage) + - 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: - - needs at the host/cluster substrate layer (see railiance-infra/-cluster) or application layer (see - railiance-apps) + - Package ownership is split to rapp repos; caches and object services are demand-led known_limitations: - - no unified top-level packaging across scripts/tools + - 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: [] --- -# Railiance Platform Services +# Secret custody and platform data services -## Overview +OpenBao policy/custody, consumer grants, secret delivery and database/backup contracts. -`railiance-platform` is the S3 Platform Services layer of the Railiance OAS Stack: shared cluster services including PostgreSQL HA, Valkey cache, OpenBao/Vault secret management, identity integration, and object storage, consumed by application and enablement layers above it. +## Reuse boundary -## Assessment notes +Package ownership is split to rapp repos; caches and object services are demand-led. -### Discovery +## Supported use cases -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). +- 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 -### Availability +## Evidence and integration -No top-level package manifest, but ships real scripts/ (OpenBao/Vault apply/verify, credential-change Python tooling) and tools/; has `.forgejo/` CI already in place. +- [SCOPE.md](../../SCOPE.md) +- [docs/openbao.md](../../docs/openbao.md) -### Completeness - -First-pass honest assessment from the REUSE-WP-0017 coverage campaign -(reuse-surface). No external consumer feedback exists yet; levels reflect -scope-vs-intent documentation quality, not internal code quality. - -### Reliability - -No production consumer telemetry exists yet; reliability level is -intentionally conservative pending REUSE-WP-0019 reuse-telemetry evidence. - -## Promotion checklist - -- [x] ID follows `capability..` pattern -- [x] Maturity enums match `specs/CapabilityMaturityStandard.md` -- [x] `external_evidence` is populated separately from `maturity` -- [ ] Relations reference valid capability IDs (none yet) -- [x] Index entry added in `registry/indexes/capabilities.yaml` +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. diff --git a/registry/indexes/capabilities.yaml b/registry/indexes/capabilities.yaml index 3c28091..c0c1c73 100644 --- a/registry/indexes/capabilities.yaml +++ b/registry/indexes/capabilities.yaml @@ -1,20 +1,24 @@ version: 1 -updated: '2026-07-06' +updated: '2026-10-14' domain: helix_forge capabilities: - id: capability.railiance.platform-services - name: Railiance Platform Services - summary: 'S3 Platform Services layer of the Railiance OAS Stack — shared cluster services: PostgreSQL - HA, Valkey cache, secret management, identity integration, and object storage.' - vector: D3 / A2 / C1 / R0 + name: Secret custody and platform data services + summary: OpenBao policy/custody, consumer grants, secret delivery and database/backup + contracts. domain: financials status: draft owner: railiance-platform - path: registry/capabilities/capability.railiance.platform-services.md tags: - railiance - platform - secrets - postgres + - security + - netkingdom + - framework-reuse + vector: D3 / A2 / C1 / R0 + path: registry/capabilities/capability.railiance.platform-services.md consumption_modes: - - cli (shell/python scripts) + - CLI + - source