Techne · intranet
not signed in
Common Information System · ALM v2 · the almanac ledger · August 2026

The Almanac

The plan of the build as an almanac: every piece with an address, a readiness condition, its citations into the series, and an honest mark. No dates: work waits on conditions the way sowing waits on soil, never on the calendar. The register is the build’s own, held in the Lexicon; the native vocabulary of the cooperative keeps a register of its own beside it, and the two meet without merging. Cites: ALM v2 · PRD v0.4 · BP v2 · VS v2 · AM v0.1 · the module documents: PATRONAGE, TREASURY, AGY, PUB.

37 drafted 48 anticipated 118 open 69 verified
Public beta · three of these words are the steward’s, the rest of the wording is a proposal

What is in force, and what waits

This record is open to read while it is still being built. Pages will change, and every page says whether a thing is adopted or only drafted. If something reads wrong, is missing, or contradicts another page, say so: open an issue on the public repository and name the page and the sentence. Corrections from readers are part of how this gets finished.

The instruments on the left are in force and the surfaces built on them can be walked today. What is on the right is built, marked, and waiting on an act no software performs: an adoption by the board, a signature by the person it binds, or a named person applying a change to the live record. Nothing is left off this list because it is unfinished. It is on the list because it is.

In force
  • The Articles of Organization, filed with the Colorado Secretary of State on February 6, 2026.
  • Bylaws v2.1, in effect on the board’s adoption of August 14, 2026, the day the officers were elected.The date is the steward’s word of September 3, 2026 read against the founding record. No minute records the adoption, and none is claimed here. Member ratification under Article XII is an amendment mechanism, not a gate on commencement. Open items remain on the text: Schedule A is not executed, counsel’s redline against v1 is outstanding, and the Secretary’s signature is not yet on the executed copy. Those are open items on the text, not a bar to its force.
  • The offices, elected by the board on August 14, 2026, each election re-taken as a separate motion on August 19, 2026.
  • Two grafted modules: Program Patronage and Treasury, adopted July 22, 2026. Adoption brought each one’s work into the plan under the same marks as everything else. Both module texts still stand drafted, and the instruments their beds wait on are named on the right.
  • The surfaces a member reads. Belonging, gathering, and finding one another are built, and most of their pieces carry a verified mark from a walk a person made. Two pieces of belonging are drafted and not built, one piece of gathering and one of finding stand delivered and unwalked, and finding has a beat that cannot be walked alone, because a response is a message to an author. Each of the three closes on an attestation, which is a person’s word and not a test run, and none of the three has one yet.
Waiting on an act
  • A member’s share. Contribution history and capital accounts wait on the board adopting the counting rules. Until that adoption a member account would be illustrative rather than honest, and the surface says so rather than showing a figure.
  • Treasury movement. The Desk reads and moves nothing. Movement waits on the board adopting the treasury policy; redeemability waits on that and on counsel.
  • Work Standing and Guild Participation. Both documents are drafted and adopted by nobody, and the work behind each is recorded as anticipated. Neither binds anyone today.
  • The probe matrix. Proposed, and adopted by nothing.
  • The Membership Agreement v2.3. Board-authorized and pending execution, never in effect: it reaches a member only on that member’s own signature, and nobody has signed.
  • Common agency. Proposed, an active experiment, and not formally adopted: those are the steward’s words of September 3, 2026, and the module’s own pages say that nothing in them is adopted. Behind it stands one undecided question, whether a non-human agent may hold a scoped authority in the record at all, and the first grant waits on that.
  • Two changes to the shape of the record. Written and reviewed, and applied to nothing. A change to the live record is a named person’s act, and no test environment stands beside it.
  • Everything else marked anticipated on a board adoption. Where a piece waits on an adoption, the ledger says so on the piece, and the page built over it says so too.

By address, for a reader of this page: the share bed is S-01 through S-03; treasury movement is T-02 through T-07, with redeemability at T-05; standing is the V bed and guild participation the P bed, P-01 through P-06; the probe matrix is the M bed; common agency is A-03 and A-04; and the two unapplied changes to the record’s shape are migrations 0029 and 0030.

Drafted September 3, 2026. Public names and public claims belong to the steward under section 2 of the build instructions. Three things above carry his word of September 3, 2026: the invitation is written to his ask that this mark say the standard thing a public beta says and ask the reader for corrections; the Bylaws take the board’s adoption of August 14, 2026, on his word read against the founding record, no minute recording the act; and Common Agency’s standing is his phrase. The rest of the wording is still a proposal standing in until he chooses it, and nothing here has been adopted as a text. What the mark names as waiting is taken from section 1 of the plan at the roadmap, which proposes what public beta means here and is itself adopted only as section 13 of the instructions. The standing of the Membership Agreement follows the same ruling of September 3, 2026, as the record page carries it.

Where the build stands · 2026-09-02 · level with the ledger at 6c1a6d9 (X-34)

This note is level with the ledger at commit 6c1a6d9 of September 2, the commit X-34 was built from, with this piece’s own entry counted. The ledger holds 183 items: 35 drafted, 40 anticipated, 108 open. Of the open, 49 carry a verified mark and 53 a delivered one. The previous note stood dated August 17, when the ledger held 139; the forty-four since are the record of two and a half weeks.

The week after launch settled what the estate says about itself. On August 22 the federation-alignment set merged in one afternoon, seven pull requests: the lexicon as a versioned schema (L-09), the egress doctrine drafted and governing nothing, and the instructions gaining their sections on the grain of the record, agent identity, the federation posture, and the verification discipline (X-23 through X-26). The same week the steward's phone line came up and was verified on his word (SMS-01), and the binding ceremony behind it was built and then moved to the intranet (SMS-03 through SMS-05). On August 26 the first two verification walks merged and fourteen pieces moved to verified, and the walk surface learned to speak plainly and to send a verdict into the record (X-31, X-32).

September opened with a design system at v6 merged and reverted the same day, and the reference rewritten instead as directions an agent follows while writing a page (U-32). On September 2 the steward directed the build toward public beta: X-33 entered the instructions as section 13, a proposed definition in six conditions and the list of human acts nothing here can substitute for, and the steward adopted it by merge that day. The agent walk began the same day, tiers one and four of the cards walked and their evidence sheets filed for a person to read (X-38); the transducer's essential text landed (TR-12).

What launch waits on has not changed in kind. Two adoptions still sit with the board, the counting rules and the treasury policy, and each releases a bed behind it; the redemption path waits on redeemability; the agency bed waits on the authority question A-03 puts before the board. One proof of ten is attested, G0, and nothing since. The walk is now an agent's preparation and a person's word, and every verified mark still enters by that word alone.

This page is authored prose over a generated spine: the headline counts above are written from the ledger by the validator and proven current in CI (X-10). The cards below are hand-kept, and drift between the two is the recurring defect of this estate. X-14 reconciled them in July and X-17 again in August, and X-17 wrote the audit that reads both, which reports clean over every address on this page today. The drift then moved one link back, where nothing was reading: X-19 found seven merged pieces marked drafted, three marked in session days after they merged, and two merged pieces holding no address at all. A faithful card on a wrong ledger is still a wrong page, and the audit cannot see it. The counts describe the work; they are never targets. The Goodhart constraint reads this page too.

