Walk, Speak, Done

No page may claim the cooperative is operating or its instruments ratified.

1. Signed in, navigate to https://techne.coop/intranet/legal/. Confirm the instrument rows carry the drafted mark. The drafted rows moved to that shelf and are no longer on https://techne.coop/legal/, which now carries the filed instruments alone and points members at the shelf; this step read /legal/ until 2026-09-04.
2. Open https://techne.coop/legal/#formation and read the notice; it should state the record's position in the counsel memo's words.
3. Spot-check the front page and /commons/ for any sentence claiming the cooperative is operating; there must be none.

Say: “FORMATION-01 holds” and one sentence of what you saw, or “FORMATION-01 fails” and what broke.

The correction log holds the estate's known wrong claims, each with its standing.

1. Navigate to https://techne.coop/legal/corrections/.
2. Count the items (eight at drafting). For each, confirm it states what was claimed, what the record holds, and who closes it.
3. Confirm no item is marked closed without naming the closing act.

Say: “DOC-01 holds” and one sentence of what you saw, or “DOC-01 fails” and what broke.

A visitor must reach class self-selection in one step and enroll along an open track.

1. From https://techne.coop/ click through to https://techne.coop/participation/ (one step from the front page).
2. Compare the four classes and their costs on the cards.
3. Navigate to https://techne.coop/commons/join/ and confirm the form offers class selection with labels bound to inputs and a live status line.
4. Confirm the legal instrument is linked from the page rather than restated in different words.

Say: “U-10 holds” and one sentence of what you saw, or “U-10 fails” and what broke.

The Share door is parked honestly: it names what is absent and whose act it waits on.

1. Signed in, open the map and find the See your share group; click through to https://techne.coop/intranet/share/.
2. Confirm the page names S-01 and S-02, says the absence is the Board's pending act (not an administrator's withholding), and links the staged counting rules.

Say: “U-07 holds” and one sentence of what you saw, or “U-07 fails” and what broke.

One formation notice, one form: a footer line everywhere, no strips.

1. Open https://techne.coop/legal/ and two or three pages beneath it (counsel memo, corrections).
2. Confirm none carries a formation strip block; each carries the one-line footer notice instead.
3. Open https://techne.coop/legal/#formation and confirm the long-form notice is intact.

Say: “P-12 holds” and one sentence of what you saw, or “P-12 fails” and what broke.

The three module documents agree with the built estate.

1. Open https://techne.coop/commons/patronage/ and confirm the tally surface address it names is /intranet/share/.
2. Open https://techne.coop/commons/treasury/ and confirm the public name it uses matches the treasury door's name in the shell.
3. Confirm each amendment line carries its date and piece address.

Say: “X-13 holds” and one sentence of what you saw, or “X-13 fails” and what broke.

Directions enter by verb only; refusals cite rules. Proven by the RLS probe matrix.

1. Open the A-01 PR or https://github.com/Techne-Co-op/techne.coop/blob/main/commons/authority-map/0017_direction_rail.sql and the probe results.
2. Your standing Direction d6e22f76 entered by verb and lives; a bare-table write was refused in the probe record. Confirm both and cite the Direction id aloud.

Say: “A-01 holds” and one sentence of what you saw, or “A-01 fails” and what broke.

The ledger and validator evolved together; verified entries are byte-stable.

1. Open https://github.com/Techne-Co-op/techne.coop/actions and confirm ledger-validate is green on main's latest run.
2. That green is the acceptance; say that you saw it and its run number.

Say: “L-03 holds” and one sentence of what you saw, or “L-03 fails” and what broke.

The audits have teeth, and the teeth are tested.

1. Open https://github.com/Techne-Co-op/techne.coop/actions latest run: style-lint green includes the almanac audit and its self-test.
2. Open scripts/almanac_audit.py at https://github.com/Techne-Co-op/techne.coop/blob/main/scripts/almanac_audit.py and confirm the self-test exists and CI runs it (verify.yml).

Say: “X-18 holds” and one sentence of what you saw, or “X-18 fails” and what broke.

Twenty-four wrong marks were corrected and the ledger now answers to the repository.

