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

2.9 KiB

Raw Permalink Blame History

SCOPE

Lightweight orientation: what this project repo is for, and when it is not the right place to work.

One-liner

Temporary coordination repo for splitting the single coulomb/ Forgejo organization into stewardship organizations without breaking GitOps, image pulls, or clones.

Project authority

This repo coordinates. It owns the inventory, the org taxonomy, the sequencing, the rollback plan, and the evidence. It does not own the repos being moved, and it hosts no production implementation.

Changes land in the repos that own them. This project links their work records by ID; it does not duplicate their tasks.

In Scope

Inventory of every coulomb/ reference across the fleet
Target org taxonomy and the assignment criteria behind it
Verification of Forgejo rename / transfer / redirect behavior, including the package registry
Migration sequencing, rollback plan, and cutover evidence
Promotion of the durable org-assignment convention to a permanent home

Out of Scope

Rapp context grouping — a separate dimension by ratified decision (d07ee5f9); see railiance-platform/docs/rapp-platform-service-pattern.md
State Hub domain taxonomy — a separate dimension, owned by the-custodian
Legal-entity structure and IP attribution — handled by LICENSE, copyright 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

Participating repos

Repo	Role
`railiance-forge`	Forgejo runtime owner — executes org/transfer operations
`railiance-platform`	ArgoCD Application sources, OpenBao lanes referencing repo URLs
`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

Relevant When

Planning or executing the Forgejo org split
Deciding which org a new repo should be created in (until G7 promotes that convention to a permanent home)

Not Relevant When

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

Work-record rule

Workplan files live in workplans/ with prefix ORGREF-WP-NNNN. Child work in participating repos keeps its own prefix and is linked by stable ID from this project's workplans, never copied.

Current State

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

2.9 KiB Raw Permalink Blame History