docs(reuse): establish reviewed NetKingdom security capabilities
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
CI Smoke / container-smoke (push) Successful in 1s

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a137ca-5c77-7a71-b9ae-23ad9b0b5684
This commit is contained in:
tegwick 2026-10-14 06:41:38 +02:00
parent 706461b845
commit 72bcad86d7
2 changed files with 55 additions and 63 deletions

View file

@ -1,8 +1,7 @@
---
id: capability.railiance.workload-deployment-tooling
name: Railiance Application Workload Deployment Tooling
summary: 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.
name: Workload release configuration and guards
summary: Helm/manifests, exact image pins, application runbooks and rollout/rollback.
owner: railiance-apps
status: draft
domain: financials
@ -11,21 +10,25 @@ tags:
- kubernetes
- helm
- deployment
- security
- netkingdom
- framework-reuse
maturity:
discovery:
current: D3
target: D4
confidence: medium
rationale: 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.
rationale: 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:
current: A2
target: A3
confidence: medium
rationale: 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.
rationale: '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.'
external_evidence:
completeness:
level: C1
@ -33,8 +36,8 @@ external_evidence:
basis: scope_vs_intent_and_consumer_expectations
satisfied_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
- smoke-test and dry-run check scripts, including a forgejo-smoke.sh already ahead
of the platform-wide Forgejo transition
broken_expectations: []
out_of_scope_expectations: []
reliability:
@ -44,33 +47,32 @@ external_evidence:
known_reliability_risks:
- no top-level packaging; tooling is a collection of shell scripts under tools/
discovery:
intent: 'Own the S5 layer of the Railiance OAS Stack: deploying and verifying user-facing application
workloads via Helm/Kubernetes with guardrails and operator runbooks.'
intent: Helm/manifests, exact image pins, application runbooks and rollout/rollback
includes:
- application Helm releases and Kubernetes workload manifests
- deployment guardrails
- smoke-test and dry-run tooling (including forgejo-smoke.sh)
- Helm/manifests, exact image pins, application runbooks and rollout/rollback
excludes:
- cluster/platform substrate (see railiance-cluster, railiance-platform)
- CI/CD enablement templates (see railiance-enablement)
- Release settings depend on underlying platform and workload owners
assumptions: []
use_cases: []
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'
research_memos: []
availability:
current_level: A2
target_level: A3
current_artifacts:
- Helm charts
- Kubernetes manifests
- tools/*.sh smoke and check scripts
- SCOPE.md
target_artifacts: []
consumption_modes:
- cli (shell scripts)
- helm/kubernetes deployment
- CLI
- source
relations:
depends_on: []
supports: []
related_to: []
related_to:
- capability.security.iam-tooling-suite
evidence:
documentation:
- SCOPE.md
@ -83,45 +85,34 @@ evidence:
incidents: []
consumer_guidance:
recommended_for:
- operators deploying or verifying Railiance user-facing application workloads
- 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
not_recommended_for:
- needs at the cluster/platform substrate layer (see railiance-cluster, railiance-platform)
- Release settings depend on underlying platform and workload owners
known_limitations:
- no unified packaging; tooling is a set of independent shell scripts
- 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.
promotion_history: []
---
# Railiance Application Workload Deployment Tooling
# Workload release configuration and guards
## Overview
Helm/manifests, exact image pins, application runbooks and rollout/rollback.
`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.
## Reuse boundary
## Assessment notes
Release settings depend on underlying platform and workload owners.
### Discovery
## Supported use cases
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.
- 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
### Availability
## Evidence and integration
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.
- [SCOPE.md](../../SCOPE.md)
### 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
- [x] ID follows `capability.<domain>.<name>` pattern
- [x] Maturity enums match `specs/CapabilityMaturityStandard.md`
- [x] `external_evidence` is populated separately from `maturity`
- [ ] Relations reference valid capability IDs (none yet)
- [x] Index entry added in `registry/indexes/capabilities.yaml`
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.

View file

@ -1,22 +1,23 @@
version: 1
updated: '2026-07-06'
updated: '2026-10-14'
domain: helix_forge
capabilities:
- id: capability.railiance.workload-deployment-tooling
name: Railiance Application Workload Deployment Tooling
summary: 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.
vector: D3 / A2 / C1 / R1
name: Workload release configuration and guards
summary: Helm/manifests, exact image pins, application runbooks and rollout/rollback.
domain: financials
status: draft
owner: railiance-apps
path: registry/capabilities/capability.railiance.workload-deployment-tooling.md
tags:
- railiance
- kubernetes
- helm
- deployment
- security
- netkingdom
- framework-reuse
vector: D3 / A2 / C1 / R1
path: registry/capabilities/capability.railiance.workload-deployment-tooling.md
consumption_modes:
- cli (shell scripts)
- helm/kubernetes deployment
- CLI
- source