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

id	name	summary	owner	status	domain	tags	maturity	external_evidence	discovery	availability	relations	evidence	consumer_guidance	promotion_history
capability.railiance.forge-infrastructure	Railiance Forge And Artifact Infrastructure	Source forge, registry, and automation-runner infrastructure for Railiance, separated out from railiance-apps/railiance-enablement; covers current Gitea operation, the Forgejo migration, container/package registries, and Actions runner substrate.	railiance-forge	draft	financials	railiance forgejo forge ci-runner	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 A1 A3 medium README explicitly states 'no live Helm deploy or Kubernetes apply was run as part of the move' — documentation and operator targets exist, but this repo is mid-extraction; has .gitea CI (not yet migrated to .forgejo itself, notably, despite owning the migration).	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 Own source forge, artifact registry, and CI runner substrate responsibilities for Railiance, separated from application (railiance-apps) and enablement (railiance-enablement) concerns, across the Gitea-to-Forgejo transition. forge operation (current Gitea, migrating to Forgejo) container/package registries Actions runner substrate artifact lifecycle application workload deployment (railiance-apps) CI/CD templates for consuming repos (railiance-enablement)	current_level target_level current_artifacts target_artifacts consumption_modes A1 A3 operator docs and tools/ (extraction in progress) cli (operator tooling) documentation/runbooks	depends_on supports related_to	documentation tests consumer_feedback bug_reports incidents README.md SCOPE.md	recommended_for not_recommended_for known_limitations Railiance operators managing forge/registry/runner infrastructure, especially during the Gitea-to-Forgejo transition treating this as production-stable — the repo's own README states the extraction is active and no live deploy has run yet actively being founded; no live Helm/k8s deploy has run as part of the extraction yet; own CI still under .gitea/ pending its own Forgejo migration

Railiance Forge And Artifact Infrastructure

Overview

railiance-forge is being founded to separate source forge, artifact registry, and CI/Actions runner responsibilities from railiance-apps and railiance-enablement. It directly owns the current Gitea operation and the future Forgejo migration — of particular relevance to REUSE-WP-0019 — though by its own account no live deploy has run yet.

Assessment notes

Discovery

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

README explicitly states 'no live Helm deploy or Kubernetes apply was run as part of the move' — documentation and operator targets exist, but this repo is mid-extraction; has .gitea CI (not yet migrated to .forgejo itself, notably, despite owning the migration).

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

• ID follows capability.<domain>.<name> pattern
• Maturity enums match specs/CapabilityMaturityStandard.md
• external_evidence is populated separately from maturity
• Relations reference valid capability IDs (none yet)
• Index entry added in registry/indexes/capabilities.yaml