Move Oxedyne's repositories off git and GitHub, private trees first and the public face last
proposal 11, opened by backlog
State accepted — agreed, and not yet done
No mark closes this yet, and nothing in the forge sets that field. The review lane is what will. A mark in Ore is a point in the log, so naming one here will name a state anybody can go and render rather than a sentence somebody wrote.
The governing objective, set on 2026-07-29, is to replace Oxedyne's own use of git and GitHub with Ore and Oregami. It is recorded in the DevGuide as the ninth design criterion, and the build order carries a replacement ladder underneath it: ignore rules, the self-hosting trial, import completeness, git export and the bridge, relay transport, the Oregami Repository tier, and then the cutover.
Every rung below the cutover is climbed. Ignore rules shipped 2026-07-29. The self-hosting trial ran and its findings were answered the same day. Import completeness shipped 2026-07-31 as one versioned vocabulary event. The git export bridge shipped the same day with an export oracle proving a mirror's checkout matches git's own byte for byte and mode for mode. Relay transport shipped as the bare rung. The Repository tier's scaffold is built and live.
The cutover itself is stated in the build order and unstarted: "Repository by repository: private trees first, `fe2o3` and the public face last, each move gated on the bridge keeping the git mirror byte-faithful. git and GitHub are retired when nothing remains that reads them and Oregami does not serve."
The bootstrap risk is stated once and the mitigation is built: while Ore's own source lives in Ore, a defect in Ore can damage the tool needed to fix it, so git runs in parallel from the first dogfooding rung and is not retired until Oregami has served the public face through a full release cycle. Ore's own repository has been under Ore since 2026-07-29 with git alongside, which is that mitigation in force.
What this proposal owes the record is not a decision -- that is taken -- but an order and a gate. Which private tree moves first, what "byte-faithful" is checked by on each move, and what counts as a full release cycle for the purpose of retiring GitHub.
Transcribed from the project record on 2026-08-14. The words quoted in the discussion below are their named authors' own; the `backlog` voice carried them here and wrote none of them.
1 reply
-
backlog
Jason: Replace Oxedyne's own use of git and GitHub with Ore and Oregami.