1. Open the X-19 PR and read the correction list.
2. Confirm the almanac audit's third check (branch names against the ledger) is in CI and green; that check is what keeps X-19 true.

Say: “X-19 holds” and one sentence of what you saw, or “X-19 fails” and what broke.

Export views follow the substrate; CI refuses a column left behind.

1. Open https://github.com/Techne-Co-op/techne.coop/actions and confirm db-verify and restore-test are green on main.
2. The refusal case was proven by regression when X-11 landed; find that run or the PR note and say what you read.

Say: “X-11 holds” and one sentence of what you saw, or “X-11 fails” and what broke.

The claim: the estate keeps one dictionary, and a word it has stopped using still answers to the word that replaced it.

1. Open https://techne.coop/commons/build/lexicon/.
2. Look up five words you use in an ordinary week: piece, bed, proof, graft, tally. Each must carry a definition on this page.
3. Scroll to the concordance table and look up two words the cooperative retired: packet, and gate in its old sense. Each must name the word that replaced it. That table is the whole claim: someone reading an old record can still find out what an old word meant.

Say: “L-01 holds” and one sentence of what you saw, or “L-01 fails” and what broke.

The claim: the Almanac speaks the current vocabulary throughout, and a retired word survives on it only inside a quotation of an older record.

1. Open https://techne.coop/commons/build/.
2. Read three bed narrations at ordinary reading speed. You are reading for retired words: packet, slice, gate in its old sense.
3. Then use your browser's find-on-page for the word packet. Every hit must sit inside a quotation of a historical record. A retired word in the page's own voice is the failure; say which one and where.

Say: “L-02 holds” and one sentence of what you saw, or “L-02 fails” and what broke.

The claim: the four companion pages use the Almanac's words with the Almanac's meanings, so a reader does not have to learn the vocabulary twice.

1. Open the four in tabs: /commons/build/gates/, /commons/build/run-through/, /commons/build/instructions/, and /commons/build/launch/.
2. Pick three terms: proof, bed, mark. On each page read one sentence that uses each.
3. Judge as a reader rather than an editor. A page using one of those words in a sense the Almanac does not carry is the failure. Different phrasing is not a failure; a different meaning is.

Say: “L-04 holds” and one sentence of what you saw, or “L-04 fails” and what broke.

The claim: the governing documents define the vocabulary the pages use, so no page leans on a word that is nowhere defined.

1. Open /commons/bp/, /commons/vs/, /commons/prd/, and /commons/series/.
2. Pick three words the estate leans on: piece, acceptance, emission are good candidates.
3. For each, use find-on-page across those four documents until you locate where it is defined. A word you use weekly and cannot find defined anywhere is the failure. Name it.

Say: “L-05 holds” and one sentence of what you saw, or “L-05 fails” and what broke.

The claim: the three module specifications were rewritten into the current vocabulary and published as new versions, and each page says so on its face.

1. Open the three and read the line directly under each title. /commons/patronage/ reads PATRONAGE v0.4; /commons/treasury/ reads TREASURY v0.1.5; /commons/agency/ reads AGY v0.2.
2. Scroll each page to its last line, which carries its own revision history. The patronage tail ends: re-cut August 2026, v0.4 against COUNTING-RULES v2 on issue #212, 2026-08-21. The treasury tail names its own supersession of TREASURY v0.1.4.
3. Read a paragraph of each in the current vocabulary and say whether it reads as one book with the Almanac. You do not need to open a pull request: the acceptance recorded in the ledger was the steward's three merges, and the published versions above are what those merges produced.

Say: “L-06 holds” and one sentence of what you saw, or “L-06 fails” and what broke.

The claim: the Almanac is a reading of the ledger and not a second record, so no page under /commons/build/ may state a count the ledger contradicts.

1. Open https://techne.coop/commons/build/ and write down two numbers you can see on it: how many proofs the proofs list carries, and how many pieces one bed section counts.
2. Signed in, open https://techne.coop/intranet/hud/ in the Maturation view and read the same two figures from the ledger's own side.
3. The two must agree. This is the exact drift the piece was cut to end: the Almanac once narrated seven beds where the ledger held nine, and the instructions counted 52 items where it held 72. A disagreement of any size is the failure; say both numbers aloud.

