railiance-forge/registry/capabilities/capability.railiance.forge-infrastructure.md

id	name	summary	owner	status	domain	tags	maturity	external_evidence	discovery	availability	relations	evidence	consumer_guidance	promotion_history
capability.railiance.forge-infrastructure	Source forge, registries and runner substrate	Forgejo operation, package registries and runner lifecycle.	railiance-forge	draft	financials	railiance forgejo forge ci-runner security netkingdom framework-reuse	discovery availability current target confidence rationale D3 D5 medium 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. current target confidence rationale A2 A3 medium 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.	completeness reliability level confidence basis satisfied_expectations broken_expectations out_of_scope_expectations C1 low scope_vs_intent_and_consumer_expectations scope separation from railiance-apps/railiance-enablement documented canonical registry operation docs and runner ownership contracts level confidence basis known_reliability_risks R0 low consumer_quality_signals 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	intent includes excludes assumptions use_cases research_memos Forgejo operation, package registries and runner lifecycle Forgejo operation, package registries and runner lifecycle Runner workload authority and independent verification coverage remain open U12: Developer builds and publishes through controlled source, dependency and runner paths	current_level target_level current_artifacts target_artifacts consumption_modes A2 A3 SCOPE.md workplans/FORGE-WP-0006-independent-secret-detection.md CLI source	depends_on supports related_to capability.security.repository-secret-prevention capability.railiance.ci-enablement capability.railiance.workload-deployment-tooling	documentation tests consumer_feedback bug_reports incidents SCOPE.md workplans/FORGE-WP-0006-independent-secret-detection.md	recommended_for not_recommended_for known_limitations Developer builds and publishes through controlled source, dependency and runner paths Runner workload authority and independent verification coverage remain open 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.	date dimension from to rationale author 2026-10-14 availability A1 A2 Interface-form reassessment from current owner sources; no completeness/reliability promotion. 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
• 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.