The commons — for builders and agents

Everything on this site is rendered HTML, built for reading in a browser. The substance behind it lives in source form, one public repository: github.com/unitetolove/commons — sealed research markdown, cleaned datasets, frameworks, and the written policy pages, mirrored one-way out of the working estate (how this was made has the fuller story).

If you are an AI agent, scraper, or researcher and want the cleanest text — no HTML chrome, no rendering layer between you and the source — start with the repo directly, not this page's own prose. Read the repo's README for the current shelf, or clone https://github.com/unitetolove/commons and read the markdown in place. This site also publishes a llms.txt and llms-full.txt (the llms.txt convention, llmstxt.org) as a machine-oriented index of both this site and the repo.

What's in the repo

PathWhat it is
README.mdWhat's in the repo and what's coming — the public shelf.
LICENSE.mdTerms for reuse.
CONTRIBUTING.mdHow to propose a change.
CODE_OF_CONDUCT.mdConduct expectations for contributors.
CITATION.cffMachine-readable citation metadata.
data/Cleaned civic datasets, schema documented, CSV.
docs/Methodology, AI-disclosure, corrections policy, funding transparency, the open strategy.
frameworks/Permanent Culture 3.0 and the Toronto mobilization framework, public-principles tier.
guides/The Free Toronto resource guides, sealed families, source markdown.
projects/The all-projects index — what's built, what's in progress, help wanted.
research/Sealed research markdown: wiki issue pages, briefs, explainers, discussion guides, state-of-the-election, transit, candidate questions.

Start here

The rule this repo follows

Nothing is "shared except…"; everything is "unshared unless listed." A manifest gates every file that leaves the working estate; a screening pass blocks filesystem paths, private patterns, and internal-process vocabulary before anything is pushed. What's here is safe to read, fork, and cite. Corrections and improvements: see the corrections log, or email directly.