railiance-cluster/registry/capabilities/capability.railiance.cluster-bootstrap.md
tegwick cb74114358
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:53 +02:00

4.2 KiB

id name summary owner status domain tags maturity external_evidence discovery availability relations evidence consumer_guidance promotion_history
capability.railiance.cluster-bootstrap Railiance Cluster Runtime Bootstrap Cluster runtime entry point of the Railiance Infrastructure-as-Code framework: from two bare Linux servers, a Git repo, and credentials, rebuilds a fully automated Kubernetes-based environment. railiance-cluster draft financials
railiance
kubernetes
iac
bootstrap
discovery availability
current target confidence rationale
D3 D4 medium README documents the 'Rails for Ops' convention-over-configuration philosophy and a concrete quick-start (clone, from two bare servers rebuild a full k8s environment); has .forgejo CI already in place.
current target confidence rationale
A2 A3 medium Real Python package (pyproject, requires-python >=3.11) plus bin/railiance CLI and ansible playbooks (bootstrap/harden), with a documented quick-start path.
completeness reliability
level confidence basis satisfied_expectations broken_expectations out_of_scope_expectations
C1 low scope_vs_intent_and_consumer_expectations
documented quick-start from two bare servers to a running Kubernetes environment
bootstrap/harden ansible playbooks
level confidence basis known_reliability_risks
R0 low consumer_quality_signals
reproducibility claims not independently re-verified (no live bootstrap run during this sweep)
intent includes excludes assumptions use_cases research_memos
Provide the cluster runtime entry point for Railiance: reproducible, self-reliant Kubernetes environment bootstrap from bare servers via convention-over-configuration IaC.
cluster bootstrap CLI and ansible playbooks (bootstrap/harden)
Kubernetes-based environment rebuild path
application workload deployment (see railiance-apps)
platform services like Postgres/Valkey (see railiance-platform)
current_level target_level current_artifacts target_artifacts consumption_modes
A2 A3
`railiance` CLI (bin/railiance)
ansible playbooks
cli
ansible playbook
depends_on supports related_to
documentation tests consumer_feedback bug_reports incidents
README.md
tests/
.forgejo/
recommended_for not_recommended_for known_limitations
operators bootstrapping a new Railiance Kubernetes cluster from bare servers
application-level or platform-service deployment (see railiance-apps, railiance-platform)
reproducibility not independently re-verified via a live bootstrap run in this sweep

Railiance Cluster Runtime Bootstrap

Overview

railiance-cluster is the cluster runtime entry point of the Railiance Infrastructure-as-Code framework: from two bare Linux servers, a Git repo, and credentials, it rebuilds a fully automated Kubernetes-based environment via convention-over-configuration IaC (Terraform/cloud-init/Ansible-adjacent tooling, railiance CLI).

Assessment notes

Discovery

README documents the 'Rails for Ops' convention-over-configuration philosophy and a concrete quick-start (clone, from two bare servers rebuild a full k8s environment); has .forgejo CI already in place.

Availability

Real Python package (pyproject, requires-python >=3.11) plus bin/railiance CLI and ansible playbooks (bootstrap/harden), with a documented quick-start path.

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