Say: “X-14 holds” and one sentence of what you saw, or “X-14 fails” and what broke.

The claim: this revision changed the Almanac's framing words only. Not one address, mark, count or citation moved with them.

1. Open https://techne.coop/commons/build/ and read the dek under the title, then the caveat under the dek.
2. Judge the framing: does it read as language someone chose, in the cooperative's own register, rather than interface labels nobody elected?
3. The other half of the claim is that the record underneath was untouched, and X-14 is the card that checks the numbers. If X-14 held, the numbers were not disturbed; say so, and give your verdict here on the framing alone.

Say: “X-15 holds” and one sentence of what you saw, or “X-15 fails” and what broke.

The claim: the three documents a new contributor reads first cite the document versions that actually exist, so nobody is sent to a retired one.

1. Open README.md, CONTRIBUTORS.md and RUN.md. GitHub renders these as ordinary pages; there is no code to read.
2. The current versions are PRD v0.4, BP v2, VS v2, SER v0.3 and ALM v2. The README's map of the estate reads The Common Record Series (SER v0.3) and The Almanac (ALM v2); CONTRIBUTORS and RUN both name BP v2 as the governing contract.
3. Read each document for a citation to any other version. One retired version cited is the failure, because a contributor will follow it. Name the document and the version.

Say: “X-16 holds” and one sentence of what you saw, or “X-16 fails” and what broke.

The claim: every address in the ledger has a card on the Almanac and every card carries the mark the ledger carries, and a check in CI now refuses any drift between them, so this stays true without anyone re-checking by hand.

1. Open https://github.com/Techne-Co-op/techne.coop/actions and open the newest completed run of the verify workflow on main.
2. Open the style-lint job and find the step named the cards answer to the ledger, the ledger to the repository (X-18). Green means that on this commit every address has a card and every mark agrees.
3. Say the run you read and the day it ran. Scale of what the green is holding: when this piece was picked up, fifty of the ledger's addresses carried no card at all, three whole beds among them, and seven cards carried a mark the ledger contradicted.

Say: “X-17 holds” and one sentence of what you saw, or “X-17 fails” and what broke.

The claim: /commons/ shows each capability with the mark the ledger actually holds, unrounded and unflattered, in the current vocabulary.

1. Open https://techne.coop/commons/ and read the four capabilities with the mark each one carries.
2. Signed in, open https://techne.coop/intranet/hud/ in the Maturation view and spot-check three of those marks against the ledger's side. A mark rounded up, or four states flattened into two, is the failure.
3. Back on /commons/, confirm the page names the intranet and states the steered garden reading, and click every link: each must land inside the estate.

Say: “U-21 holds” and one sentence of what you saw, or “U-21 fails” and what broke.

The claim: the fifteen formation conversations were published whole at techne.coop/commonplace, losing no entries and claiming no more authority than the source claims.

1. Open https://techne.coop/commonplace/.
2. Count the movements: there must be five. Spot-read three entries against your memory of the source.
3. Confirm the page states its own standing and names the steward as the author of the lens, and that /commons/ links to it and says what it is. A page that quietly claims more than the source claimed is the failure this card is watching for.

Say: “U-22 holds” and one sentence of what you saw, or “U-22 fails” and what broke.

The claim: the maturity model sits on the legal shelf where a reader can find it, labelled as something the cooperative has not adopted.

1. Open https://techne.coop/legal/maturity-model/ and then its specification subpage. Both must render.
2. Return to https://techne.coop/legal/ and find the Horizon section, placed after the analysis group. Both pages must be linked there.
3. Read the note over them: it must say plainly that these are unadopted. The note is the whole point of the card. Pages that render under a shelf of adopted instruments with no such note is the failure, because a reader will mistake the third thing for the first.

Say: “MM-01 holds” and one sentence of what you saw, or “MM-01 fails” and what broke.

The claim: a member can give a Direction from a page, watch what became of it, and read the rule behind a refusal, with no administrator standing in the middle.