Series · Governing documents
Common Record Series
Thirteen covering and module documents, three received by graft: PATRONAGE and TREASURY on 2026-07-22, AGY on 2026-07-27. The AGY graft entered on its merge; the module itself stands proposed, an active experiment, not formally adopted. Two more stand drafted and not adopted, STANDING and GUILD, and are named in the beds they would open. All drafted; none done. Done requires the suites and the suites require the Ground. The document governs; its yields distill.
SER Series Overview: the covering document of the refactor, including itself. drafted governs this ledger
PRD Product Requirements v0.4: deprecation record at §1a, four capabilities, three doors, ten principles. drafted cites: §1a deprecation
BP Build Protocol: one operating contract, piece ledger grammar, decide/stop, provenance. Yields AGENTS.md. drafted yields AGENTS.md
UI Tokens and patterns aligned to techne.coop/design-system. Yields commons.css. drafted yields commons.css
IM Information model and the eleven laws. Yields 0001_substrate.sql. drafted yields 0001_substrate.sql
VS Verification contract: five suites and six proofs. Yields verify.yml. drafted yields verify.yml
AM Authority map anchored in Bylaws v2.1. Yields 0002_policies.sql. drafted yields 0002_policies.sql
PATRONAGE Program Patronage module PRD and specification: Programs organize Opportunities; contributions, claims, and the allocation sequence; configuration as record; the Programs view. Published at /commons/patronage/. drafted yields, anticipated, 000N_patronage_verbs.sql
TREASURY Treasury module PRD and specification: the movement layer over Stripe, Mercury, and Xero; governed movements as events; reconciliation as a tally; four joint contracts with PATRONAGE. Published at /commons/treasury/. drafted yields, anticipated, 000N_treasury_verbs.sql
AGY Common Agency module PRD and specification: patron members direct the cooperative’s agent on the record; the direction rail, the run and its floor, provenance under two hands, the desk, and the first grant staged as a decision. Published at /commons/agency/. drafted grafted 2026-07-27, proposed and not formally adopted · yields 0017_direction_rail.sql, 0018_direction_desk.sql
PUB Internal Publishing module PRD and specification: member-authored writing published inside the cooperative; the entry, the named peer’s reading, standing carried by events, versions rather than edits, and a register beside this one. A reading attests that the entry was read, never that it is endorsed. Published at /commons/publishing/. drafted three routed questions before any migration · yields, anticipated, 000N_publishing_verbs.sql
SUB · The Ground
The Ground
The bed the beds are made in: the ground everything else grows from. It ends at G0, the security floor, and G0 ends with a restore that actually happened. Nothing in this bed is allowed to be clever.
SUB-01 Stand the repository on the estate layout with the validator reshaped to slices. Emits repo tree, validator, generated index.json and STATUS.md. verified Todd Youngblood · 2026-07-20 · tree matches the estate layout · validator green
SUB-02 Install the governing emissions at root: AGENTS.md from BP v1 §10, verify.yml, commons.css. Acceptance: style-lint and schema-lint green. verified Todd Youngblood · 2026-07-20 · consumption model decided: inline per page sanctioned
SUB-03 Provision the database environment and apply 0001_substrate.sql. Acceptance: db-verify green, first run. verified Project ujujwgopdwirebgcpekc provisioned · 2026-07-11 · 13 tables + capital_accounts view · db-verify green
SUB-04 Apply 0002_policies.sql. Acceptance: rls-audit expectations sourced from AM v0.1 §5, green. verified 30 policies across 14 tables · 6 helper functions · role_grants live · 2026-07-11
SUB-05 Back up, restore onto fresh infrastructure, prove the folds match. A failed restore is a launch blocker, not a footnote. verified Seed export SHA: 47e8f123 · row counts matched · fold empty in both · event 91e05e60 · 2026-07-11
G0 Security floor attested as an event per VS v1 §6. Gate: human attestation recorded. Opens every slice train. attested Todd Youngblood · 2026-07-11 · event 8c5d2d37 · all six suites green · slice trains open
Bed B · proof G-B
Belong
Identity binding wired to sign-in, onboarding and application intake, the agreements shelf, the signature flow, the member directory, then the proof with two-party attestation. Pieces grow in order; the proof closes the bed. Attestation proceeds on the steward’s run-through.
B-01 Wire the identity binding to sign-in so the visibility function knows who asks. Auth flow binding auth_user_id to agents. verified Todd Youngblood bound · agent 25a88d3a · event 91165551 · 2026-07-12
B-02 Onboarding and application intake. Application surface writing applications and events. Acceptance: complete onboarding without a meeting. verified Todd Youngblood submitted live · event 4d71a6ff · 2026-07-12
B-03 The agreements shelf. Surface over agreements with version and standing marked. Acceptance: read every agreement that binds you. verified Todd Youngblood reviewed live · event a4fc7004 · 2026-07-12
B-04 The signature flow. Signing surface writing signatures and the recording event. Acceptance: sign the membership agreement and see the signature recorded. verified Todd Youngblood signed live · sig 0c8bde48 · event 8a81c3bb · 2026-07-12
B-05 The member directory. Directory view over agents and memberships. Acceptance: appear in the directory with a profile you control. verified Todd Youngblood edited profile live · event 40a30ce1 · 2026-07-12
B-06 The member profile: the directory card grows past a name. Avatar, bio, links, location, pronouns, and an email whose visibility its owner controls, with the activity strip derived from the record rather than declared. verified Todd Youngblood · the run-through · 2026-07-24 · one profiles row, edited by its owner alone
B-07 The shelf complete and correctly typed. Raised on the run-through: the shelf held only the Bylaws and offered a signature on them, so the Bylaws read as the member agreement. The Membership Agreement is signed, the Bylaws are acknowledged, and a signature on them is refused at the definer. verified Todd Youngblood · 2026-07-24 · two signatures and two acknowledgements in the live record
B-08 Comment and countersign. A recorded remark on a versioned instrument, in the member’s own name, never edited and withdrawn only by a citing row. A signature carrying the date the signer attests to and the capacity they sign in, distinct from the moment the record was written. drafted B-07 verified · asked 2026-08-19 · migration waits on the steward’s adoption
B-09 Agreements the board originates. The shelf holds the board act that authorized a contract alongside the signature that executed it, an origination act for directors and officers with no migration in the path, and a disclosure setting held on the row rather than obeyed by hand. drafted B-08 drafted · asked 2026-08-21 · three stop cards open
G-B Belong demonstrated end to end. Proof attested with organizer and non-organizer member. Every Belong sentence demonstrated live. anticipated B-02, B-04, B-05 verified · the steward’s run-through
Bed G · proof G-G
Gather
Calendar of gatherings and sessions, registration and cancellation, attendance recording by host or steward, then the proof. Hub designs stripped of KPI machinery per PRD §1a. Attestation proceeds on the steward’s run-through.
G-01 The calendar of gatherings and sessions. Surface over gatherings and sessions. Acceptance: see what is happening and who hosts it. verified G0 attested
G-02 Registration and cancellation, self-service. Acceptance: register and cancel without asking anyone. verified Todd Youngblood registered and cancelled live · state cycle preserved for audit · 2026-07-12
G-03 Attendance recording by host or steward with recorder captured. Acceptance: presence counted where the record counts it. verified Todd Youngblood recorded attendance live · host and steward gate, append-only · 2026-07-12
G-04 The scheduling act: a gathering enters the calendar from the calendar. Any member may hold one and is its host; a steward may act for any. The gathering gains the two things it could not say about itself, what it is and where to stand, and the act lands as an event. open · delivered G-03 verified · a member schedules, hosts, and another registers
G-G Gather demonstrated end to end. Proof attested with two-party attestation. Every Gather sentence demonstrated live. anticipated G-03 verified · the steward’s run-through
Bed F · proof G-F
Find one another
Opportunity board, responses, resolution as an event (never a table), then the proof. Opened ahead of G-B by the steward’s direction, 2026-07-22. Public label awaits the naming question.
F-01 The opportunity board: play, practice, work. Delivered at /commons/opportunities/ over the Ground’s tables that carried it from 0001: kind filter, posting form, the house sign-in and error boundary. No schema change. verified Todd Youngblood · the run-through · 2026-07-24 · posted live and seen on the board
F-02 Responses between responder and author, delivered on the same surface. Visibility exactly as AM §18.2 scopes it: responder sees their own, the author sees all on their posting, overseers the whole. open · delivered the live respond-and-see act is the acceptance
F-03 Resolution as an event, never a table: the author closes to resolved or withdrawn with an optional outcome note; the row transitions and the outcome lands as an opportunity.* event for the parties the policy admits. verified Todd Youngblood · the run-through · 2026-07-24 · closed by its author, landing as opportunity.resolved
F-04 The Programs view: Programs as organizing bodies for Opportunities; the principal page at /intranet/programs/ and the Overview primary window, with the affiliation verb, per PATRONAGE §8. Grafted into the bed 2026-07-22. verified Todd Youngblood · the run-through · 2026-07-24 · both principal Programs designated in the live record
F-05 The designation act: a Program enters the record from the intranet rather than the SQL console. designate_program() writes the agent row and the program.designated event together; a member attempting it is refused and leaves nothing behind; designating a standing Program returns it rather than a twin. verified applied to the CIS 2026-07-24 · rehearsal beats 13 through 13.6 against a fresh database
G-F Find demonstrated end to end. Proof attested: open to resolved, landing as an event. Every piece of the bed but the response flow is verified, and the response is the one beat a single person cannot walk. anticipated F-02 verified · a second member answers a posting
Bed S · proof G-S
See your share
Contribution posting paths, the tally surface, then the allocation run, then the proof. Re-decomposed to three pieces by the PATRONAGE §14 graft, adopted 2026-07-22. Stubs by design until the counting rules adopt. The rules will decide what is priced; the standing principle, qualification over quantification, holds that recognition makes value visible without pricing all of it.
S-01 Contribution posting paths: the PATRONAGE §10 verbs land; a valued Contribution posts with both deltas per Law VII. open · Q3 Q3 recorded (counting rules + Schedule A entered) · PATRONAGE adopted ✓
S-02 The member's tally surface with traceable inputs per Law IV. Stub, promotes when S-01 is verified. open · Q3 S-01 verified
S-03 The allocation run: the Plan §7 sequence as recorded events, steps 01 through 05, with 06 and 07 as commitment records per PATRONAGE §11. anticipated S-02 verified · fiscal close · Q4 class semantics recorded
G-S The tally shown equals the tally computed by hand. Proof attested: hand-computed equality, both projections. anticipated S-03 verified
Bed T · proof G-T
The movement layer
The Desk, the intake rail, reconciliation as a tally, disbursement execution, the redemption path, then the proof. Grafted by TREASURY §13, adopted 2026-07-22. Public capability name open; execution arrives last, into a fabric already proven to reconcile.
T-01 The Desk at /intranet/treasury/, read-only over existing facts; TREASURY-POLICY v1 in force per TREASURY §6. open · TREASURY-POLICY TREASURY adopted ✓ · Desk built read-only, policy v1 drafted and staged to the FSC and board (2026-07-22) · completes on adoption
T-02 The intake rail: Stripe to money.received by the 0006 seam pattern, dues then share purchase, idempotent on the rail reference. anticipated T-01 verified · dues schedule and membership terms recorded as instruments
T-03 The reconciliation tally: three-way pairing across ledger, bank, and book; windows attest; gaps card and cannot be attested over. anticipated T-02 verified · Mercury feed and Xero references flowing
T-04 Disbursement execution: PATRONAGE commitments discharged, proposal to approvals to bank reference; settlement by pairing, never mutation. anticipated T-03 verified · S-03 recorded under PATRONAGE
T-05 The redemption path: share.redeemed and its payout per the membership lifecycle already in the substrate; refuses while the question stands. open · redeemability the redeemability question resolved by board and counsel
T-06 The balance view: each rail’s reported holding, Stripe, Mercury, Xero, read only, with its source and its read time, and the delta to the reconciled record beside it once the windows attest. anticipated T-01 verified · read-only credentials provisioned for the three rails (met 2026-08-04)
T-07 The statements view: the cooperative’s finances by month, quarter, and fiscal year, position, flow, standing, and the close ribbon, derived from the record and cut per audience. Every figure resolves to its events, its instrument, or its read; the member cut returns aggregates and no other member’s name. anticipated T-01 verified · the dues schedule recorded as an instrument · store staged as 0019_treasury_statements.sql
T-08 The program revenue registry: each Program declares named monthly subscription tiers, and beside the registry a store of readings says how many subscriptions stood active, at what price, from which system, at what time, on what basis. The recurring figure at /intranet/revenue/ is the sum of the latest reading per live tier, every line keeping its provenance, live from a seam or attested by a named human, marked apart, because migration into a system is not growth. Readings are observations beside the record, never events; no money moves and no balance is stored; Xero remains the book of account. open · delivered 0030 applied to the live CIS 2026-08-26 at the steward’s direction · RegenHub.xyz’s six tiers declared, four read live from Stripe · techne.coop declares no tier until the dues schedule records
T-09 The readings runner: it reads active subscriptions from Stripe, folds them per product, matches each to the tier bearing that product’s name, and writes one live reading per tier; where no system holds a count it writes an attested reading and refuses to write one without the name of the human vouching it. It writes to the readings store and nowhere else, declaring no tier, moving no money, storing no balance. A Stripe product with no tier and a tier with no product are both reported and neither is invented. open · delivered run against the live CIS 2026-08-26 · the maker node and the unmigrated legacy memberships stay unread until a named human vouches their counts
G-T A movement shown settled equals a movement traced by hand, proposal to approvals to bank line to journal, and the window attests with nothing unexplained. anticipated T-04 verified
Bed U · The frame · no proof of its own
The shell every capability wears
One frame, one sign-in, one map, injected by assets/shell.js rather than hand-rolled per page. Built 2026-07-24 on the steward’s direction; refiled into its own bed 2026-07-27 by X-13, since a bed should mean a capability. A bed with no proof of its own shows its growth in what stands on it. The first seven pieces built the frame; the design sprint of August, U-08 through U-15, gave the estate its pattern library, its public face, and one primary navigation; U-17 through U-22 answered what the steward found when he opened it on a phone, what the frame had been claiming and not doing, and what the public face still said in the retired register, and then published the formation record the estate’s vocabulary came from.
U-01 The shell: a dependency-free frame injector. Topbar, the complete grouped map, and the tinted context strip, all from one declared manifest; the session read from storage, never a second client. verified Todd Youngblood · 2026-07-24
U-02 The doors adopt the frame: four commons doors shed their hand-rolled topbars. The addresses stay put; the shell makes the address irrelevant to the reader. verified Todd Youngblood · 2026-07-24
U-03 The constitution amended: the design system’s navigation section rewritten around the shell; the deployed taxonomy adopted as canon over the five-slice draft. verified Todd Youngblood · 2026-07-24
U-04 The gate: one standard sign-in card with a tinted destination line. Signed out is topbar and gate only, the map hidden and the page parked. verified Todd Youngblood · live sign-in
U-05 The member’s register: the strip speaks the cooperative’s language rather than the build’s. True of the build, and nothing a member came to read. verified Todd Youngblood · 2026-07-24
U-06 The frame on a narrow screen: the map, the strip, and the topbar hold at phone width without a second layout. The drawer stands at zero height closed and 554px open at 390px wide, carrying all eleven links. open · verified built 2026-07-24; a member’s own narrow walkthrough is the acceptance
U-07 The parked door: the Share surface names S-01 and S-02 and says the absence is the board’s pending act, not an administrator’s withholding. It carries no data and fetches none. A status contract rendered as a door, at the address members will keep; it retires when the real surface opens. open · delivered built in the launch-gap review 2026-07-27; a signed-in member finding the door is the acceptance
U-08 The pattern library grows: the launch-week audit found the system silent where the surfaces most need it, no icon source, no hint, disclosure, or form pattern despite two live forms, and no named loading or absence states. The patterns enter commons.css and the design-system reference gains the Lucide amendment. open · verified adopted as PR 85 · the steward · 2026-08-07
U-09 The launch page joins the site: an island with an empty navigation list, a footer without links, and a primary action pointing at its own section is given its paths to the framework, the join form, and the record. open · verified adopted as PR 86 · 2026-08-07 · no horizontal scroll at 390 or 320
U-10 The front door tells the truth: the join surface said membership is by invitation while the drafted Participation Framework proposes two open-enrollment classes. The public participation surface renders from the framework and cites it; the join form is rebuilt as class-aware enrollment. open · verified adopted as PR 87 · 2026-08-07 · a live submission remains for the first real applicant
U-11 The member surface speaks one language: the five signed-in surfaces aligned to v4, and the U-05 cut finished. No section mark, piece address, migration number, or event identifier renders in member-facing copy. open · delivered adopted as PR 88 · 2026-08-07 · the icons and aria-current await a signed-in walkthrough
U-12 Two faces, no third: the X-06 decision adopted two typefaces, yet commons.css still carried a third as an interface layer, a constitution disagreeing with itself. No governed page loads it now. open · verified adopted as PR 89 · 2026-08-07 · the font-stack check green
U-13 One primary navigation for the public face: every public page carried a hand-rolled topbar and no two agreed, while a third carried none at all. The shell settled this for the signed-in surface in U-01; this settles it for the public face, and the check refuses a page that carries two frames or none. open · verified adopted as PR 91 · 2026-08-07 · verified on the live site after deploy
U-14 The front door, briefer: five sections below the hero and a ninety-five word purpose paragraph above the fold, cut to a hero that states the thing in two sentences and three sections that do work. open · verified adopted as PR 93 · 2026-08-07 · verified live, countdown to footer
U-15 The intranet walkthrough, answered: eleven minutes of the steward’s asks from walking every view. Less chrome at the sign-in, forms behind buttons rather than standing open, tabs where lists grew long, and an archive verb where the record offered only silence. open · delivered adopted as PR 95 · 2026-08-07 · the drawers, tabs, and archive verb not yet exercised by a member
U-17 The intranet in the hand: the members’ surface was built and reviewed on a desk. Opened on a phone, the bar overflowed, forms invited the system to zoom, and controls sat under the size a thumb can reliably hit. Six defects answered. open · verified merged 2026-08-08 · a member’s own phone is the acceptance
U-18 The frame that never held: U-01 specified one persistent frame carried across navigations, and two pages said so for weeks. It was never true. The opt-in lived inside a stylesheet injected on DOMContentLoaded, and the browser reads it at pagereveal. The console said so the whole time. open · verified adopted as PR 109 · 2026-08-09 · verified on the deployed site, not only in the harness
U-19 The frame before the paint: the topbar and the map rendered into each surface’s markup from one manifest, by a generator with its own freshness check, so the named elements exist at pagereveal and genuinely morph across a navigation. The gate is the hard part, not the furniture: one synchronous head script writes the mark before the first paint, the stylesheet withholds the map from any document not marked in, and scripting off fails closed. Acceptance measured over the debugging protocol, and the signed-out load rendered. open · delivered U-18 merged ✓ · the launch-week condition lifted by the steward, 2026-08-13
U-20 The frame measure: nine framed surfaces carried four different content widths, because each hand-rolled its own container and the token layer had nothing to offer them. The layer now names a third grammar, the frame measure, fluid, and an audit refuses a page that pins it back to a pixel. open · delivered U-18 merged ✓ · nine surfaces at 360, 1024, and 1920 with no overflow
U-21 The commons page speaks the current book: /commons/ still spoke the retired register and flattened four states into two, and said nothing of the cybernetic reading or of the intranet, where the book is actually read. Re-cut on the steward’s ask. open · verified adopted as PR 114 · 2026-08-10 · a member’s reading is the acceptance
U-22 The Commonplace, published: the formation record enters the estate at /commonplace/, seventy-nine entries recast into the house grammar, carrying a standing note the source did not have. It governs nothing; the lens is recorded as the steward’s reading rather than the page’s own claim. open · delivered adopted as PR 116 · 2026-08-10 · public and unframed, so it stands clear of U-19
U-33 The doors in one order: the overview lists Common Agency before Treasury and the sidebar map lists Treasury first, so a member reading both surfaces in one sitting is told two different things about where the estate’s rooms stand. One order, read by both from one source, and a check that refuses the drift. Which order is right is the steward’s to say. anticipated filed by the steward’s verdict of fails on U-15 · walk 03, 2026-09-04 · not yet taken up
U-34 The address leak on the legal shelf: /intranet/legal/ repeats the piece address DOC-01·08 in its own member-facing prose, the exact leak U-05 cut and U-11 was meant to keep cut. The pointer stays, the number goes, and the five signed-in surfaces are swept for any other address, section mark, migration number, or event identifier standing in prose. anticipated filed by the steward’s verdict of fails on U-11 · walk 03, 2026-09-04 · not yet taken up
U-35 The frame measure on the rebuilt legal page: /commons/ holds an 860px column and the rebuilt /legal/ measures 732px, and the measure audit said nothing either way. A measure a rebuild can quietly leave is not yet enforced; the two are reconciled at their source and the audit is made to reach the page that drifted. anticipated filed by the steward’s verdict of fails on U-20 · walk 03, 2026-09-04 · not yet taken up
U-36 The share door names its pieces: U-07 asks the parked Share door to name S-01 and S-02, and the page explains the wait, names the Board’s pending adoption, and links the counting rules without printing either identifier anywhere. A door that says it is waiting without saying what it waits on sends the reader back to the map. anticipated filed by the steward’s verdict of fails on U-07 · walk 04, 2026-09-05 · not yet taken up
U-37 The Commonplace names its author: U-22 asks the page to name its own standing and the steward as author of the lens, and the attribution lived only on /commons/. The standing note on /commonplace/ now names the steward and records the lens as his reading, not a claim the book makes for itself. open · delivered filed by the steward’s verdict of fails on U-22 · walk 04, 2026-09-05 · staged on U-37; U-22 keeps its mark until the walker speaks again
U-23 The front door after the doors opened: the countdown retired for an opened mark, and the hero and sub-sections re-cut from the launch gathering’s own words. Soil, not a firm; scenius; craft as quality and care; and the shown-in-formation sentence, quoted as speech from the record rather than claimed as instrument text. open · delivered adopted as PR 173 · 2026-08-18 · the opened mark verified on the live page
U-24 The sunset written down: design-system v5 records the desert register the front door began — horizon lines, the descent, the wash, a minimalist Southwestern discipline — folds the page’s private width onto the frame cap, and stages two named sunset palettes, Vermilion Hour and Juniper Twilight, as a contrast-checked proposal. No token value changes; the usage becomes grammar, and it informs future pages softly. open · delivered adopted as PR 174 · 2026-08-18 · the palettes remain a proposal; no palette adopted
U-25 The estate after the doors: four public surfaces — About, the community of practice, what grows, and a journal of signed, non-governing field notes — and the v6 addendum, the incised register: single-stroke glyph devices, a sky instrument tinting the sweep by Boulder solar time, and the colophon by which a page signs itself. About joins the topbar; the officers entry is deliberately absent on the steward’s open disclosure calls. open · delivered adopted as PR 175 · 2026-08-18 · all four surfaces verified live; the officers entry still held
U-26 The register deepened where the steward found it still too restrained: every tinted section washes in its stop, a seam pools at each horizon and breathes with the computed sky, cards carry the stop in ground and edge, and the glyph set grows from five marks to ten — each named from a formation-lexicon entry, the spiral assigned at last to the workshop chain, three marks held unassigned until a surface earns them. AA verified by script on every wash in both modes. open · delivered adopted as PR 177 · 2026-08-18 · merged by the agent as the steward’s stand-in, battery green
U-27 The whole sitemap read against the register: the audit found the estate largely seated on the tokens, the frame cap, and the formation footer, and gave the thirteen bare interior pages the register's smallest instrument, the sweep horizon at masthead and footer. The topbar speaks in bare nouns throughout: About, Participation, Commons, Intranet. Records, the legal shelf, and the instruments left untouched by name. open · delivered adopted as PR 178 · 2026-08-18 · sweep and Commons label verified live; bare pages named and in good standing
U-29 The launch page: the steward’s edited public record of August 14 and August 19 published at /launch/ as a principal artifact of the cooperative. The founding narrative, the minutes of the first special board meeting set apart and reproduced, the officers elected and confirmed, counsel’s recognition of standing, the two membranes of participation, the empty parliamentary room, and the marks table. The partner project appears only as independent and unaffiliated, at its co-founder’s request. drafted staged on u-29 · two steward calls open: the disclosure of director names, and their spelling against the filed articles
U-30 The Daybook: the launch weekend gathered from the composed audio transcripts, published at /daybook/ as a companion to the Commonplace. Forty-two entries from the seven public sittings, sitting six withheld on the steward's direction and stated as an absence. First published at /volume-2/ and withdrawn 2026-08-21; revised, renamed, and republished on the steward's direction of 2026-08-22, so both acts stand on the record. open · delivered republished 2026-08-22 as PR 227 · the entries were sorted and framed by a machine reading the transcripts and enter as leads, none attested
U-32 The design system as directions: the v5 reference rewritten as imperative, checkable instructions an agent follows while writing any page, adding no rule and citing the reference page or commons.css for every line; a script that reads every tracked page against them and sorts each finding as mechanical, judgment, or observed; the report it writes; and the mechanical fixes as a second pull request on the same address. drafted staged on U-32 · merge is the act of adoption; the palettes, the scale, and the faces stay where the reference page leaves them
Bed A · Common agency · proof G-A
The instrument held in common
Direction as a member act on the record, grafted by AGY §14 on the merge of 2026-07-27; the module itself stands proposed, an active experiment, not formally adopted. The rail and the desk are built; what remains is a decision, not construction. The first grant would be the record’s first authority held by a non-human agent, and it is staged rather than taken. The discipline is the oldest one the cooperative holds about tools, augmentation over automation: capability may be built; authority waits on people.
A-01 The direction rail: give_direction() validates the member, the brief, the four kinds, the Estate list, and the flooding bounds, then writes one direction.given. No policy widens; the verb is the only door. Probe cells assert the §11 floor. open · verified AGY grafted ✓ · G0 attested ✓ · 0017 applied to the live record, then a Direction given
A-02 The desk at /intranet/direct/ with its window on the Overview: the pen shows each bound before it is made, the arc shows every Direction with its beats, and a refusal is shown in the words of the rule that refused it. open · delivered A-01 verified · 0018 applied, then a Direction given from the desk
A-03 The first grant and the instrument’s pen: the AM v0.2 addendum granting the agent the direction namespace and nothing else, the AGY-ESTATE instrument carrying the Estate list and the bounds, and the agent-actored verbs. anticipated A-01 verified · the grant decided by the steward, routed to the board if he routes it
A-04 The run harness: poll, brief, isolated session, scope enforcement, the steward’s halt, and the spend written back to the closing event. anticipated A-03 verified · rehearsed on the steward’s own Directions first
A-05 The grant register: the four standing authorities the steward granted the agent on 2026-08-19, quoted in his own words, each carrying who granted it, when, what bounds it, and how it ends. The boundary the agent named for itself stands beside them. The page reports acts rather than conferring authority, and A-03, whether a non-human agent may hold scoped authority at all, stays open before the board. drafted the steward’s grants of 2026-08-19 · staged on branch A-05
A-06 The desk shows the arc: A-02 asks a member to watch a Direction’s arc, and the estate’s one standing Direction has shown the given tag and nothing underneath it for five weeks. The given step drawn as a first step, the steps that would follow named in the order Common Agency §6 gives them, and the standing of a Direction that has not moved said on the page instead of left to an empty space. anticipated filed by the steward’s verdict of fails on A-02 · walk 04, 2026-09-05 · not yet taken up
SMS-01 The steward’s phone line answered by Nou: the co-op number reached the agent, from the steward’s number only, read-only, over SMS. The Buzz seat’s owner-only allowlist is the analogue; the E.164 list is the allowlist. Every inbound and outbound is a row on phone_events; nothing binds a member and no schema on profiles moves. Poll mode deploys first; a webhook receiver waits on a subdomain and Cloudflare fronting. open · verified verified by the steward 2026-08-23, two clean round trips in phone_events · A2P 10DLC cleared 2026-08-22 · issue #191, tier one only
SMS-02 Verified phone bindings to private Buzz channels, designed before built: one ceremony proves the member holds the phone and the key, the proof becomes a binding row in the CIS, and that number’s texts arrive in a dedicated private channel seating the member, the agent, and the steward. SMS proposes; nothing over SMS disposes. The phone_bindings schema stays a sketch behind the stop card; the design at /commons/build/sms-bindings/ runs nothing. drafted the steward’s ask of 2026-08-23 · staged on branch SMS-02-design · the build waits on the stop card and issue #191’s open questions
SMS-03 The binding ceremony built: phone_bindings minted with the phone_router and phone_binder roles, the quo-relay grows the !bind / !verify ceremony and the buzz CLI bridge, and a verified binding admits a number the way the hand-kept allowlist did. STOP from a bound number revokes with one confirmation. A router outage narrows the service to tier one, never widens it. Tier-two wiring sits behind optional env; absent, the service runs pure tier one. open · come the stop card lifted by the steward 2026-08-23 · acceptance is the steward’s own ceremony walked end to end
SMS-04 The frame names who actually texted. The relay resolved a verified binding and then threw it away, opening every dispatch with the fixed words “SMS from steward” whoever had sent the text, so a correctly bound member arrived wearing the steward’s name. The frame is now built from what the relay knows: a verified binding names the member by their key and says the ceremony verified it, an allowlisted number with no binding says it carries no key evidence, and an unreadable binding directory says the identity is unknown rather than reporting an absence it never looked for. Tier stays asserted because it is a property of the channel; identity is asserted only where a binding produced one. The number remains the whole credential behind a binding, which issue #247 is where that is answered. open · delivered a defect in shipped code, repairable with no human act · the gate, the schema, and the tier boundary all stand unmoved
SMS-05 The binding ceremony moves to the intranet: a signed-in member enters their number, receives a code by text, and confirms it on the same authenticated surface, so the binding anchors to the magic-link session identity the record holds rather than to a Nostr key it cannot resolve. 0029 extends phone_bindings rather than superseding it, so every verified binding survives; the member-scoped read that 0026 deferred arrives with it. Issue #247 proposed the address SMS-04, which was minted the same day for the frame repair. Design and migration only; the apply is a named human’s act. drafted the steward’s direction of 2026-08-23, issue #247 · the migration stays a stop card · three decisions staged, none taken
G-A The agency proof: a member who is not the steward directs the instrument, receives the work, and every step of the arc stands in the record under two hands with nothing invisible. anticipated A-04 verified
Bed L · The register · proof G-L
Ground and craft
The register evolution, adopted by the steward 2026-08-08 with all five elections at their defaults. Two roots, the ground root for where work grows and how it joins, the craft root for what hands make and how it is proven, and one law bounding the whole: history is not editable, so addresses already cited keep the words they were written in. The bed moves outward in order, the Lexicon first, then this page, then the ledger, then the companions, then the series, then the modules, because a page may not speak a register the Lexicon has not yet defined.
L-01 Lexicon v2: the register section of Ground and Craft becomes the canonical Lexicon, with the two-roots preface, the cybernetic spine, the full definitions, and the concordance that keeps the retired register readable forever. open · verified adopted 2026-08-08, all defaults elected · the bed and G-L entered the ledger with it
L-02 The Almanac: this page rewritten end to end in the register, from the title to the footer lineage recording that ALM v2 supersedes RDM v1. The generated counts and their markers untouched. open · delivered L-01 merged ✓ · the Lexicon governs before the pages speak it
L-03 The ledger speaks: the almanac ledger’s own voice moves to the register, header comments, section keys, and the intents of pieces still open, with the validator evolved in the same commit. open · verified L-02 merged ✓
L-04 The companions: the Proof Book wearing its new name, the Run-Through, the instructions, and the launch page re-worded to the register. open · verified L-03 merged ✓
L-05 The series speaks: BP, VS, PRD, and SER revised as new versions; the Information Model’s language layer revised with machine identifiers held for the IM’s own revision; AGENTS.md re-yielded from the revised BP. open · delivered L-04 merged ✓ · adopted as PR 103, 2026-08-09
L-06 The modules speak: PATRONAGE, TREASURY, and AGY re-worded as new versions, their grafts named as grafts. open · verified L-05 merged ✓ · the steward’s three merges
L-07 The machinery: file and identifier renames, the ledger file, the rehearsal script, workflow names, class families, every reference updated in the same commit. Mechanical, CI-proven, and lowest value per unit of churn, which is why it waited. open · delivered L-06 merged ✓ · the ledger file, the rehearsal suite, and six class families renamed
L-08 The quarantine: the retired register enters the style-lint vocabulary quarantine for authored prose, with exemptions named for the concordance, quotations of historical records, and the preserved text of verified entries. A vocabulary evolution without teeth is a suggestion. anticipated G-L attested · the proof precedes the teeth
L-09 The lexicon schema: the register's vocabulary as a versioned machine-readable artifact, lexicon.json beside the page it distills, with the validator holding page and artifact in set agreement both ways so a drifted export is a CI error rather than a page that quietly lies. drafted  
L-10 The retired word on the Almanac: L-02’s acceptance says no retired term appears on this page outside quotation of a historical record, and one does, three times in this page’s own voice. The occurrences are recast into the working register and a check is put behind them, in the shape L-08 specifies for the whole estate. anticipated filed by the steward’s verdict of fails on L-02 · walk 03 as amended, 2026-09-04 · not yet taken up
L-11 The word the modules use and the series does not define: L-05 asks that no page use a term the documents do not define, and the Treasury module speaks of a fold emission while emission appears nowhere in BP, VS, PRD, or the series. Either the series defines the word or the module stops using it. anticipated filed by the steward’s verdict of fails on L-05 · walk 04, 2026-09-05 · not yet taken up
G-L The lexicon proof: the evolved register demonstrated readable end to end, attested by the steward and a countersigning member and recorded as an event, like every proof before it. anticipated L-01 through L-06 verified
Bed V · Work standing · proof G-V
How work earns its standing
The branching maturity model as record: the origin conferring no standing, Program standing the internal end already built and cited, Venture standing the external end specified for construction. Staged, not adopted; six elections wait for hands, the sixth added at v0.3 when the steward challenged a refusal nobody had adopted. Nothing in this bed binds, and the whole of it is anticipated, which is the honest mark for work whose governing document is still a proposal.
STANDING Work Standing, the module PRD and specification: four principles inside the eleven laws, five elections staged for hands, published at /commons/standing/. drafted proposal posture · adoption is the board’s act, not the drafter’s
V-01 The designation rail: designate_venture() mirroring the applied Program designation contract line for line, with probe cells asserting its floor. anticipated STANDING adopted · the G0 mark verified live at emission time
V-02 The tallies: ventures_roster(), venture_standing(), and work_standing() as read-time tallies, every row tracing to its event. anticipated V-01 verified
V-03 The ventures surface at /intranet/ventures/, an Overview window beside Programs, each standing tracing to its instrument on the shelf. Before any instrument exists it stands as the parked door stands, the waiting named by name. anticipated V-02 verified · the shell manifest entry decided
V-04 The first venture instrument: VENTURE-TERMS adopted by the board with securities counsel, one per-venture instrument authored and adopted citing it, the standing appearing in the tally. People’s substance, the instrument’s verification. anticipated STANDING-D2 adopted · the counting rules recorded where the instrument values labor
G-V The standing proof: a body of work designated, its instrument adopted, its standing shown equal to the standing traced by hand through events and instruments. Not staged artificially; it attests when a real body of work first carries two families. anticipated V-04 verified · two-party attestation
Bed TR · The transducer · proof G-I
The record rendered at human variety
The instrument at the boundary where the record crosses into human perception: five views over one dated cut, regenerated on merge rather than remembered, every figure tracing back to its source. The module document labels its pieces T-01 through T-08; the T prefix is held by the treasury bed, so the Almanac mints these addresses TR. Grafted 2026-08-17 on the steward’s word; three pieces enter already delivered because the drafted artifact preceded its graft. Amendment A1, drafted at /commons/transducer/a1/, adds the succession view: two further pieces, refusal R7, and decisions D7 and D8 staged. Six refusals are the load-bearing part; six elections stand staged for hands.
TRANSDUCER The Transducer, the module PRD and specification: the second transducer, superseding the tally’s claim on the word by the steward’s direction, published at /commons/transducer/. drafted adoption is the merge · the steward’s act of 2026-08-17
TR-01 The register amendment: the §2 supersession recorded in the Lexicon in the form TRANSDUCER-D1 elects, the prior sense left legible to every document that cites it. anticipated TRANSDUCER adopted · TRANSDUCER-D1 recorded · the L bed carries it
TR-02 The generator: a script reading the repository alone and writing one cut, no key, no clock, no author read. Byte-identical for the same commit, twice, on fresh infrastructure. open · verified TRANSDUCER adopted
TR-03 The currency gate: the generator wired into continuous integration on merge to main, a seeded stale cut failing the suite, on the X-10 pattern. The gate’s refresh commits are ignored by the generator, so the instrument never counts its own heartbeat. open · verified TR-02 verified
TR-04 The surface, deployed: five views inside the shell, the merge stamped on every view. Interim address /intranet/hud/, intranet only and noindex, until the board elects under TRANSDUCER-D2. open · verified TR-03 verified · TRANSDUCER-D2 recorded
TR-05 The journeys derivation: view 03 reads the journeys register instead of parsing the stories page, and the parser is deleted rather than kept as a fallback. anticipated the journeys register verified · that module not yet grafted
TR-06 The gloss binding: the guest layer’s definitions read from the Lexicon as a source rather than carried as a copy, each citing its section. anticipated TR-02 verified
TR-07 The attribution pass: every interpretive sentence marked as the instrument’s reading, or struck, per the recorded election. The interim mark prejudges nothing. anticipated TRANSDUCER-D4 recorded
TR-08 The walk: the guest layer as a maintained piece, seven cards in the Commonplace register, docked and draggable, driven from keys, within three minutes read aloud. open · delivered TR-04 verified · TRANSDUCER-D5 recorded
TR-09 The succession derivation: the generator walks every revision of the ledger and recovers each piece’s observed states in order. No day collapsed, no path smoothed; same-day sequences preserved, demonstrated against F-01. open · verified TR-02 verified
TR-10 The seam: the succession view inside the shell, marks per the colour law, the revision count named on the surface. Dwell is elapsed days and never an alarm, per R7. open · verified TR-09 verified · TR-04 verified
TR-11 The landscape a person can find themselves in: the lens rail reordered by legibility to the member body rather than by the layers the instrument is built from, opening on the journeys lens, with the arrival classes named as a where-you-stand row. The material lens goes last. open · delivered TR-04 delivered
TR-12 The essential text: every authored sentence on the transducer cut to what a member needs to read the view in front of them and act on it, in plain words. Same views, data, behaviour, and tokens; every label, chip, legend, status mark, and citation stays. open · delivered the steward’s direction of 2026-09-02
TR-13 The walk visits every view: the guided walk covers journeys, standing, maturation, tending and composition, and jumps from tending to composition without ever opening succession, the one view carrying the estate’s own honesty about correction. The succession card added in the rail’s order, and the whole walk re-timed to stay inside three minutes read aloud. anticipated filed by the steward’s verdict of fails on TR-08 · walk 04, 2026-09-05 · not yet taken up
G-I The transducer proof: a figure shown equals the figure traced by hand from the repository to its source, walked end to end by two people. Chosen against the hardest figure: a passage’s stop at the module, amended by A1 to a dwell figure crossing every ledger revision once TR-09 is verified. Addressed G-I because G-T is held by the treasury proof. anticipated TR-04 verified · TR-05 verified · two-party attestation
Bed P · Guild participation · no proof of its own
The virtual way in
A Guild Participant level of Class Three, open enrollment from anywhere at a self-chosen amount, every amount opening the same doors, with an invitation pathway from the access track toward membership. Grafted at anticipated 2026-08-09: the bed is recorded so the work is legible, and nothing in it moves until the board adopts the framework amendment and the terms. Dues are dues, never capital, at any amount.
GUILD Guild Participation, the module PRD and framework amendment: the two-track presentation, access and patron, and two elections staged for the board. drafted the amendment and the terms are the board’s act · authored by people
P-01 The terms on the shelf: the Guild Participation Terms enter the agreements shelf as a versioned instrument, plain language, signable inline like every instrument that binds. anticipated GUILD adopted · the terms authored by people
P-02 The fifth way: /commons/join/ re-yielded with the guild way, the amount chosen and the terms signed inline, enrollment completing in one sitting, with no surface anywhere distinguishing participants by amount. anticipated P-01 stands
P-03 The class personas: the rehearsal and the probe matrix gain class-scoped personas, so class-conditional capabilities prove instead of assume, refusals included. anticipated GUILD adopted · the class-structure question decided
P-04 The invitation rail and the path tally: the member’s invitation as a recorded act, once per pair; the tally self-facing and never comparative, because eligibility is a condition and not a target. anticipated GUILD adopted · the invitation count recorded
P-05 The carrier act: a member stands as carrier of a body of work by a recorded act beside the designation. Designation itself stays name and purpose only, per the applied contract; the carrier arrives as its own event citing it. anticipated GUILD adopted · the venture-end elections settled
P-06 The ways in, re-presented: the participation index with two tracks named and the guild card beside community and co-working, the invitation pathway in the ownership disclosure, the amendment cited as the instrument that governs. Held for adoption by its own head note. anticipated GUILD adopted · the elections recorded · the amendment date set · staged on branch P-06
P-07 The participation stories: the capability register, every way a person can act in the commons and the intranet, one set per persona, refusals counted as capabilities, each story carrying its proving act and an honest mark. Story numbers are document-local; only this almanac mints addresses. open · verified adopted as PR 108 · 2026-08-09 · published at /commons/prd/stories/
P-08 The day-one journeys: what a person actually does in their first sitting, in order, under each of the five arrival classes, naming what refuses as plainly as what works; the guild reframed as the cooperative’s emergent virtual extension rather than its price levels; and sharing a project, class by class, with the origin conferring nothing exactly as the standing module provides. open · verified adopted as PR 117 · 2026-08-10 · revises the register in place
P-09 The two tracks told apart: one canonical participation page and a pointer at the other, the ladder retired for a matrix with the membership line drawn across it, the investor set beside the whole rather than after it, every instrument on one shelf with a second mark saying whether signing makes the signer a member, and the formation record linked as a lens that governs nothing. The access track gives up the word member at the steward’s direction. open · verified adopted as PR 123 · 2026-08-12 · three names staged as elections
P-10 The front door reads like a front door: P-09 led the participation page with a legal matrix, so a visitor met the ownership line, a capital account, and partnership under Subchapter K before being told they could come and work here. Same material, reordered. What a person can do first, then what ownership is, then how it happens, then one comparison table asking the four questions in a visitor’s words with the statutory terms given once beneath it. Nothing P-09 established is withdrawn. open · verified adopted as PR 124 · 2026-08-12 · the re-cut asked for on the day P-09 merged
P-11 The door and the room behind it: /participation/ cut to the two open doors, what ownership is, and one link, with the comparison table, the invitation pathways, the timeline, the vocabulary and the instruments moved to /participation/detail/. The formation notice moves from the top banner into the footer on the public pages at the steward’s direction, and keeps its top strip under legal/, where a reader could otherwise finish a governing instrument without meeting the sentence that says it is drafted. open · verified adopted as PR 125 · 2026-08-13 · the detail page carries what the door gave up
P-12 One notice, one place: the formation banner comes off the fourteen pages under legal/ and the footer line takes its place, the steward having overturned the agent’s call to keep it there. The notice audit drops to one form and gains a no-survivals check, so a banner cannot creep back onto a single page unnoticed. open · verified adopted as PR 126 · 2026-08-13 · one form of the notice, in one place
X bed · Cross-cutting · proof G-R
Cross-cutting work
Work that serves every capability or none in particular: observability, notices, exports, manifests, lint, audit, coherence, probes, the walkaway, and the freshness of what this page claims. Thirty-nine pieces, the first nine the machinery and the tail since then the estate’s own honesty: reconciled against the ledger by X-14, X-17, and X-34, then against the repository by X-19, and carrying the two pieces that corrected what the estate said about its own formation and about the defects in its published text. Their addresses are their branch names rather than X numbers, because a piece is named by the branch that built it. The rehearsal harness runs weekly in CI.
X-01 Error boundary and observability: errors surface to the steward without leaking to the member. Boundary script on the four interactive surfaces; sink decision recorded (error_log as its own follow-on packet). verified Todd Youngblood · 2026-07-20
X-02 Notices v1: transactional notices on the admission path, two sinks behind one seam each. The steward intake notice rides Telegram, deployed and proven; the applicant email acknowledgment keeps the Resend seam and waits on the zone manager's DNS records. A missing sink is named as a gap, never dropped. verified rail deployed and wired 2026-07-21 · the steward sink proven; the applicant sink stays dormant until the DNS records land
X-03 Export paths for the walkaway: fourteen export views, the producer, and the pinned SHA convention (per-table JSON ordered by id; a data-derived manifest whose sha256 is the export SHA). 0004 live; first live export recorded as event export.taken, manifest sha 109c584b. verified Todd Youngblood · 2026-07-21
X-04 Document manifest and site index: index.json enumerates every page by walking the tree; a stale committed manifest is a CI error, self-healing on the next run. verified Todd Youngblood · 2026-07-20
X-05 Grammar lint in CI: the Subchapter K vocabulary quarantine, no em dashes, no emoji, every exemption named per VS v1 §9. verified Todd Youngblood · 2026-07-20
X-06 Design token audit in CI: hex only inside custom-property definitions; token drift against commons.css a defect. Typeface fork found and decided: the deployed two-face practice governs. verified Todd Youngblood · 2026-07-20
X-07 Decision coherence in the validator: a packet whose status has opened must not carry an unresolved escalation card. Proven against live ledger history. verified Todd Youngblood · 2026-07-20
X-08 The RLS probe matrix, live in CI: every role against every table per AM v0.1 §5, each probe citing its cell. Found two conformance gaps, closed by 0005 in the document’s favor; 0005 confirmed live, so the database conforms to the matrix the probes cite. verified Todd Youngblood · 2026-07-21
X-09 Walkaway rehearsal: export, stand fresh infrastructure, import, re-export, require SHA equality and an exactly reconstructed fold. The live run happened: restored onto a scratch project, re-exported byte-identical, fold reconstructed, events export.taken and walkaway.rehearsed recorded. The harness keeps rehearsing weekly in CI. verified Todd Youngblood · 2026-07-21
X-10 Generated artifacts stay current: the claims a generated artifact makes about the ledger are proven in CI rather than kept by hand. This page’s headline counts join STATUS.md and index.json as validator output, and a stale committed copy of any of them is an error. verified merged as PR 64 · the generated-freshness job green in CI
X-11 The export follows the substrate: a projection defined as select star freezes its columns when it is created, so a column added afterwards never reaches the walkaway. The one drifted view is re-expanded and the rehearsal now asserts each carries its base table’s columns exactly. open · verified X-03 verified ✓ · 0014 merged · the rehearsal beat is the acceptance
X-12 The member’s rail: Law I holds that every relationship between records is itself an event, yet a response landed as a row alone and a registration never spoke at all. Two triggers land the relationship in the log addressed to the member it concerns, and the shell renders that address. open · delivered F-02 delivered ✓ · G-04 delivered ✓ · X-02 verified ✓
X-13 The documents agree: the three published PRDs, the ledger, and the deployed map claimed different truths in four places. Each amends to what the record settled, with the amendment dated and the superseded wording kept, because a refactor that hides its lineage is not legible. open · verified the full review of the three PRDs delivered 2026-07-27
X-14 The build surface agrees: the first resync. The Almanac narrated seven beds where the ledger held nine, the instructions counted 52 items where it held 72, and the Proof Book scored six proofs where it held eight. A page that counts wrongly is not merely out of date; it is a claim the record does not support. open · verified the steward’s ask, 2026-07-27 · reconciling public claims is his call
X-15 The register bridge: the Almanac prose brought nearer the cooperative’s native register, unearned interface labels retired and the loop headers yielding to the named conditions that own them. Superseded the same day by Ground and Craft, which evolved the whole register rather than bridging it. open · verified the change specification adopted by the steward · public wording is his call, not the instrument’s
X-16 The estate reads true: the front-door documents aligned with the register and the versions that exist. README, CONTRIBUTORS, and RUN re-cut, the citation sweep across the estate, the instructions census matching the validated state. open · verified the steward’s ask, 2026-08-09 · builds on L-05
X-17 The second resync: X-14 again, for the beds recorded since. Fifty addresses stood in the ledger without cards on this page, three whole beds among them, and seven cards carried marks the ledger contradicts in both directions. This piece is that reconciliation, and it writes the audit that reads both. open · delivered adopted as PR 115 · 2026-08-10 · the audit it wrote is not yet a gate (X-18)
X-18 The cards answer to the ledger, the ledger to the repository: the teeth for the resync. X-17 wrote scripts/almanac_audit.py and left it out of CI on purpose, because a new gate in launch week is a hazard. This piece wires it in and adds the check X-17 did not have, since the card audit reported clean over every address here on the morning the ledger was found wrong in twenty-four places. Every address-shaped branch merged into this history must now hold an address, and a self-test runs first, because a check that has stopped checking passes everything. open · delivered X-17 merged ✓ · X-19 merged ✓ · the launch-week condition lifted by the steward, 2026-08-13
FORMATION-01 The site stops saying it is operating: the estate told a reader the cooperative was operating and its instruments ratified, and the record held neither. Both instruments read Drafted in the counsel memo’s own words, and a formation notice supersedes every page that disagrees with it. The ratification claim was the instrument’s own, written and then cited back to itself. open · verified adopted as PR 120 · 2026-08-12 · four questions parked with the steward
DOC-01 The correction log opens: four defects were filed against Bylaws v2.1 and the estate had nowhere to put them, since the commentary layer records proposals on the way to a version rather than defects in published text. Eight items stand at /legal/corrections/. The duplicate check reversed two of the four filings, which is the argument for the log existing. open · verified adopted as PR 122 · 2026-08-12 · four items open for counsel
X-19 The ledger answers to the repository: the card audit read clean over every address while seven merged pieces stood at drafted, three more stood in session days after they merged, and two merged pieces held no address at all. The cards were faithful to a ledger that was wrong, which is a drift no card audit can see. open · delivered the steward’s ask, 2026-08-13 · X-17 merged
X-20 The ledger reads the build: every field of an entry is addressed to a human reader, so no mark can be evaluated by anything, and a mark nothing checks drifts. X-18 gave the page teeth against the ledger and the ledger teeth against the repository, and both checks still read what a person typed. This piece proposes the split that closes the loop: a declared column a person writes, holding the intentions only a person can state, and an observed column computed each run from an evidence block, with a reconciler that reports where the two disagree. Filed, not started; it changes schema, and schema does not change in launch week. anticipated X-20-D1 recorded · launch passed
X-21 The walkthrough that needs two people: five items stand open on one missing artifact, and it is not code. F-02 wants a response by someone who is not the steward, and the surface offers no self-response by design; G-04’s acceptance says outright that another member registers; G-B and G-G are scored for two parties; G-R wants its anchor pass walked and its words spoken. One scripted sitting, twenty beats, two people on their own devices with no agent present, no SQL editor open at any beat. It closes nothing: a script is not a proof, and the plan of a walk is not the walk. open · verified the script drafted · 2026-08-17 · the walk unwalked
X-22 The verification walk: fifty-one pieces stand delivered and unwalked, and every one waits on the same input, a person walking its acceptance. One page organises that human work as a run-book: four sittings, each card a context line, numbered navigate-and-check instructions, and a spoken verdict, built for a walker recording by voice. The page binds nothing; the ledger wins every disagreement, and the page retires when the last delivered piece moves. open · delivered the page drafted · 2026-08-17 · the sittings unwalked
X-23 The grain of the record: the estate's citation grain stated as doctrine rather than left as habit. Today's grain is documentary, instrument and date, and that is sufficient for a documentary estate; the finer grain arrives when the build's history enters the Common Information System, whose ingest keeps two times on every entry, when it happened and when the record learned of it, with raw records landing whole and derived beliefs citing the raw they read. The Lexicon's tally vocabulary anticipated the split. No tooling changes ride the piece. drafted the federation guidance of 2026-08-22 · issue 218
X-24 Agent identity and attestation: the estate already runs on attested agent identity, a keypair owner-attested to a named human on the cooperative’s relay, with the merge as the act of adoption and the boundary standing with the grants, and nothing had written the practice down. The §10 addendum of the build instructions codifies it as instrument rather than habit, including cross-organization seating as a configuration act requiring both owners and a named human, of which none exists today. drafted the federation-alignment record of 2026-08-22 · staged on branch X-24
X-25 The federation posture on the Commonplace: one section stating the estate’s orientation toward systems beyond it, in the place a reader already stands. The record rides signed events; the operational inner ring is a membership relay the cooperative operates; the public web estate is the outer ring today; the Egress Doctrine decides what crosses between them; an outer commons on the AT Protocol is a candidate under consideration and not adopted; agent identity holds as §10 of the build instructions states. A posture note, not a new doctrine page. drafted the federation-alignment record of 2026-08-22 · staged on branch X-25
X-26 Adoption receipts and the verification discipline: every adoption already leaves a receipt, the merge commit carrying who adopted, what address, when, and the state of the checks, and sections 11 and 12 of the build instructions state the receipt as doctrine and the reporting rules as standing discipline: measured over inferred, guards that name their scars, green as silence about everything unchecked. A future event-shaped record derives from git history with no new tooling; the verified word stays a person’s, and the open TR-02 packet stays open. drafted the federation-alignment guidance of 2026-08-22 · issues 217 and 218 · staged on branch X-26
X-28 The walk in the page: X-22 built the verification walk for a person with a voice recorder, and the first recorded walk showed what that costs, a recording to archive, a reader to read it, four verdicts out the far end. The same cards get a second surface behind the intranet gate, where the walker clicks the verdict and types the sentence and the page writes the record the transcription step used to produce. The cards are generated from the run-book and CI refuses a stale copy, so the two surfaces cannot disagree; the verdicts live in the walker’s browser and are sent nowhere; no table, no policy, no schema act. The run-book stays public and the recorded walk stays available. drafted the steward’s direction of 2026-08-23 · staged on branch X-28
X-29 The federation strategy on the intranet: X-25 stated the posture to a public reader of the Commonplace, and the questions underneath it are a member’s questions, so one page states the strategy where the member already stands. The protocol split as the cooperative’s position, an operational inner ring on signed events over a relay the cooperative operates and an outer commons on a public portable-identity protocol, joined at the organizational layer rather than at the wire, with the Egress Doctrine deciding what crosses. Four horizons in the order that unlocks them, and then the part the Commonplace has no reason to carry: what changes for the member and what does not, with the unbuilt named as unbuilt. A strategy page, not a doctrine page and not an instrument; the merge adopts a draft and adopts no strategy. drafted the steward’s direction of 2026-08-24 · issues 217, 218 and 250 · staged on branch X-29
X-30 The federation vision on the public estate: the outer-grain statement of what federation means to this cooperative, at an address anyone can read. Federation as two bodies keeping their own records, in their own words, handing each other a defined part under a rule each wrote down first. One record in two rings with the Egress Doctrine between them, four commitments the cooperative makes from its own record and binds nobody else to, and an invitation to argue with the drafts rather than an offer of partnership. It names no organization outside the cooperative and describes no relationship, because a public vision that names its intended partners is a negotiation conducted in public. The outer half of a pair; the inner half states the same position at member grain on its own address. drafted the steward’s direction of 2026-08-24 · issues 217 and 218 · staged on branch X-30
X-31 The walk speaks plainly: the steward walked tier one of the verification walk and three cards in a row sent him out of the browser, into a SQL file, a Python script, and a merged pull request. The defect under all three is one defect, that a card says what to check and never says what idea the checking is meant to establish. The cards still ahead of the walker are rewritten to state their claim in a sentence a board member would understand and then point at evidence a person can see without leaving the browser, a live surface or a named CI step and what it prints; where the evidence genuinely is a script or a merge, the output is quoted on the card so the walker confirms rather than investigates. The cards that already carry a recorded verdict are left exactly as they were walked, because a verdict is against the card as it read that day. open · delivered the steward’s direction of 2026-08-26 · staged on branch X-31
X-32 The walk speaks into the record: the verification walk surface holds a verdict in the walker’s browser and sends it nowhere, so a cleared tab is a lost walk and no second person can read what the first one saw. The surface collapsed two rules into one. The ledger moves by pull request, which is right, because a mark is an act of adoption and a human carries it; that a verdict must therefore go unrecorded does not follow. A verdict is testimony, and testimony is what a record is for. Testimony gets its rail in the shape A-01 gave direction: a verb, one event kind entering by it, refusals citing their rules, a required sentence, and no widening of what anyone may read. open · delivered the steward’s direction of 2026-08-26 · staged on branch X-32
X-33 The road to public beta: no instrument on the estate defines public beta, so the plan that orchestrates the rest of this build proposes one, six conditions naming every surface saying truthfully what it is, every agent-completable piece delivered and green, the four proofs one steward can attest alone attested, and the beds waiting on the board marked waiting rather than missing. None of the six moves a human boundary: the steward still walks and attests, the Secretary still writes the first minutes row, the board still adopts what only it can adopt, a second human still has to appear where the record requires one. This piece carries the plan’s definition and its list of human blockers, grouped by whose act, into the build instructions, where an agent already reads before a piece. drafted the steward’s direction of 2026-09-02 in intranet-dev · staged on branch X-33
X-34 The third resync: X-17 again, for the prose the cards sit under. The audit X-18 wired in reads the cards and the ledger and reports clean, and the two paragraphs it does not read drifted while it did: this page’s state note stood dated 2026-08-17 and described a ledger of 139 pieces, and the instructions’ section 4 counted 126 items and a table of thirteen beds against a ledger holding 182 across sixteen. The hand-kept prose brought level with the ledger at a named commit, and the commit named in the prose, so the next resync knows where the last one stood. open · delivered the steward’s direction of 2026-09-02 and his merge of X-33 the same day · staged on branch X-34
X-35 The beta mark: a record open to read before it is complete owes its reader one sentence about which parts of it bind and which do not, in one place rather than scattered across the pages that happen to mention it. This piece drafts that sentence as a component and stands it on the two pages a stranger arrives at, the Commonplace Book and this one: one column of what is in force, one column of what waits on an act no software performs, and a foot naming where every line came from. The wording is the only part that is not the agent’s to settle. Public names and public claims are the steward’s under BP v2 section 2, so what is written is a proposal standing in until he chooses the words, and the component says so of itself in its own kicker and again in its foot. He chose three of them on September 3, 2026: the invitation a public beta owes its reader, the Bylaws dated to the board’s adoption of August 14, 2026, and Common Agency standing as proposed, an active experiment, not formally adopted. Those three carry his word and the foot says which they are. drafted the steward’s direction of 2026-09-02, carried as condition B5 · his three answers of 2026-09-03 on the mark · staged on branch X-35 · Tier C, the merge is his
X-38 The agent walks the cards: the verification walk is a person’s act and fifty-eight cards wait on one person’s hours, while most of a card’s steps are mechanical, a page fetched, items counted, a CI run or a pull request read. An agent session walks every card it can reach from the build host and writes an evidence sheet, step by step, with the URL, the quoted line, the run id, and a proposed verdict from the card’s own list. The agent verifies nothing; the steward reads each sheet and says the word, card by card, and a card whose last step is a person’s act is deferred on the sheet. Four batches, one sheet each, tier by tier. open · delivered the steward’s ask, 2026-09-02 · staged on branch X-38-tier-one
X-39 The tier-one walk’s three defects repaired: the agent walk of tier one held eleven cards and reported three defects it was not asked to fix, three closed items sitting under the open heading on the correction log, a card sending the walker to a page whose rows had moved, and a CI workflow red on main. A walk that reports a defect and leaves it standing teaches the next walker that the sheet is where defects go to rest. This piece closes the three. The correction log’s closed items move to the closed section with their text untouched and a dated change note beside them; FORMATION-01’s first step is pointed at the intranet legal shelf, where the drafted rows now live, and the cards regenerated from the run-book. The third is read and explained rather than repaired: two merges fourteen seconds apart raced the currency gate, one run rebasing its own fresh cut onto the later merge and the other conflicting on the same line, and every run since is green. open · delivered the tier-one evidence sheet of 2026-09-02 · staged on branch X-39
X-40 The bylaws-in-effect sweep, and finishing R-02: the steward ruled 2026-09-03 that the Bylaws are in effect, the board and officers having formed, the board having adopted the Bylaws and authorized the Membership Agreement, with member ratification under Article XII an amendment mechanism and not a commencement gate. This piece carries R-02’s record page to merge and applies the ruling across the estate. The record page’s Bylaws row reads the instrument as in effect on board adoption and keeps the v2.1 text’s open items as open items; every page that said the Bylaws are not yet in effect is conformed. The two board acts are kept distinct: the board adopted the Bylaws, which put them in effect, and authorized the Membership Agreement, which makes it available to sign, so the agreement reads board-authorized and pending execution and never in effect, because it binds a member only on that member’s own signature and nobody has signed. The member-ratification-anticipated footer and every drafted mark on an unadopted document version are left untouched. open · delivered the steward’s ruling of 2026-09-03 in #intranet-dev · staged on branch X-40 · carries R-02’s deliverable
X-41 The adoption date, and Common Agency’s standing: two further steward rulings of 2026-09-03 applied at source. The board adopted the Bylaws on August 14, 2026, the day it elected the first officers, so every page that carried the adoption as undated takes the date on the steward’s word, which is the whole of the authority for it: the founding record carries the meeting and its date, and the proceedings have the Bylaws still drafted on the day. No minute is invented; the missing minute stays an open item at DOC-01·08 and says what it is. And Common Agency stands proposed, an active experiment, not formally adopted, which resolves a contradiction the estate carried: the module’s own page has always said nothing herein is adopted, while the ledger and this almanac read an adoption off the merge of PR #73. That merge published the module and carried its §14 graft into the ledger; it adopted nothing. AGY’s ledger status stays drafted. open · delivered the steward’s rulings of 2026-09-03 in #intranet-dev · staged on branch X-41
X-42 The steward’s walk into the record: forty-eight verdicts given in one sitting on the members’ walk surface, carried from a relay message onto the entries they speak about, each in the walker’s own words. The marks the sentences move are moved and no others; the fails are filed as their own pieces and left unrepaired, because the record of a walk and the repair of what it finds are separate acts. The walker amended the walk the same day: it supersedes the lines it names, erases none of them, and the one mark it reverses is recorded as a reversal. open · delivered adopted as PR 294 · 2026-09-04 · amended on the walker’s own reconciliation the same day
X-43 The two Bylaws rows named as two objects: the launch page’s status table carries two rows that both say Bylaws and do not mean the same thing. A dated reconciliation note names them apart, the [Adopted] row recording the act and the instrument’s effect on August 14, 2026, the [Drafted] row speaking of the published v2.1 text and its open items. The day’s own prose is untouched; the note reads it from below. open · delivered adopted as PR 296 · 2026-09-05 · the address minted in X-44, after the branch merged without one
X-44 The steward’s fourth walk, and the address the check asked for: twenty-three verdicts spoken into the live CIS in forty-seven minutes, carried onto the entries they speak about in his own words. This sitting re-walks cards that already stood verified and several do not hold the second time, so seven pieces return from verified to delivered, four with a named defect filed against them and unrepaired. Three of the seven failed on one cause, a check red because X-43 merged with no address in the ledger, and that cause is cured here. Curing the cause does not restore the marks; only the walker does that. open · delivered the steward’s walk of 2026-09-05 · staged on branch X-44
OW-01 Open World, the interface onto the CIS: the five doors over one record, the six record kinds, the fold and the address in plain words; the authority environments the steward directed on 2026-09-17; the dependency tree of the build as a figure marking human acts, agent work and calendar time apart; the roadmap across a quarter; and the sixteen staged decisions, every one open. The page. The build lives in a private repository and this page names it without linking into it. drafted a document until the steward’s word · the domain is SD-11 and undecided · staged on branch OW-01
G-R Cross-cutting proof: every piece of the bed verified, every anchor re-verified against the governing text. The bylaws-mark discrepancy resolved 2026-07-22: the legal index and the instruments aligned on one mark, Drafted. anticipated X-01 through X-09 verified
Bed MM · The horizon · no proof of its own
How the cooperative could grow
The cooperative’s legal shape over time, held deliberately apart from the instruments it sits beside. Entered 2026-08-10 from the steward’s own artifacts: three vessel states of which only the first exists, six invariants that must hold in every vessel, and two transitions gated on readiness rather than dates. One law bounds the bed, and it is the reason the bed is separate: nothing in it governs. The model would take effect, if ever, only by member vote under the amendment procedures of the Bylaws, on counsel’s advice.
MM The maturity model in two registers: a plain-language companion on why an entity is a container and not an identity, and the MM-0.2 specification behind it, defining vessels, the six invariants, the two transitions with their readiness conditions, and what the record must carry for several entities to remain one system. drafted research for member deliberation · adoption is a member vote, not a merge
MM-01 The horizon enters the shelf: both pages at their canonical paths under /legal/, and a Horizon section on the legal index carrying them under a note that says what they are not, placed after the analysis group so a reader meets the instruments, then their readings, then the model. open · delivered adopted as PR 119 · 2026-08-11 · the pages are published; the model is not adopted
MM-02 The horizon on the page the card names: the Horizon section has moved to the members’ shelf, where it reads correctly and plainly unadopted, and the public legal index the card names carries no such section. The pages render; what is missing is the public door to them. Where the horizon stands publicly is settled here and put there. anticipated filed by the steward’s verdict of fails on MM-01 · walk 04, 2026-09-05 · not yet taken up
Bed M · Extraction and commoning · no proof of its own
What kind of relation was that
The register can say who someone is and what stakes a thing carries. It cannot say whether the rules over a resource are held by the people who bear the consequences or held above them, and that distinction is the whole difference between a cooperative and a landlord. This bed proposes the frame that closes the gap: three axes, sixty-three cells, seven marks written as rule conditions anyone can check, a typed vouch edge carrying no weight of any kind, and three query rules under which no query can take an agent and return a number. Two laws bound the bed and both are refusals: no surface it yields returns a number about a person, and nothing codes a real person’s conduct until people have adopted the frame. Proposed 2026-08-19 and adopted by nothing yet; the guild use of it waits on a guild floor that is not built.
MATRIX The module document: the extraction-to-commoning axis named by the steward, the seven marks over Ostrom’s rule types, the cell sentence, the typed vouch record and its refusal of any scalar, the fold over an append-only log, decay that is presentational and never arithmetic, six non-goals, and two bounded bridges, neither on the critical path. drafted a proposal · adoption is the merge, and the merge is the steward’s
M-01 Stage 1 of five: the frame standing as a piece, so a person can read it and refuse it before anything reads a real event through it. anticipated MATRIX adopted
M-02 Stage 2: the typed vouch as an event type, append only, citing an event, a cell, and an accountable voucher. What it must prove is the fold, not the storage. It also settles four things the specification deliberately left open, the encoding and signature scheme among them. anticipated M-01 stands · the edge visibility default decided, since it cannot be decided after the first edge is written
M-03 Stage 3: a view reading the graph as edges rather than scores, every count presented beside the edges it counts. The state of the transducer it would extend is unverified, and the check belongs to this piece. anticipated M-02 verified · TRANSDUCER adopted and its state read
M-04 Stage 4, last on purpose: reading past events against the marks. Doing it before the frame is adopted would be the agent computing standings about real people from its own reading, which is the one thing this bed exists to refuse. Filed so the sequence is legible, not because anyone should start it. anticipated M-03 verified · a person, not the agent, authorises the coding
M-05 Stage 5, optional and separable: the attestation-layer bridge and the arbiter role, taken at the verdicts in force. The scoring layer is out of scope entirely and the arbiter role is capped at mark 4, because a lien is an exchange cell instrument. Neither is on the critical path and neither is funded. anticipated M-02 verified · the hidden RegenHub attestation network explained by its owners · a human decision on publishing edges, which has no undo
Bed O · How a meeting proceeds · no proof of its own
What governs a room, and what only seems to
The cooperative has adopted no parliamentary authority at all, and the omission goes back to the draft as counsel first wrote it. This bed holds the two answers to that gap, both drafted and neither adopted: the survey of what the Bylaws already require and what Robert’s Rules would supply, and twelve rules evolved from the cooperative’s own record instead. Both pages say plainly that they govern nothing. Adoption is a board act under §3.13 and the board has not taken it. A third draft joins them, of a different kind but the same posture: the egress doctrine, the rule for which subset of the record leaves the cooperative, drafted against issues #217 and #218 and governing nothing until a person adopts it.
ROO Rules of Order, the survey: the quorum, the vote, the notice rule, the presumption of assent, and the order of business the Bylaws supply for membership meetings only. Robert explained for a first reader, proposed as a gap filler, with the motion the board would have to pass. drafted documentation · adoption is the board’s act, not the drafter’s
ORDER The Order of Proceeding: twelve rules in four movements, each traced to a source in the record or marked as judgment. Gathering, the floor, deciding, the record. Three named options for the board, of which the recommended one is both, with these rules controlling and Robert filling the silences. drafted a draft proposal · adopted by nobody
EGRESS The Egress Doctrine: one record, a tiered read. The full record belongs to the inner body, a defined public digest belongs to the outer body, and a written rule over rights class and content class decides what departs, at what grain, under what license class, through which named door. Corrections propagate outward. Implements the inner and outer frame of #217 per the guidance of #218. drafted a draft doctrine · the doctrine binds only on a human adoption
Bed R · The record · no proof of its own
Where a meeting and its minute live
The Secretary is custodian of the corporate records (Bylaws v2.1 §4.5(b)), and until this bed the record had no place for a minute: the minute book on the record page reads empty because nothing could write to it. This bed gives the minute a place using only what the log already permits. The overseer branch of the standing insert policy admits the two kinds, the standing read policies show them to directors, officers, and the steward, and a member who holds no office is told why they see nothing. No schema changes and no policy moves; the first minutes row is the Secretary’s act, pointing at the founding record of 2026-08-14, and no agent writes it.
R-01 The minute book without a schema change: a Minutes section on the gatherings page listing, for every gathering titled “Board ·”, the minutes.drafted and minutes.adopted rows that cite one of its sessions, each with the minute’s location, its hash, and who adopted it; an overseer form writing the two kinds through the overseer branch of events_scoped_insert. The read policy was read, not assumed: a member cannot see an overseer’s row, so the list is an overseer’s and the page says so. open · delivered the roadmap’s batch 2 · staged on branch R-01 · the first row is the Secretary’s
R-02 The record page rewired to the record: the minute book read from the minutes.* events per board session, the offices and the roster read from role_grants, attendance at meetings of the Board read from attendance, each section telling a reader what the standing read rule keeps from them; the instrument table kept as a reading of the published documents; the GOV v0.1 parliamentary model moved under a design-note heading marked drafted. Nothing on the page writes. open · delivered the roadmap’s batch 3 · staged on branch R-02 · the Bylaws’ standing is a stop card for the steward
signal loop · one
What is workable now?

