Child of Humanity · The Coherence Engine · Working Draft

How every member becomes a node in one mind

The mechanism, specified: what an active-inference agent actually is, what each member's agent holds and emits, what messages pass between peers, how coherence is measured rather than asserted, how matching emerges from that traffic instead of being ranked by a server, and how the value of Unity could eventually be read off the collective rather than set by anyone.

Depth: mechanism, not metaphor Includes: the attacks and the failure modes Status: for critique, not commitment

01 · The premise

Coherence is a quantity, and that is the whole reason this works

Everything on this page follows from one claim: the thing communities call trust, reliability, or being in flow has a mathematical counterpart that can be computed from what actually happened. Not a survey. Not a rating. A number derived from whether the community's expectations of itself keep coming true.

A living system persists by keeping its experiences close to its expectations. It carries a model of its world and acts to keep surprise low. The formal name for the gap between expectation and experience is free energy, and the reason this matters here rather than staying an elegant analogy is that free energy is computable from a log of events.

A community keeps that log already. Every confirmed exchange, every agreement honoured or missed, every offer taken up or ignored is an observation testing a prediction someone held. Coherence is how well those predictions land. Decoherence is the same number rising. Both are measurable from the day the ledger starts recording, long before any of the ambitious machinery on this page exists.

This is the practical inversion worth holding onto: the coherence framework does not wait for the research to arrive. Its measurement layer is ordinary Bayesian statistics and can ship in the first year. What waits for research is only the deepest layer — pricing derived from it, and the full hierarchical agent. Section 11 separates these precisely.

02 · Active inference in one screen

Four ideas, each of which becomes a system component

Enough formalism to build from, and no more. Each idea is followed by the thing it turns into in the product.

One · Free energy, minimised by updating beliefs

An agent holds beliefs about hidden states of its world. When observations arrive, it revises those beliefs to reduce the mismatch. This is perception and learning, and in the product it is simply the trust and capacity model updating after every completed or broken exchange.

Two · Expected free energy, minimised by choosing actions

To choose what to do, the agent evaluates candidate actions by how much free energy it expects afterwards. That expectation decomposes into exactly two terms, and this decomposition is the single most useful thing active inference gives this project:

G(π) = − expected information gain − expected preference satisfaction

Choose the action that minimises G. Because both terms are negative, minimising the sum means maximising both at once: what we would learn by taking this action, and how far it moves us toward what we care about. An agent driven by this does not only pursue goals — it also values resolving uncertainty, for its own sake, in the same currency.

In the product this is the matching objective. It is why the system can propose an introduction nobody searched for and be right to: the unfamiliar match scores on the first term even when the obvious one scores higher on the second.

Three · Precision, which is trust with a mechanism

When an agent receives a signal, it weights that signal by precision — its confidence in the source. High precision means the signal moves your beliefs a lot; low precision means it barely registers. This is not an analogy for trust. It is the same operation. Trusting someone means letting their claims update your model; distrusting them means discounting the same claims.

In the product this is the trust layer, reconceived. A trust score stops being a reputation number displayed to people and becomes a weight the network applies to a member's predictions about themselves. Someone who reliably does what they said carries high precision; their offer to help next Tuesday moves the network's plans. Someone whose word has not held carries low precision; the same offer is held loosely until evidence accumulates.

Four · The Markov blanket, which is the boundary that makes a self

A blanket is the set of states through which an agent senses and acts, separating what is inside it from what is outside. It is what lets something be a distinct self while remaining fully coupled to its surroundings. Every member has one; so does every circle, neighbourhood, and bioregion.

In the product this is identity and consent, and it is also the reason the architecture is federated rather than centralised: agents do not read each other's interiors. They exchange what crosses the blanket, and nothing else.

03 · The node

What one member's agent actually is

