PROTOCOL MCP-1 (GENESIS)

The Myceloom Protocol

A proposed architectural pattern for building decentralized, symbiotic digital infrastructure. One way to think about moving from digital tenancy to symbiotic sovereignty.

Inject Spore

// 01. The Manifesto

The digital world has fractured into two failing architectures: The Silo (Extractive) and The Scatter (Starving).

The Myceloom is a third architecture. It synthesizes the sovereignty of the independent node with the resilience of the distributed network. Like the mycelial networks beneath a forest floor, it is invisible infrastructure where the intelligence of the network exceeds the sum of its parts.

The Three Axioms

Axiom I: Sovereignty First. No node shall be built on rented land. A tenant can never be a true peer.
Axiom II: Reciprocal Nourishment. A link is not a transaction; it is a root system. Value must flow bidirectionally.
Axiom III: Emergent Intelligence. Intelligence is not a property of the center; it is a property of the edge.

"Unlike a hyperlink, which connects Page A to Page B, a Spore connects Page A to an Idea. It allows a network to form in the dark, without a central server knowing it exists. It is antifragile connectivity."

// 02. The Specification

The functional requirements mapped to the Myceloom Domain Architecture.

Layer I: The Substrate (Infrastructure)

1. The Network Layer (.net)

Principle: Radical Redundancy. Intelligence and routing must reside at the edges. No single node failure may compromise the whole.

2. The Intelligence Layer (.ai)

Principle: Distributed Cognition. AI agents must operate as symbiotic partners, not extraction engines. Compute occurs locally (Edge AI).

3. The Interface Layer (.io)

Principle: The Spore. Interfaces must be adaptive. Strict separation of Immutable Protocols (Warp) from Adaptive Interfaces (Weft).

Layer II: The Society (Governance)

4. The Community Layer (.org)

Principle: The Immune System. Permissionless innovation. No central authority grants the right to build.

5. The Coalition Layer (.co)

Principle: The Guild. Economic units structured as federations of independent creators. Sustainable, regenerative exchange.

Layer III: The Human (Time & Identity)

6. The Identity Layer (.im)

Principle: "I Am". Identity rooted in owned infrastructure. Relational autonomy defined by connections maintained.

7. The Temporal Layer (Heirloom)

Principle: Abyssal Time. Legibility as Legacy. All systems must document a path for succession and use human-readable formats.

Layer IV: The Dimension (Depth)

8. The Dimensional Layer (My-Sea-Loom)

Principle: Bioluminescence. Systems must generate their own light (verification) in disconnected states. Design for tidal rhythms, not flatlines.

// 03. Alignment (Not Compliance)

The Myceloom is not a product to be bought. It is a topology to be inhabited.

A project might be considered Myceloom-aligned if it owns its ground, publishes via open standards, links reciprocally to peers, and documents its succession plan. No code, certification, or permission required. This is a philosophical framework, not a technical requirement.

// 04. Optional: The Spore (Network Discovery)

If you want to make your site discoverable to other nodes in the mycelial network, you can optionally embed a Spore declaration. This is a copyable JSON-LD schema that you can self-host or modify. The @context field can point to your own vocabulary—you are not required to reference myceloom.network.

Think of this as a reference implementation, not a dependency.

spore_injection.json

<!-- Myceloom Spore (Optional Reference Implementation) -->
<script type="application/ld+json">
{
  /* You can self-host this context or create your own */
  "@context": "https://your-domain.com/context",
  "@type": "Spore",

  /* Customize these fields */
  "lineage": "sentientification", // The meme/theme you belong to
  "mutation": "v1.2",             // Your version of the idea
  "parent": "https://site-that-inspired-you.com", // Who inspired you?
  "status": "germinating",        // "germinating", "fruiting", or "dormant"
  
  /* Optional: Semantic Signals */
  "signals": [
    "digital-archaeology",
    "decentralized-protocol",
    "archaeobytology"
  ]
}
</script>

                // Field Decoder
            

lineage The central theme or meme your site belongs to. (e.g., "solarpunk", "sentientification"). This connects you to others.

mutation Your version number. Did you change the idea? Add to it? Increment this to show evolution.

parent The URL of the site that inspired you or where you got the code. This builds the family tree.

status Your node's lifecycle stage. (See "Node Health" below).

signals (Optional) A list of keywords describing your node's specific flavor or niche.

// Node Health Guide (When to update status)

germinating

Use this when your site is new, experimental, or incomplete. It tells the network: "I am growing."

fruiting

Use this when your site is active, robust, and ready for visitors. It tells the network: "I am ready to share spores."

dormant

Use this when the project is finished or archived. It tells the network: "I am static but valuable history."

// Editing Safety Manual

✓ SAFE TO CHANGE: Everything inside the quotes on the right side (e.g., "v1.2", "germinating"). This is your data.
✕ DO NOT TOUCH: The keys on the left (e.g., "lineage":, "@context":). Changing these breaks the protocol reader.
✕ DO NOT TOUCH: The structure (curly braces {} and commas). JSON is strict. Missing a comma will break the code.

// 04. Network Visualization

This is what the protocol makes visible. A live simulation of how the Myceloom browser extension renders the hidden connections between sites sharing the sentientification lineage.

See the Aspiration: For a full-screen, artistic interpretation of what this living network aspires to become, visit the Digital Monument: Myceloom Network Iteration →

LIVE SIGNAL • 0 NODES DETECTED

// 05. Compliance & Invitation

The Myceloom is not a product to be bought. It is a topology to be inhabited.

A project is considered Myceloom Compliant if it owns its ground, publishes via open standards, links reciprocally to peers, and documents its succession plan.