How to read this

There are sixteen organs in three tiers, governed by a one‑page Charter and three cross‑cutting principles. You can read the whole thing in order, or jump to the organ that interests you from the sidebar. Each section opens with a one‑line origin (when the idea first appeared in the writing this is built on), states the job that organ does, and then names the real‑world movements and methods underneath it.

None of the strange things in this design are decoration. Every framework named in an organ has a specific job that the organ would visibly lose if it were taken out.

The promise: loyal to the people, not to capital or the state. Local‑first, opt‑in, equal for everyone, overridable in one tap. The four hard limits and the three principles are above every organ, not below them.

Above every organ

The Charter

The project's constitution.

The Charter sits above every organ. Any decision, by any organ, can be challenged on the grounds that it violates the Charter. The Council can be overruled by its own constitution. Where the Charter is silent, the organs decide; where the Charter speaks, the organs yield.

The signature line

Loyal to the people, not to capital or the state.

The four hard limits

Loyal to you, not the system. The personal AI works for the resident alone. It is never a back door for the community, a company, or any external power to influence, nudge, or watch the resident. Guaranteed by: local‑first architecture — the code runs on the resident's device, not on a server.
Private and under your control. The system knows only what the resident chooses, shares only what the resident allows, acts only with the resident's say‑so. The resident can see everything held about them, and wipe it. Guaranteed by: data living on the resident's device, with backup via a Solid pod the resident encrypts and controls.
Equal for everyone. Every resident gets the same Lantern, equally capable. The system levels the field instead of widening it. Guaranteed by: one app, one model class, one feature set, free to every resident.
It advises; you decide. The system never makes decisions a human should make. Every action passes through the resident's approval queue unless they have explicitly opted into Direction mode — and even then, every plan is overridable in one tap. Guaranteed by: structural enforcement of the approval queue at the software level.

What the project will not do

A deliberate exclusion list. The Charter binds the project against these even where they would be profitable, popular, or possible:

No surveillance for any state, corporation, or third party — ever, under any framing of necessity or emergency.
No selling of resident data, under any aggregation, anonymisation, or repackaging.
No nudging residents toward consumption, purchase, engagement, or any behaviour the resident has not asked for.
No engagement metrics — time‑in‑app, session length, daily active users — as design targets. The system is built to be useful, not used.
No AI making decisions a human should make. The Council deliberates; the Hearth holds; the Mend repairs. The AI carries, suggests, and assists; it does not rule.
No closed source for any organ a resident depends on. The community must be able to read, audit, and fork the software it runs on.
No acquisition of the Choose Neighbors project organisation. Steward ownership (purpose trust) makes this structurally impossible; the Charter requires it.

The rights of every resident

The right to refuse the system entirely. Being a resident does not require running Lantern, contributing to the Sensorium, or voting via the Council. Non‑participation is a first‑class option, not a second‑class one. No community right is conditional on participation.
The right of departure. Every resident can leave at any time, with their data, in a form they can carry. Federation membership doesn't trap anyone. Solid pods make this mechanical, not promised.
The right to be heard. Every resident can post a proposal to the Council, contribute to the Lookout, add to the Lineage, list on the Twenty. Participation is opt‑in; voice is opt‑in; both are always available.
The right to be omitted from the Story. The removable‑but‑not‑destroyable pattern means a resident's personal role in any chapter can be removed without erasing the chapter's existence.
The right to challenge any decision under the Charter. Any resident can bring a Council decision, a Mend outcome, or an organ's behaviour back to the Charter and ask whether it complies. The challenge is heard.

How the Charter is changed

The Charter can be amended, but not casually. Amendment requires:

A proposal posted publicly with full reasoning.
A deliberation period of at least three months.
A citizens' assembly (sortition‑selected, as the Council uses for heavy decisions) recommending the amendment.
A supermajority of all participating residents voting in favour through the Council.
Federation review, where the community is part of the Federation — neighbouring communities have the right to flag Charter changes that would weaken the wider Federation's shared commitments.

The four hard limits cannot be removed; they can only be strengthened. Anything else in the Charter is amendable by the process above.

The Charter is short, plain, and hard to misread on purpose. The integrity of the whole design rests on it being followed even when following it is inconvenient. The organs do the work; the Charter is what they answer to.

Cross‑cutting

Three principles

CARE — the Doughnut — the Pluriverse.

The three cross‑cutting principles aren't their own organs because they run through every organ. They sit alongside the four hard limits as the project's commitments. Where the limits govern what the system is allowed to do, the principles govern how the system carries itself.

CARE — for Indigenous data governance

Developed by the Global Indigenous Data Alliance and applicable to any community that holds data about itself. Four parts:

Collective Benefit. Data serves the community's flourishing, not extraction from it.
Authority to Control. The community decides how data about it is used; consent is real and revocable.
Responsibility. Those holding data carry an obligation to the people the data concerns; benefits are shared transparently.
Ethics. Minimise harm; refuse deficit‑framings that stigmatise the community.

CARE applies across every organ that handles data. Lantern's four hard limits govern the resident's relationship to data about themselves; CARE governs the community's relationship to data about itself. Critical caveat: CARE applied superficially is worse than not applied at all. In any implementation region with Indigenous populations — certainly Australia, where the project originates — real adoption requires ongoing relationships with the relevant Indigenous data sovereignty bodies. The principle is listed honestly, with the bar named.

The Doughnut — planetary boundaries with a social floor

Kate Raworth's framework, in operational use by Amsterdam, Brussels, Portland, Melbourne, and Sydney. Two edges:

The social floor. No resident falls below the minimums of housing, food, care, dignity, voice, and belonging.
The ecological ceiling. The community's footprint stays inside what the planet can carry — measured locally as climate footprint, water use, biodiversity impact, soil health, waste production.

Every Council proposal is asked: does this keep us inside the Doughnut? Trade‑offs between the Tide and the Doughnut are made visibly, with both edges of the ring on the screen. The Sensorium measures both edges; the Garden does the ecological work; the Living and the Commons hold the social floor.

The Pluriverse — a world in which many worlds fit

Arturo Escobar's framing. The project must not unconsciously default to Western framings of community, self, time, or value. The English vocabulary the design uses (Tide, Hearth, Threshold, Garden, Lookout) is one window; the Pluriverse principle keeps the other windows open. The journals' own language — existence perception, the continuum, the black mind — is one further window; Indigenous frames are others, often deeper:

Buen vivir (Latin America, Quechua sumak kawsay) on the Tide and the Garden.
Ubuntu (Southern Africa) on the Threshold and the Hearth.
Satoyama (Japan) on the Garden — the human‑and‑nature managed landscape.
Bayanihan (Philippines) on mutual aid and arrival.
Hozhó (Diné/Navajo) on the Tide — beauty, harmony, balance as a single measure.
Country (Aboriginal Australian) on the Garden — active reciprocal relationship with place, not landscape.

The principle is: defer to local framings where implementations land; do not add other traditions as ornament to a Western design. Any localised implementation should draw on the framings native to that place, with the relationships those framings require.

The three principles run through every organ. Where the four hard limits are mechanical guarantees, the three principles are ongoing commitments — ways of carrying the work that any honest implementation has to maintain over time.

Tier 1 — core seven

The Sensorium

The community's senses.

Origin: 2014–2022 writing on community surveys, the energy survey, and the missing dimensions of what a place is actually like. The idea: before you change a community, the system reads the whole thing — including the parts that are felt rather than counted.

A community is too rich to be summarised by housing costs and crime rates. The Sensorium reads a place across sixteen dimensions and four ethnographic themes — built from resident voice first, public data second, lived patterns by consent third, and the population's own foresight fourth — then surfaces, in plain language, what would help most.

What it reads — sixteen dimensions

The first twelve are the dimensions most communities already try to measure, set out plainly. The last four are the ones the wider movement is starting to take seriously and most places have no name for yet.

Connection & belonging. How often people see others they care about. How alone they feel.
Housing. Affordability, security, and whether people own or are stuck renting.
A say in the place. Whether residents have real power over how the place is run.
Places to gather. Third places and public spaces where people can simply be together.
Care. How well the old, the young, the sick, and the struggling are held.
Things to do. Events, activities, and reasons to leave the house locally.
Walkability & access. How much is reachable on foot; how car‑dependent life is.
Local economy & work. Jobs, income, and how much is owned and earned locally.
Green space & environment. Trees, parks, clean air, daily quality of surroundings.
Safety. How safe people are, and how safe they feel.
Trust & social capital. Whether neighbours know, trust, and help one another.
Children & young people. Whether the young are safe, included, and have room to grow.
Tide‑position. Where each resident sits, on average, on the spectrum from flourishing to slipping — anonymised in aggregate, read as a community measure, never used to rank individuals. Underneath the dimensions; the Tide is what every other organ is trying to raise.
Vision‑density. How much idea–, inventive– and creative activity is happening per capita. A community with high vision‑density is somewhere people are actively making and proposing things; a low reading is the "company town" condition.
Foresight participation. How many residents are contributing predictions to the Lookout (see below). A measure of whether the community sees ahead together, or whether the future is something that happens to it.
Energy. The felt quality of the place — drawn from resident self‑report and from the patterns underneath it. Some places feel alive; some feel drained. There has never been a good word for this in the planning literature; the missing word is "energy." This dimension makes it visible.

Four ethnographic themes

Numbers don't carry everything. The Sensorium also runs a qualitative read across the four themes drawn from the 2026 cohousing ethnography (Watts et al., Journal of Community Psychology) — the same frame the recent research uses to understand what actually happens in self‑governing communities:

Social pollination. How the community protects through the daily small contacts — the brushings in shared spaces that build the social immune system.
Finding your tribe. The meaning and purpose generated by being among your people. The opposite of the anonymous suburb.
Deconstructing defensible spaces. How the community draws and crosses the boundaries between public, semi‑public, and private — whether the architecture itself helps or hinders contact.
Conflict and tension. The honest read. No real community is without these. A Sensorium that pretends otherwise is propaganda.

Where the picture comes from

The order matters: people first, data second.

Resident voice. An opt‑in survey and ongoing input from Lantern's daily check‑in: how connected, safe, and heard people feel, and what they actually want. The ground truth. This leads because a community is its people, not its statistics.
Place data. Open public data and maps — housing costs, walkability, green space, services, demographics — to fill in the measurable picture. Public, never personal.
Lived patterns, by consent. With explicit permission per category, what is actually used and needed. Always opt‑in. Anonymised in aggregate before it leaves anyone's phone. Never surveillance.
Prediction by consent. Foresight contributed by residents through the Lookout — using established participatory‑foresight methods (Real‑Time Delphi, the Polak Game, scenario voting). The community gets to see what it expects, and what it wants. This is new in the Sensorium; most existing community‑analysis systems read only the past.

From signal to suggestion

The Sensorium combines all four sources into a profile, scores each dimension, runs the qualitative read across the four themes, and identifies where the community is being let down most. It then matches each gap to the highest‑impact, most achievable changes — drawn from the fifty scored ideas already developed, plus residents' own proposals rising through the Council — and ranks them for this community.

The system serves; it does not rule. The Sensorium informs a human decision — it never makes one. Every suggestion can be questioned, reordered, refused, or replaced by the people who live there. Most communities will reject some of what it recommends. That is not a bug; it is the design.

How the data is held

Four commitments, applied at every layer:

Resident data is anonymised at aggregate before it leaves anyone's phone. The Sensorium sees the community; it never sees you. (See Lantern for the local‑first architecture that makes this mechanical, not promised.)
The CARE principles for Indigenous data governance apply across the whole system — Collective Benefit, Authority to Control, Responsibility, Ethics. Communities decide how data about themselves is used and can revoke consent. (See the three principles.)
The Doughnut — the community's reading on the social floor (no one falls below the minimums of housing, food, care, dignity) and the ecological ceiling (the footprint stays inside what the planet can carry) is part of every Sensorium read. Drawn from Kate Raworth's framework, in use in Amsterdam, Brussels, Portland, Melbourne and Sydney.
A community is more than its metrics. No score captures a place's history, character, or soul. The Sensorium is a map to start from — not the territory, and not a verdict on anyone's home.

What it connects to

The Sensorium sits at the centre of the system's reading. It is fed by Lantern (resident voice + lived patterns) and by the Lookout (foresight), and it feeds the Council (which uses gap analysis to draft proposals) and the resident's own view through Lantern (so each person sees the place they live, in the frame the research uses).

If the Sensorium is doing its job, no one in the community can say honestly that they don't know what's wrong here. The answer is on the screen, in their words, in a shape they recognise.

Tier 1 — core seven

Lantern

The personal AI. The only thing the resident actually uses.

Origin: 2014 writing on the Lumia Tick Box, which began as the reframe of a darker thought — that we were being monitored by people who didn't care for us. The question was: what if we were being looked after by something that did?

A private AI that looks after you, carries you into your community, and stays loyal to you when those two things pull in different directions. Support worker, secretary, civic proxy, creative assistant, quiet witness — one app, four hard limits, your hand on every dial. Lantern is the only thing the resident actually uses. Every other organ either runs inside Lantern as a mode, or is a layer Lantern talks to on your behalf.

Where Lantern actually lives

Lantern is local‑first. The model runs on your device. Your memory lives on your device. Your check‑ins, your Twenty, your conversations with it — your phone. Nothing about you sits on a server that could be subpoenaed, breached, sold, or quietly read.

This is the architectural answer that makes the four hard limits real instead of promised. "Loyal to you, not the system" is not a policy that could be changed in a terms‑of‑service update — it's a fact about where the code is running. "Private and under your control" is not trust in a company — it's the mechanical reality of the data never having left your hand.

What goes to the cloud, when something has to: only the work itself, anonymised at the layer below your identity, with a privacy contract you can read in plain English. For most language work, the on‑device model is enough; for the heavy lifting where it isn't, the cloud call is stripped of who you are.

Backup and continuity use a Solid pod in your name — Tim Berners‑Lee's personal‑data‑store project, the open‑standards answer to "what if my phone dies, I switch device, I want a backup." Your pod, your encryption, your call. Lantern can be reinstalled on a new phone and re‑hydrated from your pod; the pod itself is never read by anyone but you.

The check‑in — parts‑aware

The home screen of Lantern is three rows, each with four buttons:

Life — Excellent · Good · OK · Bad
Health — Excellent · Good · OK · Bad
Mind — Excellent · Good · OK · Bad

Tap a row and it expands: why? (one free‑text line), and the relevant follow‑up questions. Under a minute most days.

The check‑in is parts‑aware, in the Internal Family Systems sense. Lantern keeps a small private map of your recurring inner voices — the Manager, the Exile, the Firefighter, the Self, or whatever names you choose. As you write, it notices which voice tends to be speaking and can name the pattern back to you gently: "this sounds like the part of you that takes everything on. Would you like to hear from a quieter one before deciding?" You can ignore it, or you can take the door it just opened. The parts map is yours — editable, deletable, and never leaves your phone.

