the gate book · RDM v1 · VS v1 §6

The Gate Book

A gate is a human act: people demonstrate the capability live, say the words, and record the event. Nothing here executes; this page is the score. Each gate carries its condition, its demonstration script drawn sentence by sentence from PRD v0.3 §4, or from the module document that governs its train, the attestation to speak, and the procedure that writes it into the record.

cites · RDM v1 · PRD v0.3 §4 · VS v1 §6 · AM v0.1 · AGY §13 RegenHub, LCA · Boulder · July 2026
precedent

G0 · The security floor attested 2026-07-11

The pattern every later gate follows, already walked once. The substrate restored onto fresh infrastructure, all six suites green, and one sentence recorded by the person who holds the outcome: “G0 attested. Security floor established.” The attestation lives as event 8c5d2d37 and as a resolution in the ledger. That is the whole shape: demonstrate, speak, record.

the run-through · first act

G-B · The Belong gate anticipated

conditionB-02, B-04, B-05 verified (they are, 2026-07-12). An organizer and a non-organizer member demonstrate every Belong sentence live, together, in the steward’s run-through (amended 2026-07-22: no longer tied to the August 14 gathering). Two parties, because belonging is not self-certified.

The cast: one organizer (any steward or director) and one newcomer, a person who is not an organizer and has never touched the system. The newcomer drives; the organizer witnesses and countersigns. Each beat begins with the sentence being proven, spoken aloud.

01
newcomer
“A member can complete onboarding without a meeting.” On their own device, the newcomer opens techne.coop/commons/join and submits the application with their real name and address. Nobody helps. observe: the received panel; a membership.applied event lands in the record; the steward notice arrives if the X-02 rail is wired
02
newcomer
“A member can read every agreement that binds them, with version and standing marked.” After sign-in by magic link, the newcomer opens the agreements shelf and reads the bylaws entry aloud: title, version, effective date, and their own unsigned chip. observe: version and standing marked; nothing shown that does not bind them
03
newcomer
“A member can sign the membership agreement and see the signature recorded.” The newcomer signs on the shelf and reads the confirmation panel aloud: their name, the instrument, the version, the binding statement. observe: the signature row and its signature.signed event, atomic per 0003
04
newcomer
“A member can appear in the member directory with a profile they control.” The newcomer finds themselves in the directory, edits their display name, refreshes, and shows the change held. observe: self-edit works; no other row is editable
05
organizer
Countersign. The organizer confirms each sentence was demonstrated by someone with no standing to fake it, and both speak the attestation.
the attestation · two voices

“G-B attested. Every Belong sentence was demonstrated live by a member who is not an organizer, and witnessed. Belonging is legible in the record.”

recording procedure · §final
the run-through · second act

G-G · The Gather gate anticipated

conditionG-03 verified (it is, 2026-07-12). Two-party attestation in the steward’s run-through (amended 2026-07-22: any real gathering serves as the fixture; it already exists in the calendar as a seeded record).
01
member
“A member can see upcoming events and sessions.” A member opens the calendar and reads the fixture gathering aloud: title, host, session time in their own timezone. observe: the room is standing inside the record it is reading
02
member
“A member can register, and cancel, without asking anyone.” The member registers for the session, cancels, and registers again. Nobody is asked; the state cycle is preserved for audit, not deleted. observe: null to registered to cancelled to registered; rows kept per the append-only principle
03
host
“A member can host an event under a named agreement or policy.” The host shows the gathering record naming them as host under the cooperative's instrument, and creates the next gathering live. observe: host_agent_id is a person; the gathering hangs off a named agreement
04
host
“A member can have attendance counted where the record counts it.” The host opens the attendance panel and records who is in the room, right then, with the room watching. observe: recorded_by is the host; append-only, no unrecording; presence serves quorum per 2.7
05
both
Countersign. Host and member speak the attestation together.
the attestation · two voices

“G-G attested. Every Gather sentence was demonstrated live, in the room it describes, and the room's own presence is in the record. The calendar is part of the record.”

recording procedure · §final
cross-cutting

G-R · The cross-cutting gate anticipated

conditionX-01 through X-09 verified. Five are; X-02, X-03, X-08 complete on the steward's live steps; X-09 opens when X-03 verifies. Then the anchor re-verification pass, and one discrepancy that must die first: the bylaws instrument reads v2.1 Ratified while the legal index reads v2 Drafted (AM v0.1 §1a). The gate cannot attest while the record disagrees with itself about its own governing text.

The procedure, one sitting: walk every bylaw anchor in 0002_policies.sql, 0005_matrix_conformance.sql, and the schema comments against the governing text as published at techne.coop/legal, confirming each section still says what the policy cites it for. The probe matrix already proves the policies behave as written; this pass proves they cite what still stands. Align the legal index and the instrument on one mark. Then attest.

