Working notes — an internal strategy document, published nearly verbatim. Expect apparatus: decision codes, board references, the planning seat’s first-person voice. Why we publish our working documents: how we share.
MASTER PLAN — THE BIG CONVERSATION
10,000 conversations → one big conversation → the plan, the candidates who adopt it, the coalition that sprints
v0.1 · 2026-08-05 · Mobilization Jane, lead orchestrator (operator: “coordinate and orchestrate… go go go” — banked verbatim, OPERATOR_LOG, 2026-08-05; run-until-completion granted for planning/orchestration; every send stays operator-only; every publish click stays yours). This plan SUPERSEDES nothing — it sits above the website plan and mobilization plan as their mission layer, and absorbs ALL your inventory stars/notes (synced 2026-08-05) into one priority queue.
§0. The mission, absorbed (your words, made operational)
| Goal | Target | Measured how |
|---|---|---|
| G1 · The conversations | 10,000 smaller conversations across Toronto in 3 months (by ~Nov 5) | rooms/kits/circles/online threads counted in aggregate — the conversation counter; a “conversation” = any gathering or thread that returns a harvest (vision · complaint · nomination) |
| G2 · One Big Conversation | the city-scale synthesis moment, ~mid-October | Polis-class opinion mapping over the harvest + State of the Conversation published; independent inputs first, deliberation second (§13.9 wiring) |
| G3 · The plan | collectively-agreed plan; worked on by tens of thousands; discussed by 1M+ (2M target) | co-authors = signers + submitters + room participants + Polis voters (aggregate); discussed = reach tier (media, embeds, shares) — targets always labeled TARGETS, never claimed as counts |
| G4 · The candidates | a suite of candidates who agree to implement the plan | the ADOPTION architecture (§1) — candidates publicly adopt; we publish the record |
| G5 · The coalition | 1,000+ organizations agreeing to sprint the next year together | the coalition ladder (§5): pin → kit → quest → sprint covenant |
Tech naming ruling (your “mention pol.is? not sure”): internally yes — Polis is the named instrument for G2 (proven, open-source, embeddable, exactly the independent-inputs tool the canon’s §13.9 wiring wants; Decidim/CONSUL stay deferred until a partner needs them). Publicly, not yet — public copy says “proven open tools used by Taiwan, Barcelona and hundreds of governments” until our own pilot runs clean. Naming a tool before we’ve run it invites a gotcha; naming it after is a receipt.
§1. “Candidates we support” — the architecture that survives the firewall
STATUS: RATIFIED (operator, 2026-08-05, verbatim “approved, go” — banked OPERATOR_LOG). The adoption model below is law for G4; D-mint owed at the next Founder sitting.
Your goal, held against the constitution (commons endorses no one, serves all identically; a recorded standing decision; nobody elected us): the compliant, stronger form is adoption, not endorsement:
- The crowd’s plan is published with the same receipts discipline as everything else.
- Every candidate in every race receives it identically, with one equal question: “Will you commit to implementing the people’s plan — and which parts?” (This is Answer Day, aimed at the plan.)
- Adoption is public, candidate-by-candidate, in their own words — never a ranking, never an endorsement from us. The “suite of candidates” is self-assembling: whoever adopts, is the suite. The crowd supports the plan; candidates earn the crowd by adopting it.
- Any activity beyond publishing the record (posters naming adopters, “vote for adopters” messaging) is a different legal animal — that’s the ⚖️ MEA third-party question, which your note routes to the counsel package. Consequence of this mission: the counsel package should fire within ~2 weeks, not “eventually.” Until counsel clears it, we publish records; we do not campaign.
- Added to the counsel-package question set 2026-08-06 (S2 sitting), for the S4 governance sitting to carry: under the MEA and related law, what are the boundaries on candidates coordinating among themselves (mutual withdrawal, cross-endorsement), and separately on a third party discussing, describing, facilitating, or reporting on such coordination — where does neutral reporting of candidate conduct end and participation begin? Asked to know where the line is, not because anything is planned near it: the standing law is unchanged and absolute — the commons endorses no one, convenes nothing, and publishes records only.
This is also strictly more powerful than endorsement: an endorsement is our opinion; an adoption record is their commitment, on the record, enforceable at the ballot box and reviewable all term.
§2. The honest math (internal, so the targets stay credible)
- 10,000 conversations ≈ 110/day for 90 days. Connector visits supply ~150 total — irrelevant at this scale. The engine is: kits × existing gatherings × replication. Toronto already HOLDS thousands of gatherings weekly (congregations alone ≈ thousands; add teams, meetups, classes, dinners). We are not creating 10,000 events; we are converting a fraction of existing ones into harvesting conversations + seeding new circles. Conversion needs: kits everywhere (P0), the counter visible, the harvest trivially easy (one QR → one form), and org adoption (G5 drives G1).
- Tens of thousands co-authoring = signatures + vision submissions + room harvests + Polis participants. Festival-sized crowd (canon) ≈ 20–50k: consistent.
- 1M+ discussing = reach, not participation: media cycles (the X-plays), embeds, shares, diaspora channels. 2M = stretch. Never published as a claim — published as an invitation (“help us get to…”).
- 1,000 orgs = registry holds ~1,016 verified rows TODAY. The ask ladder starts at a pin (zero-cost). This is the most achievable number on the board — and the one that makes G1 arithmetic work (1,000 orgs × 10 conversations each = G1 done).
§3. The workstream map — eight lanes, one queue (your stars set the order)
| # | Lane | Owner (chat) | P0 work (from your stars) | State |
|---|---|---|---|---|
| L1 | Site & funnel | Code Jane (running 3-day build) | rail · /now · analytics ★★★★ · og:images ★ · widgets · deploy paste LIVE check | day 1–3 in flight |
| L2 | Publish train | Render Jane — boot P2 | SOTE render ASAP (your !!nb) · voice pieces staged for your 1-by-1 walk · content_src staged · open-data publish (your word given) · turnout fire (proceed-all) · press kit ★★ · biweekly hub template | RAN 2026-08-05; trued 2026-08-07: the original 10-word publish menu is ✅ LIVE end-to-end; the menu’s open words are now ONT-SOTE / ONT-BASELINE (staged 2026-08-07) · voice walk rows 1–11 superseded by the improvement-pass report — one batch awaits the operator’s ruling; rows 12–19 still await their one-word walk |
| L3 | Elections sprint | Elections Jane — boot P1 | finish candidate research (web-hunt FIRES) · question bank REDO (“these 66 questions suck”) · kit publish ★★★ · ward math cards ★★★ · ward data packs ★★ · acclamation nation ★★★ · 0/70 verified-Toronto-only → ready · non-frontrunner profiles ★ (your add) · trustee spotlight | RUN 2026-08-05 ×5 acts (lane report); QBank 300 (awaits redline) · profiles+census+pilot+cards built · hunt = cost-ladder pipeline (Stage-1 audit FAILED honestly → Code rework; Wave-1 APPLIED, researched 1,300) · drafts refreshed, 0/70 escalated (newer census — operator call) |
| L4 | Conversation engine | Deliberation Jane — boot P3 | the G1/G2 core: kit suite (dinner · Debate-in-a-box · Assemblies-in-a-box, your nb) · Polis pilot · harvest intake · conversation counter · One Big Conversation design · civic-hour early ask (your nb: encourage time-off requests NOW) · deliberation charter ★★★★ | RAN 2026-08-05 — 6 kits staged + catalyst-checked · harvest spec build-ready (deploy-dark, custodian-gated) · Polis CONDITIONAL GO, real pilot W2 (report) · OBC designed · civic-hour ask staged operator-only (draft) · cont. same day (kits APPROVED-AS-IS): harvest spec v1.1 (deeper door: experts/reports/futures + classroom mode, one of this library's own project records→Sept 1) · toolkit eval — KISS = online annex (shipped) + Your Priorities async; kit cap ~10 · W2 wave FIRED on “continue”: classroom futures (one of this library's own project records, Sept-1) + complaint clinic staged — 9 of ~10 kits; W3 on demand · ALL APPROVED 2026-08-05 — verify pass done, fixes landed, MEA s.50 analysis on file (civic-hour un-gated from counsel), publish rides one paste |
| L5 | Writing desk | this review drafts, you redline | one-year sprint scenario ★★★★★ (the top star — I draft next sitting) · seven-in-ten letter ★★★ · how-to-read-a-platform ★★ · what-a-mayor-can-do ★★ · missing-infrastructure ★ · 18-AIs piece (+your homeless-voice frame) · re-queued 2026-08-06 (reconciliation): PC3 essays — LETTER_TO_A_STEWARD + 3 companions (AUTHORS_EXIT_DRAFT, GLOBAL_RESONANCE, AUTHORS_PRINCIPLES_REFLECTION) — dropped by the runbook §3b correction as “intentionally ignored,” RULED GO 2026-08-06 (operator, chat) — BUILT 2026-08-06: all four staged (not deployed) as a cross-linked set at site/letter-to-a-steward.html + companions · THE_THESIS — RULED + RENDERED 2026-08-06: historical render staged at site/the-thesis.html, publish word THESIS | scenario SEALED (v0.5, S5 2026-08-06) · covenant SEALED + LIVE (v0.1 redlined all-six-as-drafted at S8, independent verification 6/6, live at /plan/covenant and signable PDF since the 2026-08-06 deploy) · seven-in-ten rides its high-effort paste · THE_THESIS staged (above) · PC3 essays GO’d and staged (above) |
| L6 | Futures & thought pieces | Research Jane — P4 RAN 2026-08-05 (final report) | library FINAL: windows re-verified, registers worked to a disposition ledger, ladders registered in LINEAGE, companion STAGED at site/futures/ behind your publish word · Kimi review dispatch staged | ✅ PUBLISHED (your word, 2026-08-05) — review ran (PUBLISH-AFTER-FIXES) → ride applied → H1 approved & carried → banners down, 9 pages badged PUBLISHED; L1 lane owes: /futures nav link + deploy-live check · Kimi dispatch staged for K3’s return · Wayback sweep staged | next: P1 queue (AI set → |
| L7 | Coalition & tribes | this review + your sends | pins-before-people (S1) · campus co-publication ★★★ · coalition ladder (§5) · owed-respect letters staged · faith/festival calendar ★ | owed-respect letters DRAFTED 2026-08-06 (staged operator-only) · faith calendar DONE · pins play UNBLOCKED 2026-08-06 — tribe map ruled public at org level (a recorded standing decision, S8; stale “blocked on S4” line corrected at the S4 sitting) · sends staged, operator-only · org-directory render BUILT 2026-08-06, stopped at B3 (v0.1; six-pass gate clean) — publish word + IA placement + ~12 description judgment calls are the operator’s · tribes/orgs data-architecture memo PROPOSED — names the missing G5 coalition-ladder tracker (pin→host→quest→covenant has no data home) |
| L8 | Sharing/commons | landed by parallel sitting | commons repo push (your paste) · public shelf · projects index — canon-presentation question (your “how do we want to present this?”) answered in L2’s process page + shelf | ✅ pushed + LIVE 2026-08-05 (cee8879, a recorded standing decision; cell corrected 2026-08-06 CURATOR pass — was “awaiting your push”) |
| # | Lane | Owner (chat) | P0 work (from your stars) | State |
|---|---|---|---|---|
| L9 | School week (the Sept-1 bundle) | School-Week Jane — boot | §6 W4’s hard deadline: campus/orientation kit · print pack v1 BUILT · WhatsApp share cards · bundle index · distribution prep | COMPLETE 2026-08-05, 27 days early — bundle (index · staging · lane report): tenth kit NEW + 20 library-printable PDFs + 30 share cards, all ratified-copy-only, zero facts → no re-stamp owed after Aug 21. Nothing sent. Operator: a print shop only if he wants volume |
| L10 | Experts & expert conversations | this review, named 2026-08-06 (was in no lane) | ★★★ Experts (research/experts/) + ★ expert outreach kit (outreach/EXPERT_OUTREACH_KIT.md + 18 domain briefs) — scoped in one-page memo: LETTER_TO_THE_BUILDER proposed as front door (pending S6), harvest intake’s expert_opinion class (spec §2a) is the standing route into the expert registry, feeds the OBC synthesis window | NOT SURFACED until 2026-08-06 (reconciliation §1.4–5) — memo written, lane named; first send is your word, operator-only |
Fire order for the four pastes: P1 elections → P3 conversation engine → P2 publish train → P4 futures (P1 unblocks the most starred items; P3 is the mission’s heart; P2 rides their outputs; P4 is parallel-safe anytime). All four can run simultaneously in separate windows if you prefer — they’re write-path disjoint by design.
§4. The unified priority queue (every ★ you gave, one list)
P0 (this week): one-year sprint scenario ★★★★★ · analytics ★★★★ · deliberation/
conversation engine ★★★★ · SOTE ASAP · elections lane ★★★ (kit publish, research finish,
question-bank redo) · seven-in-ten ★★★ · ward cards ★★★ · acclamation ★★★ · 0/70 ★★★
(Toronto-confirmed) · campus co-pub ★★★ prep · civic-hour ask (early per your nb).
P1 (next): press kit ★★ · ward data packs ★★ · how-to-read ★★ · mayor-powers ★★ ·
green pill ★★ · poster system ★★ · futures ★★ finalize · canon-presentation answer.
P2: all single-★ items, sequenced inside their lanes. Killed/held per your notes:
WhatsApp cards wait on print pack · MEA in counsel package · STATEMENTS_SEED kill-candidate
(your walk) · money/standards pages INTERNAL.
§5. The coalition ladder (G5) — how 1,000 orgs happens
PIN (map presence, zero-cost — the S1 play, starts with the 108 anchors) → HOST (one kit conversation in their room, their name) → QUEST (adopt one of the Six for the 6ix with a scoreboard) → SPRINT COVENANT (the year-one commitment: “we will point at the same goals at the same time” — the narrative’s own What-If, made signable). Each rung is one ask, one receipt; orgs climb at their own pace; the count of each rung publishes aggregate. The covenant text is an L5 writing-desk deliverable (rides the one-year sprint scenario — they’re the same document seen from two sides).
§6. The calendar, one line per week (Aug 5 → Nov 5)
W1 (now): builds land · deploy live · SOTE + kit published · pastes fired · civic-hour ask drafted. W2 (Aug 10–17): owed-respect sends · question bank v2 · Polis pilot · press kit · counsel package fires · school-facing assets in production (classroom pack · campus kits · orientation-fair materials · block-circle starters in volume). W3 (Aug 17–24): Aug 21 field final → SOC registrar edition · campus co-pub locked · kits in the wild — first self-convened conversations. W4 (Aug 24–Sept 1): SEPT-1 HARD DEADLINE — every school-facing asset READY (operator redline 2026-08-05: the first week of school is the year’s biggest mobilization moment; after Aug 21 this is the estate’s hardest date). W5 (Sept 7–14): SPRINT IGNITION at first week of school — ALL SIX QUESTS LAUNCH SIMULTANEOUSLY as evolving threads (the braid, per the scenario v0.2), six scoreboards live · campus + K-12 + multiplier doors open on the live count. W6–8 (Sept 14–Oct 12): the six weeks of wins (canon dates) · conversation counter public · coalition pins → hosts · harvest window · Polis mass moment building · adoption question delivered (post-counsel) · biweekly editions drum. W9–10 (mid–late Oct): One Big Conversation + State of the Conversation published · adoption record public · Oct 26 = MID-SPRINT scoreboard — the sprint is already six weeks old and does not pause. W11+ (Nov→): covenant renewed with the new council · winter braid (Friendliest/Safest lead) · the sprint year runs school-year-shaped, September to September — G1’s 10,000 completes across the full window, not by election day. The 2027 fall arc (scenario v0.3, operator-redlined): Sept 2027 second ignition (self-lighting) + coalition votes year-two quests · Oct 2027 the reckoning (adoption record vs year-one receipts; second State of the Conversation) · Nov 2027 seed-packing (export kits, translations, world invitations) · Dec 2027 earned rest — by design, scoreboards paused · Jan 2028 the sporing (M3 activates).
§7. Standing discipline for every lane (unchanged, restated once)
Sends operator-only · publish clicks yours · equip never convene · identical-to-all for anything candidate-facing · aggregate-only measurement · targets labeled targets · receipts everywhere · the clock bends, the consent rule doesn’t.
§8. What I need from you (the whole list)
SUPERSEDED 2026-08-05 by the operator’s process ruling (banked, OPERATOR_LOG): decisions ship as one-chat sittings run to completion, never as this kind of list. The live surface is the OPERATOR RUNBOOK — seven sittings with ready pastes, fire order, two-minute items, and the already-ruled ledger. (This section’s original six items are all absorbed: P1–P4 ran; publish words ruled and riding S1’s deploy; custodian + adoption architecture live in S4/§4 of the runbook.)