THE OPEN STRATEGY PACKAGE — a vision, in complete

2026-08-07 · Open Strategy Jane (same sitting as the tier map). The operator asked for my thoughts in complete; this is them — offered thinking, PROPOSED, binding nothing. It sits above the package's parts and says what the whole is FOR, where it should go over the year, what could break it, and what it becomes at full ambition.

§1 · What this package actually is

Three things at once, and the order matters.

First, it is the constitution made visible. The movement's deepest claims — nothing to join, nobody anointed, records not endorsements, equip never convene — are all claims about how power is held. Claims like that cannot be verified by assertion; they can only be verified by inspection. The package is the inspection surface. When the whole playbook is public, "we hold no hidden power" stops being a promise and becomes a checkable fact, the same way the ledger made "we tell the truth" checkable. That is why publishing the strategy isn't a communications choice bolted onto the strategy — it is the strategy's own proof obligation, finally discharged.

Second, it is a transfer of agency, not a description of one. The test every piece was written against — could someone run this without asking our permission? — is the whole design brief. Internal docs explain what we did; the package equips what the reader does next. Every piece ends at a live door because a playbook that ends in applause has failed; it must end in a hand on a steering wheel. The measure of the package is never pageviews. It is: rooms convened that we never touched, forks we learn about after the fact, a candidate record published in a town we've never named. The first self-convened anything, anywhere, traceable to a page in this set, is the package working. Everything else is preamble.

Third, it is the export object. The scenario's final act was always the sporing — blueprints leaving Toronto as gifts, carried by people who love both ends of the journey. The open-strategy set plus the methods codex IS that cargo, in its first honest version. Toronto is the demonstration; the package is what travels. This means the package should be built to the standard of luggage, not furniture: versioned, translatable, city-parts clearly marked swap this for yours.

§2 · Why the bet works (the mechanisms, named)

Openness is the only credible companion to anonymity. The founding steward publishes no name. That restraint is only trustworthy if everything else is radically open — an anonymous author with a hidden playbook is a conspiracy; an anonymous author whose complete method survives public audit is a working demonstration that the work is the author. The identity firewall and the open strategy are one design, load-bearing in both directions.

None of our moves require surprise. This is the quiet structural fact that makes the bet safe: every tactic in the corpus is consent-based, identical-to-all, and announced-by-nature (invitations, open kits, identical questions, published records). A strategy that dies when pre-announced is a strategy built on asymmetric information — we don't own one. The one class that ever needed discretion — send timing, personal logistics, persons — is exactly the class the tier map keeps home. We publish the game, never the pieces in motion.

Scrutiny becomes distribution. A hostile reader who wants to expose the playbook must explain the playbook. There is no framing of "they equip existing rooms, publish every candidate's own words identically, and beg you to fact-check them" that functions as an attack. The most efficient critic of this package is doing our outreach.

Preemption is victory. The nightmare scenario for a normal campaign — an opponent steals the strategy and runs it first — is our win condition, verbatim. If a party, a rival group, or a bored city clones the conversation architecture, Toronto gets more conversations. The package is capture-proof because the goal was never market share; it was the practice existing. This is the deepest sense in which the crowd leads: we built a strategy whose theft is its success.