1. Signed in, open https://techne.coop/intranet/direct/.
2. Read your standing Direction on the page (id d6e22f76-d6b0-4805-885e-68d0f90c96a2, given 2026-07-27, kind draft, repository techne.coop), or give a small real one. The page must show its arc from given onward, not merely that it exists.
3. Find where a refusal states its rule, and follow it: the rule text must be reachable from this page. A refusal that says only that something was not allowed is the failure, because a member cannot answer it.

Say: “A-02 holds” and one sentence of what you saw, or “A-02 fails” and what broke.

The claim: the transducer is live at its address and stamps every view with the commit it was cut from, so a reader can tell whether the figures are today's.

1. Signed in, open https://techne.coop/intranet/hud/.
2. Read the stamp line on the view. It names a date and a short commit hash.
3. Open the commit list for main and find that hash. It must be the head of main or within a day of it. A stamp far behind main is the failure; TR-03, further down, is the gate that keeps it close.

Say: “TR-04 holds” and one sentence of what you saw, or “TR-04 fails” and what broke.

The claim: the guided walk can teach someone who has never seen the estate what each view shows and what it refuses to show, in under three minutes.

1. On the HUD, click start here and take the walk end to end. Start a timer when you begin.
2. Three minutes read aloud is the ceiling. Note the time it actually took.
3. At the end, close the walk and say in your own words what each view shows and what it refuses to show. If you cannot, the walk did not teach it, and that is the verdict; the card is about what you retained, not about whether the cards rendered.

Say: “TR-08 holds” and one sentence of what you saw, or “TR-08 fails” and what broke.

The claim: the succession view shows the flat layer and a piece's backward steps plainly enough that a reader finds them without being told where to look.

1. On the HUD, open the Succession view.
2. Without hints from anyone, find the flat layer: the strip under the main figure. Note how long it took you.
3. Open one piece's panel and say aloud what that piece's backward steps were, from the panel alone. Having to be told where to look, or having to go to the ledger to answer, is the failure this card exists to catch.

Say: “TR-10 holds” and one sentence of what you saw, or “TR-10 fails” and what broke.

The claim: the history drawn for a piece is its true history: every state it actually held, in the order it held them, including the times it moved backwards and the times it moved twice in one day.

1. On the Succession view, pick three pieces whose history you remember. Include F-01, which is the recorded case of a piece that went backwards.
2. For each, compare the drawn history against the ledger's dated notes for that piece.
3. Two things must hold, and they are the whole card. A backward step must be drawn as a backward step rather than smoothed away. Two moves on one day must be drawn as two rather than collapsed into one. A tidier history than the record is a wrong history.

Say: “TR-09 holds” and one sentence of what you saw, or “TR-09 fails” and what broke.

The claim: the generator reads the repository alone, with no key and no clock, so the same commit always yields exactly the same cut. The figures cannot shift with who ran it or when.

1. Open Actions and select the transducer-currency workflow.
2. Open any recent run and read the step commit the refreshed cut, if the record moved. A run that prints the cut is already current is the generator regenerating an unmoved record and producing identical bytes: determinism, witnessed on the run page.
3. The controlled proof is quoted here so you do not have to reproduce it. From the record of the transducer work: run today on a fresh clone of the public repository, no key: two runs at 42f1e52, SHA-256 7a98674f, both times, byte-identical. This is a witness step, not a rerun. Say which run you read and what it printed.

Say: “TR-02 holds” and one sentence of what you saw, or “TR-02 fails” and what broke.

The claim: the figures on the transducer cannot go stale quietly. On every merge CI retakes the cut and then refuses to pass if what the page carries does not match the record beside it.

1. In Actions, open the transducer-currency workflow. The newest run must be green.
2. Open that run and read its last step, the audit · the cut beside this commit is current. That step is the gate itself: it prints current: the cut matches the record when the page is fresh, and fails with a STALE message when it is not.
3. A gate that only ever passes proves nothing, so the refusal was demonstrated too, and is quoted here: fresh cut, the check exits 0; seeded stale cut, main's page against a moved record, the check exits 1 with the STALE message; after the gate's own refresh commit, the check exits 0 again. Confirm the green run, say its number, and say that you read the refusal on the record.

Say: “TR-03 holds” and one sentence of what you saw, or “TR-03 fails” and what broke.