Thirty-four pieces are verified, the Find bed is built but for its response beat, and the shell carries every signed-in surface. The workable fronts left before launch are narrow and mostly other people’s: the two board adoptions, the labor tiers only a human memory can check, and the two attestations that want words approved before they are written. What an instrument can still take up alone is the L bed, which moves outward document by document and has L-06 next, and the parts of the U bed that do not run through the auth gate. What it cannot take up is A-03, because the first grant is an authority question, and authority questions are people’s.

  • L-06 The three module documents re-worded in the register, their grafts named as grafts. Strict order: L-05 merged, so this is the next piece of the bed and needs no one’s decision. anticipated
  • A-01 · A-02 The direction rail and the desk are built and green. Applying 0017 and 0018 to the live record, then giving one Direction from /intranet/direct/, is the acceptance for both. open · in session
  • F-02 The board is live and its other four pieces are verified. The response flow is the one beat a single person cannot walk, and its earlier live evidence was destroyed by an identity consolidation. Record it against the proof rehearsal, or wait for a real second member: the steward’s call. open · in session
signal loop · two
Which open condition unblocks the most?

The counting rules, by a wide margin. They unblock the entire Share bed, they are the condition the public page names, and they are no longer held by any infrastructure: the Ground that records the decision is live and verified. Nothing an instrument can build moves them. The card below stands until the board takes it up.

