Manifesto · v0 · placeholder — replace with the canonical pitch when drafted

Manifesto

Working frame, not final text. The canonical 30s/2min/20min pitch is still being drafted (see internal task). The section structure below is the spine — replace the prose, keep the bones.

The metacrisis is a coordination problem

Climate, AI, public health, public goods, and capital allocation share a structure: the will exists, the talent exists, the money exists. What's missing is the routing between them. Nation-states and single-issue orgs were built for a slower world. Their coordination surface area is narrow, their feedback loops are long, their legitimacy is contested. Something has to sit above and between them.

AI Control, not acceleration

AI development is inevitable. The frame we organize around is human control — not acceleration, not deceleration, not singularity. Control requires coordination at speeds and across boundaries that current institutions cannot match. Memetwork is one attempt at building those rails.

Coordination is the bottleneck

The bet: in the next decade, outcomes are shaped less by who has the best ideas or capital than by who can route ideas, capital, and people through coordinated channels faster than legacy institutions. The civilizational thesis is coordination wins.

What we build

• Coordination pilot. 30–50 people, structured profiles, org-needs maps, matching cycles. Pilot → evidence → scale.
• Map of meaning v0.1. A prioritization layer that makes the coordination space legible.
• Meta-community register. ~10 real high-trust nodes to start. Real, not aspirational.
• Talent routing for the non-research half of AI safety. Operators, founders, program leads, generalists. The cohort the current ecosystem under-absorbs.

What we won't do

• Brand-build over substance.
• Run yet another fellowship-shaped thing.
• Confuse motion or convening with coordination.
• Optimize for legibility to the wrong audience.
• Become a mass-market social platform under a different label.

Architecture

Multi-layer by design. Council, community hubs, movement layer, project office, development lab — separate functions, not collapsed into one organization-trying-to-be-everything. That was the earlier Unitaware mistake; we won't repeat it.

Disagreements and counter-arguments welcome at [email protected].