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	Workload release configuration and guards	Application Helm/manifests, exact image bindings, operator guards and bounded recovery runbooks; Forgejo identity extension remains in progress.	railiance-apps	draft	financials	railiance kubernetes helm deployment security netkingdom framework-reuse	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 Source interface assessed 2026-10-14: Helm/manifests, exact image pins, application runbooks and rollout/rollback. Availability describes the delivery form, not production acceptance. Release settings depend on underlying platform and workload owners.	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 Application Helm/manifests, exact image bindings, operator guards and bounded recovery runbooks; Forgejo identity extension remains in progress. S5 application release configuration, exact image/storage bindings and operator guardrails Current Forgejo deployment surface and reviewed source build tooling App-consistent attended backup and isolated recovery for the bound Vergabe pilot Shared platform/credential authority and application product behavior Unadmitted Forgejo identity-extension runtime and general image/schema downgrade guarantees U12: Developer builds and publishes through controlled source, dependency and runner paths 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 Makefile docs/vergabe-demo-company-binding.md docs/evidence/2026-11-06-vergabe-pilot-closeout.md docs/evidence/2026-11-06-forgejo-owner-continuation.md CLI source	depends_on supports related_to capability.security.iam-tooling-suite capability.railiance.vergabe-attended-recovery	documentation tests consumer_feedback bug_reports incidents id001 tools/forgejo-smoke.sh tools/k8s-server-dry-run.sh docs/evidence/2026-11-06-vergabe-post-restart-user-return.json docs/evidence/2026-11-06-vergabe-attended-backup-complete-return.json	recommended_for not_recommended_for known_limitations Developer builds and publishes through controlled source, dependency and runner paths Platform owner deploys and rolls back a workload with explicit substrate and custody bindings Release settings depend on underlying platform and workload owners Release settings depend on underlying platform and workload owners 2026-10-14 architecture review estimates operational maturity separately; a registry entry does not authorize execution or establish deployment. WP-0014 and WP-0015 release milestones are finished; WP-0016 is active 2/9 and awaits real owner backends, first-case registration and native acceptance. Generic release-tooling maturity is retained; a scoped recovery result does not promote all workloads.

Workload release configuration and guards

Application Helm/manifests, exact image bindings, operator guards and bounded recovery runbooks; Forgejo identity extension remains in progress.

Reuse boundary

Read SCOPE.md for current ownership and explicit limits. The June forge split is historical; the current Apps release declaration and Makefile carry deployment configuration, while forge operating contracts retain their declared owner. This entry grants no deployment or credential authority.

Current evidence — 2026-11-06

WP-0014 is finished (4/4), including two-user/restart acceptance and the first repeatable attended three-store provider/recovery run. WP-0015 is finished (9/9) with personal workspace and paired recovery acceptance. WP-0016 remains active (2/9): source candidates and break-glass do not prove native OIDC admission. The owner continuation corrects the stale review blocker and names the real remaining backends.

The broad D3/A2/C1/R1 assessment is retained; the narrower recovery entry carries its own bounded evidence and maturity. No unrelated release is promoted.