railiance-infra/registry/capabilities/capability.railiance.infra-provisioning.md

id	name	summary	owner	status	domain	tags	maturity	external_evidence	discovery	availability	relations	evidence	consumer_guidance	promotion_history
capability.railiance.infra-provisioning	RailianceHosts Infrastructure Provisioning	Git-driven server provisioning and convergence for Hosteurope/Hetzner Cloud using Terraform, cloud-init, and Ansible, with SOPS+age encrypted in-repo secrets and a servers.yaml inventory as source of truth.	railiance-infra	draft	financials	railiance terraform ansible infrastructure	discovery availability current target confidence rationale D4 D5 high README documents a complete, concrete quickstart (clone, prerequisites, SOPS/age secrets setup, provider setup, terraform apply, ansible convergence) with a specific inventory file (`inventory/servers.yaml`) as source of truth — an unusually complete operational README among the swept repos. current target confidence rationale A2 A3 high Real ansible playbooks, terraform config, and scripts/tools present; has `.forgejo/` CI already; documented as the S1 Infrastructure Substrate layer of the Railiance OAS Stack.	completeness reliability level confidence basis satisfied_expectations broken_expectations out_of_scope_expectations C2 low scope_vs_intent_and_consumer_expectations documented end-to-end quickstart from bare cloud account to converged servers SOPS+age encrypted secrets with a documented key-custody model inventory/servers.yaml as explicit source of truth level confidence basis known_reliability_risks R1 low consumer_quality_signals reproducibility not independently re-verified via a live provisioning run in this sweep	intent includes excludes assumptions use_cases research_memos Provision and manage servers on Hosteurope/Hetzner Cloud entirely from Git — Terraform for lifecycle, cloud-init for first boot, Ansible for convergence — as the S1 Infrastructure Substrate of the Railiance OAS Stack. Terraform server lifecycle management cloud-init first-boot configuration Ansible convergence playbooks SOPS+age encrypted secrets in-repo Kubernetes cluster bootstrap on top of provisioned hosts (see railiance-cluster) platform services (see railiance-platform)	current_level target_level current_artifacts target_artifacts consumption_modes A2 A3 Terraform configs Ansible playbooks scripts/ tools/ cli (terraform/ansible) gitops	depends_on supports related_to	documentation tests consumer_feedback bug_reports incidents README.md SCOPE.md sbom-tools.yaml .forgejo/	recommended_for not_recommended_for known_limitations operators provisioning Railiance bare-metal/cloud hosts from Git with encrypted-secret custody needs above the OS/host substrate layer (see railiance-cluster for Kubernetes, railiance-platform for shared services) reproducibility not independently re-verified via a live provisioning run in this sweep

RailianceHosts Infrastructure Provisioning

Overview

railiance-infra (RailianceHosts) is Git-driven automation for provisioning and converging servers on Hosteurope and Hetzner Cloud — Terraform for lifecycle, cloud-init for first boot, Ansible for convergence — with secrets encrypted in-repo via SOPS/age and inventory/servers.yaml as the source of truth. It is the S1 Infrastructure Substrate layer of the Railiance OAS Stack.

Assessment notes

Discovery

README documents a complete, concrete quickstart (clone, prerequisites, SOPS/age secrets setup, provider setup, terraform apply, ansible convergence) with a specific inventory file (inventory/servers.yaml) as source of truth — an unusually complete operational README among the swept repos.

Availability

Real ansible playbooks, terraform config, and scripts/tools present; has .forgejo/ CI already; documented as the S1 Infrastructure Substrate layer of the Railiance OAS Stack.

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