Grants and their clauses: split, re-order, a Schedule section, a top-to-bottom founding walk (#223, G1–G6)

[edsaperia]

Builds #223 — Ed's rulings G1–G6 of 2026-10-03, every sentence verbatim.

• copy: the setting-names table, the doors' ✒️/🛡️ sentences, the five grant bodies
• G1 / G1b / G2: the ✒️ and 🛡️ clauses in the lead, held-on-some lists, removed when held on none; 🎩 on the Founded line until 🍾
• G3 / G4: Proposals as five clauses ✏️ ⏱️ ⚖️ 👥 🏛️, the quorum as the pass rule
• G5: Schedule (🍾 ⏰ 🥂) above the Text; Decisions goes
• G6: ORDER reads the Rules top to bottom; SURFACE §8/§9
• gates, probes (qa-freeze), walks, card-audit, screenshots

Reports come as QUESTION / REPORT / FINAL comments on this PR.

🤖 Generated with Claude Code

https://claude.ai/code/session_018T9ZX2oB2xxzsK4Tgxpya7

---

Generated by Claude Code

[edsaperia]

QUESTION — three calls I made to build G1/G2/G6 as written. I've built my recommendation in each case and will keep going.

1. 🎩 comes before ✒️ in the walk, so how does it commit? (G6 steps 2–3)
Recommendation: ✓ (no power), as ✋ and 🖼️ do (Q980). Today 🎩 commits with ✒️ and is gated on the accepted pen, so with 🎩 above ✒️ the founding would deadlock: 🎩 holds the pen back, and the pen gates 🎩. The engine's setConvenorMembership asks for no pen, so the only gate was on the page. A ✒️ glyph before ✒️ has been accepted would be a power not yet held (T44). The other option is ✒️ with no gate: same order, but the founder presses a ✒️ they haven't accepted yet.

2. At the birth, who says (that's you!)?
Recommendation: only the two founder clauses, as your Before the save text gives it. The title clause drops its aside (backlog 140) and reads The Founder may amend this at will. Keeping the title's aside too would put it on three clauses in a row (the tic STYLE T10 guards against). This changes STYLE T10's second exception from "the title clause" to "✒️'s and 🛡️'s clauses". founding-walk now asserts the aside is on exactly grant-pen and grant-shield at the birth, and gone after the save.

3. A closed document: do the ✒️ / 🛡️ clauses stand?
Recommendation: no. Since 1541.52 a closed page states no power anywhere: no powers line, and no ✒️ 🛡️ tab. So both founder clauses go at the close, along with each setting's The Founder may amend this… line.

---

Generated by Claude Code

[edsaperia]

REPORT — G1–G6 are built and pushed. Gates and walks are running now.

Built

• The lead: title · link · Founded by [avatar] [name] 👑. (🎩 sits here until 🍾) · the ✒️ clause · the 🛡️ clause · 🌍.
  • Held on some settings, a clause names them from the table. Held on none, the clause and its tab go.
  • The doors take your whole sentences after the settings sentence, e.g. The Founder may ✒️ change the title, the link, … and the text at will. The Founder may invite people at will.
• Proposals: ✏️ (💡) · ⏱️ · ⚖️ (⚖️) · 👥 as the pass rule · 🏛️ (its grant). Each clause wears its own tab.
• Schedule sits above the Text, and Decisions is gone.
  • 🍾: The members are waiting on the Founder to begin., then Members started making proposals at 14:34 on Saturday 3 October.
  • ⏰ and 🥂 follow.
• The 👑 news hangs on ✒️'s clause where the batch laid a ✒️ down and that clause still stands, else on 🛡️'s. Once the power is gone everywhere, it hangs on the Founded line.
• ORDER now reads the Rules top to bottom. The founder-member's 🏛️ comes after 👥; an invitee's and an applicant's still come on arrival.
• The rules files: SURFACE §8/§9; SPEC v0.147 (its one sentence naming the preamble); STYLE T10. spec-check's Y23 check now points at PROPOSAL_CLAUSES.

One choice inside G1b (no question needed): the "held on every setting" test covers the surfaced settings and the two doors only. 🍾 keeps both powers on the retired catalogue keys 🌡️ 🪜 🤖 by design. If they counted, anything could never be true, and they would show up in the list as this.

Green so far: spec-check, lint, typecheck, build, clock-check, demo-check, unit tests (all four workspaces), copy-check after copy-freeze, founding-walk, founder-answers, powers-walk.

Walks re-pointed to the new order (no check dropped or loosened):

• founding-walk: the aside check.
• journey: the rail at the save is now 🎩 ✋ 🖼️, and the 🏛️ body is your text.
• slider-walk: the quorum sentence.
• setup-probe: the scenario follows the walk.

Still to come: the probes after qa:freeze, journey, card-audit at 1600 and 390, merging main, then the FINAL.

---

Generated by Claude Code

[edsaperia]

FINAL: #223's G1–G6 are built. Every check below is green on 0d9ff79, and the merge with origin/main is a no-op.

Screenshots: the Rules, before (main 757d81f) and after

Seed 42 on the dev ladder, seated as the founder with every grant accepted. The shots are cut at the Text's heading. At 390 the task sheet and the dev ⏭ bar are hidden, because a full-page capture would stand them over the Rules. The images are on a side branch, claude/issue-223-grants-clauses-shots, which is not part of this PR.

	before	after
before 🍾, 1600
before 🍾, 390
at 🍾, 1600
at 🍾, 390
closed, 1600
closed, 390

The eight gates (local, 0d9ff79)

All green:

• lint
• typecheck
• test: 781 + 554 + 451 + 32 passed
• spec-check (spec and code agree, including the seat matrix's static half: 43 rows, unread [])
• demo-check
• copy-check (after copy-freeze)
• clock-check (128 cases)
• build

CI's ci job is green on the same head.

Walks and probes

• Probes, after qa:freeze: npm run probe -- --strict (session-probe IDENTICAL; setup-probe 85 steps, 0 diffs) and probe-coverage.
• Founding walks: founding-walk (and --takeback=applications and =chamber), founder-answers, founding-golden (46 steps, re-frozen).
• The rest, run locally: journey, powers-walk, ladder, slider-walk, member-questions-walk, after-begin-walk, invite-walk, toc-travel.
• card-audit, --strict --kinds=GRAMMAR_KINDS: 0 findings at 1600 and 0 at 390, for the fast pass and the sprint tier's full pass alike.
• CI on 0d9ff79: every push job green. I ran the sprint tier by hand (run 37143991771) and every group was green: seat-member, seat-clerk, sprint-doors, sprint-motions, sprint-pages, and golden (founding-golden, card-audit 1600/390, a11y).

Checks that moved with the rulings (re-pointed, none loosened or dropped)

• spec-check: Y23's PROPOSAL_CHIPS check now holds PROPOSAL_CLAUSES against SURFACE's Proposals run and SEC.rate.keys. The lead's host map gains 🎩 and loses 🏛️.
• founding-walk: the birth's (that's you!) is asserted on exactly ✒️'s and 🛡️'s clauses (QUESTION 2).
• journey: the rail at the save is 🎩 ✋ 🖼️, and the member's 🏛️ body is your text.
• ladder: Q1503's locked-🎩 read became G2b's check: no 🎩 tab or entry after 🍾.
• member-questions-walk: 🏛️ rides its own Proposals clause.
• slider-walk: the quorum blocks use the pass-rule sentence.
• setup-probe: the scenario walks the Rules top to bottom. 💡 and ⚖️ are now opened by their own tabs.
• The copy golden walks 274 cards, not 276. The two gone are 🎩 after 🍾, on the seat:1 and settled walks, which G2b hides.

Flagged, not changed

• The doors' 🛡️ verb is block … that the membership have decided to make, while the settings' verb is refuse … the membership pass. Both are yours as written; I didn't merge them.
• The visibility name: your example lists say "visibility". The clause uses the table's the visibility rule.
• 🥂's count: [N] members have signed agrees with one, so it reads 1 member has signed. at N = 1.
• Typography only: (that's you!) and it's use the page's curly apostrophe (’), as every surface string does.
• The cap in ⏱️'s clause is the mechanism's fixed 3 (RATE_START.cap, SPEC §7).
• Left as they were: the delegated ⏰ option still says …or may be made perpetually, and the engine's meaning.ts still has the old quorum sentence. Neither is in your text, and no surface reads the engine one.
• QUESTIONS 1–3 above (🎩's ✓ commit, where the birth aside goes, no founder clauses on a closed page) are built as I recommended there.

Ledger text (uncommitted)

CHANGELOG.md, a new top section, plus a one-word edit to the intro: v0.146 today → v0.147 today.

## 2026-10-03: the Rules, re-laid

### Changed
- **The Founder's powers each have a sentence of their own**, under the *Founded by* line: one for ✒️, saying what the Founder may change at will, and one for 🛡️, saying what they may refuse. Where the Founder keeps a power on only some settings, the sentence names them. Where they have given a power up everywhere, its sentence and its tab are gone.
- **🎩 *Is the Founder a Member?* sits by the Founder** on the *Founded by* line, and is answered before Founder Actions are accepted. It is hidden once the document begins; the members list says the rest.
- **Proposals is five sentences, one per power**: proposing ✏️, the proposal rate ⏱️, voting ⚖️, the quorum 👥 (now the rule that says when a ✏️ proposal passes), and constitutional proposals 🏛️. Each of 💡, ⚖️ and 🏛️ wears its tab on its own sentence.
- **A new last section of the Rules, Schedule**, just above the text, holds 🍾 (when proposals began), ⏰ (until when they may be made) and 🥂 (when they closed, and how many have signed). The Decisions section is gone.
- **The founding reads the Rules top to bottom**, in the order they appear on the page.
- The grant cards for ✒️ 🛡️ 🏛️ 💡 ⚖️ have new wording, and the power cards name their settings the way the Rules do (*the quorum*, *anonymity of proposals*, *anonymity of votes*, *the end time*).

### For contributors
- **SPEC v0.147** (one sentence of §9.7's power-clause note); **SURFACE §8** (`ORDER`, the band table, F16, F20, F22; Y21 and Y23 retired) and §9's grant, gate, 🍾 and 🎩 rows; **STYLE T10**'s birth aside now sits on the two founder clauses (issue #223, Ed's G1–G6).
- `design/session-view.html`: `founderPowerClause`, `releaseHostOf`, `gateClause`, `PROPOSAL_CLAUSES`, the `schedule` section; `PROPOSAL_CHIPS`, `proposalsClause` and the preamble's copy retired. Every new sentence is in `design/copy.js` under `page.clause`.
- `spec-check` holds `PROPOSAL_CLAUSES` against SURFACE's Proposals run and `SEC.rate.keys`, replacing the Y23 check. `founding-walk`, `journey`, `slider-walk` and the setup-probe walk the new order; the setup reference and the copy goldens are re-frozen.

design/DECISIONS.md, appended:

## Grants and their clauses — issue #223, Ed's G1–G6 (2026-10-03)

Ed's rulings of 2026-10-03, questions G1–G6 on his page (02:14–02:23 UTC), the clause text edited in a doc (16:59), follow-ups at 17:02–17:10. Built in PR #224.

**What it replaced.** Since Q639 (a) (Ed, 2026-08-22) ✒️ and 🛡️ wrote no sentence: their tabs stood on the Founded line, and *what the Founder holds* was said only setting by setting (`holderLine`) and on the wallet's tooltip. The count clause (*The Founder holds the pen on 16 settings.*) had been retired as the third telling of one fact, and the one that went stale. 🏛️ joined the Founded line with Q1365. Since Q748–Q750 (Y21, Y23) the Proposals section opened with one preamble of three sentences, built from fragments, wearing 🍾 💡 ⚖️ and the 👑 news in one stack; the 👑 news stood there because a release batch belonged to no clause (entry 162). The Founded line carried the moment of 🍾 (*at [time] on [date]*). 🎩 stood on *Members*. The quorum stood in Decisions with ⏰ and 🥂.

**G1 / G1b.** Each power gets its own clause in the lead, under the Founded line, wearing its grant and the 👑 news that laid it down. Where the power is held on some settings, the clause names them, from one table of setting names that the power cards' own sentences read too. Where it is held on none, the clause and its tab go. The count's old objection (that it went stale) does not hold for a list derived from `pwPair` on every render. Built: the list covers the settings the surface names and the two doors. The catalogue keys no card asks about (🌡️ 🪜 🤖), on which 🍾 keeps both powers by design, are left out, or *held everywhere* could never be true. The doors take Ed's whole sentences after the settings sentence. A 👑 batch hangs on ✒️'s clause where it laid a ✒️ down and that clause still stands, else on 🛡️'s on the same test, else on the Founded line (*the 👑 news for the last power laid down*). A closed document states neither clause, under 1541.52's *no power stated on a closed page*.

**G2 / G2b.** 🎩 is a fact about membership but sits by the Founder, on the Founded line, and is hidden at 🍾. It writes no sentence, since the members list shows the answer. The exception row for *the locked 🎩 read post-start* (Q1541 stage 3b) is retired with it. Because the walk (G6) puts 🎩 before ✒️, 🎩 commits with ✓ and no power, as ✋ and 🖼️ do (Q980). Its ✒️ commit had been gated on the accepted pen, which would have deadlocked the founding. The engine's `setConvenorMembership` never asked for a pen. This is QUESTION 1 on #224.

**G3 / G4.** The preamble becomes one clause per power, ✏️ ⏱️ ⚖️ 👥 🏛️. The quorum becomes the pass rule (*A ✏️ proposal passes once at least …*, Ed's wording at 17:10) and moves from Decisions to Proposals. 💡 and ⚖️ clauses read *When the document begins, …* before 🍾. Y21's and Y23's reasoning (*the four state one rule together*) is superseded by Ed's *one clause per power*. `spec-check`'s Y23 check, `PROPOSAL_CHIPS` against the band prose, is re-pointed at `PROPOSAL_CLAUSES` and `SEC.rate.keys`.

**G5.** A new last section of the Rules, *Schedule*, holds 🍾 ⏰ 🥂, and Decisions goes. 🍾's clause carries the moment the Founded line used to carry (*Members started making proposals at [14:02] on [Friday 2 October].*). Before the press it reads *The members are waiting on the Founder to begin.* 🥂's verb agrees with one signature (*1 member has signed*), a reading of *[N] members have signed*, flagged in the FINAL.

**G6.** `ORDER` reads the Rules top to bottom: 🪶 📍 📧 (✋ 🖼️), 🎩, ✒️, 🛡️, 🌍, 🪪 🤝 💤 🥾, 💡 ⏱️ ⚖️ 👥 🏛️, 👤 👁️, ⏰, 📝, 🍾. The founder-member's 🏛️ moves from the save (Q1365, F20) to its place after 👥. An invitee's and an applicant's stays at arrival (`early`, now non-founders only). `BEGIN_ROWS` follows (⏰ after 👁️).

**The birth's aside.** G1's *Before the save* clauses carry *(that's you!)*, so the title clause gives it up (backlog 140, entry 140; STYLE T10's second exception moves). Three in a row would be the tic T10 guards against. This is QUESTION 2 on #224. `founding-walk` asserts the aside on exactly ✒️'s and 🛡️'s clauses at the birth.

**Flagged, not changed.** The doors' 🛡️ verb is *block … that the membership have decided to make*, while the settings' verb is *refuse … the membership pass*. The difference is Ed's.

---

Generated by Claude Code

[edsaperia]

COORDINATOR: Ed's answers to your three calls (20:01 UTC):

1. 🎩 commits with a plain ✓. As built.
2. (that's you!) changes. Ed: "It should only be on the Title clause during the birth - the first place you see 'The Founder', not anywhere else." This overrides the Before the save lines in Grants and their clauses: split, re-order, a Schedule section, and a top-to-bottom founding walk (G1–G6) #223's brief.
   • At the birth, the ✒️ and 🛡️ clauses read The Founder may ✒️ change anything at will. and The Founder may 🛡️ refuse proposals the membership pass., with no aside.
   • The title's clause keeps The Founder (that's you!) may amend this at will., as on main.
   • Put STYLE T10's exception back as it was.
   • Re-point founding-walk's assertion so the aside is on exactly the title clause at the birth.
   • Re-freeze the copy golden and the setup reference for this change only.
3. Closed page: waiting on Ed. Keep it as built for now.

Please push the change, re-run the eight gates, founding-walk, the setup-probe --strict and copy-check, then post a short REPORT. Ed's Merge comes after.

---

Generated by Claude Code

[edsaperia]

COORDINATOR: Ed has answered your call 3: the founder clauses go on a closed page, as built. Nothing changes for 3. Only the move of (that's you!) in my comment above remains.

---

Generated by Claude Code

[edsaperia]

REPORT: Ed's answers are in, at d16f9b0.

2. (that's you!) is back on the title clause alone at the birth.

• At the birth the ✒️ and 🛡️ clauses read The Founder may ✒️ change anything at will. and The Founder may 🛡️ refuse proposals the membership pass., with no aside.
• The title clause reads The Founder (that’s you!) may amend this at will., as on main.
• STYLE T10's second exception and founding-walk's title-alone assertion are now identical to main.
• Re-frozen for this change only:
  • the copy-source golden (the two birth strings)
  • the founding golden (the birth clauses)
  • the setup reference (copy.js, session-view.html)
• The card-copy golden did not move: none of the walked cards reads a birth clause.

1. 🎩 keeps its ✓ commit, unchanged. 3. The closed page is as built, while Ed decides.

Checks on d16f9b0:

• Eight gates green:
  • lint
  • typecheck
  • test (781 + 554 + 451 + 32)
  • spec-check (spec and code agree)
  • demo-check
  • copy-check
  • clock-check (128)
  • build
• founding-walk: page errors: none, with the aside on the title alone.
• founding-golden: 46 steps match.
• npm run probe -- --strict: session-probe IDENTICAL; setup-probe 85 steps, 0 diffs.

origin/main is still 757d81f, so there is nothing to merge. One line of the DECISIONS ledger text in the FINAL changes: drop the paragraph The birth's aside. and add to G1 / G1b: At the birth the two clauses carry no aside: Ed kept (that's you!) on the title clause alone (2026-10-03, 20:01, on #224), overriding #223's Before the save lines. In the CHANGELOG's For contributors line, drop STYLE T10's birth aside now sits on the two founder clauses.

---

Generated by Claude Code

[edsaperia]

REPORT: an addendum to the report above. Call 3 is settled, not pending: the founder clauses go on a closed page, as built. I changed no code for it. All three calls are now resolved at d16f9b0, and the PR is ready for Ed's merge.

---

Generated by Claude Code