Generated English Docs Index

Read the English Mycel docs by intent, not by directory.

This page is generated from selected English Markdown sources in the repository. It lists project docs, protocol references, profiles, and design notes with a short opening note taken from each file's heading section.

The short note prefers a leading Status: line when one exists, otherwise it falls back to the first summary paragraph under the document title.

Open Repository Browse Design Notes

16 documents

Project Docs

High-level project overviews, roadmap materials, and public-facing reference notes.

docs/DEV-SETUP.md

Dev Setup

This guide is the shortest path from a fresh checkout to a usable Mycel development environment.

Open Markdown

README.md

Mycel

Mycel is a Rust-based protocol stack for verifiable text history, governed reading state, and decentralized replication.

Open Markdown
working explanation

docs/MYCEL-CHARACTERISTICS.md

Mycel Characteristics

This document explains several characteristic terms commonly used to describe Mycel, what each term means in Mycel, and what it should not be mistaken for.

Open Markdown
working checklist

docs/FEATURE-REVIEW-CHECKLIST.md

Mycel Feature Review Checklist

This document is a recurring review list for any proposed new Mycel feature.

Open Markdown

docs/MYCEL-GRANT-CONCEPT-NOTE.md

Mycel Grant Concept Note

Mycel: Verifiable Text History, Governed Reading State, and Decentralized Replication

Open Markdown
draft

docs/PROGRESS.md

Mycel Progress View

This page turns ROADMAP.md and IMPLEMENTATION-CHECKLIST.en.md into one quick progress view.

Open Markdown
major progress

ROADMAP.md

Mycel Roadmap

This roadmap turns the current README priorities, implementation checklist, and design-note planning guidance into one repo-level build sequence.

Open Markdown
draft

SPEC-ISSUES.md

Mycel Spec Issue List

This document tracks protocol-spec issues that are likely to cause interoperability problems, ambiguous validation behavior, or incompatible implementations.

Open Markdown
M1 minimal-client gate closed and retained below as a...

IMPLEMENTATION-CHECKLIST.en.md

Mycel v0.1 Implementation Checklist

This checklist translates the v0.1 spec into an implementation-oriented build plan for a minimal interoperable client.

Open Markdown
draft discussion document for protocol-state modeling

docs/MYCEL-WIRE-SESSION-XSTATE-DRAFT.md

Mycel Wire Session XState Draft

This document sketches how we could model a minimal Mycel wire session as an XState machine. The goal is not to replace the current Rust implementation. The goal is to make session states, message ordering, guards, an...

Open Markdown

PROJECT-INTENT.md

Project Intent

Illustrative conditions and corresponding possible Mycel uses:

Open Markdown
current outward-facing naming guidance

docs/PROJECT-NAMING.md

Project Naming

This document defines how Mycel and MycelLayer should be used across the repository and public-facing surfaces.

Open Markdown

RUST-WORKSPACE.md

Rust Workspace

This note describes the first Rust workspace cut for Mycel.

Open Markdown

SECURITY.md

Security Policy

Mycel is currently an early-stage, spec-first project.

Open Markdown
explanatory note

docs/MYCEL-GAP.md

The Gap Mycel Fills

This document explains why protocols like Mycel have been relatively rare, and how the problems Mycel is trying to address are usually handled today.

Open Markdown

docs/MYCEL-VALUE.md

The Value of Mycel

This document rewrites Mycel's value proposition in a form that is easier to explain outwardly: instead of starting with protocol mechanics, it starts with the pain points people already feel in today's tools.

Open Markdown

2 documents

Protocol

Core protocol and wire-level reference documents.

PROTOCOL.en.md

Mycel Protocol v0.1

Mycel is a text protocol with the following characteristics:

Open Markdown

WIRE-PROTOCOL.en.md

Mycel Wire Protocol v0.1 (Draft)

This document defines the transport-level message format and minimum synchronization flow for Mycel nodes.

Open Markdown

2 documents

Profiles

Profile documents that define governed interpretations and application-specific shapes.

profile draft

PROFILE.fund-auto-disbursement-v0.1.en.md

Fund Auto-disbursement Profile v0.1

This profile defines a narrow interoperable model for automatic fund disbursement built on top of Mycel app-layer records, accepted-state selection, and policy-driven m-of-n custody.

Open Markdown
profile draft

PROFILE.mycel-over-tor-v0.1.en.md

Mycel over Tor Profile v0.1

This profile defines a narrow deployment model for running Mycel over Tor-oriented transport.

Open Markdown

39 documents

Design Notes

Deeper design explorations for protocol, app-layer, and governance concepts.

design draft

docs/design-notes/DESIGN-NOTES.auto-signer-consent-model.en.md

Auto-signer Consent Model

This note describes how a Mycel-based system should model consent for automatic threshold signers.