The claim: the eleven asks the steward recorded while walking the intranet on 2026-08-07 were answered on the surface, not filed away.

1. Signed out, request a sign-in link. The door must tell you Link sent rather than leaving you wondering whether anything happened.
2. Signed in, confirm there is one directory and no separate Admissions door beside it.
3. Confirm the footer spans the frame, and that the doors on the overview appear in the same order as the map beside them. An order that disagrees with the map is the failure: two orders means a member has to learn both.

Say: “U-15 holds” and one sentence of what you saw, or “U-15 fails” and what broke.

The claim: the two-person script is written well enough that two people who are not its author can walk it end to end without asking anyone a question.

1. Open https://techne.coop/commons/build/walkthrough/ and read act one in full.
2. Judge it as its reader: could you and one other person execute act one exactly as written, with nobody to ask? A beat you would have to resolve by asking the author is the failure; name it.
3. This card is about the script's legibility only. Walking it is its own sitting, and its evidence lands on the three two-person cards further down this page.

Say: “X-21 holds” and one sentence of what you saw, or “X-21 fails” and what broke.

The launch page is the site's front page and must route a visitor everywhere they may need.

1. Navigate to https://techne.coop/ on a desktop browser, signed out.
2. Click the primary hero action. Confirm it lands on the join surface, not a dead anchor.
3. Return. Click each of the three ways-in cards; each must land on the participation surface.
4. Scroll the whole page. Confirm every section of the site you can think of is reachable from here (topbar plus footer links).

Say: “U-09 holds” and one sentence of what you saw, or “U-09 fails” and what broke.

The front door was cut to a hero that reads in one breath plus three sections.

1. Stay on https://techne.coop/. Read the hero aloud; it should be two sentences plus title, countdown, and two actions.
2. Count the sections below the hero. There must be exactly three: the workshop, the ways in, the join card.
3. Click both hero actions; each must scroll or route somewhere real.

Say: “U-14 holds” and one sentence of what you saw, or “U-14 fails” and what broke.

The participation front door should open with an action, not an explanation.

1. Navigate to https://techne.coop/participation/. The first thing under the masthead must be something you can act on.
2. Confirm the four standing questions appear once, in plain words, with statutory terms once beneath them.
3. Confirm the class set is rendered once as cards and once in the table, and nowhere else.

Say: “P-10 holds” and one sentence of what you saw, or “P-10 fails” and what broke.

The claim: the participation front door holds doors and nothing else; everything a visitor might want to study moved to a page behind it.

1. Open https://techne.coop/participation/ and count the sections. Three, with no comparison table, no timeline, and no pathway prose.
2. Confirm you can reach something you can act on without scrolling past anything that is not a door.
3. Open /participation/detail/ and find the table, the two pathways and the timeline. Everything removed from the front door must be here; content lost in the move is the failure, not content moved.
4. Check the footer of both pages and of the front page for the one-line formation notice.

Say: “P-11 holds” and one sentence of what you saw, or “P-11 fails” and what broke.

The claim: the participation content lives in exactly one place, and the legal path points at it rather than keeping a second copy that can drift away from the first.

1. Open /participation/ and then /legal/participation/.
2. The legal path must render a pointer back, not a second copy of the content. Two copies is the exact defect this piece cut out: three live surfaces once described the same four classes and did not agree on the classes or the rates.
3. On /legal/ find the Guild Participation Terms row and confirm it carries a standing mark.
4. Confirm neither page shows a price ladder or any numeric progress toward membership. Membership here is not a score to climb.

Say: “P-09 holds” and one sentence of what you saw, or “P-09 fails” and what broke.

The claim: nothing a member reads carries the build's private shorthand. No piece addresses, no migration numbers, no raw event ids in the words on the page.

1. Signed in, walk the five intranet surfaces: overview, share, record, treasury, programs.
2. Read for leaks. An address like X-14 or U-11, a migration number like 0019, or a raw event id sitting in member-facing copy is the failure. The browser address bar is not member copy; the words on the page are.
3. Then look rather than read: the five must appear to be one product. Same corner radius, same buttons, same focus rings, same headings. A surface that looks like it came from somewhere else is a milder form of the same defect.

