coulomb/prj-forgejo-org-refactor
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Refresh org refactor plan against September readiness evidence

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0e782-9f45-7382-afff-77ad665b88ec
This commit is contained in:
tegwick 2026-09-28 12:20:59 +02:00
parent 2a59d0d354
commit dff3513a4f
4 changed files with 204 additions and 22 deletions
Download patch file Download diff file Expand all files Collapse all files

17
SCOPE.md
View file

@ -44,7 +44,8 @@ by ID; it does not duplicate their tasks.
headers, and `contribution-convention_v0.1`
- Renaming the `forgejo.coulomb.social` host (open question, may become scope
only if the org split forces it)
- Any repo's internal structure or content
- Forge product migration (Gitea/Forgejo)
- Any repo's internal structure or content beyond coordinated migration references
---
@ -57,7 +58,9 @@ by ID; it does not duplicate their tasks.
| `railiance-apps` | Chart image `repository:` paths and chart metadata |
| `railiance-master` | Durable home candidate for the org-assignment convention |
| `the-custodian` | Canon home candidate; repo-classification alignment |
| all 112 `coulomb/` repos | Subjects of the migration |
| Current server-backed `coulomb/` repo inventory | Subjects of the migration; 112 was the seed count |
| `railiance-enablement` | Reusable CI/CD references and developer checkout paths |
| Source/rapp owners | Release manifests, package consumers, workload declarations |
---
@ -71,8 +74,8 @@ by ID; it does not duplicate their tasks.
- Deciding which rapp a workload belongs to (different dimension)
- Deciding which State Hub domain work belongs to (different dimension)
- The entry gate in `GOAL.md` is not yet met — the project is deliberately
parked until then
- Executing T03 onward before all four entry conditions in `ORGREF-WP-0001`
hold; read-only T01/T02 preparation remains relevant and permitted
---
@ -88,4 +91,8 @@ project's workplans, never copied.
- Status: **draft, deliberately deferred**
- Seeded 2026-08-11 with the finding, blast radius, and entry gate
- Execution begins only when the `ORGREF-WP-0001` entry gate is met
- Reviewed 2026-09-28: local family validator green; fresh deployable coverage,
stable full reference inventory and transfer rollback evidence still needed
- T01/T02 preparation can proceed now; execution requires the unchanged
`ORGREF-WP-0001` entry gate and resolution of its circular rollback dependency
- Evidence and next sequence: [readiness review](history/2026-09-28-readiness-review.md)