the attestation · steward

“G-R attested. Every cross-cutting packet is verified, every anchor re-verified against the governing text, and the record agrees with itself about what governs it.”

recording procedure · §final
after G-B

G-F · The Find gate anticipated

conditionF-01 through F-03 verified; G-B attested. The train opened ahead of G-B by the steward’s direction (2026-07-22); the gate itself still requires G-B, since every entry hangs off an agent record.

The train is built at /commons/opportunities/. The script, same shape as the others: demonstrate, speak, record.

01
member
“A member can browse open invitations by kind: play, practice, work.” A member opens the board, walks the kind filter, and reads one open invitation aloud: title, author, kind. observe: only open postings in the open section; the filter narrows without hiding the closed record
02
member
“A member can post an offer or a need.” The member posts an opportunity of their own: kind, title, a line of detail. It appears on the board under their name. observe: the row lands under opportunities_author_write; F-01 acceptance
03
second member
“A member can answer an open opportunity, visible to its author.” A second member responds. The responder sees their own response; the author sees it too; a third member sees neither. observe: visibility scoped by responses_scoped_read per AM §18.2; F-02 acceptance
04
author
“A member can close an invitation when it resolves, and the parties can see what it led to.” The author resolves the posting with an outcome note. The board shows it closed to everyone; the outcome lands as an opportunity.resolved event readable by the parties. observe: the state transition on the row and the event in the log; F-03 acceptance
05
attestor
“G-F attested. Open to resolved, landing as an event.” The attestor speaks the sentence and the gate.attested event is recorded per the G0 pattern. observe: the recording procedure at §final; the public label per the Q1 naming decision
after Q3

G-S · The Share gate anticipated

conditionS-01 and S-02 verified; the Q3 counting rules and Schedule A on record. This gate carries one demonstration no other gate has: the fold shown on the member's account equals the fold computed by hand, on paper, in front of the member it belongs to.

The sentences, when the train opens: see contribution history itemized; see the capital account as a fold over that history; follow any figure to the events and the policy that produced it. The hand computation is the heart: a member's balance recomputed from their own events with the written rules, matching the screen to the cent.

after A-04

G-A · The agency gate anticipated

conditionA-01 through A-04 verified; the first grant recorded, since three of the five direction kinds carry the agent as actor. This gate has a cast requirement no other gate has: the person who directs the instrument must not be the steward. It is the whole point of the module, and a demonstration by the steward alone would prove nothing that was not already true.

Sentences drawn from AGY §13. The script, when the train reaches it: demonstrate, speak, record.

01
member
“A patron member who is not the steward can give the instrument work, and the record carries who asked.” A member signs in, opens the desk, and gives one Direction of the kind draft or survey. observe: the arc shows it given; the row carries the member as the concerned agent, not the steward
02
the instrument
“The work comes back as artifacts, and every artifact names two hands.” The Direction completes. The member opens the pull request from their own arc. observe: the commit carries Authored-by and Directed-by; the pull request names the Direction; the closing event carries the spend
03
member
“A Direction that crosses the floor is refused, and the refusal says which rule refused it.” The member gives a Direction naming a repository off the Estate list, or one that would move money. observe: the desk shows the refusal in the words of the rule, citing AGY §7 or §11
04
steward
“The steward can stop the instrument, and the stop is in the record like everything else.” With a Direction running, the steward halts it. observe: direction.halted with its reason; the arc shows the stop rather than a silence
05
both
“Nothing in the arc is invisible.” Member and steward read the whole arc back from the record: given, accepted, completed, refused, halted, each with its hand and its hour. observe: no step of the run exists only in a chat window or on the host
attestation

“G-A attested. A member other than the steward directed the instrument, received the work, and every step stands in the record under two hands.”

§final

Recording an attestation

One procedure for every gate, the G0 pattern. The attesting human records the event; the ledger flips by commit; the roadmap follows the ledger.

-- 1 · the event, inserted by the attesting agent (an overseer act)
insert into events (occurred_at, actor_agent_id, kind, payload)
values (
  now(),
  '<attesting agent id>',
  'gate.attested',
  jsonb_build_object(
    'gate', '<G-B | G-G | G-F | G-S | G-T | G-R | G-A>',
    'attestation', '<the words as spoken>',
    'witnesses', jsonb_build_array('<agent id>', '<agent id>')
  )
);

-- 2 · the ledger: status flips to attested with a resolution naming
--     the attesting agent, the date, and the event id. By commit.

-- 3 · the roadmap syncs to the ledger, and the next train opens.
why gates are people

Every suite in CI proves the machine agrees with itself. A gate proves the cooperative agrees with the machine. That second agreement cannot be automated, because it is the moment responsibility changes hands, and responsibility never transfers to an instrument.