coulomb/railiance-cluster
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
railiance-cluster/registry/capabilities/capability.railiance.cluster-bootstrap.md
codex 750c3e5b9b
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
Details
CI Smoke / container-smoke (push) Successful in 2s
Details
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:41:51 +02:00

3.7 KiB
Raw Blame History

id name summary owner status domain tags maturity external_evidence discovery availability relations evidence consumer_guidance promotion_history
capability.railiance.cluster-bootstrap Kubernetes runtime and cluster controls k3s, ingress, CNI, operators and kubeconfig/runtime checks. railiance-cluster draft financials
railiance
kubernetes
iac
bootstrap
security
netkingdom
framework-reuse
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 Source interface assessed 2026-10-14: k3s, ingress, CNI, operators and kubeconfig/runtime checks. Availability describes the delivery form, not production acceptance. Single-node runtime and workload recovery are distinct from bootstrap success.
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
k3s, ingress, CNI, operators and kubeconfig/runtime checks
k3s, ingress, CNI, operators and kubeconfig/runtime checks
Single-node runtime and workload recovery are distinct from bootstrap success
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
current_level target_level current_artifacts target_artifacts consumption_modes
A2 A3
SCOPE.md
CLI
source
depends_on supports related_to
capability.security.iam-tooling-suite
documentation tests consumer_feedback bug_reports incidents
SCOPE.md
tests/
.forgejo/
recommended_for not_recommended_for known_limitations
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
Single-node runtime and workload recovery are distinct from bootstrap success
Single-node runtime and workload recovery are distinct from bootstrap success
2026-10-14 architecture review estimates operational maturity separately; a registry entry does not authorize execution or establish deployment.

Kubernetes runtime and cluster controls

k3s, ingress, CNI, operators and kubeconfig/runtime checks.

Reuse boundary

Single-node runtime and workload recovery are distinct from bootstrap success.

Supported use cases

  • 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

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.