This page was written three weeks before launch as a list of conditions, each with an owner and a test. The cooperative launched on August 14, 2026 with almost every one of them still open. That is the finding, and it is kept here rather than tidied away: the page was wrong about what launch waited on, and the conditions were real anyway. Each row now carries what the original said and what actually happened, marked as of 2026-08-19.
Launch did not wait. The doors opened on August 14 with the two board adoptions undecided, the authority question unrouted, the labor schedule unwritten, and two of the four proofs still wanting a second human. Nothing on this page was overruled; the list was simply not what governed the date. The gathering governed the date.
The honest reading is that the page confused two things: what the record needs in order to be complete, and what the cooperative needs in order to open. The first list is still open and is still owed. The second list was shorter than anyone wrote down, and the front door, the agreements, the directory, the calendar, and the board of opportunities were all on it, and all of them stood.
One thing closed that is not on any row below, because it was not foreseen as a condition: officers were elected on August 14, and the steward confirmed on the record on 2026-08-17 that he holds Secretary. The roster is not public yet, and that is its own open item rather than a launch condition.
| condition | owner | test before launch | review it wants |
|---|---|---|---|
| COUNTING-RULES | the board, with tax counsel | After adoption, the instrument enters and the tally reads its parameters from the record rather than from any number in code | A named vote on the four values of §4 and on formation-period recognition. The draft stands at counting-rules; nothing binds until adopted |
| TREASURY-POLICY | the FSC, then the board | After adoption, the Desk renders its thresholds cited to the instrument, not to code | The FSC signs off the band amounts and decides the Coordinator-in-the-trail provision, still marked keep or strike |
| AGY first grant | the steward, routed to the board if he judges it theirs | The instrument writes direction.accepted under its own grant, and the probe shows it can write nothing else | Whether a non-human agent may hold a scoped authority in the record at all. AGY §5 proposes the narrowest form: the direction namespace, its own Runs, revocable by one policy change. Nothing is granted by drafting |
Each releases a bed behind it: the counting rules open the Share bed and the member's own account; the treasury policy completes the Desk; the first grant opens A-03, A-04, and the agency proof. Without it, direction still works and still records, with the steward relaying by hand, which is how every mark the instrument has made has entered the record to date.
None of the three closed. COUNTING-RULES still stands as a draft at its address and binds nothing; TREASURY-POLICY is still staged to the FSC and the board, and T-01 still carries the mark open · TREASURY-POLICY. The Share bed and the Desk are held exactly where this page said they would be.
The counting rules gained a clock they did not have here. The treasury committee named four deliverables on a ninety-day term running from the first member sign-up: the counting rules, the labor schedule, the treasury policy, and a payout, cash-out, and reinvestment schedule that has not been started. So the first row is now dated by an event rather than by a launch that has already passed.
On the first grant: the board question is untouched. A-03, whether a non-human agent may hold a scoped authority in the record at all, is still open before the board and gates A-04 and the agency proof. Separately, on 2026-08-19, the steward made four standing grants of his own in conversation and they are registered at the grant register under A-05. Read the difference carefully, because it is the whole point: those are the steward's grants, made in words and written down, not the board's act, and not a policy in the record. Nothing the register says changes what the instrument may write. A-03 stays open.
| condition | test before launch | review it wants |
|---|---|---|
| LABOR-SCHEDULE | Once entered, an HOURS contribution values at the tier in force | A second reading that the four tiers as entered match what is understood to have been settled in June 2026. Nothing but a human memory can check this: the rates exist nowhere in the estate |
| G-B, G-G attestations | None. The walking was the test | The attestation text approved before it is written, each citing the beats it stands on |
| AGY §15 visibility | The desk ships with the commons shelf absent and its absence explained; deciding fills the hole either way | Whether a member's completed Directions are common reading or private to the member who gave them. The drafter's cut is visible, on the ground that common means visible; it is one sentence to overturn |
| 0017 and 0018 | Applied to the live record, then one Direction given from the desk: that walk is the acceptance for both A-01 and A-02 | None beyond the usual care with a migration. Neither widens a policy |
| F-02 | A second member answers a posting; a response is a message to an author, so no one can test it alone | Whether to record it on the proof rehearsal, which proves the flow and the visibility rule against three personas, or to wait for a real second member. See the piece's note |
LABOR-SCHEDULE is the hard one, and it got harder. The row above assumed four tiers settled in June 2026 and needing only a second reading. Looking for them found nothing: no rates anywhere in the estate, and the only citation for the tiers is PATRONAGE §7, a page drafted by the instrument. A page of ours cannot be the evidence for what the cooperative decided. The steward's direction on 2026-08-13 was therefore to benchmark public wage data rather than reconstruct a memory, and until that lands the schedule is a hole, not a draft. It has no ledger address of its own, and PATRONAGE and the adopted counting rules disagree on the point in the meantime.
G-B and G-G are unattested. AGY §15 visibility is undecided. F-02 is unchanged and remains the steward's single call, record it against the rehearsal beats or wait for a real second member, and the live evidence that would have settled it was destroyed by an identity consolidation and cannot be regenerated by one person.
0017 and 0018 are the one row that moved. A Direction stands in the live record, given from the desk, and it is still open. The ledger marks for A-01 and A-02 were never flipped from open · delivered to verified, so the walk happened and the record does not say so. That flip is owed, and it is the kind of debt this page exists to make visible.
| condition | owner | what it costs if it slips |
|---|---|---|
| The notices rail's email sink | the zone holder | Nothing fatal: the steward's Telegram sink carries notices alone. Worth deciding out loud whether that is acceptable at launch rather than discovering it |
| The record's own housekeeping | the steward, with the instrument | Test residue remains in the live record from the run-through. Done last, after every attestation and acceptance, so nothing is deleted that is still wanted as evidence |
| The build account's credential | the steward | It expires two days after launch. Rotated before, it is routine; rotated during, it is an incident |
No decision was recorded on the notices rail's email sink, and no housekeeping pass on the run-through residue is recorded either. Both were written as things worth deciding out loud rather than discovering, and both were discovered rather than decided, which is a small vindication of the row and no credit to anyone.
The credential row is the one that resolved, and it resolved the way the row warned. It was not rotated before launch. It was rotated on 2026-08-19, in response rather than on schedule, and the replacement runs to 2026-11-07. The lesson stands as written three weeks earlier: an expiry that is known in advance and left to the last is not a schedule, it is a wager.
Recorded here so the list above is read for what it is, a short one. A newcomer comes in through the front door without a meeting and is admitted by a steward's act. Agreements read and sign and acknowledge, and refuse a second signature. The directory shows the cooperative and lets each member edit only their own profile. Gatherings register, cancel, register again, and count presence where the record counts it. The board of opportunities posts, answers, and closes, and the outcome lands as an event. Programs stand designated from the intranet. The desk for Direction stands at /intranet/direct/, with the rail behind it, so a member may give the instrument work as a recorded act. Every signed-in surface sits behind one frame and one sign-in and speaks in the cooperative's language. The record exports, restores, and reconstructs itself from the public repository.
All of it still stands, and it carried the launch. The estate around it grew afterwards: the front door was re-cut from the launch gathering's own words, the design system wrote down the register the page had started reaching for, and four public surfaces joined the estate. The findings from the visibility audit were closed in the live record on 2026-08-17 by two migrations applied and verified against the policies actually in force.
What this section was for is worth restating now that the date has passed. It was written so the list above would be read as a short one. Read back, it is the section that turned out to be true, and the three sections above it are the ones that turned out to be a schedule nobody was keeping.
Launch readiness · the Common Record Series · drafted with machine assistance · RegenHub, LCA · Boulder, Colorado · 2026-07-24, amended 2026-07-27 for the agency bed, read back 2026-08-19 after a launch that did not wait