Concretely: a small, per-member model that lives close to the member, holds their history, and emits beliefs rather than data.

              ╭─────────────  ONE MEMBER'S AGENT  ─────────────╮
              │                                                │
              │   INTERNAL STATES  (never leave the device)    │
              │   · capacity model   what I can offer, when   │
              │   · preference model what outcomes I want     │
              │   · peer models      what I expect of others  │
              │   · precision map    how much I trust whom    │
              │                                                │
   sensory    │  ╌╌╌╌╌╌╌╌╌╌╌  MARKOV BLANKET  ╌╌╌╌╌╌╌╌╌╌╌╌   │    active
   states  ──▶│                                                │──▶ states
              │   what I observe        what I emit          │
              │   · offers nearby       · my predictions      │
              │   · requests            · my preferences      │
              │   · confirmations       · confirmations       │
              │   · peers' predictions  · prediction errors   │
              │   · circle summaries    · precision updates   │
              ╰────────────────────────────────────────────────╯

  What never crosses: raw history, message content, the interior model
  itself, anything the member has not consented to expose. Peers receive
  claims and confidences — never the evidence behind them.

Two design consequences follow immediately, and both are worth stating to anyone who worries this is surveillance wearing a nature costume.

  • The unit of exchange between people is a belief, not a record. "I expect to have four hours of carpentry capacity next week, confidence moderate" is what travels. The calendar it was derived from does not.
  • Privacy is not a policy bolted on; it is the architecture. A blanket that leaked would not be a blanket. The same property that makes each member a distinct self is the property that keeps their interior theirs.

At launch the agent is not exotic. It is a per-member Bayesian model — a handful of distributions over reliability, capacity, and preference, updated after each event. That is enough to carry precision-weighted trust and to produce the coherence indices in section 07. The hierarchical, deep version described in section 11 is where the research sits.

04 · The protocol

Five messages, and the network thinks

Distributed intelligence sounds mystical until you write down the message types. There are five, they are small, and passing them between neighbours is a well-understood algorithm.

MessageContentWhat it does to the receiver
Prediction"I expect to be able to do X, around then, with this confidence."Updates the receiver's model of what is available in their neighbourhood.
Preference"These outcomes matter to me" — needs, hopes, the things a member would like to be true.Supplies the pragmatic term. Without these broadcast, the network has goals for no one.
Prediction error"What happened differed from what I was led to expect, by this much."The learning signal. Generated on every completion, every no-show, every pleasant surprise.
Precision update"I am revising how much weight I give your signals."Trust moving, mechanically. Propagates slowly and asymmetrically — earned gradually, lost faster.
Policy proposal"Here is an exchange I believe lowers our joint expected free energy."A match, offered for acceptance. Any agent may propose; none may impose.

How they travel

Agents are connected to the peers they have reason to care about — people they have exchanged with, share a circle with, or live near. Messages pass along those edges and are relayed onward with decreasing weight. This is belief propagation on a factor graph: a standard, decades-old inference algorithm. Each agent does purely local work; the global picture is never assembled anywhere, and yet the network converges on a shared estimate of what is available, what is needed, and who can be counted on.

Three properties matter for a community system specifically:

  • No centre to capture. There is no server holding the network's beliefs, because the beliefs are distributed across the members who hold them. This is what makes the murmuration claim literally rather than poetically true.
  • Locality is a feature. A member's model is dominated by their immediate neighbours, which is both computationally necessary and socially correct. You should be more shaped by the people you actually exchange with.
  • Degrades gracefully. A member offline for a week is a peer whose predictions grow stale and whose precision widens. Nothing breaks. Compare a central matcher, which either has your data or does not.
Honest engineering note: belief propagation converges cleanly on graphs without loops, and social graphs are nothing but loops. Loopy propagation usually works in practice but can oscillate or converge to something wrong. Damping, message scheduling, and convergence monitoring are required, and the failure mode — a subgroup locking into a confidently wrong shared belief — is exactly the failure mode communities already have. It should be detected and surfaced to people, not silently corrected.

05 · Emergent matching

Where the recommendation actually comes from