Open Markdown
design draft

docs/design-notes/DESIGN-NOTES.canonical-text-profile.en.md

Canonical Text Profile

This note describes a neutral text profile for carrying structured, cited, and annotated canonical corpora on top of Mycel.

Open Markdown
design draft

docs/design-notes/DESIGN-NOTES.client-non-discretionary-multi-view.en.md

Client-Non-Discretionary Multi-View

This note describes one way to keep Mycel multi-view while minimizing how much ordinary clients can influence the active accepted head.

Open Markdown
design draft

docs/design-notes/DESIGN-NOTES.commentary-citation-schema.en.md

Commentary and Citation Schema

This note defines a narrow app-level schema for maintainer-authored commentary works that heavily cite one or more source documents without overwriting them.

Open Markdown
design draft

docs/design-notes/DESIGN-NOTES.donation-app-layer.en.md

Donation App Layer

This note describes a donation-oriented application layer carried by Mycel while keeping payment execution outside the core protocol.

Open Markdown
design draft

docs/design-notes/DESIGN-NOTES.dynamic-module-loading.en.md

Dynamic Module Loading for Mycel Apps

This note proposes a conservative way for a Mycel-based app to load executable extension logic at runtime and download missing modules on demand.

Open Markdown
design draft

docs/design-notes/DESIGN-NOTES.enterprise-messenger-app-layer.en.md

Enterprise Messenger App Layer

This note describes how Mycel can carry an enterprise instant messenger app for internal planning, operations, and compliance-heavy collaboration without turning the core protocol into a chat transport, DLP engine, or...

Open Markdown
design draft

docs/design-notes/DESIGN-NOTES.first-client-scope-v0.1.en.md

First-client Scope v0.1

This note defines the narrowest practical first-client scope for Mycel.

Open Markdown
design draft

docs/design-notes/DESIGN-NOTES.forum-qa-relationship.en.md

Forum and Q&A Relationship

This note defines the relationship between the Forum App Layer and the Q&A App Layer.

Open Markdown
design draft

docs/design-notes/DESIGN-NOTES.forum-app-layer.en.md

Forum App Layer

This note describes how Mycel could carry a forum-style application layer while keeping forum semantics outside the protocol core.

Open Markdown
design draft

docs/design-notes/DESIGN-NOTES.future-software-ecosystem-on-mycel-runtime-substrate.en.md

Future Software Ecosystem on Mycel Runtime Substrate

This note imagines a future where Mycel-style signed, on-demand runtime loading is no longer a niche architecture choice, but part of the mainstream software environment.

Open Markdown
design draft

docs/design-notes/DESIGN-NOTES.governance-history-security.en.md

Governance History Security

This note describes how a Mycel-based system should secure governance history so that decisions remain verifiable, replayable, and recoverable over time.

Open Markdown
design draft

docs/design-notes/DESIGN-NOTES.interpretation-dispute-model.en.md

Interpretation Dispute Model

This note describes how Mycel can model, preserve, and arbitrate interpretation disputes without silently replacing root text or forcing all deployments into one universal reading.

Open Markdown
design draft

docs/design-notes/DESIGN-NOTES.metadata-merge-boundaries.en.md

Metadata Merge Boundaries

This note records the current M2 metadata-merge boundary for the conservative merge-authoring flow.

Open Markdown
design draft

docs/design-notes/DESIGN-NOTES.minimal-mycel-host-bootstrap.en.md

Minimal Mycel Host Bootstrap

This note describes the smallest practical local bootstrap that could host Mycel as a signed, on-demand runtime substrate.

Open Markdown
design draft

docs/design-notes/DESIGN-NOTES.mycel-anonymity-model.en.md

Mycel Anonymity Model

This note describes how a Mycel-based system should reason about anonymity as a multi-layer property rather than a single transport setting.

Open Markdown
design draft

docs/design-notes/DESIGN-NOTES.mycel-app-layer.en.md

Mycel App Layer

This note describes an application layer carried by Mycel while keeping side-effect execution outside the core protocol.

Open Markdown
design draft

docs/design-notes/DESIGN-NOTES.app-signing-model.en.md

Mycel App-signing Model

This note describes how a Mycel-based system should think about application signing as a layered model rather than one single signature decision.

Open Markdown
design draft

docs/design-notes/DESIGN-NOTES.signed-on-demand-runtime-substrate.en.md

Mycel as a Signed On-Demand Runtime Substrate

This note explores a more ambitious interpretation of Mycel: not only as a protocol for verifiable text and governance, but as a substrate where most application logic can be fetched, verified, and executed on demand.

Open Markdown
design draft

docs/design-notes/DESIGN-NOTES.blind-address-threat-model.en.md

Mycel Blind-address Threat Model

