# Forge Source Of Truth Decision

Date: 2026-06-05

## Decision

`railiance-forge` is the source of truth for current Gitea operation, future
Forgejo migration, forge runtime deployment, source hosting, container and
Python package registries, Actions runner substrate, artifact retention, and
forge operating evidence.

`railiance-apps` consumes those forge capabilities only as release
infrastructure for S5 application workloads. It does not keep Gitea
deploy/status wrappers, forge SOPS sentinels, registry-retention procedures, or
local compatibility copies of forge registry docs.

## Rationale

The forge layer is cross-cutting infrastructure for source control, packages,
images, runners, and promotion evidence. Keeping it in S5 made app release
runbooks responsible for non-app runtime state. The dedicated forge repo gives
operators one place to change forge runtime behavior while allowing S5 app
runbooks to cite forge evidence and consume published artifacts.

## Consequences

- Forge runtime changes start in `/home/worsch/railiance-forge`.
- S5 app release work links to forge docs instead of duplicating registry or
  runner operating procedures.
- App-specific charts, values, manifests, smoke tests, and runbooks remain in
  `/home/worsch/railiance-apps`.
- Source repos still own application code, package metadata, package publishing,
  image build definitions, and lock regeneration.