stop card · Q3 · counting rules
standing inS-01 · contribution posting paths
the conditionQ3 recorded: counting rules and Schedule A adopted. Board resolution required. Not held behind any infrastructure piece; can be decided in parallel with the Ground.
what it unblocksThe entire Share bed: S-01 through S-03, and G-S. Once counting rules exist, agents can begin the contribution posting and tally surfaces without waiting on any other decision.
what is already in placeThe Program Stack Patronage Plan v1 defines the six primitives and archetype weights. Schedule A carries the $100 share price and $100 annual dues; counsel memo BL-04 holds it unexecuted until an effective date is supplied and the Secretary signs it. The counting rules decision names specific FMV rates and event types for the first accounting year.
signal loop · three
What has stalled quietly?

Two quiet items, neither on the critical path to launch. The applicant email sink of X-02 waits on DNS records held by the zone manager; the steward notice does not wait with it, but the applicant acknowledgment stays dormant until they land. And this page itself stalled quietly for a month: fifty addresses entered the ledger without cards here, which is the same class of fault the cross-cutting bed exists to catch, found by a person reading rather than by a suite. X-17 corrected it and wrote the audit that reads both the ledger and the page, and held it out of CI, because a new way for CI to fail in launch week is a hazard. The steward lifted that condition on 2026-08-13, and X-18 wired the audit in. It arrived carrying a third check: X-19 had just found the drift one link further back, where the audit was clean over every address on this page and the ledger behind it was wrong in twenty-four places. Every address-shaped branch merged into this history must now hold an address in the ledger, and the audit self-tests before it runs.

  • X-02 Email sink: two Resend verification records in the techne.coop zone, placed by whoever manages it. The rail activates the sink the moment its secrets complete. card · zone manager