Say: “U-11 holds” and one sentence of what you saw, or “U-11 fails” and what broke.

The claim: the estate sets its type in exactly two faces, the serif and the mono, and no third face survives anywhere in the system.

1. Open https://techne.coop/design-system/ and read the typography section. It must name exactly two faces, Libre Baskerville and IBM Plex Mono, and specify no third.
2. On any public page, right-click a heading, choose Inspect, and read the rendered font in the browser's panel. Do the same on a paragraph. A third face, Inter above all, is the failure.
3. If you would rather not open the inspector, compare headings and body text across three pages by eye. A third face is easy to see once you know there should not be one.

Say: “U-12 holds” and one sentence of what you saw, or “U-12 fails” and what broke.

The claim: every public page carries the same single navigation bar, and no page carries a second one of its own.

1. Open five public pages of your choosing, from different parts of the estate.
2. The same slim topbar must render at the top of each. Switch the site between light and dark mode once and confirm it survives both.
3. No page may show a second, page-specific navigation bar beneath or beside it. Two bars is the failure this piece ended: the public pages each carried a hand-rolled bar and no two of them agreed on contents, height, or type size.

Say: “U-13 holds” and one sentence of what you saw, or “U-13 fails” and what broke.

The claim: the framed pages share one text column, so the estate reads as one document rather than nine differently sized ones.

1. Open /commons/ and /legal/, and view each at a narrow window, a laptop width, and full screen.
2. At each width the text column and the gutters must look the same on both pages. One page hemmed in tighter than its neighbour is the failure: nine framed pages once carried four different widths, and the steward could see the two clumps at a glance.
3. At every width, confirm nothing scrolls sideways.

Say: “U-20 holds” and one sentence of what you saw, or “U-20 fails” and what broke.

The claim: on a phone the member's page opens on the page they came for, with the map tucked into a drawer that gets out of the way once used.

1. On your phone, signed in, open https://techne.coop/intranet/.
2. The page must begin under the topbar, not beneath an overlap that hides its first line.
3. Open the map with the Menu control in the topbar, then close it with the same control.
4. Open it once more, tap a destination, and confirm the drawer is not still standing open over the page you landed on. A drawer left open over its own destination is the failure.

Say: “U-06 holds” and one sentence of what you saw, or “U-06 fails” and what broke.

The claim: the members' surfaces behave in one hand. Nothing scrolls sideways, and no field is small enough to make the phone zoom in when you tap it.

1. On your phone, signed in, visit each members' surface at normal zoom.
2. Swipe sideways on each one. Any sideways movement at all is the failure; name the surface.
3. Tap into any input field. If the phone zooms in as the field takes focus, the text is under the 16px floor and the card fails. This is the ordinary expectation of a page held in one hand, and the surface was built and reviewed on a desk.

Say: “U-17 holds” and one sentence of what you saw, or “U-17 fails” and what broke.

The claim: the frame is in the page before any script runs, and a signed-out reader never sees the member map, not even for a single frame.

1. Signed in, hard-reload a members' surface. The topbar and the map must be there immediately, with no flash of a frameless page first.
2. Sign out and load the same URL again. The member map must never appear, not for an instant.
3. The second step is the one that matters: this is a gate, not a decoration. If you ever glimpse the map while signed out, the card fails, and say exactly which surface and what you saw.

Say: “U-19 holds” and one sentence of what you saw, or “U-19 fails” and what broke.

The claim: moving between two pages of the estate now carries a view transition, which it never did before, and the fix is measurable rather than a matter of taste.

1. In a desktop Chromium browser, open https://techne.coop/commons/ and navigate to https://techne.coop/commons/build/. Both are public and both carry the frame, so you do not need to sign in for this card.
2. Watch the topbar as the page changes. It should carry across rather than blink out and back.
3. The measurement is quoted here so you need not take one. From the record of this piece: A navigation between them reports viewTransition: true at pagereveal with the stylesheet present and zero unhandled rejections. Before the change, the same measurement reported no transition and an AbortError every time. If you cannot perceive the transition by eye, say so plainly and rest your verdict on the measurement rather than guessing.

