Consilient Network· The graph of everyone who built this · Add your entry ↗
Ways through

Connections

A graph with no single root can be entered anywhere, which is liberating and useless in equal measure. These are curated routes through it — each one an argument with an order, and each built for somebody in particular.

21 pathsOr search everything →
Concept path

What it argues

Connections built around a capability — follow one to see how a claim is actually supported, and where it would break.

6 stops · Anyone who wants to know where packet switching actually came from

The internet exists because of a requirement my grandfather wrote

The internet exists because somebody had to guarantee that command could still reach the missile silos after a first strike. The man who wrote that requirement is Hare's grandfather.

Follow the path →5 stops · Anyone evaluating the Quantum Genome

Why a policy attached to data never survives the data being used

A policy attached to a dataset does not survive the dataset being joined, transformed or trained on. Hare proposed the fix in 1998, applied it to the wrong substrate, and spent twenty-eight years getting it right.

Follow the path →5 stops · Anyone evaluating the Unified Trust Model

Every attempt at values-by-committee dies on one question: whose values?

Every attempt at values-alignment-by-committee has failed on the same rock: whose values? The question does not have to be settled, because coherence does not require agreement.

Follow the path →5 stops · Anyone worried about capture, and anyone contemplating it

The network that eats its captors: why taking it over destroys it

Capture is futile rather than prohibited — and it is also unnecessary, because there is no ceiling on what contribution can legitimately obtain. Those two facts together are what make the structure stable.

Follow the path →7 stops · Anyone asking why this took thirty-five years

Four companies, thirty-five years, one missing layer

The Business Process Abstraction Layer was named at Microsoft in 1991. Everything since is the same problem attacked with whatever the substrate of the moment allowed — and each attempt failed at a level below the one it was working on.

Follow the path →8 stops · Anyone asking why this is architecture rather than policy

Rome, Cromwell, Newton: every coordination system fails the same way

Every coordination system in this record failed the same way: the guarantee lived in a person, an office or a state, and when the holder weakened the guarantee went with it. The alternative has been demonstrated exactly once at scale, in silver, by Isaac Newton.

Follow the path →
Outreach path

Who it is for

Connections built around a particular reader. If you know someone on one of these, the path is the thing to send them.

5 stops · Apple, Disney, and anyone who worked on the interface revolution

Jeff Raskin, Larry Tesler and Alan Kay solved accessibility. This is the same move, one level down

The people who made computing available to ordinary humans solved the last great accessibility problem. This is the same move, one level down — and four of them are already in this record.

Follow the path →7 stops · Google, Alphabet, and the 2006 summit attendees

Google's best engineers told E. O. Wilson his wish was impossible

In December 2006 Google's most capable technical leadership told E. O. Wilson that what he wanted was impossible. They were right about every obstacle they named. This is the architecture that removes them.

Follow the path →6 stops · The Santa Fe Institute community, and complexity researchers

The Santa Fe Institute coffee room: Gell-Mann, Kauffman, Holland, Arthur

Complex Adaptive Systems Theory describes what self-organizing systems do. This is the constructive version — the same mechanisms treated as design requirements rather than observations.

Follow the path →7 stops · Cisco, Sun alumni, and the networking industry

Cisco and Sun: Cheriton, Bechtolsheim, Joy and the decade that decided everything

Most networking companies ended up inside Cisco. The relationships that produced this architecture ran through the same rooms, and several of them are still reachable.

Follow the path →6 stops · AI laboratories, safety researchers, and anyone who has read Hinton lately

From Geoffrey Hinton's back-propagation paper to the alignment problem it created

Hare was handed Hinton's back-propagation paper by his advisor in the eighties. Forty years later he has taken a position on what Hinton now says about safety — and built the mechanism for it.

Follow the path →7 stops · Multi-generational capital, family offices, sovereign wealth, and public-benefit trusts

Why Kleiner, NEA and Oak Hill structurally cannot hold this

A ten-year fund life cannot hold a multi-century instrument. The structures that can are the ones organized around perpetual trusts — and there are not many of them.

Follow the path →5 stops · Hedera, its Governing Council, and ecosystem partners

Hedera: the assembly Tier 0 needs has already happened

Tier 0 requires an anchor network with enough category diversity that it cannot be characterized, contained or bought. Assembling that from scratch takes years. One ecosystem already is it.

Follow the path →5 stops · Faith and tradition institutions, foundations, and anyone who works on equity

Justice as a design condition, not an aspiration bolted on afterwards

A system that can be made to admit people can be made to exclude them again. The alternative is to build the admitting into the substrate, where no one can reach it.

Follow the path →7 stops · AI researchers, the geometric deep learning community, and anyone who has read Hinton lately

Feature vectors, manifolds, and the metric of trust: the geometry AI rediscovered

Modern AI's deepest design principles — the manifold hypothesis, metrics on latent spaces, hyperbolic embeddings, equivariance — are one lesson learned repeatedly: meaning is what survives coordinate change. Hare learned that lesson in APL at Berkeley in the 1980s, was handed back-propagation by his advisor, and built the constructive version: a metric for coordination space, specified rather than learned, enforced rather than observed.

Follow the path →
Story path

Why it lands

Connections that work on anyone. Start here if you have no idea what this is.

4 stops · Anyone in SaaS, cloud, or platform economics

A man invented software-as-a-service in 1975. His grandson did it again, not knowing

A man built a hosted application service in his basement in 1975. His grandson arrived at the same model independently in the nineties. Other people built it both times.

Follow the path →5 stops · Everyone. This is the one to send first.

Three generations of one family, three existential threats

One man helped build the deterrent that held for fifty years. His son spent his life arguing with what it became. The third is trying to build the layer that makes both arguments unnecessary.

Follow the path →4 stops · Anyone who wonders how this person got made

The door E. O. Wilson opened, and what was behind it

The most durable lesson in this record was delivered without a sentence. That is also the method the whole site is built on.

Follow the path →12 stops · Founders, investors, and anyone deciding whether to believe the record

Evolve, Consilient, Resilient: what actually ended each one

From outside, Evolve, Consilient and Resilient look like a decade of near-misses. The outcomes were real. But two of the three were ended by instruments Hare designed or agreed to himself — which makes this the specification for the architecture rather than a list of regrets.

Follow the path →7 stops · Engineers, and anyone who wants the technical formation rather than the biography

Punch cards at eight, a PDP-8 at fifteen, and what each machine taught

Every layer of this architecture was preceded by a smaller version of the same problem, encountered on real hardware, twenty to forty years earlier.

Follow the path →
Make your own

Connections are a format, not a fixed set

The record is CC BY 4.0 and every page has its own address. A connection is just an ordered set of them with an argument attached — which means anyone can build one, publish it anywhere, and monetize it however they like.

If you make one, send it. It enters the graph attributed to you.

Build a connection

Pick a thesis, pick the stops that support it, and say why each one is there. Send it to evidence@qpncatalyst.io and it joins these — with a timestamped confirmation back to you as your own record.

The license and the terms → Browse every node →
← PreviousExplore
+ Add to the record