railiance-forge/registry/capabilities/capability.railiance.forge-infrastructure.md
tegwick 6e8f657e55
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 2s
docs(reuse): establish reviewed NetKingdom security capabilities
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a137ca-5c77-7a71-b9ae-23ad9b0b5684
2026-10-14 06:42:15 +02:00

124 lines
4.1 KiB
Markdown

---
id: capability.railiance.forge-infrastructure
name: Source forge, registries and runner substrate
summary: Forgejo operation, package registries and runner lifecycle.
owner: railiance-forge
status: draft
domain: financials
tags:
- railiance
- forgejo
- forge
- ci-runner
- security
- netkingdom
- framework-reuse
maturity:
discovery:
current: D3
target: D5
confidence: medium
rationale: README and SCOPE.md explicitly name 'current Gitea operation, future
Forgejo migration, container and package registries, Actions runner substrate,
artifact lifecycle' as the scope; status noted as 'active forge extraction'
with canonical registry operation docs already landed.
availability:
current: A2
target: A3
confidence: medium
rationale: 'Source interface assessed 2026-10-14: Forgejo operation, package registries
and runner lifecycle. Availability describes the delivery form, not production
acceptance. Runner workload authority and independent verification coverage
remain open.'
external_evidence:
completeness:
level: C1
confidence: low
basis: scope_vs_intent_and_consumer_expectations
satisfied_expectations:
- scope separation from railiance-apps/railiance-enablement documented
- canonical registry operation docs and runner ownership contracts
broken_expectations: []
out_of_scope_expectations: []
reliability:
level: R0
confidence: low
basis: consumer_quality_signals
known_reliability_risks:
- repo is actively being founded/extracted; no live deploy yet by its own account
- directly relevant to REUSE-WP-0019 but hasn't migrated its own CI to .forgejo/
yet
discovery:
intent: Forgejo operation, package registries and runner lifecycle
includes:
- Forgejo operation, package registries and runner lifecycle
excludes:
- Runner workload authority and independent verification coverage remain open
assumptions: []
use_cases:
- 'U12: Developer builds and publishes through controlled source, dependency and
runner paths'
research_memos: []
availability:
current_level: A2
target_level: A3
current_artifacts:
- SCOPE.md
- workplans/FORGE-WP-0006-independent-secret-detection.md
target_artifacts: []
consumption_modes:
- CLI
- source
relations:
depends_on: []
supports: []
related_to:
- capability.security.repository-secret-prevention
- capability.railiance.ci-enablement
- capability.railiance.workload-deployment-tooling
evidence:
documentation:
- SCOPE.md
- workplans/FORGE-WP-0006-independent-secret-detection.md
tests: []
consumer_feedback: []
bug_reports: []
incidents: []
consumer_guidance:
recommended_for:
- Developer builds and publishes through controlled source, dependency and runner
paths
not_recommended_for:
- Runner workload authority and independent verification coverage remain open
known_limitations:
- Runner workload authority and independent verification coverage remain open
- 2026-10-14 architecture review estimates operational maturity separately; a registry
entry does not authorize execution or establish deployment.
promotion_history:
- date: '2026-10-14'
dimension: availability
from: A1
to: A2
rationale: Interface-form reassessment from current owner sources; no completeness/reliability
promotion.
author: codex
---
# Source forge, registries and runner substrate
Forgejo operation, package registries and runner lifecycle.
## Reuse boundary
Runner workload authority and independent verification coverage remain open.
## Supported use cases
- U12: Developer builds and publishes through controlled source, dependency and runner paths
## Evidence and integration
- [SCOPE.md](../../SCOPE.md)
- [workplans/FORGE-WP-0006-independent-secret-detection.md](../../workplans/FORGE-WP-0006-independent-secret-detection.md)
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.