docs(reuse): establish reviewed NetKingdom security capabilities
Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a137ca-5c77-7a71-b9ae-23ad9b0b5684
This commit is contained in:
parent
51a7c4cee6
commit
ce9f6d1be8
2 changed files with 56 additions and 64 deletions
|
|
@ -1,9 +1,7 @@
|
|||
---
|
||||
id: capability.railiance.ci-enablement
|
||||
name: Railiance Developer Enablement And CI/CD Templates
|
||||
summary: S4 Developer Enablement layer of the Railiance OAS Stack — reusable CI/CD workflow templates,
|
||||
developer portal paths, platform templates, SDKs, and buildpacks, using forge capabilities without owning
|
||||
forge runtime.
|
||||
name: Developer delivery and CI templates
|
||||
summary: Reusable CI workflows, build and deployment patterns.
|
||||
owner: railiance-enablement
|
||||
status: draft
|
||||
domain: financials
|
||||
|
|
@ -12,20 +10,24 @@ tags:
|
|||
- ci-cd
|
||||
- developer-enablement
|
||||
- forgejo
|
||||
- security
|
||||
- netkingdom
|
||||
- framework-reuse
|
||||
maturity:
|
||||
discovery:
|
||||
current: D3
|
||||
target: D4
|
||||
confidence: medium
|
||||
rationale: SCOPE.md places this repo precisely at S4 in the Railiance OAS Stack, explicitly scoped
|
||||
to reusable CI/CD templates and enablement tooling while using (not owning) forge capabilities.
|
||||
rationale: SCOPE.md places this repo precisely at S4 in the Railiance OAS Stack,
|
||||
explicitly scoped to reusable CI/CD templates and enablement tooling while using
|
||||
(not owning) forge capabilities.
|
||||
availability:
|
||||
current: A2
|
||||
target: A3
|
||||
confidence: high
|
||||
rationale: Ships real, reusable Forgejo Actions workflow templates (container-build-push.yaml, container-build-push-multirepo.yaml,
|
||||
ci-smoke.yaml) plus `tools/promote-repo-to-forgejo.sh` — directly relevant tooling for the ecosystem-wide
|
||||
Gitea-to-Forgejo transition (REUSE-WP-0019).
|
||||
rationale: 'Source interface assessed 2026-10-14: Reusable CI workflows, build
|
||||
and deployment patterns. Availability describes the delivery form, not production
|
||||
acceptance. Templates do not prove mandatory checks or runner isolation.'
|
||||
external_evidence:
|
||||
completeness:
|
||||
level: C2
|
||||
|
|
@ -33,7 +35,8 @@ external_evidence:
|
|||
basis: scope_vs_intent_and_consumer_expectations
|
||||
satisfied_expectations:
|
||||
- reusable Forgejo Actions CI/CD workflow templates already in production shape
|
||||
- a repo-promotion-to-forgejo script directly usable for the platform-wide forge transition
|
||||
- a repo-promotion-to-forgejo script directly usable for the platform-wide forge
|
||||
transition
|
||||
broken_expectations: []
|
||||
out_of_scope_expectations: []
|
||||
reliability:
|
||||
|
|
@ -41,35 +44,35 @@ external_evidence:
|
|||
confidence: low
|
||||
basis: consumer_quality_signals
|
||||
known_reliability_risks:
|
||||
- templates are workflow YAML, not a packaged/versioned artifact; consumption is copy/reference rather
|
||||
than dependency-managed
|
||||
- templates are workflow YAML, not a packaged/versioned artifact; consumption
|
||||
is copy/reference rather than dependency-managed
|
||||
discovery:
|
||||
intent: Give Railiance repos reusable CI/CD templates and developer-enablement tooling (including forge-promotion
|
||||
tooling) without each repo owning the forge runtime or runner substrate itself.
|
||||
intent: Reusable CI workflows, build and deployment patterns
|
||||
includes:
|
||||
- reusable Forgejo Actions CI/CD workflow templates
|
||||
- repo-to-forgejo promotion tooling
|
||||
- developer portal/platform template scope (per SCOPE.md)
|
||||
- Reusable CI workflows, build and deployment patterns
|
||||
excludes:
|
||||
- forge runtime and runner substrate ownership (see railiance-forge)
|
||||
- Templates do not prove mandatory checks or runner isolation
|
||||
assumptions: []
|
||||
use_cases: []
|
||||
use_cases:
|
||||
- 'U12: Developer builds and publishes through controlled source, dependency and
|
||||
runner paths'
|
||||
- 'U14: Framework adopter validates and reuses selected contracts, tools and reference
|
||||
compositions'
|
||||
research_memos: []
|
||||
availability:
|
||||
current_level: A2
|
||||
target_level: A3
|
||||
current_artifacts:
|
||||
- workflows/container-build-push.yaml
|
||||
- workflows/ci-smoke.yaml
|
||||
- tools/promote-repo-to-forgejo.sh
|
||||
- SCOPE.md
|
||||
target_artifacts: []
|
||||
consumption_modes:
|
||||
- ci workflow template (copy/reference)
|
||||
- cli (promote-repo-to-forgejo.sh)
|
||||
- CLI
|
||||
- source
|
||||
relations:
|
||||
depends_on: []
|
||||
supports: []
|
||||
related_to: []
|
||||
related_to:
|
||||
- capability.security.iam-tooling-suite
|
||||
evidence:
|
||||
documentation:
|
||||
- SCOPE.md
|
||||
|
|
@ -80,46 +83,34 @@ evidence:
|
|||
incidents: []
|
||||
consumer_guidance:
|
||||
recommended_for:
|
||||
- Railiance repos needing reusable Forgejo Actions CI/CD templates, or any repo executing a Gitea-to-Forgejo
|
||||
promotion
|
||||
- Developer builds and publishes through controlled source, dependency and runner
|
||||
paths
|
||||
- Framework adopter validates and reuses selected contracts, tools and reference
|
||||
compositions
|
||||
not_recommended_for:
|
||||
- needs for owning forge runtime/runner infrastructure itself (see railiance-forge)
|
||||
- Templates do not prove mandatory checks or runner isolation
|
||||
known_limitations:
|
||||
- templates are consumed by copy/reference, not as a versioned dependency
|
||||
- Templates do not prove mandatory checks or runner isolation
|
||||
- 2026-10-14 architecture review estimates operational maturity separately; a registry
|
||||
entry does not authorize execution or establish deployment.
|
||||
promotion_history: []
|
||||
---
|
||||
|
||||
# Railiance Developer Enablement And CI/CD Templates
|
||||
# Developer delivery and CI templates
|
||||
|
||||
## Overview
|
||||
Reusable CI workflows, build and deployment patterns.
|
||||
|
||||
`railiance-enablement` is the S4 Developer Enablement layer of the Railiance OAS Stack: reusable CI/CD workflow templates and developer-enablement tooling, including a `promote-repo-to-forgejo.sh` script directly relevant to the ecosystem-wide Gitea-to-Forgejo transition tracked in REUSE-WP-0019.
|
||||
## Reuse boundary
|
||||
|
||||
## Assessment notes
|
||||
Templates do not prove mandatory checks or runner isolation.
|
||||
|
||||
### Discovery
|
||||
## Supported use cases
|
||||
|
||||
SCOPE.md places this repo precisely at S4 in the Railiance OAS Stack, explicitly scoped to reusable CI/CD templates and enablement tooling while using (not owning) forge capabilities.
|
||||
- U12: Developer builds and publishes through controlled source, dependency and runner paths
|
||||
- U14: Framework adopter validates and reuses selected contracts, tools and reference compositions
|
||||
|
||||
### Availability
|
||||
## Evidence and integration
|
||||
|
||||
Ships real, reusable Forgejo Actions workflow templates (container-build-push.yaml, container-build-push-multirepo.yaml, ci-smoke.yaml) plus `tools/promote-repo-to-forgejo.sh` — directly relevant tooling for the ecosystem-wide Gitea-to-Forgejo transition (REUSE-WP-0019).
|
||||
- [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.
|
||||
|
|
|
|||
|
|
@ -1,22 +1,23 @@
|
|||
version: 1
|
||||
updated: '2026-07-06'
|
||||
updated: '2026-10-14'
|
||||
domain: helix_forge
|
||||
capabilities:
|
||||
- id: capability.railiance.ci-enablement
|
||||
name: Railiance Developer Enablement And CI/CD Templates
|
||||
summary: S4 Developer Enablement layer of the Railiance OAS Stack — reusable CI/CD workflow templates,
|
||||
developer portal paths, platform templates, SDKs, and buildpacks, using forge capabilities without
|
||||
owning forge runtime.
|
||||
vector: D3 / A2 / C2 / R1
|
||||
name: Developer delivery and CI templates
|
||||
summary: Reusable CI workflows, build and deployment patterns.
|
||||
domain: financials
|
||||
status: draft
|
||||
owner: railiance-enablement
|
||||
path: registry/capabilities/capability.railiance.ci-enablement.md
|
||||
tags:
|
||||
- railiance
|
||||
- ci-cd
|
||||
- developer-enablement
|
||||
- forgejo
|
||||
- security
|
||||
- netkingdom
|
||||
- framework-reuse
|
||||
vector: D3 / A2 / C2 / R1
|
||||
path: registry/capabilities/capability.railiance.ci-enablement.md
|
||||
consumption_modes:
|
||||
- ci workflow template (copy/reference)
|
||||
- cli (promote-repo-to-forgejo.sh)
|
||||
- CLI
|
||||
- source
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue