FIG.07 · GOVERNANCE

Governance.

Mesh Cognition is stewarded at meshcognition.org. SYM.BOT contributes as the founding implementer. The protocol evolves through a public RFC process; the editor is Hongwei Xu.

01 · FILE

Open an RFC issue

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.

02 · COMMENT

14-day public window

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.

03 · DECIDE

Editor merge

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.

04 · VERSION

Semver discipline

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. The editor commits to a 30-day deprecation window before any breaking change ships.

Out-of-band channels

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.

License

Specification text: CC BY 4.0. Reference implementations: Apache 2.0.

Back to home Spec → v1.0