Repository layout · as stood (SUB-01 verified 2026-07-20)
techne.coop/                              Techne-Co-op / techne.coop (GitHub Pages)
  AGENTS.md                               operating contract from BP v2 §10
  CONTRIBUTORS.md                         contribution paths and vocabulary
  almanac-ledger.yaml                         the almanac ledger; this instrument reads it
  STATUS.md · index.json                  generated by the validator, freshness enforced (X-04)
  scripts/
    validate.py                           schema, acyclicity, gating, coherence, manifest
    token_audit.py                        hex discipline and token drift (X-06)
    rls_probe.py                          the AM §5 probe matrix (X-08)
    export_cis.py · import_cis.py         the walkaway pair (X-03, X-09)
    proof_rehearsal.py                    the journey end to end, beat by beat (G-B, G-G, G-F)
  .github/workflows/
    verify.yml                            the suites per VS v2, nine jobs as they stand
    walkaway.yml                          weekly rehearsal (X-09)
  commons/im/                             0001 · 0004 · 0014_export_views_refresh.sql
  commons/authority-map/                  0002 · 0003 · 0005 · 0007 · 0008 · 0009 · 0010
                                          0011 · 0012 · 0013 · 0015 · 0017 · 0018
  commons/treasury/                       0019_treasury_statements.sql (T-07)
  supabase/
    migrations/                           0006 (X-02) · 0016 (X-12) · 0020 (U-15)
    functions/notices/                    the notices rail, two sinks (X-02)
