railiance-platform/registry/capabilities/capability.railiance.platform-services.md
tegwick 7c598c2715
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
Draft capability entry (reuse-surface REUSE-WP-0017-T04, cohort 3)
Honest first-pass maturity vector grounded in README/docs/tests present
in this repo; no invented evidence. Flagged for human review before
publish. See reuse-surface history/2026-07-06-coverage-classification.md.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-06 19:50:54 +02:00

4.1 KiB

id name summary owner status domain tags maturity external_evidence discovery availability relations evidence consumer_guidance promotion_history
capability.railiance.platform-services Railiance Platform Services S3 Platform Services layer of the Railiance OAS Stack — shared cluster services: PostgreSQL HA, Valkey cache, secret management, identity integration, and object storage. railiance-platform draft financials
railiance
platform
secrets
postgres
discovery availability
current target confidence rationale
D3 D4 medium 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).
current target confidence rationale
A2 A3 medium 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.
completeness reliability
level confidence basis satisfied_expectations broken_expectations out_of_scope_expectations
C1 low scope_vs_intent_and_consumer_expectations
OpenBao/Vault secret-management apply/verify scripting
credential-change tooling
level confidence basis known_reliability_risks
R0 low consumer_quality_signals
no top-level packaging; scripts/tools have no unified install path
intent includes excludes assumptions use_cases research_memos
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.
PostgreSQL HA and Valkey cache service management
secret management (OpenBao/Vault) apply/verify tooling
identity integration and object storage
host/cluster substrate provisioning (see railiance-infra, railiance-cluster)
application workload deployment (see railiance-apps)
current_level target_level current_artifacts target_artifacts consumption_modes
A2 A3
scripts/ (OpenBao/Vault, credential-change tooling)
tools/
cli (shell/python scripts)
depends_on supports related_to
documentation tests consumer_feedback bug_reports incidents
SCOPE.md
tests/
recommended_for not_recommended_for known_limitations
Railiance operators managing shared platform services (Postgres, Valkey, secrets, identity, storage)
needs at the host/cluster substrate layer (see railiance-infra/-cluster) or application layer (see railiance-apps)
no unified top-level packaging across scripts/tools

Railiance Platform Services

Overview

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.

Assessment notes

Discovery

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

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.

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

  • ID follows capability.<domain>.<name> pattern
  • Maturity enums match specs/CapabilityMaturityStandard.md
  • external_evidence is populated separately from maturity
  • Relations reference valid capability IDs (none yet)
  • Index entry added in registry/indexes/capabilities.yaml