prj-forgejo-org-refactor/README.md
tegwick ec2a72f435 Seed the org refactor: goal, scope, blast radius, entry gate
Establishes the prj- flavor baseline (GOAL.md, SCOPE.md, AGENTS.md,
.repo-classification.yaml, genesis, foundation workplan) for splitting the
single coulomb/ Forgejo org into stewardship orgs.

Records the blast radius verified 2026-08-11: 112 repos with a coulomb/ origin,
ArgoCD repoURL sources, Chart.yaml metadata, and - the finding that made this
project-sized rather than workplan-sized - container image paths, since
Forgejo's package registry is org-scoped. That failure is deferred: it does not
appear at rename time but at the next pod reschedule.

Seeded deliberately deferred per operator decision. ORGREF-WP-0001 is backlog
and carries a four-part entry gate (validator live, deployable coverage known,
stable re-runnable inventory, demonstrated rollback) so the decision to start
is made against evidence rather than memory. T01 and T02 are read-only and safe
to advance at any time.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-11 13:39:24 +02:00

30 lines
1.4 KiB
Markdown

# prj-forgejo-org-refactor
A migration to establish `railiance`, `netkingdom`, `helixforge`, `binky` and
`experimental` as Forgejo orgs next to `coulomb`, with the relevant repos
changing their org to better structure discoverability and responsibility.
**Status: seeded, deliberately deferred.** The finding and its blast radius are
recorded; execution waits until the entry gate in `ORGREF-WP-0001` holds.
## Why this is a project and not a workplan
All 112 repos with a Forgejo origin currently sit under `coulomb/`. Renaming
touches Git remotes, ArgoCD `repoURL` sources, `Chart.yaml` metadata — and,
most dangerously, **container image paths**, because Forgejo's package registry
is org-scoped. That last one fails *deferred*: not at rename time, but at the
next pod reschedule.
## Start here
- [`GOAL.md`](GOAL.md) — outcome, invariants, blast radius, success gates
- [`SCOPE.md`](SCOPE.md) — authority, participating repos, what is out of scope
- [`AGENTS.md`](AGENTS.md) — session protocol
- [`history/2026-08-11-genesis.md`](history/2026-08-11-genesis.md) — why this exists
- [`workplans/ORGREF-WP-0001-foundation-and-entry-gate.md`](workplans/ORGREF-WP-0001-foundation-and-entry-gate.md) — foundation and entry gate
## Not this repo
Rapp context grouping and State Hub domains are **separate dimensions** by
ratified decision (`d07ee5f9`, OAS P1). Org membership is a stewardship
grouping; it does not determine what deploys together.