TOOLKIT // SHARED MACHINE

Use the machine without giving up your own banner.

Future Union should be useful before it is famous. The toolkit is where useful people get repeatable actions, templates, and mission briefs that convert attention into pressure.

KITS

The first public tools.

OPEN ACTION BOARD

Council pressure kit

Drafting

Letter templates, meeting scripts, local press email drafts, and the first version of a planning-blocker evidence checklist.

Get notified when it ships

FOI and receipts kit

Pilot

Plain-English FOI prompts and document review workflows for finding the timeline, the blocker, and the human-readable claim.

Use the pilot

Chapter starter pack

Planned

How to run a no-drama local meetup, collect issue submissions, and turn five useful people into a working cell.

Get notified when it ships

Share-card bank

Planned

Reusable graphics for Growth Index ranks, source-backed claims, local asks, and 'send this to one useful person' moments.

Get notified when it ships

PATHWAYS

Pick a lane. Bring receipts.

ROLE 01

Supporter

Turn attention into distribution without becoming a Reply Guy for Britain.

First action: Join the list, then share one receipt card with one useful person.
Starter kit: Share cards, story links, explainer threads, and the weekly action digest.
Good output: One new person understands the claim, the source, and the next useful link.

Join the list

ROLE 02

Researcher

Turn public documents into claims the public can understand and inspect.

First action: Open the Planning Blockers Sprint and return one reviewable output.
Starter kit: FOI prompts, source-pack checklist, evidence grading, and output template.
Good output: A short Markdown evidence pack with links, timeline, caveats, and one publishable claim.

Open the sprint

ROLE 03

Local organiser

Turn local frustration into a repeatable proof cell.

First action: Open the local issue map and capture five useful local inputs.
Starter kit: Meetup script, sign-up form copy, local press email, and council-pressure checklist.
Good output: A named local issue map with at least five human inputs and source links where possible.

Start issue map

ROLE 04

Builder/operator

Improve the machine itself: data, design, tooling, ops, media, or automation.

First action: Open the local runner preview and run one bounded mission in your own workspace.
Starter kit: Open task spec, acceptance criteria, submission route, and QA checklist.
Good output: A shippable improvement with before/after notes and clear owner handoff.

Run locally