This note describes the main threat surfaces, trust boundaries, and control requirements for a Mycel deployment that uses a blind-address custody model.

Open Markdown
design draft

docs/design-notes/DESIGN-NOTES.mycel-full-stack-map.en.md

Mycel Full-stack Map

This note maps the current Mycel document set into a full-stack system view.

Open Markdown
design draft

docs/design-notes/DESIGN-NOTES.maintainer-conflict-flow.en.md

Mycel Maintainer Conflict Flow

This note describes how a Mycel deployment should model and preserve a conflict between maintainers over a document idea or direction without collapsing the conflict into silent overwrite.

Open Markdown
design draft

docs/design-notes/DESIGN-NOTES.mycel-protocol-upgrade-philosophy.en.md

Mycel Protocol Upgrade Philosophy

This note describes how Mycel should evolve its protocol, profiles, and design notes without turning the core specification into a fast-moving target.

Open Markdown
design draft

docs/design-notes/DESIGN-NOTES.signature-role-matrix.en.md

Mycel Signature Role Matrix

This note maps the main object families in the current repo to the roles that should sign them.

Open Markdown
design draft

docs/design-notes/DESIGN-NOTES.signature-priority.en.md

Mycel Signature-priority Note

This note organizes which object families in the current Mycel repo should require signatures first, rather than treating every possible object family as equally urgent.

Open Markdown
design draft

docs/design-notes/DESIGN-NOTES.signer-activity-model.en.md

Mycel Signer Activity Model

This note describes how a Mycel-based custody deployment should evaluate signer activity rather than treating signer availability as a binary guess.

Open Markdown
design draft

docs/design-notes/DESIGN-NOTES.signer-availability-emergency-response.en.md

Mycel Signer-availability Emergency Response

This note describes how a Mycel-based m-of-n custody deployment should detect dangerous signer-availability decline and trigger emergency rotation, address renewal, or other recovery paths before practical lockout occ...

Open Markdown
design draft

docs/design-notes/DESIGN-NOTES.peer-discovery-model.en.md

Peer Discovery Model

This note describes how a Mycel-based system should discover, classify, and retain peers without assuming one universal global discovery mode.

Open Markdown
design draft

docs/design-notes/DESIGN-NOTES.peer-simulator-v0.en.md

Peer Simulator v0

This note defines a narrow multi-peer simulator for early Mycel implementation testing.

Open Markdown
design draft

docs/design-notes/DESIGN-NOTES.policy-driven-threshold-custody.en.md

Policy-driven m-of-n Custody

This note describes a custody model where Mycel carries the policy and governance history for fund movements, while an m-of-n signer network executes approved transactions automatically under fixed policy constraints.

Open Markdown
design draft

docs/design-notes/DESIGN-NOTES.qa-app-layer.en.md

Q&A App Layer

This note describes a Q&A application layer carried by Mycel while keeping domain-specific interpretation and advisory workflows outside the core protocol.

Open Markdown
design draft

docs/design-notes/DESIGN-NOTES.qa-minimal-schema.en.md

Q&A Minimal Schema

This note defines a minimal app-level schema for a Mycel-carried Q&A application.

Open Markdown
design draft

docs/design-notes/DESIGN-NOTES.realtime-media-app-layer.en.md

Realtime Media App Layer

This note describes how Mycel can support realtime audio/video services without turning the core protocol or wire layer into a media-streaming transport.

Open Markdown
design note

docs/design-notes/DESIGN-NOTES.relay-node-layering.en.md

Relay Node Layering

This note defines where a relay node belongs in Mycel's layer model.

Open Markdown
design draft

docs/design-notes/DESIGN-NOTES.sensor-triggered-donation.en.md

Sensor-triggered Donation App/Profile Architecture

This note describes an app/profile architecture where a runtime observes machine-derived user-state events and may create donation-related records under a pre-authorized consent policy.

Open Markdown
design draft

docs/design-notes/DESIGN-NOTES.text-worker-editor.en.md

Text-worker Editor

This note describes a future editor surface for serious text work on top of Mycel.

Open Markdown
design draft

docs/design-notes/DESIGN-NOTES.text-worker-editor-implementation.en.md

Text-worker Editor Implementation Sketch

This note describes a plausible implementation plan for a future Mycel text-worker editor.

Open Markdown
design draft

docs/design-notes/DESIGN-NOTES.two-maintainer-role.en.md

Two-Maintainer-Role Model

This note proposes splitting maintainer responsibility into two explicit roles:

Open Markdown
design draft

docs/design-notes/DESIGN-NOTES.viewer-editor-view-maintainer-checks-and-balances.en.md

Viewer-Editor-View-Maintainer Checks and Balances

This note proposes a checks-and-balances model for Mycel with three distinct roles:

Open Markdown