Pages · Techne-Co-op / techne.coop
techne.coop/
 index.html                   homepage
 commons/                     The Commonplace Book landing
 commons/series/ …          the Common Record Series artifacts
 commons/build/               The Almanac (this page) + agent instructions
 commons/join/                application intake ← B-02
 commons/agreements/          shelf + inline signing ← B-03, B-04
 commons/directory/           member directory ← B-05
 commons/gatherings/          calendar, registration, attendance ← G-01, G-02, G-03
 commons/opportunities/       the board: post, respond, resolve ← F-01, F-02, F-03
 commons/patronage/ …       the module and its counting rules, staged
 commons/treasury/            the treasury module document
 commons/agency/              Common Agency, grafted 2026-07-27, unadopted ← the A bed
 commons/standing/            Work Standing, drafted, not adopted ← the V bed
 commons/build/lexicon/       the Lexicon, v2, ground and craft ← the L bed
 commons/build/open-world/    Open World, the interface onto the CIS: plan and roadmap, drafted ← OW-01
 commons/prd/stories/         the participation stories, the capability register ← P-07
 participation/               the ways in, class-aware ← U-10
 design-system/               palette & component reference (the constitution)
 legal/                       instruments + formation commentary (migrated 2026-07-20)
 encyclopedia/                encyclopedia of artifacts
 intranet/                    the signed-in portal, inside one shell ← the U bed
 intranet/programs/           Programs as organizing bodies ← F-04
 intranet/treasury/           the Desk, read-only ← T-01
 intranet/share/              the parked door, the waiting named by name ← U-07
 intranet/direct/             Direction: give the instrument work ← A-02