Say: “U-18 holds” and one sentence of what you saw, or “U-18 fails” and what broke.

The claim: the design system documents the patterns the surfaces actually use, and those patterns still work for a reader whose scripts do not run.

1. Open https://techne.coop/design-system/ and find the sections for icons, term hints, disclosure, forms, participation cards, member curve, and states. Each must show its markup, not merely describe it.
2. On a page that uses term hints, disable JavaScript in your browser (on a phone, long-press instead) and confirm the hints still appear on hover and on keyboard focus.
3. Confirm the disclosure pattern is a native details element by opening and closing it with scripts off. A pattern that needs a script before it can be read is the failure.

Say: “U-08 holds” and one sentence of what you saw, or “U-08 fails” and what broke.

The claim: the stories page describes what a person can do today and marks everything else as waiting, rather than describing a system that does not exist yet.

1. Open https://techne.coop/commons/prd/stories/.
2. Find the level machinery and the class personas. Each must read as waiting rather than live.
3. Find the carrier and the path tally. Each must carry its reconciliation note from the corrections of 2026-08-09. Anything stated as live that is not live is the failure, and it is the failure that matters most here, because this page is where a newcomer forms their expectations.

Say: “P-07 holds” and one sentence of what you saw, or “P-07 fails” and what broke.

The claim: every kind of arrival has an honest account of a first sitting, in which each claim either points at a story on the page or names the piece it is waiting on.

1. Stay on /commons/prd/stories/ and read one day-one passage end to end.
2. Take its claims one at a time. For each, the page must either show you the story that backs it or name the piece it waits on. A claim that does neither is the failure; quote it.
3. Find the guild hand-off note and the P3 refusal statement. Both must be visible to a plain reader rather than buried, because both are places the system says no.

Say: “P-08 holds” and one sentence of what you saw, or “P-08 fails” and what broke.

The claim: a member can answer someone else's posting and both of them see the answer. The system refuses a self-response by design, which is exactly why this card needs a second person.

1. You, signed in: open https://techne.coop/commons/postings/ and confirm a real posting is there, or make one.
2. The other person, signed in on their own device: open the same posting and respond to it.
3. They say aloud that they can see their own response.
4. You say aloud that you, the author, can see it too, without anyone telling you where to look. Needing to be told where to look is a partial failure; record that rather than smoothing it over.

Say: “F-02 holds” and one sentence naming who responded, or “F-02 fails” and what broke.

The claim: any member can put a gathering on the calendar, and any other member can register for it. A calendar only one person can write to is not the cooperative's calendar.

1. You, signed in: open https://techne.coop/commons/gatherings/ and schedule a real gathering with a title and a start time.
2. Confirm it appears on the calendar with you named as its host, carrying what it is for and where to stand. Both of those must show; a gathering that cannot say its purpose or its place is half a failure, and say which half.
3. The other person, on their own device: find that gathering and register for it.
4. Both of you confirm aloud that the registration shows.

Say: “G-04 holds” and one sentence covering both clauses, or “G-04 fails” and which clause broke.

The claim: when someone acts on your posting or your gathering the system tells you, and tells only you. The member it does not concern hears nothing.

1. Do this immediately after F-02 and G-04, while both turns are fresh.
2. You, without navigating anywhere: look at the notices panel in the shell. The response and the registration must both be there. Having to go and look for them is the failure.
3. The other person: confirm on their device that they did not receive a notice for an event that does not concern them. That half is the point of the card; a system that notifies everyone has not addressed anyone.
4. One clause of this piece is proven in CI rather than by hand: replaying the whole log on a restore mints no new notices. Witness the green db-verify and restore-test jobs on main in Actions rather than re-running anything, and say that is what you did.

Say: “X-12 holds” and one sentence covering addressed-to and not-addressed-to, or “X-12 fails” and what broke.

An attestation is not a check you run. It is a statement two people make together, on the record, that the Belong bed is whole: B-02, B-04 and B-05 all stand verified.

1. Both of you, at the HUD in the Maturation view, find B-02, B-04 and B-05.
2. Read each mark aloud, in turn. Every one must say verified.
3. If they all do, both of you say the proof address, then attested, then your names and the date. If any piece is short, say the address, then not ready, then which piece is short. Not ready is a correct outcome and closes the card honestly; attesting over a short piece is the only wrong answer here.

