sym.bot

Intellectual Property & Attribution

Last updated: April 2026

SYM.BOT publishes specifications, reference implementations, and applications under a combination of open-source licenses and proprietary terms. This page establishes canonical attribution requirements, citation formats, trademark usage, and authority-record anchors for anyone implementing against, citing, or referencing SYM.BOT work.

For application-level licensing terms (subscriptions, credit-based payment, warranty, liability), see the Software License Agreement.

1. Canonical citation formats

Copy-paste ready citation blocks for the three SYM.BOT-authored specifications currently in public circulation.

Mesh Memory Protocol (MMP) v0.2.3

Academic (full form):

Xu, H. (2026). Mesh Memory Protocol: Semantic Infrastructure for Multi-Agent LLM Systems. arXiv [MMP_PAPER_ARXIV_ID], cs.MA (primary) + cs.AI (cross-list). CC BY 4.0.

Implementation reference (README / product docs):

Built on the Mesh Memory Protocol (MMP) v0.2.3, an open specification from SYM.BOT. Specification: https://sym.bot/spec/mmp (CC BY 4.0). Reference implementations: @sym-bot/sym (Node.js, Apache 2.0), SYM Swift (iOS/macOS, Apache 2.0).

BibTeX:

@misc{xu2026mmp,
  author       = {Xu, Hongwei},
  title        = {Mesh Memory Protocol: Semantic Infrastructure for Multi-Agent LLM Systems},
  year         = {2026},
  howpublished = {arXiv preprint [MMP_PAPER_ARXIV_ID]},
  eprint       = {[MMP_PAPER_ARXIV_ID]},
  archivePrefix = {arXiv},
  primaryClass = {cs.MA},
  note         = {Specification: https://sym.bot/spec/mmp (CC BY 4.0)},
}

Symbolic-Vector Attention Fusion (SVAF)

Academic (full form):

Xu, H. (2026). Symbolic-Vector Attention Fusion for Collective Intelligence. arXiv:2604.03955, cs.MA.

Implementation reference:

Per-field evaluation uses Symbolic-Vector Attention Fusion (SVAF), as specified in Xu (2026, arXiv:2604.03955).

BibTeX:

@misc{xu2026svaf,
  author       = {Xu, Hongwei},
  title        = {Symbolic-Vector Attention Fusion for Collective Intelligence},
  year         = {2026},
  howpublished = {arXiv preprint arXiv:2604.03955},
  eprint       = {2604.03955},
  archivePrefix = {arXiv},
  primaryClass = {cs.MA},
}

MMP Consent Extension v0.1.0 (archived)

The MMP Consent Extension v0.1.0 is an archived specification. It was published on sym.bot/spec/mmp-consent on 28 March 2026 and withdrawn from current publication on 21 April 2026. The authorship record and specification content are permanently preserved via the Internet Archive Wayback Machine.

Academic (full form):

Xu, H. (2026). MMP Extension: Consent — Protocol-Level Consent Primitive for Cognitive Mesh Coupling, v0.1.0. Originally published 28 March 2026 at sym.bot/spec/mmp-consent; archived 21 April 2026. Internet Archive Wayback Machine snapshot: https://web.archive.org/web/20260421104850/https://sym.bot/spec/mmp-consent-v0.1.0.html. Zenodo DOI: [ZENODO_DOI_WHEN_ASSIGNED]. SYM.BOT, CC BY 4.0.

Implementation reference:

Implements the MMP Consent Extension v0.1.0 (specification by Xu / SYM.BOT; archived 2026-04-21, Wayback Machine canonical record).

2. Attribution requirements under CC BY 4.0

The MMP specification and the MMP Consent Extension v0.1.0 are published under Creative Commons Attribution 4.0 International (CC BY 4.0). Implementations, derivative works, and any public-surface representation of these specifications must satisfy the attribution requirements of the license.

Section 3(a): accurate attribution

CC BY 4.0 §3(a) requires that licensees:

  • Identify the creator of the Licensed Material — SYM.BOT / Hongwei Xu as the specification author.
  • Preserve a copyright notice — © 2026 SYM.BOT, CC BY 4.0.
  • Include a URI or hyperlink to the material — https://sym.bot/spec/mmp for MMP; relevant Wayback snapshot for the archived Consent Extension.
  • Indicate if the material has been modified — implementation deviations from the specification must be documented.

Section 6: termination and cure

CC BY 4.0 §6(a) provides that the license automatically terminates upon any breach of its attribution requirements. §6(b) provides a 30-day cure period: if the licensee becomes compliant within 30 days of discovering or being notified of the breach, the license is reinstated.

SYM.BOT reserves all rights regarding enforcement of the attribution clause, including the §6 termination and cure mechanism, for the MMP specification and the MMP Consent Extension.

3. Attribution — what accurate looks like

Concrete examples to guide implementers and public-surface descriptions.

For README files, product documentation, and website copy

✓ Accurate:

Our system implements the Mesh Memory Protocol (MMP) v0.2.3, an open specification from SYM.BOT (CC BY 4.0). Specification: https://sym.bot/spec/mmp.

✗ Inaccurate (co-authorship misattribution):

Our system uses MMP, jointly developed with SYM.BOT.

✗ Inaccurate (silent implementation without attribution):

Our system uses an open mesh protocol for cognitive state exchange. (Missing required identification of creator + URI.)

✓ Accurate for reference implementations:

Reference implementation of the MMP Consent Extension v0.1.0 (specification by Xu, SYM.BOT; archived 21 April 2026, canonical record at Wayback Machine).

✗ Inaccurate for reference implementations:

Co-designed consent primitive for [domain] — implemented jointly with SYM.BOT.

For academic papers

✓ Accurate (citation + acknowledgment):

We build on the Mesh Memory Protocol (MMP) specification (Xu 2026, arXiv [MMP_PAPER_ARXIV_ID], CC BY 4.0) and its evaluation framework SVAF (Xu 2026, arXiv:2604.03955).

✗ Inaccurate (uncredited use of framework language):

We employ per-field attention fusion for cognitive state evaluation. (If the per-field evaluation is implemented per SVAF, citation is required.)

For GitHub repository Collaborations tables

✓ Accurate:

SYM.BOT | MMP specification author (CC-BY-4.0); Consent Extension v0.1.0 specification author (archived). Our contribution: Rust reference implementation of the Consent Extension primitive.

✗ Inaccurate:

SYM.BOT | MMP protocol co-design · Consent Extension · Joint arXiv paper (overstates collaborative scope across MMP and Consent Extension; misrepresents paper status).

4. Trademark policy

SYM.BOT holds trademark rights in the following marks:

  • SYM.BOT — company name and corporate identifier
  • MMP and Mesh Memory Protocol — protocol name
  • SVAF and Symbolic-Vector Attention Fusion — evaluation framework name
  • SYM — reference implementation product family
  • Mesh Cognition — architectural term
  • MeloMotion, MeloTune, MeloMove — product names

Permitted naming usage

✓ Acceptable without prior permission:

  • Referring to specifications by their full proper name in implementations, academic citations, and technical documentation (e.g., “implements the Mesh Memory Protocol”, “uses SVAF per Xu 2026”)
  • Referencing SYM.BOT as the specification author in attribution notices
  • Using product names in editorial/journalistic context with accurate description

Requires prior written permission (email ip@sym.bot):

  • Use of SYM.BOT, MMP, SVAF, or other marks in a product name, service name, or domain name
  • Use implying endorsement, partnership, or certification by SYM.BOT that is not documented
  • Use in advertising or promotional materials beyond accurate descriptive reference

Not permitted:

  • Use of marks in a manner that is misleading, defamatory, or implies a collaboration that does not exist
  • Use of product names (MeloMotion, MeloTune, MeloMove) without descriptive context

5. Authority records

Permanent public-record anchors for SYM.BOT specifications. These supplement the current-state publication URLs; where current publication state changes, archival snapshots preserve the authorship timestamp.

MMP v0.2.3

SVAF (Symbolic-Vector Attention Fusion)

MeloTune reference deployment paper

MMP Consent Extension v0.1.0 (archived)

Reference implementations

6. Reporting attribution concerns

For suspected license non-compliance, attribution disputes, or DMCA-reportable content:

Email: ip@sym.bot

Please include:

  • The specific URL or artifact where the attribution issue appears
  • The specification or implementation that is the subject of the concern (MMP, SVAF, MMP Consent Extension, SYM Node.js, SYM Swift, sym-mesh-channel)
  • The specific attribution that is missing, inaccurate, or at issue
  • Your role (specification user, third-party observer, or representative)

SYM.BOT reviews reported concerns and responds in writing with the applicable resolution path — typically (a) a specific correction request under the CC BY 4.0 §3(a) attribution clause with a 7-day compliance window, or (b) a clarification that the described usage is compliant.

For GitHub-hosted content, SYM.BOT may additionally use GitHub’s content removal / DMCA reporting process where the attribution concern remains unresolved after a direct correction request.

7. Third-party implementations are welcome

SYM.BOT supports and welcomes third-party implementations of MMP, SVAF, and the archived MMP Consent Extension under the published license terms. The specifications are designed to be implementable without gatekeeper review, interop-testable against the SYM Node.js and SYM Swift reference implementations, and composable with existing multi-agent frameworks.

If your implementation conforms to the specification and maintains accurate attribution, it is welcome to:

  • Self-describe as “implements the Mesh Memory Protocol” (or the specific extension/version implemented)
  • Participate in the SYM.BOT mesh ecosystem (cross-implementation interop testing)
  • Be referenced from sym.bot/spec/mmp implementers list upon request

Accurate attribution is the one ongoing requirement; the specification grant itself is permissive.

8. Related pages