S3 Platform Services — PostgreSQL HA, Valkey, object storage
Consolidates what this session established: the four orthogonal repo-family axes and the separation rule that keeps Forgejo orgs, State Hub domains and rapp contexts from being derived from each other; the stack levels plus the concerns that sit beside the stack; the self-evidencing thread and its two halves (evidence plane, now owned by railiance-telemetry, and the conformance loop, still unowned); verified repository status including the two superseded lineages; and the open placement decisions, each naming railiance-master as the decider rather than settling them here. Records that the railiance-forge retirement hypothesis was tested and rejected - it and helix-forge are different lineages, one operational and one methodological - so forge should be placed, not retired. Also notes for tooling that the bootstrap/cluster/hosts/infra repos have unrelated histories but near-identical content, so fleet inventories must deduplicate by origin URL rather than by directory. SCOPE.md gains the telemetry emission relationship and a pointer to the blueprint. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|---|---|---|
| .claude/rules | ||
| .forgejo/workflows | ||
| argocd | ||
| credential-change-requests | ||
| credential-grants | ||
| docs | ||
| helm | ||
| history | ||
| lib | ||
| openbao | ||
| registry | ||
| schemas | ||
| scripts | ||
| tests | ||
| tools | ||
| workplans | ||
| .custodian-brief.md | ||
| .gitignore | ||
| .repo-classification.yaml | ||
| .sops.yaml | ||
| AGENTS.md | ||
| ArchitectureBlueprint.md | ||
| CLAUDE.md | ||
| INTENT.md | ||
| LICENSE | ||
| Makefile | ||
| SCOPE.md | ||
| WORK-RECORDS.md | ||