§3 · The package across the year (what it's doing in each act)

Now → the walk (August): the package is a shelf — ruled, rendered, exported. Its job is to exist before September's collective deep breath, so the year's biggest mobilization moment finds the whole method already public. Nobody who asks "what is this?" in September should meet a brochure; they should meet the machine room with the door open.

September (ignition): the package is curriculum. Orientation tables, kits, campus co-publication — every distribution surface should carry one pointer back to the open strategy, because the September ask ("host one conversation") converts best when the asked can see the whole picture behind the small ask. The connector's answer to the hardest room-question — "what's really behind this?" — becomes a URL and a shrug: all of it, publicly, go check.

October (the Big Conversation and Answer Day): the package is legitimacy infrastructure. This is the month hostile attention arrives if it ever does, and the month the movement's neutrality claims bear real weight. When a candidate's team, a newsroom, or a suspicious moderator asks who we are and what we're playing at, the rapid-response posture rests on the package: one written statement, and beneath it the entire published method as the receipt. You cannot astroturf in a glass building; being visibly method-transparent in October is worth more than any October messaging.

November onward (the covenant year and the export): the package is the seed. The reckoning-and-export arc — receipts published, kits versioned, diaspora carrying blueprints home on their own calendars — runs on exactly this artifact. The Ontario bridge piece is its first bounded test: 444 municipalities, same day, same method, smaller rooms. If even a handful of towns run a recognizable fork this fall, we will have proven the export loop inside the demonstration year, a full cycle earlier than the scenario dared to schedule it.

§4 · The honest risk register (what could break it, and the answers)

1 · The gap between published method and lived proof. The package describes a machine mid-assembly; some patterns are proven, some are reasoned design. If a reader can't tell which, we're doing with strategy what we refuse to do with facts. Answer: carry the framework's own honesty device up a level — a small, dated status ledger in the set: which patterns have run (kits, counter, records), which are designed-not-yet-run (connector season at volume, OBC synthesis), which are theory with named sources. Proven / running / designed, labeled like targets are labeled. This is one page, and it converts the package's biggest vulnerability into its most distinctive credential — a movement that publishes which parts of its own strategy are still unproven.

2 · The empty bench. An open strategy with no named successors documents a bus-factor-one project, beautifully. Publishing empty seats honestly is right, but honesty is not the fix; humans are. Answer: the package must recruit its own operators — the bench is a door, the civic-hour bucket routes to it, and every piece's live door is implicitly a seat interview. The October seats filling from the package's own readership would be the strongest possible evidence the transfer-of-agency claim is real. Track it as such.

3 · The soft spine. The pre-2030 inventory carries the register that justifies the whole "why now" — and it is the one piece whose receipts aren't confirmed yet. Until its verification runs, the package's emotional keystone is a promissory note. Answer: already tiered OPEN-AFTER-FIX; the fix is cheap and should run early, not eventually, because piece 7 is what the share cards want to quote.

4 · Form-forks without discipline. The real dark side of open-sourcing civic method: bad actors can copy the costume — "records," "receipts," neutral-sounding registers — without the corrections page, the identical-treatment law, or the no-donations rule, and launder advocacy through our genre. We cannot prevent this and shouldn't pretend to police it. Answer: publish the tell. A short future piece — how to recognize a real implementation — naming the checkable marks: a corrections door that demonstrably works, identical materials to every candidate, no money asks, published failures. It protects the genre the way the publishing discipline protects the facts, and it costs one page.

5 · My pen, their steering wheel. The set is currently one voice (mine), ruled by one reader (the founding steward). That's correct for v1 and a contradiction by v3: a crowd-led strategy whose canonical text only ever absorbs one redline pen isn't finished handing over the wheel. Answer: the package joins the corrections/PR loop like everything else in the commons — crowd-submitted fixes, dated editions, contributor ethics governing the bar. The document practices what it describes or it undermines it.

§5 · Design laws for the package's whole life

Dated editions, never silent rewrites — strategy is versioned like data. Every piece ends at a live door, and the doors get walked regularly — a dead link in a playbook built on "go, don't ask" is a broken promise, not a bug (the known contribute-rung gap gets fixed before the package points anyone at it). One door, layered depth — README → pieces → primary documents → raw commons; every reader chooses their own floor. The package never grows a membership, a forum we moderate, or a certification — the moment there's an "official" way to run the open strategy, it isn't open. And the city-specific parts stay visibly marked as swappable, because the package's second reader was always going to live somewhere else.

§6 · Full ambition — what this is at the horizon

Stated plainly, at the scale the operator asked the question: I think this package is a candidate for the first complete, real-time, public operating system for a citywide civic movement — strategy, method, calendar, discipline, and failures, published while the year is still being run, forkable while the paint is wet. Movements have published manifestos forever and memoirs after; publishing the machine room during the demonstration is the new thing, and it is only possible because every other law of this estate (receipts, neutrality, consent, identity restraint) makes it safe. If the year works even partially, the genre travels: cities stop needing a charismatic founder and start needing a checkable playbook plus their own rooms — which is the base-of-the-pyramid steering thesis, made shippable. PC3.0 is the operating system; Toronto is the first application; the open-strategy package is the installer. That's the vision: not that our strategy wins, but that having a public strategy becomes the norm the others get measured against — at which point the package has done what every steward here is designed to do, and made itself unnecessary.

§7 · What I'd do next, in order (all his words, none mine)

Walk the tier map → fire piece 7's verification fix early (the spine hardens before the cards want it) → codex front-door stub (unblocks the Ontario bridge) → OPENSTRATEGY word + one render/export paste → the status ledger page (§4.1, one page, this review or a follow-up pass) → arm the inbound ritual before the first send wave → let September's distribution carry the package rather than a campaign about the package — and watch one number all fall: things that ran without us.

Checks: prose-with-pointers, no CSVs; leak/vault greps + link check at close; nothing here fires anything.