(This is a UX metaphor, not a clinical claim — Lantern is not therapy. But treating the user as a parliament of parts rather than one flat mood lets the app do something most wellbeing apps refuse to do: speak to the part of you that's currently in charge.)

With Activity‑level visibility on (see the dial below), the check‑in gains a fourth axis: Body. Polyvagal‑style somatic state from wearable signals — heart‑rate variability, sleep continuity, breathing rhythm — a separate read from Mind, because some days the body is the problem and some days the body is the clue.

Three dials, your hand on all three

Three dials live in settings — visible at any time, movable any time.

Visibility: How much of your life Lantern can see. Three positions: Words only (default), Activity (calendar, screen time, location patterns — each opt‑in per category), Anything that helps (cameras, microphone, wearables, for people who want them). Reversible any time.
Engagement: How directive Lantern is allowed to be. Witness (default — answers when asked), Coach (suggests; you decide), Direction (gives you a plan and follows up). Direction mode is opt‑in only, local‑first only, and overridable in one tap. For some people it's the difference between drift and not drifting.
Conviction: How much your standing preferences accumulate weight over time. A preference you've held for two years pulls harder on Lantern's decisions on your behalf than a preference you set yesterday — unless you tell it not to. Drawn from conviction‑voting research; the dial lets you choose "weight my old commitments more" or "treat every day fresh." Either is honest; the dial makes the choice visible.

Below the three dials is an importance allocation view — a small quadratic‑voting interface where you distribute strength‑of‑preference across the decisions Lantern has queued for you. You don't just approve or reject; you say how much something matters. Same maths the Council uses at civic scale, fractal down to the personal.

The protocol library — indexed by parts

When you tell Lantern what's wrong, it doesn't reach into the void. It reaches into a library of crowd‑sourced protocols indexed two ways: by what's happening ("can't sleep," "lonely," "stuck on a decision") and by which part of you is in charge ("Manager won't switch off," "Firefighter looking for something to fix," "Exile loud and unattended").

The intersection is the protocol set you actually get. "Sleep — when the Manager won't switch off" is a different falling ladder of things to try than "Sleep — when the body is wired." They're filed separately because they help differently.

Each protocol is a small executable step (behavioural‑activation style: start low, finish, track, fall through if it didn't help). Moderation is rank‑by‑result, weighted by your web of trust — protocols that worked for people you trust, and people they trust, carry more weight in your view than protocols ranked by popularity alone. Strangers' contributions still appear; they just don't drown the signal from people whose taste you've earned a reason to share.

Vision‑state mode — and your own ideas, returning

If Lantern notices you keep returning to a topic, generate a lot of related ideas quickly, or fit the diagnostic profile of an idea‑flooded thinker, it offers vision‑state mode: quieter UI, fast‑capture surface, no notifications, and the Lineage workspace one tap away.

A second mechanism inside vision‑state is spaced resurfacing of your own thinking. Lantern brings your past notes back to you at increasing intervals — the way spaced repetition brings back what you're trying to learn — except here you're not memorising someone else's content, you're re‑encountering your own.

The recurring complaint in twelve years of idea‑people's writing is "I keep re‑deriving ideas I've already had." Spaced resurfacing is the structural fix. Your past self is one of the people on your team.

The quiet watch

With permission, Lantern notices when something's slipping — withdrawal, escalating distress, isolation, a pattern that has gone badly before. With Activity‑level visibility on, sustained low HRV or disrupted sleep can join the watch — the body signals that often lead clinical risk before they reach conscious worry.

Nothing is logged anywhere it could be subpoenaed (everything is on your phone). The watch surfaces to you, gently, with a protocol to try and the option to ask for a human. Predict and prevent, but on your side — never the state's.

How Lantern weaves into the community

The other organs aren't other apps. They're layers Lantern operates in. Here's how each one plugs in.

The Sensorium — your window onto the place: Lantern contributes your check‑in data and your Twenty to the Sensorium — anonymised in aggregate before it leaves your phone, never as you. In the other direction, you see the community's profile through Lantern. Where the place is strong, where it's struggling, where your Twenty could land. The Sensorium isn't a planner's dashboard; it's your window onto your place.
The Twenty — your standing offer: Your list of up to twenty things you'd offer the community lives inside Lantern. Editable in seconds. Carried outward by Lantern — anonymised where appropriate, named where you've consented to be named.
The Lineage — no idea lost: Not a separate app. The workspace Lantern opens in vision‑state mode, or when you tap "capture an idea" from anywhere. Ideas auto‑tag into your knowledge graph, kept on delay (your thinking develops before being matched to anyone else's), and carry their source forward so when someone builds on yours, your name rides along.
The Lookout — foresight, contributed: Once a week, maybe, Lantern asks: "What do you think happens next, with X?" — using established participatory‑foresight methods (Real‑Time Delphi, the Polak Game, scenario voting). Your prediction joins thousands on the branching graph. The other direction: if the Lookout sees a branch you're on dim, Lantern gently surfaces you to the people who could help. Real‑time, consensual hand‑up. This is the heart of the project.
The Tide — the shared measure: Lantern carries your private Tide reading — where on the line from flourishing to slipping you are this week. Anonymised at every aggregate level, never shared without consent, never used for any system decision about you. Your mirror, for your own life.
The Council — your voice in the room: Lantern carries your vote, preferences, and Twenty into community decisions. For meetings you can't attend, for proposals you don't have time to read, Lantern votes the way it has reason to believe you would vote, and queues anything important enough for your direct approval. Reviewing the queue, it uses Pol.is‑style bridging on your behalf — shows you where bridges across difference land, not just where the majority sits. You vote into consensus, not blindly against the half of the room you disagree with.
The Fringe — when you need the why: The philosophy and origin stories live as their own pages, but Lantern knows when to point you to them. "You've been in self‑criticism for three days. Would you like to try the Three States exercise?" "You're moving into vision‑state more often. Here's why we built the Lineage." The Fringe is the why; Lantern is the how. When you need the why, it shows you the door.

The four hard limits, technically guaranteed

Wider doesn't mean looser. Local‑first makes wider survivable. The four limits are the architecture of every feature above.

Loyal to you, not the system. Your Lantern works for you alone. It is never a back door for the community, a company, or the powerful to influence you, nudge you, or watch you. Guaranteed by: the code running on your phone, not theirs.
Private and under your control. It knows only what you choose, shares only what you allow, acts only with your say‑so. You can see everything it holds, and wipe it. Guaranteed by: the data living on your phone, not theirs; backup via your own Solid pod.
Equal for everyone. Everyone gets one, equally capable — so it levels the field instead of handing yet another advantage to whoever can pay for the best. Guaranteed by: one app, one model class, one feature set, free.
It advises; you decide. It never manipulates you or anyone else; a human is always the one who chooses. A tool in your hand, not a hand on your shoulder. Guaranteed by: every action passing through your approval queue unless you've opted into Direction mode — and even then, every plan is overridable in one tap.

What runs underneath

A pinned audit, so a builder or sceptic can verify the integrations are real. Every framework named has a specific job; remove the framework and the design visibly loses something.

Layer	Doing what job
Plurality (Tang & Weyl)	Lantern as one resident's slice of the Plurality stack
Local‑first AI	Privacy contract becomes mechanical fact
Solid pods (Berners‑Lee)	Backup, transfer, continuity across devices
Internal Family Systems	Parts‑aware check‑in; parts‑indexed protocols
Polyvagal theory	Body‑state axis on the check‑in
Conviction voting	The Conviction dial — standing‑preference weighting
Quadratic voting	The importance allocation view
Behavioural activation	Step‑structured protocols with fall‑through
Web of trust	Trust‑weighted protocol ranking
Spaced repetition	Your own ideas resurfacing at intervals
Pol.is + bridging‑based ranking	Cross‑cluster consensus on your behalf at the Council
Participatory foresight (Delphi, Polak)	Weekly foresight prompts feeding the Lookout

One app. Three dials. Fifteen other organs underneath. The resident only opens Lantern; the rest is plumbing. That's the design.

Tier 1 — core seven

The Twenty

Your standing offer to the community.

Origin: 2014–2022 writing on "the 20 options" — the observation that most jobs are made up of tasks people would happily do, but the matching system between what someone has to offer and what their community needs is either missing, hidden, or too rigid to use. The Twenty is the simplest possible fix: every resident maintains their own list, in their own words.

Every resident keeps a standing list of up to twenty things they would offer the community — skills, work, projects, hobbies, hours, problems they'd help with, things they'd like to learn from someone who's done it. Their list, in their words, editable in seconds, ordered by their priority. The Twenty is the bridge between Lantern's inner‑life half and Lantern's community half.

What goes on the list

No format. No required fields. Twenty slots, in your own words. Some of the things they tend to be:

Skills you could share or teach (formally or just by doing it alongside someone).
Work you'd take on, paid or unpaid — the things you're good at and the things you simply don't mind doing.
Projects you'd join if someone else was starting one.
Hobbies you'd be willing to do with people rather than alone.
Hours you'd give — to whoever, for whatever, without needing to know in advance.
Problems you'd help someone work through, having been through it yourself.
Things you'd like to learn from someone in the community who already knows how.
Roles you'd accept in community life if asked.

Most people, asked once what they'd offer, freeze. The Twenty asks twenty times, slowly, over months, in any order. By the end, the list says something about the person that no resume or job title ever did.

Two modes per item

Each item on your Twenty can run in one of two modes, your choice per item:

Open offer: Listed as available; matched when someone in the community needs it. No accounting, no ledger — if you help, you help. Most items, for most people, sit here.
Time‑banked: The offer is denominated in hours that build credit you can spend on others' offers later. Mutual‑credit and time‑banking systems have a forty‑year track record — Sardex in Sardinia (~10,000 businesses), Time Banks USA, the UK Timebanking network. Borrowed engineering, not invention. Useful where someone wants to give a lot but doesn't want to feel like they're being taken advantage of.

Some people will have all twenty items in open‑offer mode and no time‑bank at all. Others will time‑bank everything. Both are fine. The design doesn't push you toward either.

How matching works — trust‑weighted

When another resident's Lantern looks at the Twenty pool to find what's on offer, it walks your web of trust first — friends, friends of friends, the transitive cluster you already have reason to share taste with — before reaching the wider community. This is how cohousing already works informally; the Twenty just makes the existing pattern legible to the system.

Strangers' offers still appear; they just don't drown out the signal from people whose contributions you've earned a reason to trust. The web‑of‑trust weight is something you can see and adjust — one resident might want strangers boosted (to meet new people); another might want them filtered down (to keep things small).

How it propagates

The Twenty lives inside Lantern, on your phone. It moves outward through Lantern, never as you, except where you choose to be named:

To the Sensorium — anonymised in aggregate — so the community can see what it is capable of, collectively. "Three people offer carpentry." "Eleven people offer to teach a language they speak fluently." "Forty people would join a kitchen co‑op if one started." Never named to who; always real numbers.
To the Council — named, with your consent — when community roles are being allocated. A role gets posted; the Twenty surfaces people whose lists touch it, who can decline or accept.
To the Hearth when care is needed and your Twenty includes a relevant offer. The Hearth doesn't broadcast a need; it asks one or two matching residents quietly first.
To other residents' Lanterns when their need matches your offer and trust permits. Direct, person to person, with the option to decline without explanation.

What it replaces

The Twenty replaces a stack of things that, separately, have never quite worked: the resume (which says what you've done, not what you'd do), the skills marketplace (too formal, never current), the volunteer form (too rigid), the classified ads (never indexed by trust), the LinkedIn profile (designed for selling yourself, not contributing). One self‑authored thing in your own words, current today, gone tomorrow if you change your mind.

People work hard on hobbies and skills that have no employment pathway. The old assumption was that anything worth doing should become a business. The Twenty lets the skill stay a skill, the hobby stay a hobby — while still being findable by people who could receive it.

Editing and change — low friction by design

Add an item: tap, type, save. Remove an item: tap, swipe, gone. Reorder: drag. The change propagates to everywhere your Twenty touches, instantly.

Old offers don't haunt you. By default, items renew quietly every few months — Lantern asks "still on offer?" and you confirm or change it. Anything not renewed quietly retires. The list always shows who you are this season, not who you were three years ago.

This matters: a Twenty that locks you into past selves is worse than no Twenty. Trivially editable is the whole point.

What it connects to

The Twenty is the connective tissue between the personal and the communal. It lives inside Lantern, is read in aggregate by the Sensorium, allocates roles through the Council, matches needs through the Hearth, and surfaces who could teach what to whom through the Forge. When you list something you'd like to learn, that's read by the Forge as a need; when you list something you'd teach, the Forge can match it to learners.

What runs underneath

Layer	Doing what job
Time banking / mutual credit (Sardex, Time Banks USA, UK Timebanking)	The time‑banked operating mode for items where accounting helps
Web of trust	Trust‑weighted matching across the resident base
ACT (Acceptance and Commitment Therapy) values clarification	Helps a resident articulate what they'd actually offer, vs what they think they should
Self‑authored profile (vs algorithmic profile)	The whole design principle — the list is yours, not inferred from your data
Slow renewal cadence	Old commitments retire quietly; the Twenty stays current

Some people will fill all twenty slots. Others will stop at three. Both are fine. The number isn't the point. The point is that what you're willing to give is in your own words, current, and visible to people who could receive it — without anyone having to ask, without you having to perform.

Tier 1 — core seven

The Lineage

No idea lost.

Origin: 2014–2022 writing on the help‑inventors‑system, the Invention Analyser Under Agreement, and the journals' returning observation that the most idea‑flooded thinkers are also the people most likely to lose their ideas — to forgetting, to theft, to never finding the right collaborator, to the simple fact of nobody listening. The original name was Ostinv. The original mission line was "Save Inventor Johns on the Time Tree." Both have been retired in favour of plainer English. The mission line that replaced them is the tagline above.

The Lineage is the intranet for the idea‑flooded. It captures ideas without breaking flow, protects them on delay while the thinker develops the thought, carries source‑credit forward so that when an idea is built on, the person who had it first is named, and routes the right ideas to the right minds without anyone having to pitch themselves. The Lineage is the infrastructure side of Lantern's vision‑state mode — Lantern is the front door; the Lineage is the room.

Who the Lineage is for — the diagnostic

The Lineage isn't for everyone. It's specifically built for a cognitive profile that the wider design names but most other systems don't support: the person who, in the journal's exact phrasing,

"is consumed by so many thoughts they change their mind on what they want to do so often they get stuck moving forward on one thing, and this condition causing other problems due to being consumed by ideas."

Other registrations from the same journals: "have you often felt really creative and have powerful visions of …?" — the classic 2014 questionnaire fragment. And from the same notebooks, the same person seen from inside their own life:

"Inventor philosophers with good interesting perception of life … epiphanies consider with feeling of higher spirit … otherwise it can be a bit like a black mind without any of it much."

What unites these is the same shape: an excess of generative thinking with no infrastructure to hold it, leading to lost ideas, derivative work by others, paralysis, or the slow dimming the journals just call the black mind. The Lineage exists for this cognitive profile. Other organs serve other shapes.

Capture without breaking flow

Idea‑flooded thinkers lose ideas because the friction of recording is higher than the rate at which ideas arrive. The Lineage's capture surface is the lowest‑friction possible: one tap from any Lantern screen, voice or text, no required fields, no folder choice, no tags, no metadata. The idea goes in raw. Sorting happens later — by Lantern, in the background, with your eventual review.

Capture also runs inside vision‑state mode — the quieter UI Lantern enters when it notices the pattern. In vision‑state, the capture surface stays open, notifications stay off, and your past nodes around the current topic are reachable without leaving the page. The state the journals called "consumed by ideas" gets a room of its own.

The delay mechanism

From the 2014 writing, one line:

"Perhaps the DB will be on 'delay' to see what people come up with before matching them."

That single sentence is one of the most original mechanisms in the design. Most idea databases match instantly — you type something, you immediately see similar work, and your thinking gets dragged into the shape of what already exists. The Lineage does the opposite. Your ideas develop on delay (typically days to a week, configurable) before the matching layer is allowed to show you what others have written on the same subject. The delay is yours to override when you want to compare; the default is: think first, see later.

After the delay, you have actually thought the thought — not the shape of it that already exists. Matching shows you what other people came up with from your direction, rather than collapsing your direction into theirs.

Source‑credit, carried forward

Every node in the Lineage carries a source‑credit chain: who had it first, who built on it, what each contribution added. When an idea is matched, developed further, or appears in someone else's output, the chain travels with it. There is no Lineage‑bound output that doesn't say where it came from.

The 2014 framing was direct:

"Ideas lost in time or not come to light or stolen in time due to people not working on them."

The source‑credit chain is the structural answer to "stolen in time." It doesn't stop someone from refusing to credit you outside the system; it does mean that within the system, attribution is mechanical, not optional. Every developed output ships with its lineage attached.

The Invention Analyser Under Agreement

The 2014 writing imagined a confidential analysis tier — the Invention Analyser Under Agreement:

"Must make people feel secure in confidentiality like a psychologist, but in their minds be a multi‑skilled technology and science expert … someone who must see logic in good ideas, see possibility potential of ideas, someone who cares about technological development for world / human progression, not evil."

In the Lineage, this becomes the optional second tier of the system — confidential AI analysis of an idea, returning a structured assessment: technical feasibility, prior art, similar ongoing work, paths to development, who in the community might collaborate. The "agreement" is a contract: nothing analysed under this tier is shared, indexed, or matched without your explicit per‑output consent. The analysis lives on your phone (Lantern's local‑first architecture — same place every other private thing lives).

Knowledge graph, opinionated default

Under the surface, the Lineage is a knowledge graph — nodes for ideas, edges for inspirations and developments, parents for source‑credit, children for branches. The structural ancestry is Obsidian, Logseq, Roam Research, and the personal‑knowledge‑management lineage of the last decade.

But raw knowledge‑graph interfaces have a notoriously steep learning curve. The Lineage ships with an opinionated default view — a linear list of recent ideas, a "what I keep coming back to" cluster, a "what hasn't been touched in a while" list, and a search box. Power users can drop into the graph view at any time; everyone else never has to. The structure is there underneath; the UI is gentle.

Spaced resurfacing — your past self on your team

The journals contain a complaint that repeats year after year, with the same shape if not the same words: "I keep re‑deriving ideas I've already had." Across multiple notebooks, the same insight gets discovered fresh, half‑formed, lost, and rediscovered five months later.

The Lineage solves this with spaced resurfacing. Past nodes return to you at increasing intervals — like spaced repetition for flashcards, except for your own thinking. After a week, after a month, after six months, your own ideas float back to the top. Most will glance off; some land different the second time, because the rest of your life has caught up. Your past self stops being a stranger you keep accidentally meeting and becomes one of the people on your team.

The connection to the Lookout — finding the lost thinkers

The 2014 mission line was "Save Inventor Johns on the Time Tree" — find the people who would otherwise be lost on declining futures, and rescue them through what they were trying to make. The naming is retired; the mechanism isn't.

The Lineage and the Lookout are wired together. When the Lookout reads a resident as being on a declining branch — isolation, distress, the patterns that have gone badly before — and the Lineage sees that same resident has been producing ideas without traction, the system surfaces both signals together. Through Lantern. To people who could help: collaborators, mentors, funders, or simply other lonely thinkers in the same shape. A real‑time, consensual hand‑up to the kind of person the journals called John.

The 2014 writing said exactly what this is for:

"To use his positive inventions and give him life based on contribution, and save him on the Time Tree, and give him power to save other peoples' continuums."

Word for word, that's still the design.

What it connects to

The Lineage lives inside Lantern (vision‑state mode is its door), feeds the Sensorium (in aggregate, as the community's vision‑density reading), is wired to the Lookout (for lost‑thinker rescue and for foresight applied to ideas), and surfaces capable contributors to the Council when proposals need technical or creative input. It also threads into the Forge — what you're learning sits alongside what you're making, and mentors find you through the Lineage as much as through the Twenty.

What runs underneath

Layer	Doing what job
Delay mechanism (your own 2014 writing)	Your thinking develops before being matched against existing work
Source‑credit chain (your own 2014 writing)	Attribution is mechanical, not optional, inside the system
Invention Analyser Under Agreement (your own 2014 writing)	Confidential analysis tier with a psychologist‑grade trust contract
Knowledge‑graph PKM (Obsidian / Logseq / Roam lineage)	The Lineage's underlying data structure, with a gentler default view on top
Spaced repetition	Your own ideas resurfacing at increasing intervals
Local‑first architecture (from Lantern)	The Lineage lives on your phone; nothing is exposed without your per‑output consent
IndieWeb principles	If you ever export or publish from the Lineage, the canonical version lives on your own domain
Behavioural activation	Step‑structured paths from raw idea to developed work, when you want them

If the Lineage is doing its job, no idea this community had goes uncredited, undeveloped, or alone. The hardest thing in a thinker's life — being seen as the source of something they made — becomes a fact, not a fight.

Tier 1 — core seven

The Lookout

Foresight, contributed.

Origin: 2014–2022 writing on the Time Tree — a branching graph of possible futures, "real foresight" built from "the opinions of future outcomes from people who can see what may happen," with red‑dot markers for the branches that head into disaster. The original conception fused two things: an operational community‑foresight tool and a cosmic mythology (alien analysers, the Animus Collector, the Demon of Stupidity). This page is the operational organ. The cosmic layer survives in the Fringe, clearly marked as fiction.

The Lookout is a live branching graph of the community's possible futures, built from public data, predicted patterns, and — crucially — the foresight of residents themselves, contributed weekly through Lantern. It is used (1) as a planning tool, to model a community change before it happens; (2) at the person level, to surface residents on declining branches to the people who could help; and (3) as honest signage — a place that can see ahead a little, together.

What the Lookout shows

The journals described the Time Tree directly:

"Time tree is 'Flow cart' software based on data mining and / or the opinions of future outcomes from people who can see what may happen."

The Lookout is exactly that, built without inventing anything new. A branching graph of futures over the next weeks, months, and years — some branches bright, some dim, some narrowed to the journal's red dot at the end of a line that is followed by more red dots. Each branch carries a probability, a desirability rating, and the question that produced it. You can zoom into a branch and see the assumptions behind it, who contributed, and what would have to change for the branch to fade.

The Lookout is not an oracle. It is a council screen, in the older sense — what watchmen on a tower used to do, with binoculars and each other. Pooled foresight, made visible, kept honest.

How residents contribute — the methods

Participatory foresight is a 50‑year academic field with working methods. The Lookout uses three of them as actual Lantern prompts, not vague invitations. Each takes under two minutes.

The Polak Game: Once a week, Lantern asks two questions in succession. "What future do you expect?" — one or two sentences. "What future do you want?" — one or two sentences. The two answers map onto the two‑axis grid the field has been using since 1971 (Fred Polak's The Image of the Future). The gap between expected and wanted is the most useful single signal a community can produce.
Real‑Time Delphi: For specific questions facing the community ("Will the council approve the new building plan in the next six months? At what probability?"), residents see the current distribution of anonymised predictions and can revise their own in light of it. Iterated to convergence. The classic foresight method for questions where the population's collective estimate is more accurate than any one expert's.
Scenario voting: For larger choices facing the community (a development, a cultural shift, a change in policy), the Lookout presents three or four pre‑built scenarios — each a paragraph — and asks residents to rank them by likelihood and by desirability. The ranked scenarios feed into the Council's decision queue.

A resident contributing forty answers a year across these three methods is doing more participatory foresight than most citizens of any country have ever been asked to do in their lives. The point isn't expertise — it's seeing the place ahead together.

The three uses

Planning, before action. Before the Council commits to a change, the Lookout models its likely branches and shows where the bright and dim futures cluster. Not a prediction — a structured conversation about what residents collectively expect to happen. The Council can decide differently from the Lookout, but it has to do so visibly.
Person‑level, by consent. When the Lookout reads a resident as being on a declining branch — the patterns the data and the foresight together flag as leading somewhere bad — Lantern surfaces them, gently, to whoever could help. Real‑time, consensual hand‑up. Never a record, never a database; the action is a conversation, not a flag.
Honest signage. The Lookout is the page a resident reads when they want to know where is this place going? Not as PR. As pooled human foresight, visible to everyone, with the gaps marked.

The lack of foresight as the project's antagonist

The journals named the thing communities most lack, and named the absence as the project's adversary:

"The demon is stupidity … and the lack of council knowledge strategy and foresight is a black cloud that hovers over peoples' heads to make them not design the time machine, see the time lines, or react."

Strong language; correct diagnosis. Most communities make bad decisions not because the right call was hidden but because nobody was looking. The Lookout is the structural answer: pooled, visible, contributed‑to foresight, every week, by everyone who wants in. The black cloud doesn't disappear, but it gets visibly mapped — and a community that can see its own black cloud is a community that can do something about it.

Anti‑gaming

Open foresight is manipulable. A motivated minority can flood the Real‑Time Delphi with predictions designed to nudge the community's apparent consensus. The Lookout borrows from twenty years of prediction‑market research to harden against this:

Reputation weighting. Predictions are weighted by the contributor's track record on past questions — not who they are, but how often they've been right.
Cluster detection. Bridging‑based ranking (the same maths the Council uses) detects when contributions cluster suspiciously and flags the cluster visibly, rather than removing it.
Open audit. Anyone can see the full distribution of predictions and the weighting that produced the displayed consensus. The Lookout never claims a certainty it can't show.
Time‑decay. Old predictions fade faster than new ones. Last year's foresight doesn't dominate this year's reading.

The Lookout is still gameable — everything human is. But the design makes the gaming visible, which is what honest foresight requires.

Lost‑thinker rescue — the connection to the Lineage

The 2014 mission line was specific:

"Ways to help John the inventor — to use his positive inventions, and give him life based on contribution, and save him on the Time Tree, and give him power to save other peoples' continuums."

The Lookout and the Lineage are wired together for exactly this. When the Lookout reads a resident on a declining branch and the Lineage sees that same resident has been producing ideas without traction, both signals reach Lantern at once — and Lantern surfaces them, with the resident's consent, to the collaborators, mentors, and funders who could help. A real‑time, consensual hand‑up to the kind of person the journals called John. This is the heart of the project.

Horizon — multi‑agent simulation as the next step

Frontier research now lets you do something the original Time Tree only imagined: simulate a community decision before making it. Project Sid (Altera AI) is running 50–1,000 LLM‑agent civilisations that develop professional identities, obey rules, and form cultural transmission patterns. Adjacent research from across the multi‑agent field is reaching the point where you can populate a small simulated version of your community, introduce a proposed change, and see what plausibly happens over a year of simulated days.

This is imagination aid, not verdict. The model will import biases of whoever built it. Used well, it catches obvious mistakes before they're made; used badly, it produces false confidence in nonsense. The Lookout adds simulation as a Tier 3 (Horizon) capability, deliberately downstream of the human‑foresight methods it sits next to. Humans first.

What it connects to

The Lookout is fed by Lantern (weekly foresight prompts), by the Sensorium (the place's current state, which sets the starting branch), and by the Lineage (idea‑work in progress that may or may not change the future). It feeds the Council (which uses scenarios to structure heavy decisions), feeds back into Lantern (which surfaces residents on declining branches to the people who could help), and informs the Tide reading (foresight participation is one of its dimensions).

What runs underneath

Layer	Doing what job
Participatory foresight (Nesta 2019, IFTF, the Delphi tradition)	The academic field this organ is grounded in
The Polak Game (Fred Polak, 1971)	Weekly two‑question expected/wanted prompt
Real‑Time Delphi	Iterated convergence on specific predictive questions
Scenario voting	Structured input on larger community choices
Bridging‑based ranking (Pol.is research)	Cluster detection in the prediction pool; anti‑gaming
Prediction‑market research	Reputation weighting, time‑decay, open audit
Time Tree mechanism (your own 2014 writing)	The red‑dot branch visualisation and the lost‑thinker rescue mission
Multi‑agent simulation (Project Sid and adjacent)	Tier 3 / Horizon: simulating community decisions before making them
Long Now Foundation	Fellow traveller: the practice of taking long‑term thinking seriously as infrastructure
Wisdom Council Process (Jim Rough)	Deliberation method when scenario voting needs facilitated discussion

If the Lookout is doing its job, the community sees its own futures — including the dim ones — in time to do something about them. The black cloud the journals named gets mapped, named, and worked on. Not by an oracle. By a council screen built from the foresight that's already in the people.

Tier 1 — core seven

The Council

Your voice in the decisions about your place.

Origin: 2014–2022 writing on the Continuum Party — "idea / technology brainstorming and research group for best options for peoples continuums." The mechanism was an always‑open ideas database with public voting, a compensation model for the people whose ideas were used, and a proof‑of‑knowledge gate to keep votes weighted by understanding. Modern participatory‑democracy work (Pol.is, citizens' assemblies, quadratic voting) has independently arrived at most of the same conclusions. This page is the Continuum Party with the working pieces named.

The Council is the decision layer of the community. Proposals rise from the Sensorium's gap analysis, the Lineage's ideas, the Lookout's foresight, and any resident's direct input. The Council picks a method suited to the decision — from a menu of four — and runs it. Every resident's Lantern carries their vote, even when they can't attend. The decision interface mirrors Lantern's personal approval queue; the same shape, scaled up.

Where proposals come from

The 2014 writing was direct:

"Open input listing and voting system for every issue up for debate. Open listing system for all ideas to be considered by different areas of government."

The Council inherits exactly that. Proposals can rise from anywhere:

Sensorium gaps. Where the community's profile is weakest, the Sensorium auto‑drafts proposals — "this community scores poorly on places to gather; here are three changes the literature and the 50 scored ideas would suggest." The Council debates them.
Lineage ideas. Residents working on something in the Lineage can promote it (with the delay mechanism still protecting their authorship) into a Council proposal. The idea‑flooded thinker becomes a contributor to civic design without having to start a campaign.
Lookout foresight. When the Lookout sees a branch the community is on heading dim, the Council gets a pre‑drafted proposal: "here is what changing course would look like."
Direct resident input. Any resident can post a proposal from Lantern. Twenty seconds, plain language. The Council's intake takes it the rest of the way.

The result is what the journals asked for: "open listing system for all ideas to be considered." Nothing gets lost for lack of a champion.

The method menu

The Council doesn't have a single voting mechanism. Different decisions deserve different methods. Lantern routes each proposal to the right one.

Pol.is — for open‑ended issues: Where consensus discovery matters more than tallying votes. Residents submit short opinion statements; everyone votes agree / disagree / pass on each other's statements; bridging‑based ranking surfaces the statements that most people across difference can support. Already used by vTaiwan (80% of issues led to government action), Bowling Green Kentucky's 25‑year plan (2,370 of 3,940 ideas agreed on by 80% of respondents), and the UN's largest online deliberation. Open source. Working today.
Quadratic voting — for tightly contested choices: When strength of preference matters more than the bare count of yes/no votes. Each resident has a budget of voting credits and allocates them across competing options — care strongly about three things, you can vote heavily on those three; care mildly about ten things, you can spread thinly. Same maths Lantern uses on the importance dial; fractal up to civic scale. Glen Weyl's work; adopted by RadicalxChange, Gitcoin, and others.
Sortition + citizens' assemblies — for heavy decisions: For the largest choices, where deliberation matters as much as voting. A panel of residents is randomly selected (sortition) from those who have opted in via Lantern. They deliberate over weeks, with expert input and full access to the Sensorium and Lookout, and produce a recommendation. Used by Ireland for abortion law and France for climate policy; quietly one of the most effective democratic innovations of the last decade.
Conviction voting — for standing positions: For ongoing questions where a resident's position should pull harder the longer it's been held. Your support builds weight over time; you can withdraw any time, but consistent positions count more than fashionable ones. From the Commons Stack work; the same mechanism powers Lantern's Conviction dial.

The four methods aren't ranked or ordered. Each suits a different decision. Lantern (and a small Council intake process) routes proposals to whichever method fits.

Voting that respects knowledge — the proof‑of‑knowledge gate

One of the most original mechanisms in the journals:

"As people with no knowledge of a subject or wisdom will make wrong decisions on what is good or bad, there should be some requirement to prove knowledge on subject or problem solving or high IQ or wisdom. But with feedback / additions from anyone."

Modern liquid democracy and expertise‑weighted voting have arrived at the same place from a different direction. The Council borrows the working version: proof‑of‑knowledge weighting on the votes that matter. On a question about water infrastructure, the votes of residents who have engaged with the relevant material — or worked in the field, or contributed to the Lineage on it — weight more heavily. Anyone can still contribute statements, comments, and proposals ("with feedback / additions from anyone" is the journal's own caveat). But on the binding vote, demonstrated knowledge counts more than uninformed enthusiasm.

The gate is opt‑in (you can engage with the material to earn weight), light (it's a weighting, not a veto), and auditable (you can see exactly why a vote was weighted how it was). It is the structural answer to the journal's worry that "public voting may not work because new ideas may be left at the bottom — people don't read all the entries correctly and may just vote for ones at the top."

Compensation for the ideas that get used

The 2014 writing was specific about one more thing:

"People who submit important ideas get compensated, so to help them continue thinking of new ideas and getting paid for their talent, and have a constructive outlet for ideas."

The Council carries this forward. When an idea from the Lineage is taken up as policy, the contributor is compensated — through a community fund, time‑banked credit, or direct payment, depending on what the contributor has set on their Twenty. The source‑credit chain the Lineage already maintains makes the attribution mechanical. Idea‑flooded thinkers, who in the existing economy have nowhere to put what they generate, find here a structural outlet that doesn't require them to become founders or businesses.

Lantern carries your vote

For meetings you can't attend, for proposals you don't have time to read, for the hundred small choices a community makes weekly, Lantern votes on your behalf — the way it has reason to believe you would vote, drawn from your Twenty, your standing preferences, and (with your consent) your past pattern.

Reviewing the queue, Lantern uses Pol.is‑style bridging on your behalf — shows you not just the majority position but where the bridges across difference land, and where your own view appears in the cluster map. You vote into consensus, not blindly against the half of the room you disagree with.

You can always see what Lantern voted, and reverse anything, any time. The four hard limits hold absolutely here. Lantern is not a back door for the Council into your life. It is your mouthpiece into theirs.

The decision interface is fractal

The interface a Council voter uses on a civic question is the same shape Lantern uses on a personal question. Approval queue, importance allocation, plain language, one‑tap reverse. A resident who has used Lantern for a month already knows how to vote in the Council; a Council member voting on policy uses the same patterns they use to decide what to have for dinner.

This isn't dumbing down. It's the opposite: civic interfaces that demand a separate vocabulary from daily life lose participants. Civic and personal share an interface because they share a logic. What you would choose for yourself is structurally similar to what you would choose for the place you live in.

Legitimacy — what the Council promises

The Council's standing rests on five visible commitments:

Every vote auditable. Lantern's votes on your behalf are listed, regularly nudged for your review, and reversible in one tap.
Every proposal visible. All sources, the method used, the weighting (including any proof‑of‑knowledge gating), and the result are published. No back rooms.
Refusal is allowed. Any resident can decline to participate without losing any community right. Non‑participation is a first‑class option, not a second‑class one.
The Charter governs everything. Any Council decision can be challenged on the grounds that it violates the Charter — the four hard limits, the three cross‑cutting principles, the refusal‑of‑harm commitments. The Council can be overruled by its own constitution.
Sortition catches what voting misses. Where a decision is too important to leave to the volunteers who happen to vote, sortition randomises a deliberation panel — so the people who decide aren't only the people who shout.

What it connects to

The Council is fed by the Sensorium (gap analysis), the Lineage (ideas, with source‑credit), the Lookout (foresight on each proposal's likely branches), and Lantern (resident votes, importance allocations, the Twenty). It feeds the Tide (the test of every proposal is does this raise the Tide?), the Commons (which Council decisions become resource allocations), and the Living (which decisions become economic adjustments). The compensation mechanism is shared with the Living; the proof‑of‑knowledge gate draws on records from the Forge.

What runs underneath

Layer	Doing what job
Pol.is + bridging‑based ranking	Cross‑cluster consensus discovery for open‑ended issues
Quadratic voting (Glen Weyl / RadicalxChange)	Strength‑of‑preference allocation for contested choices
Sortition + citizens' assemblies (Ireland, France)	Random‑selection deliberation for heavy decisions
Conviction voting (Commons Stack)	Standing positions accumulate weight over time
Liquid democracy / expertise weighting	The proof‑of‑knowledge gate on binding votes
Loomio	Working open‑source decision software used in cooperatives
Decidim (Barcelona)	Open‑source participatory‑democracy platform
Better Reykjavík	Reference implementation of citizen idea‑and‑voting at city scale
Open Space Technology, World Café, Appreciative Inquiry	Facilitation methods for citizens' assemblies and large meetings
Asset‑Based Community Development (ABCD)	Proposal framing that starts from community strengths, not deficits
Continuum Party / ideas DB / compensation mechanism (your own 2014 writing)	The governance shape, the open‑input listing, and the contributor‑pays mechanism

If the Council is doing its job, every resident's voice reaches the room — even the resident who can't speak up, can't make the meeting, or doesn't know the issue is being decided. The Continuum Party's original demand was an open listing of every idea and every voice. The Council, with the working pieces named, is that demand made operational.

Tier 1 — core seven

The Hearth

Care that holds.

Origin: 2014–2022 writing on isolation, loneliness, the person stuck for years in a room contemplating bad futures, and the recurring journal observation that "over 50% of people are single in Western countries" and the support that exists for them is mostly absent until they break. The Guardian / Support / Mentor App from 2014 (which became Lantern) was the individual‑facing version of this; the Hearth is the community‑facing one — what Lantern's quiet watch escalates to, when something has to be more than an app.

The Hearth is distributed care across the lifespan — old, young, sick, dying, new‑parent, grieving, isolated, in crisis. Not a directory of services. A self‑managing infrastructure of small autonomous care teams, trained peer networks, and structural ways for neighbours to hold each other before professional services need to be called. When professional services are needed, they plug in; they don't take over.

The Buurtzorg model

The organising principle of the Hearth is borrowed wholesale from Buurtzorg — the Dutch home‑nursing organisation founded in 2006 by Jos de Blok. Around 15,000 nurses work in small autonomous teams of ~12, with no managers, no bureaucracy layer, and total local decision‑making authority. The result: roughly half the overhead of traditional home care, better health outcomes, and (this is the part most people don't believe until they see it) higher job satisfaction among nurses than any other care employer in the Netherlands.

The Hearth applies the same shape to community care more broadly. Small teams. Local authority. Long‑term relationships between the cared‑for and the carers — the same faces, week after week. No central call centre. No re‑explaining your situation to the next person on the rota. The structural enemy is the "who are you and what's the issue today?" phone call, which is how almost every existing care system experiences itself.

The three plagues

Bill Thomas's Eden Alternative (nursing‑home reform, 1991) names the three problems that turn out to be fatal to wellbeing in care settings — loneliness, helplessness, and boredom. Originally identified in elder care; equally true at every other age.

The Hearth treats them as the three things care has to interrupt:

Loneliness. Someone whose week contains no meaningful contact. Lantern's quiet watch surfaces this; the Hearth holds a roster of trained peers who can simply turn up. Not a "wellness check." A cup of tea.
Helplessness. Someone whose life has no decisions in it. The Hearth's care teams refuse to do for people what they can still do for themselves — even slowly, even badly. Helping that erases agency is harm in a kind disguise.
Boredom. The Eden Alternative's original prescription: gardens, animals, children. The Hearth treats these as care infrastructure, not amenities. Care settings with no other living things in them are designed to fail.

Care across the lifespan

The Hearth holds, by design:

The new‑parent and the small child: The community version of the missing extended family. Trained peers, lent items, meal trains, structural recognition that the first year of a child's life is when families most often break.
The young person in trouble: Peer‑support networks (more on these below) and at‑need connection to the adults in the community whose Twenty includes this kind of help, before clinical services are needed.
The chronically ill and the disabled: The Buurtzorg shape: small teams who know you, with long relationships, who plug into clinical services without those services running the show.
The mentally unwell, in crisis or maintenance: Through Open Dialogue (see below) and through peer‑support networks like the Hearing Voices Network and Alternatives to Suicide — lateral, non‑hierarchical, survivor‑led.
The old: The Buurtzorg model in its original form, plus Eden Alternative principles applied to whatever care setting exists, plus structural intergenerational connection so elders are inside the community, not parked alongside it.
The dying and the grieving: Compassionate Communities (Allan Kellehear) is the working model — end‑of‑life care at neighbourhood scale, with the surrounding community trained and organised. The Compassionate Frome project in the UK ran this model and showed dramatic reductions in emergency hospital admissions; ordinary people, trained to hold their dying neighbours, turn out to be better at it than institutions are.

Mental‑health crisis — Open Dialogue

The default response to mental‑health crisis in most places is medication and hospitalisation, often in that order, often without the person's family or networks in the room. Open Dialogue (developed in Finnish Western Lapland in the 1980s, now used internationally) does the opposite: immediate response within 24 hours, the meeting includes the person's whole network from the start, the conversation continues over weeks, medication is a last resort rather than a first one.

The outcomes are striking enough to be controversial: first‑episode psychosis treated under Open Dialogue in Western Lapland shows long‑term recovery rates that most psychiatric services consider impossible. The Hearth adopts Open Dialogue as its mental‑health crisis method — with clinical professionals plugged in but not in charge, and the community at the table from day one.

Adjacent to Open Dialogue, the Hearth supports Soteria‑style alternatives where they exist — small house‑based settings for people in acute mental distress, relationship‑first rather than medication‑first, originally Loren Mosher's work in the 1970s and quietly continued in Europe and parts of the US.

Peer support — lateral, not hierarchical

A large part of care that actually works isn't professional. It is people who have been through the same thing, sitting with people going through it now. The Hearth runs, hosts, or plugs into:

Hearing Voices Network (Marius Romme, 1988) — peer groups for people who hear voices, treated as a human experience to be made meaning of rather than a symptom to be silenced.
Alternatives to Suicide — peer groups for people with suicidal experience, talking honestly about what most clinical settings refuse to discuss.
Recovery cafes — informal community spaces for people in addiction recovery and the people around them.
Death cafes — small gatherings to talk honestly about dying, run as a global movement since 2011.
Compassionate Frome‑style neighbourhood networks — volunteers trained to sit with the lonely, the bereaved, and the recently discharged from hospital.

The architecture — trauma‑informed by default

The Hearth isn't only an organisational pattern. It is also a set of architectural and environmental commitments — trauma‑informed community design. Spaces that don't surprise. Predictable rhythms. Quiet corners available without explanation. Lighting that doesn't fight the nervous system. The Hearth's input into the Garden (place and ecology) is to make sure the physical environment of the community supports the settling of distressed nervous systems, rather than producing them.

How Lantern feeds the Hearth

Lantern's quiet watch is the upstream of the Hearth. When a resident's check‑in patterns, activity signals, or Lookout‑flagged branch suggest something is wrong, Lantern surfaces this to the resident first, with options — including the option to be quietly connected to a peer or a care team. With consent, the Hearth receives a request, not a diagnosis. No database, no log, no record outside the resident's own phone.

The Twenty feeds the Hearth too — people who have listed care‑related offers are who the Hearth contacts when a need matches. Most care, by volume, isn't done by professionals; it's done by neighbours who know how to. The Twenty makes those neighbours findable.

What it connects to

The Hearth is fed by Lantern (need surfaced from the quiet watch), the Twenty (residents whose offers match the need), and the Sensorium (which reads the care dimensions of the community in aggregate). It feeds the Mend (when conflict and care overlap), the Threshold (new arrivals often need holding before they need anything else), and the Commons (which provides the physical spaces care happens in). The Council allocates the Hearth's budget and method choices through the same proposal‑and‑vote process as anything else.

What runs underneath

Layer	Doing what job
Buurtzorg (Jos de Blok, Netherlands)	Small autonomous teams, no managers, long relationships
The Eden Alternative (Bill Thomas)	The three plagues diagnostic; gardens / animals / children as infrastructure
Open Dialogue (Western Lapland)	Mental‑health crisis method: 24‑hour response, networks included, medication last
Soteria houses (Loren Mosher)	House‑based, relationship‑first alternatives in acute mental distress
Compassionate Communities (Allan Kellehear)	End‑of‑life care at neighbourhood scale
Compassionate Frome project (UK)	Working evidence that volunteer‑led community connection reduces emergency admissions
Hearing Voices Network, Alternatives to Suicide	Peer‑support networks for experiences clinical settings often refuse to discuss honestly
Recovery cafes, Death cafes	Informal community spaces for honesty about addiction and dying
Trauma‑informed community design	Architectural and environmental commitments that don't produce distress
Universal Basic Services (Anna Coote / IGP)	The policy frame: care as infrastructure, not commodity
Guardian / Support / Mentor App (your own 2014 writing)	The individual‑facing precursor that became Lantern; the Hearth is the community side

If the Hearth is doing its job, no one in the community sits in a room for ten years contemplating bad futures alone. The journal's recurring observation — that the support a person needs before they break almost never arrives — becomes structurally false, here. Care that holds, before the breaking. The fire people sit around.

Tier 2 — expansion nine

The Commons

What we hold together.

Origin: the journals' returning observation that almost everything important — land, knowledge, the tools and machines a community needs to feed and shelter itself, the digital infrastructure people now live on — has been quietly transferred from "held in common" to "owned by someone." The Commons is the organ that holds the things a community does not allow itself to lose. Elinor Ostrom won the 2009 Nobel in Economics for showing this can be done well; the design here is hers, with the contemporary movements that have carried her work forward.

The Commons is the layer of the community's shared resources — land, housing infrastructure, tools, knowledge, energy, digital infrastructure, working capital, seeds — held in common, governed by the people who use them, protected from enclosure (privatisation, extraction, capture) by visible governance rules. What gets shared, who shares in it, how it's protected, and how it's grown are the four questions every Commons decision answers.

Ostrom's eight principles

The empirical answer to "can commons actually be governed sustainably, or do they always collapse into the tragedy of the commons?" is Elinor Ostrom's. After decades of field research on commons that didn't collapse — irrigation systems in Spain and the Philippines, fisheries in Maine, forests in Nepal, grazing lands in Switzerland — she identified eight design principles that successful commons share. The Commons adopts all eight as governance requirements:

Clearly defined boundaries. Who has rights to the commons, and what the commons covers, is unambiguous.
Rules fit local conditions. Governance matches the actual circumstances of the people and the resource — not copied from anywhere else.
Those affected can change the rules. Participatory governance, not top‑down imposition. (This is where the Council plugs in.)
The rules are respected by outside authorities. The commons is recognised, not overridden, by surrounding governments and institutions.
Monitoring by accountable monitors. The people watching the commons answer to the people who use it.
Graduated sanctions. Rule violations get warnings first, escalating only where needed.
Cheap and accessible dispute resolution. Conflicts get worked out locally and quickly. (This is where the Mend plugs in.)
Nested governance. Smaller commons sit inside larger ones, with appropriate authority at each level — how local commons relate to federated and regional ones. (This is where the Federation plugs in.)

What gets held in common

The Commons holds, by design:

Land: Through Community Land Trusts — non‑profit entities holding land permanently on behalf of the community, separating the value of the land from the value of what's built on it. CLTs have a 50‑year track record in the US and UK; they make permanently affordable housing structurally possible. The land‑value capture mechanism is Henry George's land‑value tax: the uplift in land value created by community development returns to the community, not to private owners.
Tools and machines: Through libraries of things (working examples in hundreds of cities), tool libraries, seed libraries, and repair cafes (over 2,000 worldwide; meet monthly to repair what's broken rather than replace it). The Right to Repair movement extends this: legislation requiring manufacturers to release parts and schematics, so things can actually be fixed.
Open hardware and machines for community resilience: Open Source Ecology (Marcin Jakubowski) has designed 50 industrial machines — tractors, brick presses, bakery ovens, solar collectors — with full open‑source blueprints, buildable from scrap and modular parts, deliberately so any community can produce its own. The Commons holds the local versions.
Knowledge: Open libraries, open data, open educational resources, open research. What the community learns is owned by the community and contributes to the wider knowledge commons. The Lineage's source‑credit chain makes attribution mechanical, so contributors are honoured without enclosure.
Energy and water infrastructure: Community‑owned solar arrays, batteries, microgrids, water systems. Working examples from Feldheim (Germany) to Wolfhagen to community energy cooperatives across the EU. Commons‑owned energy is mechanically resilient against utility price shocks and politically resilient against capture.
Digital infrastructure: The community's servers, identity systems, mesh networks, communication tools. Where possible, federated and open‑source — so that the digital substrate the community runs on is owned by the community, not by a platform whose terms can change overnight.
Working capital — mutual credit: Community currency / mutual credit systems like Sardex (Sardinia; ~10,000 businesses, 40+ years of operating data) and the Bristol Pound tradition. Local economic activity gets denominated in a unit that can't leave the community and can't be hoarded, only spent. Borrowed engineering — this works and has worked for decades.
Seeds: Through local seed libraries and seed‑saving networks. Plant genetic diversity is one of the most fragile commons, collapsing globally; community‑held seed is one of the most quietly important things a place can keep.

Worker cooperatives — commons applied to work

The Commons extends to how livelihoods are organised. The reference implementation is Mondragon: the network of worker cooperatives in the Basque region of Spain, started in 1956 with one small workshop, now ~80,000 worker‑owners across industrial, retail, financial, and educational enterprises. Decisions are democratic. Pay ratios between highest and lowest are capped (originally 3:1, now ~6:1 — still an order of magnitude tighter than capitalist firms). The cooperative network reinvests in its own workers.

The Commons is the layer that supports founding, capitalising, and federating worker cooperatives inside the community — with the legal and financial scaffolding most aspiring co‑op founders currently have to invent alone. The Living handles the day‑to‑day economics; the Commons handles the structural ownership.

Platform cooperativism — the digital version

Where extractive platforms (Uber, Airbnb, Deliveroo) have captured swathes of the local economy in the last 15 years, platform cooperativism (Trebor Scholz) is the parallel movement: digital platforms owned by the workers and users they serve. Working examples: Stocksy United (photographer‑owned stock photography), Up & Go (worker‑owned house cleaning in NYC), Fairbnb (community‑owned home rental). The Commons is the substrate platform cooperatives are built on locally.

Protecting the Commons from enclosure

The historical pattern is clear: commons that aren't actively defended get enclosed. Land, knowledge, infrastructure, digital substrate — all routinely transferred from community ownership to private capture, often quietly, often framed as efficiency. The Commons holds three structural defences:

The Charter (see above) explicitly lists what cannot be sold, privatised, or enclosed. The list is short, plain, and amendable only by a supermajority through the Council.
Steward ownership structure for the community organisation itself — a purpose trust or foundation that legally cannot be sold (Patagonia 2022, Mozilla, Carlsberg Foundation are well‑known examples). The container the Commons sits in can't itself be acquired.
Transparent monitoring by the people who use the commons (Ostrom's principle 5). Quiet enclosure requires darkness; visible commons are harder to take.

What it connects to

The Commons is governed by the Council (proposals to add, remove, or change commons rules), monitored by the Sensorium (the state of each commons feeds the community profile), defended by the Charter (the anti‑enclosure clause), federated through the Federation (smaller commons nested in larger ones, Ostrom's principle 8), used as infrastructure for the Living (worker cooperatives, mutual credit) and the Hearth (which uses the Commons' physical spaces for care).

What runs underneath

Layer	Doing what job
Ostrom's 8 principles (Nobel 2009)	The governance framework for sustainable commons
Community Land Trusts	Permanent community ownership of land, with separated land/improvement values
Henry George land‑value tax	Community capture of land‑value uplift created by community development
Libraries of Things, tool libraries, seed libraries	Shared physical resources, low‑friction access
Repair Cafes (2,000+ worldwide)	Repair culture against disposability
Right to Repair movement	Legislative defence of repairability
Open Source Ecology (Marcin Jakubowski)	Open hardware for community resilience — 50 industrial machines
Mondragon (Basque cooperative network)	Worker‑cooperative reference implementation, 80,000 worker‑owners
Platform cooperativism (Trebor Scholz)	Worker‑ and user‑owned digital platforms
Mutual credit (Sardex, Bristol Pound)	Local community currency / working capital that can't leak out
Community energy cooperatives (Feldheim and many others)	Community‑owned energy infrastructure
Steward ownership / purpose trusts	The container that can't be sold; protects the Commons from acquisition
Foundational Economy framework	The intellectual frame: what infrastructures everyday life actually depends on

If the Commons is doing its job, the things a community cannot afford to lose — its land, its tools, its knowledge, its capacity to feed and shelter itself, its digital substrate — stay held in common across generations. The tragedy of the commons is a story about badly‑governed commons. Well‑governed commons last for centuries.

Tier 2 — expansion nine

The Mend

Repair, not punishment.

Origin: every community produces conflict. The question isn't whether harm happens but whether the community has the structural capacity to repair it. The dominant inherited system — punitive justice, courts, prisons — has the worst evidence base of any major social institution. The Mend uses the alternative bodies of work that do have evidence: restorative justice, nonviolent communication, and circle process. None of them are new. All of them work.

The Mend is the community's conflict and repair infrastructure — trained facilitators, established methods, and clear pathways for what happens when someone has been harmed, something has been broken, or two people in the community cannot work it out themselves. The goal is repair of relationship and obligation, not punishment. Where professional services are needed (police, courts, medical), they plug in; they don't take over. Where they aren't, the community handles it — well, structurally, with named methods.

Why "Mend" and not "Justice"

The word "justice" carries the inherited shape: accusation, trial, verdict, punishment. The Mend's working assumption is that this shape is rarely what produces repair. People who have caused harm need to face it, understand it, and act on it; people who have been harmed need to be heard, believed, and made whole as far as is possible; the community around them needs to be re‑knit.

"Mend" names the work directly. What got broken is being repaired. What got torn is being knit. What got lost is being acknowledged. Punishment is the failure mode the Mend works to avoid, not the goal it works toward.

Three methods

The Mend draws on three bodies of practice as load‑bearing:

Restorative justice: Originally drawn from Indigenous practices worldwide (Māori, North American Indigenous, African) and formalised in the modern era through Howard Zehr's work in the 1970s. The structure: harmed person, harming person, and the surrounding community meet (when both consent) to establish what happened, what's needed for repair, and what the person who caused harm will do. Working evidence from Norway, New Zealand, Belgium, the schools movement, and community settings worldwide. Reoffending rates drop substantially. Both parties report higher satisfaction than with court processes.
Nonviolent Communication (NVC): Marshall Rosenberg's framework, 1960s onward. A structured way of speaking and listening across conflict: observations (without judgement), feelings (without attribution), needs (without strategy), requests (without demand). Used in schools, prisons, hospitals, and conflict zones. The Mend trains a working subset of community members in NVC so facilitation is locally available without external consultants.
Circle process: Drawn from Indigenous talking‑circle practices and brought into Western frame by Kay Pranis and others. A seated circle, a talking piece, structured rounds, no cross‑talk. Used for everything from light community decision‑making to serious harm response (peacemaking circles in sentencing contexts). Slow, deliberate, and effective at producing the kind of listening adversarial processes structurally prevent.

What the Mend handles

By design:

Interpersonal conflict — neighbours, housemates, colleagues, family members in the community who cannot resolve something without help.
Low‑level harm — theft, damage, breaking community rules — where restorative process produces better outcomes than punitive ones and the harmed party consents.
Group conflict — when a sub‑community, working group, or cohort has fractured and needs structured repair work.
Charter conflicts — when someone believes a community decision or another member's action has violated the Charter's commitments, the Mend is the first venue.
Historical repair — longstanding unresolved harms within the community, where a structured process is finally possible.

When the community handles it, and when it doesn't

The Mend is not a substitute for police, courts, or medical services where they are genuinely needed — serious violence, abuse of children, situations where someone is in immediate danger. The Mend's working assumption: the community handles what the community can handle, and the triage is honest about what it can't. Where professional services are needed, they are called. The Mend holds the relationship work that runs alongside (and often survives long after) the formal process.

The boundary is drawn visibly — published, debated by the Council, available to anyone who wants to know what the Mend will and won't take on. No pretence of competence the design doesn't have.

How the Mend connects to the rest

The Hearth. When conflict and care overlap — family conflict during a parent's illness, housing conflict during a mental‑health crisis — the Mend and the Hearth work together. Repair often needs care; care often needs repair.
The Council. When conflict is about a community decision (a resource allocation, a rule, a proposal), the Mend can run parallel to the Council's process — ensuring the relational work happens alongside the governance work.
The Charter. The Charter's anti‑harm commitments are enforced through the Mend, not through sanction. If someone's behaviour violates the Charter, the first response is structured repair, not exclusion. Where repair fails, where harm continues, exclusion exists as a last resort — named, visible, decided by the Council with the Mend's input.
Lantern. Lantern carries the Mend's methods into ordinary daily friction — NVC framing suggestions when you're writing a difficult message, circle‑process invitations when a small thing shouldn't get bigger.

What it connects to

The Mend is fed by Lantern (which surfaces situations that may benefit from facilitated repair), the Hearth (where care and conflict overlap), and the Council (which sets the Mend's scope and resourcing). It is held to the Charter's commitments and feeds back to the Story — the community's own record of repair, kept honestly, is part of how it remembers itself.

What runs underneath

Layer	Doing what job
Restorative justice (Indigenous origins; Howard Zehr, 1970s onward)	Structured harmed‑person / harming‑person / community repair process
Nonviolent Communication (Marshall Rosenberg)	Speaking and listening framework for conflict
Circle process (Indigenous origins; Kay Pranis)	Talking‑circle method for decisions and repair
Conflict transformation (John Paul Lederach)	Theoretical frame for long‑term relationship work
Sociocratic objection‑handling	Light‑weight conflict method for governance disagreements
Truth and Reconciliation models (South Africa, Canada)	Process for historical repair at community scale
Therapeutic jurisprudence; community / drug courts	Working precedents for non‑punitive responses to harm
Loomio	Software for working through governance disagreements

If the Mend is doing its job, conflict in the community produces repair more often than it produces exclusion, and the community gets better at handling its own friction over time. No community is without conflict. The mark of a healthy one is what happens next.

Tier 2 — expansion nine

The Threshold

How people arrive, and how they leave.

Origin: communities that work spend visible effort on arrival and departure. Communities that don't, don't. The instinct in modern housing is to skip both — you sign a lease, you live there, you stop living there. The Threshold is the organ that names arrival and departure as infrastructure, not formalities.

The Threshold holds the structures through which people arrive in the community (move‑in, orientation, integration into the other organs), through which people visit (different rights from residents but real belonging while present), and through which people leave (chosen departures honoured; difficult departures handled with care).

Arrival — the missing organ in most places

Most modern communities (estates, suburbs, apartment blocks, even most cohousing) do arrival badly. A new resident moves in. There may be a welcome pack. There is almost never a structured process for being introduced to neighbours, learning the community's quiet rules, finding the residents whose Twenty might match theirs, or being held while they figure out where they fit. The cost — in loneliness, in early‑departure, in the slow ambient unwelcome that most newcomers experience — is enormous and largely invisible.

The Threshold treats arrival as a real process with stages.

Three stages of belonging

The Threshold borrows the structure that anthropologist Arnold van Gennep identified in 1909 across hundreds of cultures' rites of passage — the same shape recurring everywhere because it works:

Separation: The arriving person leaves their previous context. Recognised: this is a real loss, not just a logistic. The Threshold's first contact is acknowledgement of what's being left.
Liminality — the in‑between: The arriving person is neither outsider nor full resident yet. They have help (a host or buddy from the existing community), reduced expectations, time to learn how things work. The Threshold's structural job is to make this stage hospitable rather than disorientating — it usually lasts weeks to months.
Incorporation: The arriving person becomes a resident. Marked, named, witnessed. Lantern activates fully (the Twenty becomes live, the Council voice becomes counted, the Hearth becomes available). A small ritual — a meal, a gathering, a written welcome — not because ritual is required but because the threshold from "newcomer" to "one of us" deserves a marker.

What arrival actually involves

In practice:

A host or buddy from existing residents — someone who knows how things work, available for questions, present at the first weeks' community events.
Orientation to the organs — not as paperwork, but as a guided tour. Where the Hearth meets, how the Council works, what the Sensorium says about the community right now, how to use the Commons (libraries of things, mutual credit, shared spaces).
Twenty‑building — the buddy helps the new resident build their initial Twenty, slowly. Most people freeze when asked what they'd offer; with help and time, the list fills in naturally.
Permission to refuse — from day one, the new resident is told what's optional. Lantern is opt‑in. Council voting is opt‑in. The Twenty is opt‑in. Participation is invitation, not requirement. The Charter's right to refuse the system entirely is named at the threshold, not buried.

Visitors — belonging without residency

The Threshold also holds visitors: people who are in the community for days, weeks, or months but aren't moving in. Friends, family, exchange residents from other federated communities, journalists, researchers, prospective residents. Visitors get real belonging while present — access to the Commons' shared spaces, invited to events, given a host — without the rights or obligations of residency. The distinction is visible, not hidden.

This matters more than it might seem. Communities that can't receive visitors well become brittle and inward‑facing. Communities that can become trans‑local nodes.

Departure — honoured, not erased

When a resident chooses to leave, the Threshold treats it as a real event: marked, witnessed, with the community having a chance to say goodbye. The departing resident takes their Lantern with them (local‑first; nothing was ever held elsewhere). Their contributions to the Lineage remain with their source‑credit intact. Their seat in the Story is preserved — departure is not erasure.

Where someone wants their record removed (the right to be forgotten), the Threshold runs that process — balancing individual right against the community's memory. Default resolution: removable‑but‑not‑destroyable — the community remembers that a chapter happened, without preserving the departed resident's role in it, if they so choose. Most residents won't want this; the small number who do are accommodated structurally.

Difficult departures — when someone is asked to leave

Rare, but possible. Where the Mend's repair process has failed and harm is ongoing, the Council can decide on exclusion as a last resort. The Threshold holds the process:

The decision is named, with reasons published.
The person being asked to leave has the right to be heard and to appeal through the Mend.
The community provides genuine practical support for the next housing — expulsion into homelessness is harm the community refuses to inflict.
Where appropriate, federated communities are notified so the same person can be received elsewhere with full context — not blacklisted, but not hidden either.

What it connects to

The Threshold is the front door (and the back door) to every other organ. Arrival activates Lantern, builds the Twenty, opens the Hearth, enters the Council. Departure is honoured through the Story and accompanied by the Mend where needed. Visitors connect via the Federation. The Charter's rights of refusal and departure are named at the Threshold, every time, by design.

What runs underneath

Layer	Doing what job
Rites of passage (Arnold van Gennep, 1909)	The three‑stage structure separation / liminality / incorporation
Cohousing welcome practices (literature 1990s onward)	Working examples of structured arrival in intentional communities
Buddy / host systems	The peer model for guiding new residents through their first weeks
Welcoming Cities movement	Working frameworks for receiving newcomers at municipal scale
Ubuntu philosophy	"I am because we are" — the framing for what belonging means
Bayanihan (Philippines)	Mutual‑aid practice during transitions like moving
Right to be forgotten / data‑portability rights	Departing residents' control over their record
Solid pods (from Lantern)	Mechanically, what departing residents take with them

If the Threshold is doing its job, no one arrives in this community and feels lost, and no one leaves and feels erased. Arrival is held; departure is honoured. The two ends of belonging matter at least as much as the middle.

Tier 2 — expansion nine

The Forge

Learning, mutual and lifelong.

Origin: the dominant model of education — one‑directional, age‑segregated, credential‑focused, ending in your twenties — is a 19th‑century industrial design that suits almost nobody. The journals returned often to the observation that most people lose access to learning roughly when they need it most. The Forge is the organ for what learning looks like when the community designs it for itself.

The Forge is the community's learning infrastructure — for children, for adults, for elders. Mutual rather than hierarchical (most teaching is done by other community members, not professionals), lifelong rather than front‑loaded (you keep learning until you stop), and self‑directed rather than curricular (you learn what you want, not what a syllabus says you should). Professional educators plug in where their expertise is needed; they don't run the show.

The premise

What the Forge assumes that most education systems don't:

People learn best when they choose what to learn.
Mixed‑age learning works better than age‑segregated learning — for both ends and the middle.
Most genuinely useful knowledge in any community is in the heads of the residents already, not professional teachers.
Learning is a lifelong activity; the idea that it ends in your twenties is a recent and damaging anomaly.
Credentials are sometimes useful; they are not what learning is for.

Children — Sudbury and Reggio Emilia

Two working models, fifty years of evidence each:

Sudbury Valley School (Massachusetts, 1968) and the network of Sudbury‑model schools worldwide. Self‑directed democratic education — children decide what they do each day, governance is by one‑person‑one‑vote among students and staff equally, no curriculum, no grades, no tests. Graduates do as well as or better than conventionally schooled peers on standard outcome measures; they do dramatically better on measures of agency, self‑direction, and adult satisfaction.

Reggio Emilia (Italy, post‑WWII). Early‑childhood approach treating children as competent, capable, full of potential rather than empty vessels to be filled. Learning emerges from the child's interests, with educators as collaborators and documenters, not deliverers. Now adopted in early‑childhood settings across the world.

The Forge supports children's learning along these lines — not as a replacement for whatever formal schooling parents choose, but as the community's parallel infrastructure for the kinds of learning formal schooling doesn't do.

Adults — folk schools and study circles

The Danish folk high school tradition (højskole, founded by Grundtvig in 1844) is the working model for adult learning at community scale. Non‑credential, non‑graded, weeks‑to‑months immersive learning in subjects chosen by the learners — politics, philosophy, crafts, languages, sciences, music. 70+ folk schools currently operating in Denmark; the model has been adopted by Sweden, Norway, Germany, and the wider Nordic region.

Smaller in scale, equally important: study circles (the Swedish studiecirklar tradition). Six to twelve people, meeting weekly for a season, working through a subject together. No teacher; the participants are the teachers. Sweden has roughly 280,000 study circles a year operating at this scale. The Forge runs them as a routine offer.

The Living Library

The Living Library / Human Library movement (Copenhagen, 2000) treats people as "books" that can be "borrowed" for conversation. The Forge runs an ongoing version: residents who hold particular knowledge, lived experience, or skill can be "checked out" for a structured conversation by anyone in the community who wants to learn from them. Combined with the Twenty's teach‑offers, this turns the community's collective knowledge into a navigable resource.

Apprenticeship as default

For skills that need to be learned by doing, the Forge runs on apprenticeship. A new resident wanting to learn carpentry finds (through the Twenty) the residents who already do it, and asks. The structure: the apprentice works alongside the practitioner, learns by doing, is paid (often through mutual credit from the Commons) for contribution rather than charged for tuition.

This is how almost all skills used to be learned, in almost every culture, before industrial schooling. It still works. The Forge makes it structurally available again.

How the Twenty feeds the Forge

The Twenty is the Forge's directory. Residents whose Twenty includes "I'd teach X" become findable by residents whose Twenty includes "I'd learn X." Lantern handles the matching, trust‑weighted as everywhere else, and lets the conversation happen directly.

This is the simplest piece of infrastructure the Forge provides — and one of the most important. Most adults don't learn what they want to learn not because no one in their community knows it, but because they have no way of finding out who does.

The Lineage and the Forge — making contributes to learning

The Lineage and the Forge are closely coupled. When a resident makes something through the Lineage, others can learn from how it was made. Apprentices can see the full chain of ideas, drafts, dead‑ends, and decisions. Learning by reading isn't replaced by learning by doing, but the two reinforce each other — the practitioner sees how the maker thought; the maker sees what the apprentice didn't understand.

What it connects to

The Forge is fed by the Twenty (teach and learn offers), the Lineage (making as learning material), the Calendar (when sessions happen), and the Commons (libraries, tools, the physical infrastructure of learning). It feeds the Hearth (intergenerational contact is care; learning together holds people together), the Council (the proof‑of‑knowledge gate draws on Forge records), and the Story (the community teaches itself about itself through what the Forge holds).

What runs underneath

Layer	Doing what job
Sudbury Valley School and the Sudbury network	Self‑directed democratic education for children
Reggio Emilia approach (Italy)	Early‑childhood education treating children as competent collaborators
Danish folk schools (Grundtvig, 1844 onward)	Non‑credential immersive adult learning
Swedish study circles (studiecirklar)	Small peer‑led adult learning groups, ~280,000 / year
Living Library / Human Library (Copenhagen 2000)	Residents as "books" available for structured conversation
Apprenticeship traditions (worldwide, all eras)	Skills learned by working alongside practitioners
Communities of practice (Etienne Wenger)	Theoretical frame for how learning happens in groups
Open education resources (MIT OCW, Khan Academy, OER movement)	Public free knowledge the Forge can draw on
Unschooling tradition (John Holt onward)	The intellectual frame for self‑directed learning
Bildung (German tradition)	The concept of lifelong self‑cultivation through community

If the Forge is doing its job, no one in the community loses their access to learning because they aged out of school or never went, and the knowledge held inside the community's own residents stays alive by being passed on. Learning is not something that happens to you when you're young. It's something you do for as long as you're awake.

Tier 2 — expansion nine

The Garden

Place, kept.

Origin: a community is its place. Not its people abstractly, but its people in this particular soil, with this particular light, near these particular trees and waters. The dominant pattern of the last century has been to treat place as backdrop — interchangeable, paveable, sellable. The Garden treats it as substrate. What is grown, built, kept, rewilded, and honoured on the land is part of who the community is.

The Garden is the organ for the community's relationship with its place — the land, the water, the air, the plants, the animals, the built environment, the seasonal rhythms. It holds what is grown (food, materials, beauty), what is built (the physical patterns the community lives in), what is restored (ecological repair work), and what is kept (the land's stories, both colonial and Indigenous, and the obligations they carry).

Permaculture as the backbone

Permaculture (Bill Mollison and David Holmgren, Tasmania, late 1970s) is the design framework for the Garden's ecological and agricultural work. Three ethics — care for the earth, care for people, fair share of surplus — and twelve design principles that produce productive, resilient, low‑input landscapes. Used at every scale from backyard to bioregion, with five decades of practical evidence. Australian in origin; well‑suited to the project's likely climates.

The community's food production, water systems, energy siting, and waste cycles are designed under permaculture principles. Where industrial agriculture extracts, the Garden cycles. Where industrial development levels, the Garden contours.

The Doughnut, applied locally

The cross‑cutting Doughnut principle does its operational work in the Garden. Above the social floor, the community meets its residents' needs (housing, food, care, dignity); below the ecological ceiling, it fits inside what the planet can carry — measured locally as climate footprint, water use, biodiversity impact, soil health, waste production. The Garden is where the ecological half of the Doughnut becomes routine measurement and routine intervention, not slogan.

Working examples: Amsterdam, Brussels, Portland, Melbourne, and Sydney are all running community‑scale Doughnut implementations through the Doughnut Economics Action Lab. Recent academic work (Berg & de Schutter, 2026) is starting to assess these as tests of degrowth transformative capacity. The Garden adopts this work as its measurement layer.

The 15‑minute community

Carlos Moreno's 15‑minute city framework (the working version of an idea Jane Jacobs and others articulated decades earlier): everything a resident needs for ordinary daily life should be reachable within 15 minutes on foot or by bike — food, work, schooling, care, green space, sociability. Adopted in policy form by Paris (Anne Hidalgo, 2020 onward), Milan, Melbourne, Portland, and many smaller cities.

The Garden treats the 15‑minute structure as a design target for any community implementation. The walkability dimension in the Sensorium is what measures progress against it.

Pattern Language — the building‑scale design

Christopher Alexander's A Pattern Language (1977) and the wider body of his work give the Garden its architectural and built‑environment design language: 253 patterns from "Mosaic of Subcultures" at city scale to "Window Place" at room scale, each describing a recurring problem and a working solution. Alexander's claim — that there are objectively better and worse ways to build the environment human beings live in — has stood up surprisingly well; subsequent research on biophilic design, fractal complexity in environments, and trauma‑informed architecture has converged on much of his work.

Where the community builds, it builds patterns. Where it inherits ill‑designed structures, it modifies toward them.

Indigenous land relationships — Country

In any place the community settles — certainly in Australia, where the project originates — the land has prior custodians whose relationship with it precedes the community by tens of thousands of years. The Garden does not treat acknowledgement of country as a formality. It treats the relationship as ongoing infrastructure.

Country (the Aboriginal Australian frame) is not landscape but active reciprocal relationship — Country has obligations to its people; its people have obligations to Country. The Garden's working practice includes:

Real relationships with the traditional owners of the specific land the community sits on — not symbolic acknowledgements, actual partnerships where the traditional owners consent to and shape what happens.
Indigenous fire management practice (cultural burning) where local knowledge holders are available to teach and lead it.
Native species and traditional plant knowledge centred in the community's food and medicine systems.
The CARE principles for any data collected about the land or its Indigenous heritage.

The same shape applies in other places with different Indigenous frames: satoyama in Japan, buen vivir across Latin America, Hozhó in Diné country — each with its own depth, each carrying frames of human‑and‑land relationship the dominant Western paradigm has lost.

What the Garden grows

Food first — through community gardens, market gardens, food forests, and home growing supported by shared knowledge and seeds (the Commons' seed library). The Edible Schoolyard tradition (Alice Waters, 1995) provides one working model for combining food‑growing with the Forge.

Materials second — wood, fibre, dye plants, building materials grown on land the community controls.

Beauty third — ornamental and wild plantings that turn out, on close inspection, not to be third at all. Communities surrounded by beauty tend to flourish; communities surrounded by ugly built environments tend to fall apart. The Garden takes this as design constraint, not luxury.

Restoration and rewilding

The Garden also holds the community's restoration work — bringing back what was lost. Local rewilding (often small‑scale: a riverbank, a corner of paddock, a road verge), native species reintroduction, soil rebuilding, water‑system repair. Transition Towns (Rob Hopkins, 2005, now ~1,400 communities across 50 countries) provides the working community‑scale version of this work; the Garden adopts what they've learned.

Trauma‑informed and biophilic architecture

The Hearth's trauma‑informed commitments do their built‑environment work here. Spaces that don't surprise the nervous system. Predictable rhythms. Quiet corners. Lighting that doesn't fight the body. Biophilic design — following Edward O. Wilson's framing — treats human contact with living systems (plants, water, animals, daylight, weather) as nervous‑system nutrition rather than decoration. The Garden is the layer that ensures the physical environment supports the settling of distressed nervous systems rather than producing them.

What it connects to

The Garden is held in common through the Commons (land, water, infrastructure), governed by the Council, monitored by the Sensorium (the green‑space, walkability, environment, energy dimensions all read the Garden), rhythmed by the Calendar (seasonal work), and connected outward through the Federation (ecological systems don't respect community boundaries; bioregional cooperation is necessary). It supplies the Hearth with trauma‑informed environments and the Forge with outdoor learning sites.

What runs underneath

Layer	Doing what job
Permaculture (Mollison & Holmgren, Tasmania)	The agricultural and ecological design framework
Doughnut Economics (Kate Raworth)	The ecological‑ceiling / social‑floor measurement frame
15‑minute city (Carlos Moreno)	Walkable‑community design target
A Pattern Language (Christopher Alexander)	The architectural and built‑environment design vocabulary
Country (Aboriginal Australian frame)	Active reciprocal relationship with the specific land
Satoyama, buen vivir, Hozhó (other Indigenous frames)	Place‑based relationship vocabularies in other regions
Transition Towns (Rob Hopkins, 2005)	Community‑scale restoration and resilience practice
Edible Schoolyard (Alice Waters, 1995)	Food‑growing as community infrastructure and learning
Cultural burning / Indigenous fire management	Where local knowledge holders are available, central to land care
Biophilic design (E. O. Wilson onward)	Human contact with living systems as nervous‑system nutrition
Trauma‑informed architecture	Built environments that don't produce distress
Cradle‑to‑Cradle design (McDonough & Braungart)	Material flows that return to soil or industrial loops
Bioregionalism	The intellectual frame for thinking at watershed and ecosystem scale

If the Garden is doing its job, the community lives inside its place rather than on top of it, and the land is better for the community's presence rather than worse. Permaculture's third ethic — fair share of surplus — turns out to be most of what the entire design is trying to live up to.

Tier 2 — expansion nine

The Living

Work and care, fairly held.

Origin: 2014–2022 writing on the people who work hard on the things that matter but earn nothing from them, on the "20 options" mismatch between skills offered and jobs taken, on the inventor stipend ("minimal income to survive to work on the ideas until the ideas produce outcome"), and on the journals' direct policy proposal — "everyone should get a base income or cheap housing with people put in areas of similar types and interest, for meaning to life it works." The Living is the organ that handles the day‑to‑day economic flow on top of the structural ownership held by the Commons.

The Living is the community's livelihood layer: how people actually pay for things, get paid for things, and have their contribution acknowledged whether or not the market values it. Most residents will combine waged or salaried work, cooperative member income, mutual credit earned and spent locally, care obligations honoured as work, community‑funded contribution stipends, and (when an idea they had becomes policy) ideas compensation through the Council. The Living is the accounting layer that holds the mix.

The premise

Industrial‑era work makes assumptions that are quietly falling apart. That income comes from one place (an employer); that unpaid work doesn't count (it does — the entire care economy sits on it); that earning your living and being useful are the same thing (often they aren't, in either direction); that the day is divided into nine‑to‑five waged hours and "free time" (most people's lives don't fit this shape); that work is paid in only one currency (this has never been true in any healthy community).

The Living doesn't try to abolish waged work — for most residents most of the time, it remains a major part of income. It does refuse to treat waged work as the only legitimate economic activity, and it builds the layers underneath that let other forms of contribution actually pay.

The income mix

A typical resident's income, in the Living, might be a combination of:

Waged or salaried work: Conventional employment, either outside the community or inside it.
Worker‑cooperative income: Income from cooperative ventures the resident is a member of — profit‑sharing rather than wages, democratic governance rather than employment. The Commons holds the legal and capital scaffolding; the Living handles the day‑to‑day accounting.
Mutual credit: Hours given through the Twenty's time‑banked mode build credit, spent on other residents' offers. Working examples: Sardex (Sardinia), Time Banks USA, the UK Timebanking network.
Care work, honoured as work: Care for children, the old, the ill, the disabled, the grieving — named, counted, and compensated through the community fund. The 50‑year feminist economics tradition (Marilyn Waring's If Women Counted, 1988 onward) is operationalised here: unpaid care work is the bedrock of every economy, and a community that doesn't compensate it is extracting from its own residents.
Contribution stipends: The 2014 writing's "minimal income to survive while developing ideas" becomes structural. Where a resident is working on something the community has reason to want — an invention, a long‑form project, research, community organising — the community fund (governed by the Council) provides a contribution stipend for the duration. Not charity; the community is making a bet on what the resident is making.
Ideas compensation: When an idea from the Lineage becomes Council policy, the originator is compensated — from the community fund, time‑banked credit, or direct payment, depending on what they've set on their Twenty. The Lineage's source‑credit chain makes attribution mechanical.
Basic services and (where adopted) basic income: Universal Basic Services (Anna Coote, IGP) makes some categories of need — housing, transport, food, care, digital connection — collectively provided rather than individually purchased. Where a Universal Basic Income programme exists at policy level (Iran, Mongolia, Alaska, Kenya, Finland trials), the Living receives it. Where it doesn't, the community fund + UBS arrangement does some of the same work locally.

Worker cooperatives — the day‑to‑day

The Commons holds the legal and capital scaffolding for worker cooperatives; the Living is where they operate. Mondragon remains the reference implementation (~80,000 worker‑owners, 6:1 pay ratio cap, democratic governance), but smaller working examples are everywhere: Cooperative Home Care Associates (NYC, ~2,000 worker‑owners), Suma Wholefoods (UK, operates with flat pay across all roles), the cooperative networks of Emilia‑Romagna in Italy.

For new co‑op founders, the Living provides the practical infrastructure most aspiring founders have to invent alone: shared bookkeeping, shared legal templates, shared mentorship from existing co‑ops, mutual‑credit bridging capital. The historical reason most worker co‑ops fail isn't internal — it's that the surrounding economy isn't built to support them. The Living fixes this locally.

The care economy, made visible

The single largest piece of work happening in any community is unpaid care — raising children, caring for the old and ill, holding the household, maintaining the relationships the rest of the economy rests on. Industrial economics structurally ignores this work; the gender gap in lifetime earnings is largely the bill for ignoring it.

The Living makes care visible by counting it. Hours of care given are recorded (with the carer's consent, in the carer's own words). The community fund compensates them at a rate set by the Council. Care obligations are visible in the Sensorium's care dimension. The Foundational Economy framework (Welsh Government adoption; broader European movement) provides the policy frame.

The 4‑day week and the rhythm of work

Multi‑year trials in Iceland (2015–2019, 86% of workforce now on shortened weeks), the UK (2022 trial, ~92% of participating companies continued), and Belgium have shown the same result: reducing the working week by 20% does not reduce output and does improve every measurable welfare metric. The Living adopts the 4‑day (or equivalent shortened) week as a default for cooperative work inside the community, while remaining neutral about what residents choose outside it.

Beyond the 4‑day week, the Living holds the longer rhythms: sabbaticals (a season off every seven years, or similar), parental leave (real, not the legal minimum), eldership transitions (formal acknowledgement that someone is moving out of full economic activity into community eldership). The Calendar holds the shared time these rhythms run on.

Wellbeing economy alignment

The Wellbeing Economy Governments partnership (Scotland, Iceland, Wales, Finland, New Zealand, Canada — formed 2018) has been working on replacing GDP with multi‑dimensional wellbeing measures as the indicator of economic health. Bhutan's Gross National Happiness (operational since 2008) is the longer‑running version. The Living's measurement targets are aligned with this work: the Sensorium reads the same dimensions; the Council's decisions are scored on the same metrics; the Tide is the community's analogue to the wellbeing index.

Steward ownership of the project itself

The Living holds one structural commitment: the Choose Neighbors project organisation, as it grows, adopts steward ownership (purpose trust) so it cannot be sold, acquired, or extracted from. Patagonia 2022 is the famous example (the founding family transferred ownership to a purpose trust); smaller examples include Mozilla, the Carlsberg Foundation, the Bosch Foundation. The container the project lives in is structurally protected.

This matters most when funding succeeds. Most ambitious community projects, having grown, sell or get acquired by the next layer of capital. Steward ownership is the legal structure that prevents this.

What it connects to

The Living draws structural support from the Commons (ownership of land, capital, infrastructure), is governed by the Council (which sets community‑fund priorities, care rates, stipend decisions, and ideas compensation), is rhythmed by the Calendar (4‑day week, sabbaticals, sabbaths), and is measured by the Sensorium's economic, work, and Tide‑position dimensions. It supplies the Hearth with the resources care work requires and the Forge with apprenticeship compensation.

What runs underneath

Layer	Doing what job
Worker cooperatives (Mondragon and the wider movement)	Democratic, capped‑ratio, profit‑sharing work
Mutual credit / time banking (Sardex, Time Banks USA, UK Timebanking)	Local economic activity in a unit that can't leak out
Universal Basic Services (Anna Coote, IGP)	Collective provision of need categories
Universal Basic Income research and trials (worldwide)	Income floor where policy supports it
Wellbeing Economy Governments (Scotland, Iceland, Wales, Finland, NZ, Canada)	Replacing GDP with multi‑dimensional wellbeing measures
Gross National Happiness (Bhutan)	Operational alternative to GDP since 2008
4‑day week trials (Iceland, UK, Belgium, others)	Working evidence that reducing work hours preserves output and improves welfare
Foundational Economy framework	What infrastructures everyday life depends on; care as central
Feminist economics (Marilyn Waring onward)	Unpaid care work made visible and counted
Steward ownership / purpose trusts (Patagonia 2022, Carlsberg Foundation)	Legal structure preventing acquisition of the project organisation
Inventor stipend / contribution support (your own 2014 writing)	Minimal income for residents developing things the community wants
Ideas compensation (from the Council)	Payment when a resident's idea becomes community policy

If the Living is doing its job, no one in this community has to choose between doing the work that matters and earning enough to live. The mix of income forms is rich enough that most contributions find a way to be honoured — whether or not the market notices them. The journals' returning observation that people waste themselves in wrong jobs because nothing else pays becomes structurally false.

Tier 2 — expansion nine

The Calendar

Shared time.

Origin: industrial time is private time. Everyone has their own schedule, their own days off, their own holidays; nothing is shared except deadlines. Communities that work, historically and now, are communities that share time — days of rest together, festivals together, mourning together, seasonal work together, song together. The Calendar is the organ that restores shared time as infrastructure.

The Calendar holds the community's rhythms — daily, weekly, seasonal, yearly — and the marked days (festivals, sabbaths, rites of passage, memorials, communal gatherings) that punctuate them. Most of the Calendar is opt‑in; none of it is coerced. But what's available to opt into is structural, visible, and reliable — the community has a shared pulse if its residents want one.

The premise — time as infrastructure

Time, like land, can be held in common or privatised. The last century privatised most of it. Each household keeps its own calendar, watches its own television, eats its own meals, grieves its own dead in private. The cost is roughly the cost of every loneliness study in the literature.

The Calendar's design instinct is that some hours of every week should be hours the community shares, in rhythms that recur, that residents can rely on, that build the kind of belonging only repeated presence produces.

Rhythms

Daily: A shared meal once a day where possible. The Commons often holds a kitchen and dining space that's open at predictable times. The Mediterranean evening walk (the paseo) and the Latin American sobremesa (the long after‑meal conversation) are working examples.
Weekly: A communal day of rest — the sabbath, in the broad sense, drawn from Jewish and Christian traditions but available secularly. Wayne Muller's Sabbath and Walter Brueggemann's Sabbath as Resistance articulate the case: a day not for productivity, sale, or improvement. One day in seven, the community is allowed to simply be. Plus a weekly community gathering — meal, song, ritual, discussion — that anyone can attend.
Monthly: A repair café (broken things fixed together), a death café (conversation about dying, drawn from the global movement since 2011), a Council meeting open to all, a longer gathering or festival depending on the season.
Seasonal: Marked transitions at the solstices and equinoxes; the planting and harvest cycles tied to the Garden; locally appropriate Indigenous seasonal calendars where they apply (the D'harawal six‑season calendar in the Sydney basin; the Noongar six‑season calendar in southwest Western Australia; equivalent frames in other regions). Industrial four‑season thinking misses most of what's actually happening on the land.
Yearly: The community's anniversaries, founders' days, remembrance days for those who have died, the Story's annual review (see the Story), the Council's annual cycle, the Forge's apprentice transitions.
Longer than yearly: Sabbaticals (a season off every seven years, where the Living makes this possible), generational markers, decadal community reviews. The Long Now Foundation's framing — thinking and planning in centuries rather than quarters — lives in the Calendar's longer scales.

Sabbaths and rest, taken seriously

The case for a weekly sabbath isn't religious (though it can be); it's structural. Communities that share a day of rest flourish in ways communities that don't, can't. The reasons are partly biological (synchronised rest matters more than individual rest), partly economic (no one is at a disadvantage for stopping if everyone stops), and partly psychological (the discipline of doing nothing productive is the foundation of being able to do anything else well).

The Calendar's sabbath isn't enforced. It's offered. Shops in the Commons close. The Council doesn't meet. The Forge doesn't run sessions. Lantern dims its prompts. What happens instead is whatever the resident chooses — sleeping, walking, eating slowly, being with people, doing nothing. The point is the choice exists, and is held by enough of the community at once that doing nothing isn't isolating.

Festivals

A community without festivals is a community that doesn't know how to celebrate itself. The Calendar holds the community's festivals — some inherited (whatever religious and cultural traditions residents bring), some invented, some seasonal, some commemorative. Festivals are the visible work of the Story; they're how the community tells itself who it is, out loud, with food and music and other people present.

The Calendar's working test for whether a festival belongs: does at least a third of the community show up? If not, it isn't a festival yet — it's an event. Festivals accrete over years.

Communal singing — on the calendar by design

Research on choral singing has shown effects most other interventions can't match: synchronised heart‑rate variability between singers, reduced stress markers, measurable mental‑health improvements in clinical populations. The Calendar treats group singing as care infrastructure — weekly or fortnightly, no audition required, no skill barrier. The Hearth co‑hosts. The evidence base is strong enough that not running this is a design failure.

Rites of passage on the calendar

Birth, naming, coming‑of‑age, partnership, death, grieving. The Threshold handles the structural process of these transitions; the Calendar holds the marked days. The community gathers, in public, when these things happen. Modern life mostly privatised them; the Calendar offers a venue for residents who want them shared.

What it connects to

The Calendar holds the rhythms the Living runs on (4‑day week, sabbaticals, sabbaths), the seasons the Garden works to (planting, harvest, fire), the gatherings the Hearth uses for communal care (singing, death cafes, recovery gatherings), the meeting cycle the Council runs on, the apprenticeship transitions in the Forge, and the festivals through which the Story tells the community to itself. It is one of the most connected organs in the system — nearly everything else runs on time it holds.

What runs underneath

Layer	Doing what job
Sabbath traditions (Jewish, Christian, Muslim, secular)	The weekly day of communal rest
Slow Food and Slow City (Carlo Petrini onward)	The intellectual frame for shared meals and unhurried gathering
Death cafes (Jon Underwood, 2011)	Monthly honest conversation about dying
Communal singing research	HRV synchronisation; mental‑health intervention with cardiology evidence
Indigenous seasonal calendars (D'harawal, Noongar, and others)	Locally accurate seasonal reading where applicable
Long Now Foundation	Long‑timescale thinking and ritual
Rites of passage (van Gennep)	The structure for marked life transitions
Festivals and feast‑day research	Sociology of how shared celebration produces community
Mediterranean and Latin American eating rhythms (paseo, sobremesa)	Working examples of daily shared‑time practice
Repair café movement (2,000+ worldwide)	Monthly communal repair practice

If the Calendar is doing its job, the community has a pulse residents can feel — daily, weekly, seasonally, yearly — and being part of it doesn't require remembering or arranging anything. Belonging is partly the experience of shared time, returning. The Calendar makes it return.

Tier 2 — expansion nine

The Story

How the community tells itself who it is.

Origin: a community without a story it tells about itself is a community that forgets itself. The dominant cultural narratives — consumer identity, national identity, online persona — do most of the storytelling for most people now, and most of that storytelling is doing the storyteller harm. The Story is the organ that lets a community tell its own story, in its own voice, across time.

The Story holds three things: the community's history (where it came from, including the parts that hurt), the community's present (the ongoing chronicle of what's happening, in residents' own words), and the community's working future narrative (the version of what it's becoming that residents broadly recognise and contribute to). Not PR. Not branding. The honest, evolving, contested self‑narrative a community keeps when it's awake.

Why a Story organ at all

Identity is upstream of almost everything. A community that doesn't know who it is can't decide what to do; a community whose story is borrowed from elsewhere finds its decisions drifting toward whoever wrote the story. Big platforms understand this perfectly — the borrowed identities they hand out (consumer, follower, gig worker, brand affiliate) are designed to direct behaviour. A community designing for itself has to write its own.

The Story isn't optional infrastructure. It's the layer that makes everything else legible to the people living inside it.

Three layers

The history: Where the community came from. The land's deeper history (Indigenous custodianship, see the Garden); colonial and settler history honestly told; the community's founding story; its key events, both the proud ones and the painful ones. Held as a chronicle anyone can read, written collaboratively, revisable as new understanding emerges.
The present chronicle: The ongoing record of what's happening — the Council's decisions, the Garden's seasons, the Forge's apprenticeships, the births and deaths and arrivals and departures. Drawn from the Sensorium, the Threshold, and direct resident contribution. Updated continuously; reviewed annually.
The working future narrative: Not prediction (that's the Lookout) but aspiration in plain language — what the community is trying to become, in a form residents can assent to or push back on. Most communities have one implicitly; the Story makes it explicit, debatable, and revisable.

Oral histories — the StoryCorps model

StoryCorps (Dave Isay, 2003) is the working reference for community oral history at scale. A simple structure: two residents sit together; one asks the other questions about their life; the conversation is recorded (with consent), preserved, and where the participant agrees, added to the public archive. Over 600,000 conversations recorded; the archive sits in the Library of Congress.

The Story runs the same model locally. Every resident is invited (never required) to record their story, in their own words, with someone they trust asking the questions. Stored on their Lantern's Solid pod, contributed to the community archive only with explicit per‑recording consent. Most communities lose 90% of their elders' lived memory because no one asks before it's too late. The Story refuses this loss as a design choice.

The honest history — including the dark parts

Communities that only tell flattering stories about themselves end up unable to repair their actual failures. The Story explicitly holds the parts of the community's history that aren't proud: the exclusions, the harms, the decisions that aged badly, the conflicts that weren't well handled, the people who were hurt. The Mend's repair work feeds the Story; the Story's record of past harms keeps the Mend's work in living memory.

Truth and Reconciliation processes (South Africa, Canada, others) are the working model at larger scale. At community scale the work is smaller but the structure is the same: name what happened, hear the people who were hurt, document the repair, keep the record honest. A community that can name its own failures is a community capable of not repeating them.

The community's chronicle keepers

Many cultures have had a designated role for the chronicle‑keeper, the bard, the griot, the village historian. Modern life mostly abolished the role; the Story brings it back as a community position, filled in rotation or by inclination. Chronicle keepers don't make decisions about what's true; they collect, weave, and steward the Story for the rest of the community. They're paid for the work through the Living, like any other contribution.

Festivals as the Story told aloud

Most of the Story is read on the page; some of it is told aloud, in public, on marked days. The Calendar's festivals are when the community recites its Story to itself — founders' days, remembrance days, seasonal markers, the annual community review. The Story isn't only what's written; it's also what gets sung, performed, eaten, and danced when residents gather.

The right to be omitted

Tension worth naming honestly: the Story's preservation function pulls one way (remember everything), and individual residents' right to privacy and to be forgotten pulls another. The Story resolves this with the removable‑but‑not‑destroyable pattern named at the Threshold: a resident can have their personal role in a chapter removed, while the community's memory that the chapter happened is preserved. The default is to keep names where people want them kept and to remove them where they don't.

Counter‑narratives

The dominant cultural narratives a community is embedded in — about success, identity, productivity, what a good life looks like — are usually written by people whose interests aren't aligned with the community's. The Story is where the community writes its own. Not propaganda; not even necessarily optimistic. Just honest about who we are and what we're trying. Counter to the surrounding noise, by default.

What it connects to

The Story is fed by the Sensorium (the present state of the community), the Threshold (arrivals and departures), the Council (decisions made), the Mend (repair work, including historical), the Lineage (ideas the community has had), and direct resident contribution. It feeds the Calendar (festivals tell the Story aloud), the Threshold (the Story is part of what new residents are oriented to), and the Federation (the community's public story is how other federated communities know it). The Charter governs what the Story can and cannot do with resident records.

What runs underneath

Layer	Doing what job
StoryCorps (Dave Isay, 2003)	Working reference for community oral history at scale
Truth and Reconciliation models (South Africa, Canada)	Process for honestly naming and repairing historical harm
Indigenous oral history traditions	Working frame for transmitting knowledge across generations without writing
Bardic / griot / chronicle‑keeper traditions	The designated‑role pattern for community history work
Community Archives Movement	Models for community‑owned, not state‑owned, archives
Narrative therapy (Michael White, David Epston)	The intellectual frame for how identity and story interact
Long Now Foundation	The frame for long‑timescale narrative thinking
Place‑based storytelling / psychogeography	How story binds to land
Right to be forgotten / removable‑but‑not‑destroyable	The privacy / preservation balance
Wikipedia and community‑edited knowledge traditions	Working models for collaborative, revisable, source‑cited records
Solid pods (from Lantern)	Mechanical basis for resident‑owned story contributions

If the Story is doing its job, the community knows who it is — including the parts that hurt — and it tells that story to itself often enough that newcomers can join it and elders can hand it on. A community awake to its own story is structurally harder to capture, redirect, or erase than one whose story is told by someone else.

Tier 2 — expansion nine

The Fringe

Where the project gets strange — and why.

Origin: 2014–2022 writings on existence perception, the states of consciousness the journals returned to over and over, the Animus Collector and the Demon of Stupidity that framed the original Time Tree fiction, and the deep claim that runs under the whole design — that the religious, philosophical, and fictional languages humans have used to describe inner states are all pointing at real phenomena, just in the vocabularies their cultures had available. The Fringe is where the philosophy and the cosmic mythology live, named clearly as what they are.

The Fringe is the page where the project's strangest material is held openly rather than hidden. The cosmic mythology (alien analysers, the Animus Collector, the Demon of Stupidity) is marked as fiction‑doing‑philosophical‑work — not literally true, but pointing accurately at things the working organs implement. The states of perception the journals named (existence perception, X‑being perception, the black mind) are held as a small contribution to phenomenology — not clinical, not mystical, just an honest reading of states the writer has lived through and that other people will recognise. The convergence test — the working assumption that when independent thinkers and traditions arrive at the same conclusion, the conclusion is probably tracking something real — is the Fringe's epistemic rule.

Why a Fringe section at all

Most ambitious community designs strip out their philosophy in the published version. The reasoning is usually that philosophy makes the project sound less professional and therefore less fundable. The cost is that the project loses its why — the underlying claims about humans, consciousness, and what a good life is that the design rests on become invisible, and the design becomes harder to defend or extend when challenged.

The Fringe page is where the why is kept honest. Anyone reading the design seriously can come here, see what it actually believes, and decide whether they share the framework. The strangeness is the integrity, not a problem.

States of perception — the journals' small phenomenology

The journals return again and again to a set of distinguishable states of consciousness that don't quite fit standard psychological vocabulary:

Existence perception: The journals' own term. A heightened state of seeing‑things‑as‑they‑are — "almost constant epiphany or wonder feeling," a clear sight of how things actually work, why life is the way it is, what the people around you are. The journals note the German Eigentlichkeit (Heidegger's term, usually translated authenticity) as the closest existing word. Adjacent traditions: Plato's coming‑out‑of‑the‑cave; Buddhist vipassana; the contemplative traditions across religions; aspects of what William James called the mystical experience. The journals' contribution is to describe the state in plain English, from the inside, without dressing it as enlightenment or pathology.
X‑being perception: A related but different state — "normal to me, higher state of being with good spirit and strong self awareness," distinct from existence perception in that it preserves more self‑awareness while existence perception takes some of that away. The journals note this state is harder to talk about and they have written about it less. It might be what some traditions call equanimity or presence; it might be something the existing vocabulary doesn't quite capture. Held here as an open phenomenological question.
The black mind: The absence. "It can be a bit like a black mind without any of it much." Not depression exactly — depression has a recognised clinical shape and this is something adjacent: the state where neither existence perception nor ordinary engagement is happening, where the world goes flat and the inside goes empty. The journals identify it as the state much of modern life produces by default, especially in people who would otherwise be capable of the higher states. Most of the working organs in the design are, indirectly, structures to make the black mind less structurally easy to slip into.

Religion as language pointing at real phenomena

A claim the journals make repeatedly, in their own framing: the religious language humans have used for thousands of years to describe inner states is mostly accurate description in pre‑scientific vocabulary. "Holy spirit" describes a state of higher consciousness that the journal‑writer has experienced; "father in heaven" describes human potential and the spirit's capacity to see it; "this life, next life" describes the generational continuity of the practice. The mystic and the neuroscientist are looking at the same phenomena from different sides of language.

This isn't a reduction of religion to brain‑function; it's a refusal to treat the religious vocabulary as automatically less truthful than the scientific one. Both are pointing at things. The Fringe holds this as the project's working stance — religious, mystical, philosophical, and scientific languages are each tracking parts of the same human reality, and the project draws on all of them when each is useful.

The convergence test

The journals' epistemic rule, in their own words:

"Don't listen to philosophers that paraphrase without quoting, as they are frauds making their other ideas seem better — why would I write something that has already been written. Their ideas however seem almost the same which shows me their right."

The convergence test is the philosophical rule of the project: when independent thinkers and traditions, working without contact, arrive at the same conclusion, the conclusion is probably tracking something real. The design draws on Plurality (Tang & Weyl), Plato (the cave), Heidegger (authenticity), Buddhist phenomenology (mindfulness, the aggregates), Stoicism (the dichotomy of control), Aristotle (eudaimonia, the polis), Confucian role‑ethics, Indigenous reciprocity frames, and the journals' own independent first‑person observations — consistently, where these converge, the project takes the convergence as evidence.

The cosmic mythology — fiction doing philosophical work

The 2014 Time Tree fiction was a frame for thinking about foresight and human potential when the underlying technologies didn't yet exist. Two figures from it are worth keeping visible, marked as fiction, because they still do philosophical work:

The Animus Collector: The fictional alien‑analyser device that "sees problems, minds of 50,000,000 people, follows those of interest and ability, gets people to write about problems, publish as solution for answers." What this was reaching for — a system that genuinely cared about and could see the inventive potential of every person — turns out to be roughly what Lantern + the Lineage + the Lookout together, done with consent and opt‑in rather than surveillance, actually produce. The cosmic fiction was a working specification. The opt‑in version is what graduates to the operational organs; the involuntary‑collection version stays fiction.
The Demon of Stupidity: The fictional antagonist: "the demon is stupidity … and the lack of council knowledge strategy and foresight is a black cloud that hovers over peoples' heads to make them not see the time lines or react." Not a literal demon. A name for the structural failure mode the project exists to address. The Demon is the absence of pooled foresight, the lack of collective sense‑making, the black cloud that descends on communities that have lost the capacity to look ahead together. The Lookout is the operational answer; the Demon is the mythological way of naming what the Lookout is fighting.

The Three States exercise

A small practice referenced inside Lantern: when a resident is in a difficult mental place, Lantern can offer the Three States exercise — bringing into conscious recognition which of the journal's three states the resident is currently in (existence perception, X‑being perception, or the black mind), and naming it. The discipline is the recognition itself. Naming the state changes the resident's relationship to it, which is often what's needed before anything else can shift. Adjacent to (but not the same as) the Internal Family Systems work in Lantern's parts‑aware check‑in; the Three States are about overall states of consciousness, where IFS is about which inner voice is currently dominant.

Where this project sits philosophically

The Fringe positions the project, plainly:

Inside the Plurality conversation (Tang & Weyl, 2024): the broader framework of technology strengthening democracy rather than tearing it apart. The sixteen organs are a localised, fully‑fledged Plurality stack.
Inside the post‑growth and Doughnut conversation (Raworth, the degrowth movement, the wellbeing‑economy partnership): the design is structurally post‑growth without making a doctrine of it.
Inside the pluriversal frame (Escobar): no claim of universal applicability; this design is one window onto the wider work of communities designing themselves, with deference to local framings where implementations land.
Continuous with the contemplative and phenomenological traditions: the states of perception the journals describe are part of the same family of phenomena Plato, Heidegger, the Buddhist traditions, William James, and others have described in their own vocabularies. Not new; freshly named.
Continuous with the Indigenous knowledge traditions (Country, ubuntu, buen vivir, satoyama, hozhó and many more): not appropriating them, but structurally deferring to their depth where implementations sit on their lands.

The reader's permission to disagree

None of the philosophy here is required for the working organs to function. A resident who finds the cosmic mythology silly can ignore it; the Lookout still works. A resident who doesn't recognise the states of perception can ignore the Three States exercise; Lantern's other features still help. A resident who rejects the religious framing entirely can read it as metaphor and lose nothing operational. The Fringe is the project's why; it isn't the project's gate.

Equally: the strangeness is honestly held rather than smuggled. A reader who would prefer not to know what the project actually believes is encouraged to read the operational organs and stop. The Fringe is here for the readers who want the rest.

What it connects to

The Fringe is upstream of all the operational organs — every working organ is a structure built to honour or address something articulated here. The Three States exercise lives in Lantern. The Animus Collector is the fiction‑version of Lantern + the Lineage + the Lookout. The Demon of Stupidity is the fictional antagonist the Lookout exists to address. The states of perception are the inner‑life referent underneath the Hearth, the Tide‑position dimension in the Sensorium, and the design's overall theory of why communities matter.

What runs underneath

Layer	Doing what job
Plurality framework (Audrey Tang & Glen Weyl, 2024)	The umbrella framing for technology strengthening democracy
Plato — The Allegory of the Cave	Existence perception's oldest Western description
Heidegger — Eigentlichkeit / authenticity	The German vocabulary the journals identify as the closest fit
Buddhist phenomenology (vipassana, the aggregates, mindfulness)	2,500‑year tradition of careful state‑observation
William James — Varieties of Religious Experience	The scientific‑era treatment of mystical states
Internal Family Systems (Richard Schwartz)	Parts‑aware framing adjacent to but distinct from the Three States
Indigenous knowledge traditions (Country, ubuntu, buen vivir, satoyama)	Place‑based and relational philosophical frames
The Doughnut / post‑growth conversation (Raworth, degrowth movement)	The economic philosophy the design is structurally aligned with
The pluriversal frame (Arturo Escobar)	The meta‑framing for the design's non‑universalism
Existence perception, X‑being, the black mind (your own journals)	Small contributions to phenomenology, in plain English
The Animus Collector and the Demon of Stupidity (your own 2014 fiction)	The fictional frames that specified what the working organs now do
The convergence test (your own epistemic rule)	How the project decides which philosophical sources to trust

If the Fringe is doing its job, the strangeness of the project is held honestly — not hidden, not smuggled, not apologised for. The philosophy and the cosmic mythology are visible to anyone who reads carefully, and a reader who finds them silly can still use the working organs without being asked to believe anything. The integrity is the strangeness, openly named.

Tier 3 — the horizon

The Federation

Communities don't exist alone.

Origin: every intentional community that has lasted more than a generation has been part of a trans‑local network. Mondragon (now ~80,000 worker‑owners across a federated cooperative network, 70 years), Transition Towns (~1,400 communities across 50 countries since 2005), the Foundation for Intentional Community (~30 years stewarding the wider movement), the Global Ecovillage Network, the Cohousing Association, the Camphill villages, the L'Arche network. The Hanseatic League ran on this principle for four centuries before "globalisation" had a name. Without federation, every Choose‑Neighbors community is an island; with it, the project becomes a movement.

The Federation is the layer through which Choose‑Neighbors communities relate to other Choose‑Neighbors communities, and to other movements that share enough values for federation to make sense (cohousing networks, ecovillages, worker‑cooperative federations, mutual‑credit networks, transition initiatives). It holds inter‑community matchmaking, solidarity, shared infrastructure, cultural exchange, and collective response when a member community is threatened. It is in Tier 3 because it depends on critical mass — useless with one community, transformative with twenty.

Why federation matters — the island problem

A single community designed along the lines this page describes is a working proof point, but it is structurally fragile. The surrounding economy still rewards extraction. The surrounding political system still doesn't recognise it. The community's residents still need things that no single community can produce. The cost of being good in a bad surrounding system is borne entirely by the community itself.

Federation solves this by making the surrounding system larger. When twenty communities share a mutual‑credit network, the credit has somewhere to circulate. When a hundred communities federate their political voice, they are no longer ignorable. When a thousand communities share infrastructure, infrastructure becomes affordable. The Federation is the layer that turns isolated proof points into a working alternative.

What gets federated

Inter‑community Twenty matching: Your Twenty can find offers and needs not only in your community but in federated communities — with consent, with appropriate privacy boundaries. A resident with a rare skill can be found by someone three communities over who needs it.
Solidarity and mutual aid: When a member community faces a shock (flood, fire, economic crisis, political pressure), the rest of the Federation responds. Material aid, temporary housing for displaced residents, political support, infrastructure lent.
Shared infrastructure: The Commons can pool with neighbouring Commons: shared specialised tools, shared legal templates, shared technical infrastructure, shared research, shared training. The Lookout can pool foresight; the Council can pool deliberation on issues that cross community boundaries.
Cultural exchange and travel: Residents move between member communities for stretches — weeks, months, even years — without losing their belonging at home. The Threshold receives visitors from federated communities with full context; the visitor's home community is acknowledged. The Camphill movement and the wider intentional‑community tradition have run this for decades.
Collective defence: When a member community is threatened — legally, economically, politically — the Federation responds. Legal solidarity (shared lawyers, shared precedent). Economic solidarity (boycotts, capital flight, support contracts). Political solidarity (joint statements, mobilisation of the wider network). A single community can be picked off; a federation cannot.
Knowledge transmission: What one community learns is available to the rest. The Federation maintains the shared archive — what worked, what failed, what should never be tried again, what's worth attempting. Each community avoids the hardest lessons by inheriting them.

Subsidiarity — decisions at the right level

The Federation's governing principle is subsidiarity: decisions are made at the lowest level competent to make them. Most decisions stay within a single community; some decisions belong at regional scale; a few belong at the full Federation level. The principle is old (rooted in Catholic social teaching and adopted by the EU and many federated systems) and the working examples are clear: Mondragon's cooperative federation makes group‑level decisions about capital but leaves member co‑ops fully autonomous about their work; Transition Towns sets movement‑wide direction but never tells a local transition initiative what to do.

This connects directly to Ostrom's eighth principle (see the Commons): nested governance, smaller commons sitting inside larger ones with appropriate authority at each level. The Federation is the operational answer.

Technical federation — how the digital layer connects

The infrastructural side of the Federation runs on open federated protocols. ActivityPub (the standard underneath Mastodon, Lemmy, PeerTube, and the wider Fediverse) is the working reference: each community runs its own instance, instances talk to each other through a shared protocol, no central authority. Federated identity (resident accounts that work across communities), federated Twenty matching, federated foresight pools, federated Council consultation for cross‑community issues — all of this is built on open standards rather than proprietary platforms.

The result: a community can join the Federation without surrendering its sovereignty, and can leave without losing its data. The technical architecture matches the political one.

When federation works and when it doesn't

Federation isn't free. The failure modes are visible in the history. Federations that try to standardise too much collapse the local autonomy that made the member communities work. Federations that don't standardise enough become talking shops with no actual collective capacity. Federations captured by their central organisations become bureaucracies indistinguishable from any other large institution.

The Federation's working assumption is to federate capabilities, not identities. Each community keeps its own character, its own Story, its own particular shape; what they share is the infrastructure that lets them act collectively when needed. The mark of a healthy Federation is that you can't tell two member communities apart from each other by their Federation participation — they are still distinctly themselves.

Phased growth

The Federation is in Tier 3 because it makes no sense for a single community. The honest growth path:

Phase 0 (1 community): The Federation exists as an idea and a template. No operational function.
Phase 1 (2–5 communities): Informal mutual aid, shared infrastructure where practical, beginning of inter‑community Twenty matching. No formal Federation governance yet.
Phase 2 (5–20 communities): Formal Federation structure with subsidiarity principles. Shared lawyers and infrastructure cooperatives. Inter‑community Twenty matching at scale. Collective defence capability.
Phase 3 (20+ communities): The Federation becomes a movement‑scale actor — political voice, federated foresight, shared capital infrastructure. The point at which the working alternative becomes visible to people outside the network.

What it connects to

The Federation connects every other organ outward. The Twenty federates for inter‑community matching. The Commons pools across communities. The Council can run cross‑community deliberation on shared issues. The Lookout can pool foresight at regional scale. The Hearth can share specialist care across communities. The Threshold receives federated visitors and honours federated departures. The Story shares knowledge across the network. The Charter governs how a community can join or leave the Federation without coercion.

What runs underneath

Layer	Doing what job
Mondragon Corporation (Basque cooperative federation, 1956 onward)	The working reference for federated worker cooperatives at scale
Transition Towns network (Rob Hopkins, 2005)	~1,400 federated communities working on local resilience
Foundation for Intentional Community (FIC)	~30 years stewarding the wider intentional‑community movement
Global Ecovillage Network (GEN)	The federated ecovillage movement worldwide
Camphill, L'Arche, cohousing federations	Long‑running care‑and‑community federation models
Subsidiarity principle (Catholic social teaching, EU)	Decisions at the lowest competent level
Ostrom's eighth principle (nested governance)	The theoretical frame for commons federation
ActivityPub and the Fediverse (Mastodon, Lemmy, PeerTube)	Open federated digital protocols
Federated identity standards (Solid, OAuth, WebAuthn)	The technical layer for cross‑community resident accounts
Bioregionalism	Federation by ecological region (watersheds, ecosystems) rather than political boundary
The Hanseatic League (historical, 13th–17th century)	Proof that federated communities can run trans‑regional infrastructure for centuries
Federated cooperative finance (e.g. credit‑union networks, mutual‑insurance cooperatives)	Working examples of pooled capital across cooperatives

If the Federation is doing its job, this community is not alone. What it can't do alone, it does with others. The surrounding system that punishes single communities for being good becomes structurally less able to do so, because the alternative system is large enough to push back. The Hanseatic League ran the trading economy of northern Europe for four hundred years on a federation of free cities. The Federation is that pattern, returned, for communities designing themselves around something more important than trade.

Tier 3 — the horizon

The Tide

What every other organ is trying to raise.

Origin: the journals returned often to what makes a person's continuum good or slipping — "save him on the Time Tree, and give him power to save other peoples' continuums." Each resident has a continuum: a direction of travel through their life, rising or falling. A community is, in part, the aggregate of its residents' continuums. The Tide is the measure of that aggregate — the shared, anonymised, ongoing reading of how well the community's people are actually doing, beneath all the organs that work to support them.

The Tide is the project's single shared measure. Each resident has a private Tide‑position (where they sit, this week, on the spectrum from flourishing to slipping). The community has an aggregate Tide (the anonymised distribution of its residents' positions). Every other organ is, in its way, trying to raise it. The Council's working test for any proposal is: "Does this raise the Tide, and does it keep us inside the Doughnut?" The Tide is the answer to is this working?

Why "Tide"

The metaphor matters. A tide is a real measure — it rises and falls, you can read it, you can map it — but it isn't a single number. It's a level that lifts or lowers everything in the bay together. A community whose Tide is rising is a place where most people, most of the time, are moving toward flourishing rather than away from it. A community whose Tide is falling is one where the average direction is the other way, even if individual successes obscure the trend.

The Tide refuses two opposite errors. It refuses to summarise human flourishing as a single number (the GDP error). It also refuses to refuse measurement altogether (the romantic error). It is a careful, multi‑dimensional reading that produces a single visible direction without pretending the direction is the whole story.

What the Tide measures

The Tide is built from the dimensions the Sensorium already reads — the original twelve and the four added ones, plus the four ethnographic themes. It draws weight from those that affect the resident's actual lived life most directly:

Connection and belonging.
Material security (housing, income, basic services).
Health (physical and mental, the journal's "good consciousness" range).
Agency — whether the resident's day contains choices that matter.
Meaning — whether the resident's life has direction they recognise.
Care — whether the resident is held by anyone and holds anyone in turn.
Time — whether the resident has unhurried hours, not only working hours.
Place — whether the resident is somewhere they feel they belong, in the Garden's sense.
Foresight participation — whether the resident is contributing to seeing the community's future together.
The black mind reading — how often, this week, the resident has been in the journals' described state of dim flatness.

Each dimension is read through Lantern's check‑in, the Twenty's activity, and (with consent) the activity signals Lantern is permitted to see. The reading is private to the resident. The aggregate is anonymised before it leaves the phone.

Personal Tide and community Tide

Two reads, distinct and never confused:

Your personal Tide: Where you are this week. A reading you can see in Lantern. A line over time, showing your direction. Yours to read and yours to act on. Never shared, never used by any other organ to decide anything about you, never surfaced to anyone else without your explicit per‑event consent (and even then, only as "I'd like some help" — the number itself doesn't leave your phone).
The community's Tide: The aggregate of all residents' Tides, anonymised mathematically before transmission. A distribution, not a number — you see the spread, not a single average. The shape tells you whether the community is rising, falling, or fragmenting (most flourishing but a quiet tail in serious trouble is a different signal from everyone treading water). The Council uses this to set priorities. The Sensorium reads it as one of its dimensions.

The two readings never collapse into each other. A resident can be flourishing in a slipping community, or struggling in a rising one. The Tide refuses to treat either case as less real than the other.

The test — does this raise the Tide?

Every Council proposal is asked two questions, structurally:

Does this raise the Tide? — would this proposal, if implemented, plausibly move the community's aggregate Tide upward?
Does it keep us inside the Doughnut? — would this proposal, if implemented, stay inside the ecological ceiling and above the social floor?

A proposal that does both passes the test. A proposal that does one but not the other is allowed only with the trade visible: "this raises the Tide for human residents but increases the ecological cost; we know." Or: "this stays inside the Doughnut but flattens the Tide; we know." Honest trade‑offs are made; invisible trade‑offs aren't.

Wellbeing economy alignment

The Tide is the project's analogue to the work the Wellbeing Economy Governments partnership (Scotland, Iceland, Wales, Finland, New Zealand, Canada, founded 2018) is doing at national scale. Bhutan's Gross National Happiness index has been operational since 2008. The OECD's Better Life Index, the Social Progress Index, and the Happy Planet Index are converging frames in the same conversation.

The Tide doesn't compete with these indicators — it works at community scale, where they work at national. The dimensions overlap substantially. A community implementing the Tide is producing data structurally compatible with the wider wellbeing‑economy work; a Wellbeing Economy Governments partnership country adopting community‑scale instrumentation would find the Tide already aligned with their indicators.

Anti‑gaming the Tide

Any single measure can be gamed. The Tide's defences:

Multi‑dimensional. The Tide is built from ten weighted dimensions; raising any one in isolation barely moves the Tide. You can't game one number.
Distribution, not average. The community Tide is read as a distribution. Raising the average by improving the already‑flourishing while ignoring the struggling is visible in the shape change, not hidden.
Long‑term weighting. The Tide reads slowly. A week's bump from a popular intervention barely moves it; a year's structural improvement does. This filters out short‑term theatrics.
Audit. The community can see how the Tide is computed, dimension by dimension, weighting by weighting. Any change to the formula requires Council decision.

What the Tide is not

Three explicit refusals worth naming:

The Tide is not a score. No leaderboard, no comparison to other communities, no rank. Communities have characters as different as people; reducing them to a competitive ranking is a category error.
The Tide is not individualised. Your personal Tide‑position never leaves your phone except as anonymised aggregate. No system decision is ever made about you based on your Tide. No Hearth or Council action is triggered by your number; only by your explicit consent or your own request.
The Tide is not the whole answer. A community whose Tide is rising might still be failing in ways the Tide can't see. The Tide is the most useful single signal the design can produce. It is not the truth about whether the community is good.

What it connects to

The Tide is read by Lantern (personal reading), produced from the Sensorium's dimensions, used by the Council as the test on every proposal, measured against by the Doughnut principle, watched over time by the Lookout, and shared in aggregate through the Federation where federated communities pool their Tide data for movement‑scale visibility. Every working organ in the design is, in some way, trying to raise it.

What runs underneath

Layer	Doing what job
Wellbeing Economy Governments partnership (Scotland, Iceland, Wales, Finland, NZ, Canada)	National‑scale work the Tide aligns with at community scale
Gross National Happiness (Bhutan, operational since 2008)	Longest‑running working alternative to GDP
OECD Better Life Index	Multi‑dimensional wellbeing framework
Social Progress Index	Working alternative measure of national progress beyond GDP
Happy Planet Index	Wellbeing measured against ecological footprint
Wales Future Generations Act 2015	The legislative implementation of wellbeing measurement
Doughnut Economics (Kate Raworth)	The companion measure — social floor and ecological ceiling
Continuum framing (your own 2014–2022 writings)	The journal‑rooted concept the Tide is the operational form of
The Sensorium's dimensions	The underlying readings the Tide aggregates
Network contagion research (Christakis & Fowler)	Theoretical basis for how wellbeing spreads through community networks

If the Tide is doing its job, the community knows whether it's actually working — not by trusting its own PR, not by reading individual stories that confirm or contradict, but by watching its shared measure rise or fall over time, dimension by dimension, with the honesty to see when something needs to change. The journals' continuum, each resident's and the community's, made structurally visible.

Tier 3 — the horizon

The parking lot

Yes, we know.

Every ambitious design has problems it hasn't solved. Most published designs hide this list, which is how they end up failing in the same predictable ways their critics already saw. The parking lot is the honest record of what this design hasn't figured out, organised so an implementer can see the real questions before they hit them.

The parking lot collects the project's known unresolved problems, internal tensions, implementation gaps, and open ethical questions. It is intended to be added to as the design is implemented and as readers raise problems the authors haven't thought of. Nothing here is a critique of the project; everything here is a problem the project expects to keep working on.

Tensions inside the design

Right to refuse the system vs. free‑riding. The Charter promises non‑participation as a first‑class option. But residents who don't contribute to the Sensorium, the Twenty, or the Council are still benefiting from infrastructure participating residents provide. Where the line sits between "respecting refusal" and "asking for some baseline contribution" is genuinely unresolved.
Right to be forgotten vs. the Story's preservation function. Resolved with the removable‑but‑not‑destroyable pattern, but the tension is real. Some residents will want their full record gone in a way the community's memory can't accommodate without distortion. No clean answer.
Conviction voting weights long‑held preferences — but what about legitimate changes of mind? The Conviction dial is reversible, but the social pressure to keep a position once it has accumulated weight is a real cost the design hasn't fully addressed.
Proof‑of‑knowledge gates could entrench existing privilege. Residents with time to study get more voting weight on technical questions. The opt‑in design helps but doesn't eliminate the worry that the gate reproduces educational inequality at civic scale.
The compensation‑for‑ideas mechanism could be gamed. By writing many marginal ideas hoping some get used. Source‑credit chains help but don't fully prevent volume‑over‑quality gaming. The Council's intake process has to do real work here.
The Tide could subtly pressure residents toward "good" scores. Even with strong privacy and no system action triggered by Tide‑position, the existence of the measure can shape behaviour. Residents may try to perform flourishing for a measure that's only ever supposed to be their own.
The Lineage's narrowness. Lineage is built for a cognitive profile that not everyone shares. Residents who don't fit it may feel that a chunk of the design isn't for them. This is honest (other organs serve other shapes) but the social effect should be watched.

Implementation gaps

Open Dialogue is hard to staff. Requires trained practitioners who don't exist in most regions yet. The Hearth's mental‑health crisis method depends on training pipelines that don't currently exist outside Finnish Western Lapland and a handful of other sites.
Buurtzorg‑style teams need critical mass. A 12‑person autonomous care team needs a community large enough to sustain it. Below ~150 households the Hearth has to work differently.
The Hearth's "no records" commitment may conflict with safeguarding requirements. Legal obligations to report child abuse, certain serious risks, and other statutory duties may require records the design otherwise refuses to keep. The boundary needs careful local design.
Mental‑health crisis response can't always wait for Open Dialogue. Some crises are 000 / 911 situations. The Hearth has to know its own limits in real time, which is exactly the situation in which limits are hardest to know.
Multi‑agent simulation requires technical expertise. The Lookout's Tier 3 simulation capability could easily become a feature controlled by whoever can build it, rather than the community using it. Local capacity matters or it becomes another extractive service.
The Sensorium's "lived patterns by consent" could still be surveillance‑adjacent. Even with explicit consent, normalising data collection at community scale is a slope worth being honest about. Strong defaults (consent off) and easy withdrawal matter.
The whole system depends heavily on Lantern working well. A bug or model failure in the personal AI cascades into every other organ. The design is structurally exposed to Lantern's quality.

Things requiring outside conditions

Henry George land‑value tax requires legal/political conditions that not every region has. The Commons can adopt the principle internally but cannot impose it on surrounding tax structures.
Mondragon's success has been hard to replicate elsewhere. Even with the same structure, the Basque cultural context matters. Worker cooperatives have failed in many other places that adopted the formal structure without the surrounding ecosystem. The Living can't assume Mondragon‑style outcomes from Mondragon‑style governance alone.
Compassionate Frome outcomes were impressive but context‑dependent. UK NHS, with professional GP buy‑in. Hard to replicate without that surrounding clinical infrastructure.
The Charter's exclusions (no surveillance for the state, etc.) may conflict with legal obligations in some jurisdictions. Real legal work needed in each implementation region.
Federation creates dependency risks. A federated community can be dragged down by problems in other member communities. The Federation's defences have to include exit and quarantine mechanisms.

Ethical and epistemic questions still open

CARE principles applied superficially is worse than not applying them at all. The cross‑cutting CARE principle from Indigenous Data Governance requires ongoing relationships with the relevant Indigenous data sovereignty bodies in each implementation region. Anything less is the kind of tokenism the principle was designed to push against.
The pluriversal frame risks the same tokenism. Name‑checking non‑Western frameworks without depth is a category of harm. The Garden's relationships with traditional owners have to be real, not symbolic. The design as published does not yet meet this bar.
The convergence test can confirm bias. Multiple traditions arriving at the same conclusion can be evidence the conclusion is tracking truth — or evidence the traditions share underlying biases. The Fringe relies on the convergence test more than is strictly defensible without further work.
Cohousing research is mostly Western. The four ethnographic themes in the Sensorium come from Western cohousing studies. Whether they translate to other cultural contexts is an open empirical question.
The cosmic mythology may scare off serious funders and partners. The Fringe is held openly for integrity reasons, but it has an opportunity cost. Whether the integrity is worth the cost is a real strategic question, not a rhetorical one.

Scale and time

The whole 16‑organ system needs 10–15 years to mature. Most people want quicker results. The phased launch (Tier 1 first) helps but doesn't solve the impatience problem.
The Federation needs critical mass. Useful starting around 5 communities, transformative around 20+. The first community is operating in a pre‑Federation reality for years.
The personal AI side (Lantern) is more buildable than the community side. Lantern's working version could exist in 1–2 years; many other organs need 5–10. There's a risk the personal AI ships while the community infrastructure doesn't, leaving residents with the most surveillance‑capable individual tool and none of the collective benefits.
Steward ownership should happen before fundraising. Once capital is in, restructuring to a purpose trust gets exponentially harder. The decision has a deadline, even if it doesn't feel like one.

Strategic and political risks

A working version of this design is a political threat. Systems that genuinely look after residents structurally reduce dependence on the surrounding political and economic order. Successful implementations will attract opposition; the Federation's collective‑defence capability is a structural response, but it doesn't appear overnight.
Co‑option risk. Pieces of the design (Lantern's local‑first AI, the Sensorium's community profile, the Council's Pol.is integration) are attractive enough that surrounding institutions may adopt them without the Charter's commitments. A Sensorium‑like product in a corporate platform's hands is surveillance; the same instrumentation under community governance is care. The difference is the governance.
Founder dependency. A project rooted in one person's writings is structurally fragile to that person's continuing engagement. The steward‑ownership move, the Federation, and the Charter all reduce this, but they don't eliminate it.

How the parking lot is used

The parking lot is not a list to be cleared. Most items here are permanent tensions a working implementation has to keep working with; some are solvable problems the design hasn't yet addressed; a few are open empirical questions that will be answered as implementations run. The honest posture is to keep the list visible, add to it as new problems emerge, and resist the temptation to declare items closed when they're still alive.

Readers spotting problems not listed here are encouraged to name them. The list grows by contribution, like everything else in the design.

The mark of a healthy ambitious project is the size of its parking lot. A design with no deferred problems is a design that hasn't been looked at honestly. The aim is not to clear the parking lot — that would be impossible — but to make sure the items in it are seen, named, and addressed in priority order as the work continues.