Say: “G-B attested” with both names and the date, or “G-B not ready” and which piece is short.

An attestation is not a check you run. It is a statement two people make together, on the record, that the Gather bed is whole: G-03 stands verified, and G-04 is the two-person card you walked above.

1. Both of you, at the HUD in the Maturation view, find G-03 and G-04.
2. Read each mark aloud, in turn. Every one must say verified.
3. If they all do, both of you say the proof address, then attested, then your names and the date. If any piece is short, say the address, then not ready, then which piece is short. Not ready is a correct outcome and closes the card honestly; attesting over a short piece is the only wrong answer here.

Say: “G-G attested” with both names and the date, or “G-G not ready” and which piece is short.

An attestation is not a check you run. It is a statement two people make together, on the record, that the Find bed is whole: F-01, F-02 and F-03 all stand verified. F-02 is the two-person card above, so this proof follows it directly.

1. Both of you, at the HUD in the Maturation view, find F-01, F-02 and F-03.
2. Read each mark aloud, in turn. Every one must say verified.
3. If they all do, both of you say the proof address, then attested, then your names and the date. If any piece is short, say the address, then not ready, then which piece is short. Not ready is a correct outcome and closes the card honestly; attesting over a short piece is the only wrong answer here.

Say: “G-F attested” with both names and the date, or “G-F not ready” and which piece is short.

An attestation is not a check you run. It is a statement two people make together, on the record, that the evolved vocabulary is readable end to end: L-01 through L-06 all stand verified. Five of the six are cards on the tiers above, so this is usually the first proof to ripen.

1. Both of you, at the HUD in the Maturation view, find L-01 through L-06.
2. Read each mark aloud, in turn. Every one must say verified.
3. If they all do, both of you say the proof address, then attested, then your names and the date. If any piece is short, say the address, then not ready, then which piece is short. Not ready is a correct outcome and closes the card honestly; attesting over a short piece is the only wrong answer here.

Say: “G-L attested” with both names and the date, or “G-L not ready” and which piece is short.

An attestation is not a check you run. It is a statement two people make together, on the record, that the cross-cutting bed is whole: X-01 through X-09 all stand verified.

1. Both of you, at the HUD in the Maturation view, find X-01 through X-09.
2. Read each mark aloud, in turn. Every one must say verified.
3. If they all do, both of you say the proof address, then attested, then your names and the date. If any piece is short, say the address, then not ready, then which piece is short. Not ready is a correct outcome and closes the card honestly; attesting over a short piece is the only wrong answer here.

Say: “G-R attested” with both names and the date, or “G-R not ready” and which piece is short.

An attestation is not a check you run. It is a statement two people make together, on the record, that a figure the instrument shows equals the figure two people traced by hand from the repository: TR-04 and TR-05 stand verified, and the tracing agrees.

1. Both of you, at the HUD in the Maturation view, find TR-04 and TR-05.
2. Read each mark aloud, in turn. Every one must say verified.
3. This proof carries one extra act, and it is the whole reason the proof exists. Both of you open the HUD, pick the dwell figure, and trace it by hand from the repository to its source. The traced figure and the shown figure must agree. If they do not, say not ready and say by how much.
4. If they all do, both of you say the proof address, then attested, then your names and the date. If any piece is short, say the address, then not ready, then which piece is short. Not ready is a correct outcome and closes the card honestly; attesting over a short piece is the only wrong answer here.

Say: “G-I attested” with both names and the date, or “G-I not ready” and which piece is short.

The claim: this walk carries everything a walker needs. If you had to ask a person, read source code, or open a pull request to work out what a card wanted, the page failed at the one thing it exists to do.

1. Speak this card last, after every other card is walked or deferred.
2. Say whether at any point you had to go outside this page for an instruction: to ask someone, to read code, or to open a pull request to find out what was meant. Naming the cards is more useful than the verdict.
3. That answer is this card's verdict. A page that sent you elsewhere fails here even if every other card held.

Say: “X-22 holds” and one sentence of what you saw, or “X-22 fails” and what broke.