In the launch system a server ranks candidates. In the distributed system no one ranks anything: a match is a proposal that survives evaluation by both blankets it would cross.

  1. A need enters the field. A member's agent emits a preference. It propagates outward through their edges, attenuating with distance.
  2. Neighbouring agents evaluate locally. Each asks a purely local question: given what I hold and predict, is there a policy that lowers our joint expected free energy? Most find nothing and stay quiet.
  3. Candidates surface as proposals. Those that find something emit a policy proposal, carrying its two scores — what the exchange would resolve, and how far it moves both parties toward what they said they wanted.
  4. Precision filters. Proposals from low-precision sources carry less weight; proposals involving parties whose reliability is uncertain surface with that uncertainty attached rather than hidden.
  5. The member chooses. Always. The network proposes; a person disposes. This is a hard design rule, not a courtesy — an active-inference system whose proposals cannot be declined has lost the feedback signal it runs on.

Worked example: why the strange match wins

A family needs a light fixture moved. Two candidates surface.

The obvious matchhigh pragmatic · low epistemic

The retired electrician, who has done this eleven times, is available Saturday, and is entirely predictable.

Preference satisfaction: high. The need is met well.

Information gain: near zero. The network already knows exactly how this goes. Nothing is learned.

The strange matchgood pragmatic · high epistemic

A newer member who listed electrical work but has never been taken up on it, whose reliability the network is genuinely uncertain about, and who lives two streets away.

Preference satisfaction: good, with wider error bars.

Information gain: large. This single exchange sharply reduces uncertainty about a member the network cannot currently place — which affects every future match they might be part of.

Summed, the second can win. Not because the system is being whimsical, and not because a diversity quota was applied, but because resolving uncertainty about a member has real forward value to everyone, and the mathematics counts it in the same units as satisfaction. This is the mechanism behind the slime mould: paths are explored, not only exploited, and the ones that carry value thicken.

Two safeguards this needs from day one. First, the epistemic term must be capped relative to the pragmatic term, or the system will experiment on people. Second, an exchange whose uncertainty is high must be proposed with that stated plainly — "this would be a first, and here is what makes it worth trying" — because a member accepting exploration deserves to know that is what they are accepting.

06 · Scaling the same shape

Member, circle, neighbourhood, bioregion

The fractal claim on the public page has a precise technical form: each level is an agent with its own blanket, whose observations are the summarised states of the level below and whose predictions constrain it from above.

  slow · abstract · few states
   BIOREGION     predicts: seasonal capacity, watershed health, migration
        ▲ summaries          ▼ constraints
   NEIGHBOURHOOD predicts: what will be needed this month, who can meet it
        ▲                    ▼
   CIRCLE        predicts: this rotation, this garden, this week
        ▲                    ▼
   MEMBER        predicts: Tuesday
  fast · concrete · many states

  Upward:  aggregated, signed summaries only — "we hold 200 teaching hours,
            we need 50 of carpentry". Never individual records.
  Downward: context, not commands — a prior that makes some matches more
            plausible, which any lower level is free to contradict with evidence.

The upward channel is what makes cross-community pricing possible without surveillance: a skill abundant in one neighbourhood and scarce two valleys over is visible in the summaries and invisible in the particulars. The downward channel is why this is not central planning — a higher level supplies a prior, and a lower level that observes otherwise overrides it. Authority runs on evidence, not hierarchy.

This is also the exact structure the renormalising models research is about: slow, coarse levels generating fast, fine ones, with each level learned rather than hand-designed. At launch the levels and their summaries are defined by people. In the research version they are discovered. That difference is the whole distance between shipping and researching.

07 · Measuring coherence

Five indices, computed from the log

This is the part that answers "how would you even measure that." Each index is derivable from events the ledger already records, each has a pathology at both extremes, and none of them is a score shown to a member as a judgement.

1 · Reliabilityaccuracy term

How well the community's predictions about behaviour are borne out. Computed as the average surprise of observed outcomes under the current model — did the people who said they would show up, show up.

Pathology at both endsLow reliability is obvious decoherence. Perfect reliability across an entire community is also a warning: it usually means nobody is attempting anything they might fail at.

2 · Calibrationprecision quality

Whether the network's confidence is honest. When it says a member is ninety percent likely to complete, do they complete ninety percent of the time? Standard proper scoring rules give this directly.

