Mycel is a protocol stack for long-lived texts, commentary systems, and governed reference corpora. It separates replay-verifiable history, governance signals, and replication while keeping them interoperable.
Public-facing materials may also use the name MycelLayer. The default
reading version is not network-wide consensus. It is the result derived from verified
objects under one fixed profile.
`v0.1` spec-first project. Current work keeps narrow-scope M2 closed
while moving M3 past the landed independent dual-role closure toward
broader governance persistence, governance tooling, and reader-profile ergonomics
follow-up, plus the remaining M4
session/capability/error-path interop proof.
Not a blockchain, not a Git clone, and not a generic file-transfer layer. Mycel is aimed at governed text systems with verifiable history.
Most distributed collaboration systems either centralize mutable state or optimize for code collaboration and global consensus. Mycel takes a narrower path: text-first history, profile-governed accepted reading, and decentralized replication with explicit replay and verification boundaries.
Revisions are meant to be replayed, checked, and rebuilt from canonical objects.
Accepted heads come from fixed selector rules and verified View objects.
Multiple valid heads can coexist without forcing one global truth for all readers.
The current CLI is not yet a production client or node, but it is useful for internal validation and simulator workflows inside this repository.
If you are starting from a fresh environment, read Dev Setup first.
cargo run -p mycel-cli -- info
cargo run -p mycel-cli -- validate fixtures/object-sets/minimal-valid/fixture.json --json
cargo run -p mycel-cli -- sim run sim/tests/three-peer-consistency.example.json --json
If you want the fastest way into the project, start with the current build lane and setup notes first, then move into the implementation and design references that match your interests.
Get a fresh workspace into a usable state before you pick up any implementation or documentation slice.
See the active M2 / M3 / M4 lane, what comes next, and which gaps are intentionally still open.
Read the public summary view first if you want a compressed picture of milestone status before diving into repo-level detail.
Read the public field notes when you want the design arguments and coordination patterns behind the repo workflow.
Use the project overview as the general entry point when you want context before choosing a code, doc, or design slice.
We are interested in design partners, grant support, and early collaborators working on governed text systems, commentary layers, or durable reference corpora. Support now helps finish the first interoperable client core: verification, replay, rebuildable storage, shared canonicalization closure, and profile-governed accepted reading/rendering.