---
id: capability.railiance.forge-infrastructure
name: Railiance Forge And Artifact Infrastructure
summary: 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.
owner: railiance-forge
status: draft
domain: financials
tags:
- railiance
- forgejo
- forge
- ci-runner
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: A1
    target: A3
    confidence: medium
    rationale: 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).
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: 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.
  includes:
  - forge operation (current Gitea, migrating to Forgejo)
  - container/package registries
  - Actions runner substrate
  - artifact lifecycle
  excludes:
  - application workload deployment (railiance-apps)
  - CI/CD templates for consuming repos (railiance-enablement)
  assumptions: []
  use_cases: []
  research_memos: []
availability:
  current_level: A1
  target_level: A3
  current_artifacts:
  - operator docs and tools/ (extraction in progress)
  target_artifacts: []
  consumption_modes:
  - cli (operator tooling)
  - documentation/runbooks
relations:
  depends_on: []
  supports: []
  related_to: []
evidence:
  documentation:
  - README.md
  - SCOPE.md
  tests: []
  consumer_feedback: []
  bug_reports: []
  incidents: []
consumer_guidance:
  recommended_for:
  - Railiance operators managing forge/registry/runner infrastructure, especially during the Gitea-to-Forgejo
    transition
  not_recommended_for:
  - treating this as production-stable — the repo's own README states the extraction is active and no
    live deploy has run yet
  known_limitations:
  - 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
promotion_history: []
---

# 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

- [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`