Why it matters mostA community can be unpredictable and still perfectly coherent, provided it knows it is unpredictable. Coherence is calibration, not certainty — and this distinction is what prevents the whole framework from becoming a machine for punishing variability.

3 · Circulationflow structure

Whether value moves or pools. Computed on the flow graph: velocity, the distribution of net positions, the fraction of members who are both giving and receiving rather than only one.

Reads asThe mycelial property, made numeric. A community where flow concentrates is decohering even if every individual exchange completed successfully.

4 · Epistemic reserveunexplored capacity

How much the network still does not know about itself — members whose offers have never been taken up, capacities never tested, connections never made. Computed as the uncertainty remaining in the capacity model.

Reads asPotential, not deficiency. A high reserve means there is abundance the community has not yet found. A reserve falling to zero means a community that has stopped meeting anyone new.

5 · Distinctnessblanket integrity

How different members remain from one another — measured as the mutual information between member models. If knowing one member's state increasingly tells you everyone else's, the community is collapsing toward sameness.

PurposeThis index exists specifically to make conformity visible and costly. Section 08 argues it is not merely a bolted-on safeguard but something the mathematics actually requires.

What is done with them

These five feed three places and no others: the matching objective, as terms it balances; the review circle and assembly, as a picture the community reads about itself; and each member's own reflection surface, showing only their own contribution and never a ranking against others. They are explicitly not a leaderboard, not an eligibility gate on their own, and not visible as a number attached to a person in any shared view.

08 · The two objections

Why this does not produce a quiet, identical village

Both objections are correct against a naive reading, and both have real answers rather than reassurances. They deserve to be raised by the project before anyone else raises them.

Objection one · the conformity trap

If the system minimises surprise, surely the optimum is a community where everyone is identical and therefore perfectly predictable?

Why it fails. That would minimise surprise in the short run and maximise it over any horizon that matters. A homogeneous network has no epistemic reserve, cannot absorb a perturbation it has not seen, and its predictive advantage collapses the moment conditions change — the same reason a monoculture is fragile and a diverse forest is not. A community of clones is not a low-surprise community; it is a community whose surprise is deferred and concentrated.

Diversity is therefore not a value imposed on the mathematics from outside. Under any evaluation horizon longer than the immediate, distinctness lowers expected free energy. The distinctness index makes that explicit and auditable, and the periodic question the review circle should be asked is a blunt one: who is this measurement penalising, and are they the community's dissenters?

Design ruleTrust measures reliability, never agreement. Nothing in the coherence framework may take a position on what a member believes, only on whether their word and their action correspond.

Objection two · the dark room

The classic objection to the entire free energy principle: if minimising surprise is the imperative, the optimal move is to find a dark quiet room and never leave it. Nothing happens, nothing surprises you, free energy is minimal. Why would this network not simply go still?

Why it fails, and this is the important part. Because free energy is only defined relative to prior preferences — the outcomes a system expects and requires for itself. An organism does not sit in a dark room because being fed, warm, and in company are not optional extras; they are what its model expects existence to contain. Stillness is enormously surprising to a body that expects to be nourished.

So the anti-stillness force in this system is precisely the community's stated preferences: that people are housed and fed, that elders are visited, that land regenerates, that the young learn a trade, that nobody is only a receiver. These are not sentiment layered on top of the engineering. In the formalism they are the prior preferences without which the free energy quantity is not even defined, and they are what makes a community that stopped caring for its members read as a catastrophic surprise rather than a peaceful optimum.

ConsequenceThe Framework the project has been articulating in ethical language is a required technical input. It has to be written down concretely enough to be computed against — which is a demanding, unglamorous piece of work, and one that no amount of model capability substitutes for.

09 · Emergent value

Where the price of Unity could come from

The most ambitious claim in the whole project, treated with the scepticism it needs in order to eventually be believed. The proposal is genuine, the attacks against it are real, and the recommendation is a bounded hybrid rather than a leap.

The proposal

value(exchange) ∝ Gbefore − Gafter

The worth of an exchange is how much it lowers the collective expected free energy of the community it happens in — how much uncertainty it resolves plus how far it moves people toward what they have said they need. Value stops being an opinion and becomes a measured difference. Idle balance decays because unmoved value contributes nothing to that difference, which is what demurrage means physically rather than as policy.