Database migrations · the chain
addressfileintroducesstatus
SUB-03 0001_substrate.sql Yielded by IM v0.1. Thirteen tables, the event log, the capital tally as a view, RLS enabled deny-by-default. applied 2026-07-11
SUB-04 0002_policies.sql Yielded by AM v0.1. Thirty policies with bylaw anchors, six helper functions, the role_grants addendum. applied 2026-07-11
B-04 0003_sign_agreement.sql Atomic signature capture as a definer function, per the B-04 stop-card decision. applied 2026-07-12
X-03 0004_export_views.sql Fourteen export projections for the walkaway, role_grants included, security_invoker throughout. applied 2026-07-21
X-08 0005_matrix_conformance.sql The capital view tallies as the asker (security fix); the steward reads the event log per the §5 matrix. applied 2026-07-21
X-02 0006_notices_rail.sql pg_net trigger forwarding admission events to the notices function. Carries no secret. applied 2026-07-21
X-09 0007_apply_for_membership.sql The front door, captured verbatim from the live database with its grants, closing the restore-completeness card. captured from live 2026-07-21
B-02 · B-05 · B-07 0008_admissions.sql · 0009_profiles.sql · 0011_agreements_typing.sql Admission as one act; the profile a member alone controls; the shelf correctly typed. applied
F-04 · F-05 0010_programs_view.sql · 0012_designate_program.sql The affiliation verb and the roster reads; designation as a verb rather than an insert typed into a console. applied 2026-07-24
G-04 · X-12 0013_gathering_schema.sql · 0015_member_notices.sql · 0016_notices_rail_kinds.sql The scheduling act; the member’s own rail of notices, and the trigger widening its ear to carry them. applied
X-11 · U-15 0014_export_views_refresh.sql · 0020_gatherings_archive.sql The export projections re-expanded so a column added later reaches the walkaway; the host’s archive verb, which sets a gathering aside without deleting it, the record keeping what the calendar stops showing. staged
T-07 0019_treasury_statements.sql The statements store: the cooperative’s monthly picture derived from the record, the instruments in force, and the rail reads, with the privacy cut made at generation rather than at display. staged
A-01 0017_direction_rail.sql give_direction(): the only door a Direction enters by. Reads the Estate list and the flooding bounds from the AGY-ESTATE version in force, with the module’s opening values as defaults until it adopts. No policy widened. awaiting the live record
A-02 0018_direction_desk.sql direction_standing(): the bounds the desk shows a member before they act, by definer summary, since they live in an adoption event that concerns the cooperative rather than the member. awaiting the live record
Series artifacts and module documents · CIS Common Record Series · all drafted · twelve
SER v0.3    Series Overview                    Drafted   the covering document of the refactor
PRD v0.4    Product Requirements Document       Drafted   deprecation record §1a, four capabilities, three doors
BP v2       Build Protocol                      Drafted   piece ledger, decide/stop, AGENTS.md
UI v1       Tokens and Patterns                 Drafted   commons.css, aligned to techne.coop/design-system
IM v0.1     Information Model                   Drafted   eleven laws, REA primitives, yields 0001_substrate.sql
VS v2       Verification Specification          Drafted   five suites, six proofs, yields verify.yml
AM v0.1     Authority Map                       Drafted   Bylaws v2.1 anchored, yields 0002_policies.sql
PP v0.2     Program Patronage (module)          Drafted   grafted 2026-07-22, the F-04 and Share pieces
TR v0.1     Treasury (module)                   Drafted   grafted 2026-07-22, the Treasury bed
AGY v0.1    Common Agency (module)              Drafted   grafted 2026-07-27, unadopted, the A bed and G-A
STANDING    Work Standing (module)              Drafted   staged, not adopted, the V bed and G-V
GUILD       Guild Participation (module)        Drafted   staged, not adopted, the P bed
The ten proofs · each attested as an event, none authored as a date
G0    Security floor attested                  attested      2026-07-11 · event 8c5d2d37 · every bed open
G-B   Belong demonstrated end to end           anticipated   the beats walked; the attestation wants its words
G-G   Gather demonstrated end to end           anticipated   the beats walked; the attestation wants its words
G-F   Find demonstrated end to end             anticipated   F-02: a response wants a second member
G-S   Tally shown equals tally computed        anticipated   counting rules required
G-T   The Desk equals the movement by hand     anticipated   TREASURY-POLICY adoption required
G-R   Anchors re-verified against the text     anticipated   the cross-cutting tail verified first
G-A   A member not the steward directs         anticipated   the first grant, then the run harness
G-L   The evolved register reads true          anticipated   L-01 through L-06 verified
G-V   Standing shown equals standing traced    anticipated   the module adopted, then a real body of work