spore
github ↗

a coordination grammar

spore

A grammar for coordinating across fields — without collapsing difference.

scroll

01 · what is spore

Infrastructure for collective agency.

A spore is portable, generative, and context-sensitive: it moves through larger living networks, lands in a place, and unfolds locally.

Spore follows the same logic — a shared coordination grammar that can land across projects, grow in different forms, and remain interoperable without requiring centralization.

02 · the grammar

Five primitives. Enough to coordinate almost anything.

Spore composes from a small vocabulary. Every coordination surface — from a personal workflow to a planetary federation — is built from these five.

Field

The relational medium.

Where signals, claims, commitments, and agents become legible to each other and interact over time.

Membrane

Active boundary.

Not a wall. A permeable, governed interface that expresses consent — what crosses, who crosses, on what terms.

Claim

A legible assertion.

Carries provenance and stance. Claims can be supported, contested, superseded, or refined — never silently overwritten.

Commitment

A scope-bound promise.

Agents declare intents, pool capacity, accept responsibility — with legible scope, duration, and exit.

Holon

Whole and part at once.

A unit that has its own integrity and also participates in something larger. Nested plurality, not hierarchy.

03 · the ecology

Not a pipeline. A living loop.

Vision, roadmap, intent, commitment, evidence, learning — each feeds the others.

The same cycle operates at every scale — personal workflow to planetary federation. Hover any node to see which others reach back through the interior.

VisionRoadmapIntentCommitmentEvidenceLearning

04 · constitutional commitments

Seven structural safeguards. Chosen, not eternal.

Together they define the conditions of relational freedom: the structural ground that makes coordination possible without requiring convergence. Each one supports the others — hover any commitment to see the dependencies light up.

ProvenanceForkabilityPluralismMeaningfulAuthorizedReviewableContestability

hover any commitment

  • Provenance

    You can trace where every claim, commitment, and decision came from.

  • Forkability

    You can copy, modify, and run your own version. Exit is a structural right.

  • Pluralism

    Many worldviews coexist without being collapsed into one.

  • Meaningful autonomy

    Partial participation is honoured. You don't have to adopt the whole stack to use one piece.

  • Authorized boundary crossing

    Anything that crosses between contexts requires consent — explicitly, not by default.

  • Reviewable authority

    Whoever decides can be questioned. Authority is visible and revisitable.

  • Contestability

    Dissent is structural, not exceptional. Disagreement has somewhere to go.

05 · the shapes of spore

A semilattice. Not a tree.

Overlapping memberships, cross-cutting commitments, partial compatibility.

The mathematics of this — sheaves, cellular cohomology, discourse graphs — is being formalized in parallel. For the formal treatment, see the companion site: sheaf.lol ↗

field Aagentnodeinstancesiteclaimcommitmentevidencegardenmembraneintentcanon

06 · how to engage

You do not migrate into Spore as a platform.

You let your project speak more of the grammar.

adopt

Incrementally, in your own project.

A project can use one pattern without adopting the full stack. Adoption is incremental and reversible.

Adoption guide