generated from coulomb/repo-seed
tegwick
36a3030f78
Registration guidance now prescribes file-first + fix-consistency (C-06) instead of manual create_workplan/create_workstream calls; progress-event examples use workplan_id; legacy field names annotated. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
railiance-forge
Railiance forge and artifact infrastructure.
This repository is being founded to separate source forge, registry, and
automation runner responsibilities from railiance-apps and
railiance-enablement.
Start with:
INTENT.mdSCOPE.mdAGENTS.mddocs/workplans/
Current implementation status: active forge extraction. Canonical registry operation docs, runner ownership contracts, deploy-capable Gitea files, and operator targets live here now. No live Helm deploy or Kubernetes apply was run as part of the move.
Key contracts:
docs/initial-operating-contracts.mddocs/ci-runner-actions-gitops-ownership.mddocs/gitea-actions-runner-substrate.mddocs/gitea-actions-runner-evidence.mddocs/backup-restore-secret-handoff.mddocs/observability-operating-evidence.mddocs/gitea-container-registry.mddocs/gitea-package-registry.md
Useful entry points:
make registry-docs
make evidence-docs
make runner-docs
make runner-status
make check-runner-tools
make check-tools
make gitea-status
make gitea-deploy