# 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.