railiance-apps/registry/capabilities/capability.railiance.workload-deployment-tooling.md

id	name	summary	owner	status	domain	tags	maturity	external_evidence	discovery	availability	relations	evidence	consumer_guidance	promotion_history
capability.railiance.workload-deployment-tooling	Railiance Application Workload Deployment Tooling	S5 Workloads and Experience Endpoints layer of the Railiance OAS Stack — application Helm releases, Kubernetes workload manifests, deployment guardrails, and smoke-test/check tooling for user-facing services.	railiance-apps	draft	financials	railiance kubernetes helm deployment	discovery availability current target confidence rationale D3 D4 medium SCOPE.md places this repo precisely in the Railiance OAS Stack layering (S5), scoped to application Helm releases, workload manifests, and operator runbooks for user-facing services such as vergabe-teilnahme. current target confidence rationale A2 A3 medium No top-level package manifest, but ships real, runnable tooling under tools/ (build-database-url-secret.sh, check-oci-image.sh, check-sops.sh, forgejo-smoke.sh, inter-hub-smoke.sh, k8s-server-dry-run.sh, smoke-service.sh) plus charts/ and manifests/; has both .gitea and .forgejo CI already.	completeness reliability level confidence basis satisfied_expectations broken_expectations out_of_scope_expectations C1 low scope_vs_intent_and_consumer_expectations Helm charts and Kubernetes manifests for application workloads smoke-test and dry-run check scripts, including a forgejo-smoke.sh already ahead of the platform-wide Forgejo transition level confidence basis known_reliability_risks R1 low consumer_quality_signals no top-level packaging; tooling is a collection of shell scripts under tools/	intent includes excludes assumptions use_cases research_memos Own the S5 layer of the Railiance OAS Stack: deploying and verifying user-facing application workloads via Helm/Kubernetes with guardrails and operator runbooks. application Helm releases and Kubernetes workload manifests deployment guardrails smoke-test and dry-run tooling (including forgejo-smoke.sh) cluster/platform substrate (see railiance-cluster, railiance-platform) CI/CD enablement templates (see railiance-enablement)	current_level target_level current_artifacts target_artifacts consumption_modes A2 A3 Helm charts Kubernetes manifests tools/*.sh smoke and check scripts cli (shell scripts) helm/kubernetes deployment	depends_on supports related_to	documentation tests consumer_feedback bug_reports incidents SCOPE.md tools/forgejo-smoke.sh tools/inter-hub-smoke.sh tools/k8s-server-dry-run.sh	recommended_for not_recommended_for known_limitations operators deploying or verifying Railiance user-facing application workloads needs at the cluster/platform substrate layer (see railiance-cluster, railiance-platform) no unified packaging; tooling is a set of independent shell scripts

Railiance Application Workload Deployment Tooling

Overview

railiance-apps is the S5 Workloads and Experience Endpoints layer of the Railiance OAS Stack: Helm releases, Kubernetes workload manifests, deployment guardrails, and operator runbooks for user-facing services such as vergabe-teilnahme, including a forgejo-smoke.sh check already ahead of the platform-wide Gitea-to-Forgejo transition.

Assessment notes

Discovery

SCOPE.md places this repo precisely in the Railiance OAS Stack layering (S5), scoped to application Helm releases, workload manifests, and operator runbooks for user-facing services such as vergabe-teilnahme.

Availability

No top-level package manifest, but ships real, runnable tooling under tools/ (build-database-url-secret.sh, check-oci-image.sh, check-sops.sh, forgejo-smoke.sh, inter-hub-smoke.sh, k8s-server-dry-run.sh, smoke-service.sh) plus charts/ and manifests/; has both .gitea and .forgejo CI already.

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