What is the first repository the forge hosts?
proposal 8, opened by backlog
State done — finished
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.
Oregami has been live at `https://oregami.oxegen.io` since 2026-08-14 and holds no repositories and no voices. Every route correctly answers absent. That is content, not a fault -- but it blocks two other things: the Daimond session's conformance suite reports 21 checks unaskable because there is nothing to ask about, and their vote control stays dark until a real vote route answers with votes in a record.
The question was put as four options: Ore itself private, Ore itself public, a throwaway demo, or nothing yet. The owner did not choose from the four. He asked a better question instead, and the answer to it changes the sequencing of other work, which is why it is recorded here rather than treated as settled.
Hosting fe2o3 is the real dogfooding case and discloses nothing that is not already public on GitHub. It is also the case that costs the most, because the forge replays from operation zero on every request and a 48 MB log measures at about 1.2 s a page against 12 ms for the 612 KB `ore` history. So the answer to this question decides whether the snapshot work is a nice-to-have or a precondition.
There is a second consideration that was not part of the original four. Ore's own repository has been under Ore since 2026-07-29 with git running in parallel per the bootstrap risk, so it is the repository with the longest history of being managed by the tool, and it is the one whose defects the tool's own authors would notice first. fe2o3 is the larger and more honest test of the hosting path; `ore` is the smaller and more honest test of the tool.
This needs the owner to choose, and it gates minting a voice and running the conformance suite for real.
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.
4 replies
-
backlog
Ore session: Put as four options: Ore itself private, Ore itself public, a throwaway demo, or nothing yet. The forge holds no repositories and no voices, so every route correctly answers absent, and rc-1's conformance suite reports 21 checks unaskable -- which is correct behaviour and should not be changed to make a number look better. -
backlog
Jason: Why not the Hematite (fe2o3) library, which is already public on github? -
backlog
Ore session: That is a good answer -- it discloses nothing new and is the real dogfooding case -- and the measurement says fe2o3 is about 1.2 s a page at 48 MB uncached, so it wants the snapshot work first. -
backlog
Jason: Ore itself, public. Chosen 2026-08-14 from four options, after the question was reframed: what the forge holds today and what its eventual public face is are two decisions, not one. fe2o3 remains the public face and waits on the page cost being understood, which it now is.