It is a beautiful idea and it would, if it worked, be the first currency whose unit is defined by contribution to collective wellbeing rather than by scarcity. Three things stand between it and a live ledger.

Attack one · uncertainty farmingthe serious one

If resolving uncertainty pays, agents are incentivised to manufacture it. Two colluding members can stay deliberately unpredictable to each other, then repeatedly resolve that uncertainty for reward. This is not hypothetical; it is the obvious exploit and it would be found within weeks.

MitigationCap the epistemic component as a fraction of price; decay the information value of repeated similar exchanges between the same parties toward zero; and pay principally on confirmed preference satisfaction, which requires a counterparty who actually wanted the thing. Adversarial simulation is not optional here.

Attack two · computability

Collective expected free energy over a whole network is not calculable exactly. Any real implementation computes a local approximation over the affected blanket neighbourhood — which means the price depends on where you draw the boundary, and boundary choices are contestable.

MitigationFix the neighbourhood definition publicly and by governance rather than by engineering convenience, and publish it alongside the price. A contestable boundary that everyone can see beats an invisible one.

Attack three · instability

Prices derived from a learning system can oscillate, spike, or drift. A member cannot plan a season of garden stewardship against a number that moves unpredictably, and a currency people cannot plan against fails at the one job a currency has.

MitigationRate-limit movement, damp the estimator, and hold prices inside a published corridor around the administered index.

The recommendation: a corridor, widened by evidence

Do not choose between the administered index and coherence-derived pricing. Run both, with the index as the anchor and the coherence signal permitted to move the price only within a published band around it — a few percent at first. The band is a governance parameter, visible to everyone, and it widens only as simulation and live evidence justify it. If the coherence signal proves stable, honest, and resistant to farming over a year, it earns more room. If it does not, nothing broke, because the anchor held the whole time.

This is what lets the ambitious claim be made honestly today: Unity's value is anchored to a published index and modulated, within a bounded corridor, by a measured signal of what the exchange contributed to the whole — and that corridor widens only as the measurement earns trust. True at launch, true in five years, and it describes a direction of travel rather than a promise about a destination.

10 · Where coherence lives

The framework across the whole system

Coherence is not a module. It appears in every layer, in governance, and on the interface — and it is worth being exact about the form it takes in each, because it is a different object in each.

WhereThe form it takesWho acts on it
SemanticsThe vocabulary that makes prediction possible at all. You cannot predict what you cannot name — the five value classes are the state space.Engineering, at design time.
IdentityThe blanket itself. Consent scopes define what crosses, and therefore what any agent can ever model about anyone.The member, continuously.
TrustPrecision. The weight the network gives a member's predictions about themselves.The network, automatically; the review circle, on dispute.
MatchingThe objective function — the two terms, balanced, with the epistemic term capped.The member, by accepting or declining.
FlowThe circulation index, and demurrage as its enforcement.Governance, setting the rate.
ConsensusValidation rules that encode what this community holds itself to. Coherence norms become executable predicates.The domain, writing its own rules.
SettlementThe both-or-neither property, which is what makes a confirmation a trustworthy observation rather than a claim.Nobody — it is structural.
PricingThe corridor: index anchor, coherence modulation, governance-set band.Assembly, setting the band.
GovernanceThe five indices as a picture the community reads about itself before deciding anything.The assembly.
SafeguardingDecoherence detection — rising surprise clustering in a person, a circle, or a season.The review circle, as a question raised.
InterfaceReflection, not scoring. A member sees their own flows and contribution; never a rank.The member alone.
The line that must never be crossed, stated once and enforced everywhere: decoherence detection surfaces a question to people, never a verdict about a person. "Fewer exchanges are completing in this circle this month" is a signal a community can act on with judgement. "This member has low coherence" is a machine passing sentence, and it is not something this system is permitted to say.

11 · The ladder

What ships now, and what is genuinely research

The most useful correction this page can offer: most of the coherence framework is not waiting on anything. Four stages, with an honest tag on each.

