FIG.09 · GOVERNANCE
Mesh Cognition is stewarded at meshcognition.org. SYM.BOT contributes as the founding implementer. The protocol evolves through an open, editor-led RFC process; the editor is Hongwei Xu.
Maturity, stated plainly. MMP is currently an editor-maintained open specification with one principal implementation. It is not yet a multi-party industry standard. Independent implementations, conformance tooling operated separately from the reference runtime, and broader stewardship are explicit prerequisites for that designation.
Spec change proposals are filed as GitHub issues at github.com/sym-bot/mesh-memory-protocol/issues
with [spec-rfc] in the title. Implementation-specific issues (Node.js, Swift, Python) belong on each impl's own tracker.
Every RFC stays open for at least 14 days of public comment before any decision. This is the floor for a workable change; complex proposals stay open longer until discussion converges.
After the comment window, the editor (editor@meshcognition.org) decides: accept, accept-with-revisions, defer, or reject — with reasoning posted to the issue. Accepted RFCs land in the next spec release and appear in the Change Log.
From v1.0 onward: major bumps signal breaking wire-protocol or schema changes; minor bumps add backwards-compatible features; patch bumps are editorial or clarification-only. Breaking changes require a major version, an explicit migration path, and a publicly announced deprecation period appropriate to the impact.
For security-sensitive disclosures or matters that don't fit a public issue, contact spec@meshcognition.org. Routine spec questions and clarifications belong on the public issue tracker.
Specification text: CC BY 4.0. Reference implementations: Apache 2.0.