Working notes

These are the internal strategy documents this project actually runs on — plans, doctrines, audits, independent reviews — published nearly verbatim. We think a project asking a city to think in public should think in public itself, so this is the working shelf, not a cleaned-up summary of it. Redactions, where law or privacy requires them, are visible in place — never silent. Why we publish this way: how we share.

• The master plan — the internal strategy document for the ten thousand conversations: the candidate adoption architecture and the coalition sprint.
• The open-strategy vision — the internal vision document for the open-strategy package, laid out in complete.
• The network doctrine — the internal design doctrine for Block Circles, the organizing space, and every gathering surface, mapped through Permaculture 3.0.
• The Toronto listening project — the intake memo for a listening project: its scope, tensions, phased shape, and the operator's rulings on testimony, consent, and the complaint pipeline.
• The sharing tiers — the internal memo working through why a semi-private "internal commons" repo is unstable, and the three-lane sharing doctrine used instead.
• The sharing architecture — the internal memo on how Civic Tech, and anyone, actually gets our work, and why read-only repo access is the wrong design.
• The unthought map — an internal thinking document mapping what we haven't written, built, needed, or dared yet.
• Can this run without us? The systemization audit — an internal audit answering, verdict and all, whether the organization can run without its founders.
• The tri-seat assessment — one sitting assessed across the Founder, Mobilization, and Research seats together.
• State of the mission — a comprehensive state-of-the-mission review, published nearly verbatim with named redactions.
• An independent model's path to October — a working note tracing the vision's chain from a stranger to a decided city, dated against the October 26 election calendar.
• Candidate capacity & grand challenges — the candidate-capacity thesis held against our law and made operational, published with named redactions.
• The inbound triage ritual — the standing daily walk for corrections, press, invite-me, civic-hour, and partner inbound, plus the rapid-response protocol for a hostile media cycle.
• How this project runs — the operator's guide to running this project, published nearly verbatim with named redactions.
• How this system runs: the canon, part 1 — the canon README and the Founder judgment-seat prompt, published nearly verbatim with named redactions.

More pages join this shelf as they're courted. The full machine-readable corpus lives in the commons.