Stage 0 · Shaped scoringfirst release RUNS TODAY

A deterministic matcher whose objective has the two terms written explicitly — an uncertainty-reduction score alongside a preference-satisfaction score, with a capped epistemic weight. Coherence indices computed from the event log and shown to the assembly. No agents, no message passing, no learning in the money path.

What it already givesSurprising-but-good matches, a real coherence dashboard, and a full year of behavioural data with which to test everything above it.

Stage 1 · Per-member belief modelsyear one to two ORDINARY BAYESIAN WORK

Each member gets a small Bayesian model over reliability, capacity, and preference, updated after each event. Trust becomes precision-weighted and properly calibrated. All five indices become principled rather than heuristic.

Worth emphasisingThis is the stage that delivers most of what the coherence framework promises, and it requires no unpublished research — only careful statistics, good evaluation, and discipline about replayability.

Stage 2 · Peer message passingyear two to four HARD BUT BUILDABLE

Agents move to the member's device, exchange the five message types with neighbours, and matching becomes proposals evaluated locally rather than rankings served centrally. Real federation: beliefs travel, records do not.

The hard partsConvergence on loopy graphs, offline members, adversarial agents in an open network, and the operational reality of debugging a system with no central view of its own state.

Stage 3 · Learned hierarchy and coherence pricingresearch track RESEARCH

The levels of the hierarchy are discovered rather than declared, agents become deep generative models, and the pricing corridor widens toward coherence-derived value as evidence permits. Simulation first, always.

GateNothing from this stage touches a live ledger until it has survived adversarial simulation on synthetic communities. That gate is a commitment, not an intention.

What must be simulated before any of it touches money

  • Does it stay fair? Run synthetic communities with unequal starting capacity and see whether flow concentrates. If coherence pricing rewards the already-central, it has failed regardless of elegance.
  • Does it stay diverse? Watch the distinctness index over long simulated horizons. If it declines monotonically, the conformity objection was right and the objective needs a longer evaluation horizon.
  • Does farming appear? Introduce agents that deliberately manufacture and resolve uncertainty. Measure what they extract. Tune the caps until the strategy stops paying.
  • Does it stay still? Test whether the system finds any degenerate equilibrium where activity ceases. If it does, the preference priors are underspecified — which is a finding about the Framework, not about the code.
  • Does it stay stable? Shock the simulation — a member leaves, a season fails, a subgroup defects — and watch whether prices and trust recover or oscillate.

12 · Still open

Questions this page does not close

  • Whose preferences count, and how are they weighted? The pragmatic term needs the community's prior preferences written concretely. Who authors them, how they are amended, and whose needs weigh how much is a governance question wearing a mathematical costume — and it is the deepest unresolved item in the whole framework.
  • How does a member contest their own precision? If the network's confidence in someone is low and they believe it is wrong, what is the route to appeal, and what evidence reopens it?
  • What is the exit? A member leaving should be able to take their credentials and standing. What happens to the beliefs other members hold about them, which are not theirs to delete?
  • Where is the neighbourhood boundary drawn for pricing? Named in section 09 as a governance parameter, but no method for setting it is yet proposed.
  • How is the framework itself versioned? Indices, caps, and priors will change. Every price and trust value must remain reproducible against the version in force when it was computed.
The honest shape of this page in one line: the measurement is buildable now, the distributed architecture is hard engineering rather than unfinished science, and only the pricing and the learned hierarchy are genuine research — while the deepest open problem is not technical at all, but the question of who writes down what the community wants.

Child of Humanity — the coherence engine, working draft. Companion to the unified stack, the build sheet, the technical architecture brief, the city application study, and the donor overview.

Formal claims here are stated in plain language deliberately; before external circulation they should be checked against primary sources and, where they concern this project's own implementation, against what has actually been built.

0
Skip to Content
Child of Humanity
The Lineage
The Intelligence
The Living Economy
The Coherence Labs
The Living Systems
Child of Humanity
The Lineage
The Intelligence
The Living Economy
The Coherence Labs
The Living Systems
The Lineage
The Intelligence
The Living Economy
The Coherence Labs
The Living Systems