coulomb/railiance-apps
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
railiance-apps/registry/capabilities/capability.railiance.workload-deployment-tooling.md
tegwick b7fb7b226f Wave-2 right-sizing and inter-hub removal (RAPPS-WP-0018, CSOC-WP-0017, REUSE-WP-0026) 
- coulomb-social: requests 100m/256Mi -> 15m/176Mi (limits unchanged)
- reuse-surface: main 100m/256Mi -> 5m/64Mi, landing 10m/32Mi -> 5m/16Mi
- vergabe-demo-company: memory request 256Mi -> 512Mi, CPU 60m kept
- inter-hub (retired, CORE-WP-0007): delete chart, values, Make targets,
  smoke script and production deploy workflow; release to be uninstalled

Full renders vs live: resources only, except the vergabe release-unit label
from 64530e1 not yet on its Service and PVCs.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 276069@bnt-lap001
Assistant-Session: 2e192b3d-b3e8-4403-94d4-d55a2c8b476c
2026-10-22 00:03:48 +02:00

3.8 KiB
Raw Blame History

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 Helm/manifests, exact image pins, application runbooks and rollout/rollback. 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
Helm/manifests, exact image pins, application runbooks and rollout/rollback
Helm/manifests, exact image pins, application runbooks and rollout/rollback
Release settings depend on underlying platform and workload owners
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
CLI
source
depends_on supports related_to
capability.security.iam-tooling-suite
documentation tests consumer_feedback bug_reports incidents
SCOPE.md
tools/forgejo-smoke.sh
tools/k8s-server-dry-run.sh
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.

Workload release configuration and guards

Helm/manifests, exact image pins, application runbooks and rollout/rollback.

Reuse boundary

Release settings depend on underlying platform and workload owners.

Supported use cases

  • 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

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.