MCP-1 Core
This page contains actual sections from the MCP-1 portion of the full specification.
Open full MCP-1 section in archive →Foundational Axioms
The Myceloom Protocol rests on foundational axioms. These are not merely design principles but constitutive requirements: systems violating these axioms cannot be considered myceloom-aligned.
Axiom I: Sovereignty First
Statement: No node SHALL be built on rented land.
- Nodes MUST control their own data storage.
- Nodes MUST control their own identity infrastructure.
- Nodes MUST support independent operation without third-party platform dependence.
Axiom II: Reciprocal Nourishment
Statement: A link is not a transaction; it is a root system. Value MUST flow bidirectionally.
- Inter-node connections MUST provide value to both parties.
- Systems MUST NOT extract value from participation without contribution.
- Resource sharing SHOULD include reciprocity mechanisms.
Axiom III: Emergent Intelligence
Statement: Intelligence is not a property of the center; it is a property of the edge.
- Decision-making MUST occur at the lowest capable level.
- Network behavior MUST emerge from local interactions.
- Collective intelligence MUST enhance rather than replace node autonomy.
Axiom IV: Intentional Patterning
Statement: Structure MUST NOT be accidental; it MUST be the result of intentional craft.
Systems distinguish protocol as load-bearing structure and interface as adaptive expression.
The My-Sea-Loom Synthesis
- My (Sovereignty): Axiom I.
- Sea (Interconnection): Axioms II and III.
- Loom (Structure): Axiom IV.
- Heirloom (Time): persistence through sovereign structure.
Therefore: A system is myceloom-aligned when the Loom (Axiom IV) weaves the Sea (Axioms II/III) into the My (Axiom I).
Architecture Overview
MCP-1 defines an eight-layer architecture organized into four functional domains: Substrate, Society, Human, and Dimension.
DOMAIN IV: DIMENSION → Layer 8 DOMAIN III: HUMAN → Layers 7, 6 DOMAIN II: SOCIETY → Layers 5, 4 DOMAIN I: SUBSTRATE → Layers 3, 2, 1
Each layer builds on lower layers while remaining loosely coupled; higher layers may be implemented independently if functional requirements are satisfied.
Read full architecture details →