From f5e71151c1bf26f8e6db5a6e5ef902c9302d28c1 Mon Sep 17 00:00:00 2001 From: QunYu Date: Fri, 20 Mar 2026 22:06:34 +0800 Subject: [PATCH 1/3] Delete IMPLEMENTATION_NOTICE.md --- IMPLEMENTATION_NOTICE.md | 14 -------------- 1 file changed, 14 deletions(-) delete mode 100644 IMPLEMENTATION_NOTICE.md diff --git a/IMPLEMENTATION_NOTICE.md b/IMPLEMENTATION_NOTICE.md deleted file mode 100644 index bdcbe42..0000000 --- a/IMPLEMENTATION_NOTICE.md +++ /dev/null @@ -1,14 +0,0 @@ -SwarmPlug Specification vs Implementation Boundary - -This repository documents the SwarmPlug infrastructure specification. - -It does not contain implementation source code. - -All runtime components, executable systems, -protocol engines, translation layers, transport mechanisms, -and coordination logic remain proprietary. - -SwarmPlug is a trademark of QunYu Technology. -Use of the name in derivative works must not imply official endorsement. - -This repository contains specification materials only. From 3d97775f94ee644e1d4b15bf926dbeaf06c09a9f Mon Sep 17 00:00:00 2001 From: QunYu Date: Fri, 20 Mar 2026 22:07:14 +0800 Subject: [PATCH 2/3] Delete LICENSE --- LICENSE | 58 --------------------------------------------------------- 1 file changed, 58 deletions(-) delete mode 100644 LICENSE diff --git a/LICENSE b/LICENSE deleted file mode 100644 index 1953ab9..0000000 --- a/LICENSE +++ /dev/null @@ -1,58 +0,0 @@ -# SwarmPlug Documentation License v1.0 - ---- -**Copyright (c) 2026 QunYu Technology** -This repository contains architectural documentation and versioned infrastructure specifications for the SwarmPlug project (the “Documentation”). -This license governs use of the Documentation only. - ---- -## 1. Definitions -**“Documentation”** refers to all textual materials, diagrams, architectural descriptions, version specifications, and related materials contained in this repository. -**“SwarmPlug”** refers to the project name and associated infrastructure concept described in the Documentation. - ---- -## 2. Scope of License -This license applies solely to the Documentation. -This license does **not** grant: -- Any right to implement software or hardware under the name “SwarmPlug”; -- Any right to distribute software or hardware under the name “SwarmPlug”; -- Any right to commercialize systems derived from the Documentation; -- Any right to claim official compatibility, certification, or endorsement. -Nothing in this license grants rights to any executable system, runtime component, protocol engine, hardware product, or commercial deployment related to SwarmPlug. - ---- -## 3. Permitted Uses -You may: -1. View and read the Documentation. -2. Share the unmodified Documentation in whole for academic, research, and informational purposes. -3. Cite the Documentation with proper attribution. - -Attribution must clearly reference: -- **SwarmPlug** -- **QunYu Technology** -- The official repository URL (where reasonably practicable) - ---- -## 4. Implementation Boundary -This repository does not contain implementation code. -All runtime systems, protocol engines, canonical identity mechanisms, snapshot schema engines, transport mechanisms, coordination logic, hardware systems, executable software, and commercial deployments are not included and remain proprietary. -Commercial collaboration or licensing inquiries may be directed to: -**swarmplug@gmail.com** - ---- -## 5. Trademark Notice -“SwarmPlug” is a trademark of QunYu Technology. -Use of the name must not imply official endorsement, certification, affiliation, or approval. - ---- -## 6. No Patent License -No patent rights are granted under this license, whether express or implied. - ---- -## 7. No Implied License -No rights or licenses are granted by implication, estoppel, or otherwise, except as expressly stated in this license. - ---- -## 8. Reservation of Rights -All rights not expressly granted under this license are reserved. ---- From de9337737eecd019d646f6ebfbc9a128c2a2812e Mon Sep 17 00:00:00 2001 From: QunYu Date: Fri, 20 Mar 2026 22:08:09 +0800 Subject: [PATCH 3/3] Revise README for SwarmPlug ver0.4 Updated README to reflect version 0.4 changes, including new definitions and principles for SwarmPlug. --- README.md | 263 ++++++++++++++++++++++++++++++++++++------------------ 1 file changed, 175 insertions(+), 88 deletions(-) diff --git a/README.md b/README.md index 86af960..85205f7 100644 --- a/README.md +++ b/README.md @@ -1,156 +1,243 @@ -# SwarmPlug -### A Versioned Infrastructure Specification for Semantic Normalization in ROS-based Systems ---- -## 1. Statement -SwarmPlug is a **versioned infrastructure specification**. +# SwarmPlug ver0.4 + +**Mesh Semantic Snapshot Exchange and Re-Exposure Specification** + +--- -It defines deterministic structural layers for semantic normalization -in heterogeneous ROS-based environments. +## Statement -SwarmPlug does **not**: +SwarmPlug ver0.4 defines a deterministic mesh-based semantic snapshot exchange +and controlled re-exposure mechanism across distributed SwarmPlug nodes. -- Replace ROS -- Define control logic -- Implement coordination strategies -- Provide intelligence systems +It does not anchor. +It does not decide. +It does not control. -**SwarmPlug defines infrastructure boundaries.** +**It distributes semantic state and re-exposes it locally.** --- -## 2. Development Model +## Problem -SwarmPlug evolves through **explicit version layers**. +Once semantic snapshots have been generated (ver0.3), +they must be made observable across multiple nodes. -Each version: +However, direct cross-node integration of host runtime (e.g., ROS topics) leads to: -- Has a narrowly defined responsibility -- Is boundary-limited -- Is version-scoped -- Does not expand retroactively +- Tight coupling between distributed runtimes +- Uncontrolled propagation behavior +- Recursive forwarding and message amplification +- Loss of deterministic boundaries -**New capabilities are introduced only through new versions.** +A dedicated infrastructure layer is required to: + +- exchange semantic state across nodes +- preserve system boundaries +- enable distributed observability without runtime entanglement --- -## 3. Version Index +## Position + +SwarmPlug ver0.4 defines the exchange layer above semantic snapshot generation. + +`Host Runtime → Host Attachment → Canonical Identity → Semantic Snapshot → Mesh Exchange → Local Re-Exposure` + +**ver0.4 completes the distributed semantic exchange layer.** -| Version | Responsibility | -|----------|----------------| -| **ver0.1** | Host attachment | -| **ver0.2** | Canonical identity | -| **ver0.3** | Semantic snapshot model | +It explicitly separates: -Each version defines a **strict normalization boundary**. -Later versions extend the structure without modifying previous layers. +- local runtime (host) +- semantic state (snapshot) +- distributed exchange (mesh) +- local re-exposure (receiver-side reconstruction) --- -## 4. Layered Direction -``` -Attachment -↓ -Identity -↓ -Semantics -↓ -Future Layers -``` +## Architecture (Conceptual) -Each layer must remain: -- Deterministic -- Versioned -- Infrastructure-oriented -- Boundary-defined +```mermaid + flowchart TB ---- + subgraph "Producer Node" + A1["ROS Runtime"] + A2["Canonical Identity"] + A3["Semantic Snapshot v0.3"] + A4["Mesh Exchange Endpoint"] + end -## 5. Scope Discipline + subgraph "Mesh Layer" + B1["Snapshot Delivery"] + end -SwarmPlug explicitly separates normalization infrastructure from: + subgraph "Receiver Node" + C1["Receive Snapshot"] + C2["Remote Cache"] + C3["Semantic Parsing"] + C4["Local Re-Exposure"] + end -- Runtime control systems -- Transport mechanisms -- Distributed coordination logic -- Intelligence or learning layers -- External anchoring or persistence systems + A1 --> A2 --> A3 --> A4 + A4 --> B1 --> C1 --> C2 --> C3 --> C4 -SwarmPlug does **not mutate host behavior**. -These domains are outside the core normalization layer. +``` ---- -## 6. Stability Principle -Once defined, a version: +## Determinism -- Remains version-scoped -- Remains boundary-limited -- Does not absorb new responsibilities +Given: -Evolution occurs by addition, not modification. +- identical snapshot content + +- identical sender identity + +- identical exchange topology + +- identical trigger conditions + ---- +ver0.4 produces deterministic cross-node state distribution. -## 7. Repository Structure -``` -/ver0.1 → Host attachment layer -/ver0.2 → Canonical identity layer -/ver0.3 → Semantic snapshot layer -``` +Received snapshots: -Each directory documents a completed infrastructure layer. +- are treated as external state + +- are not re-emitted as local-origin snapshots + +- do not trigger recursive exchange + -Subsequent versions will be added as independent directories. +This guarantees stability under concurrent multi-node transmission +and prevents message storm amplification. --- -## 8. Foundational Principle +## Exchange Boundary + +ver0.4 defines: -> Infrastructure precedes coordination. -> Normalization precedes orchestration. -> Versioning precedes expansion. +- snapshot as the only exchange object + +- node-to-node delivery semantics + +- producer / receiver role separation + +- single and multi-producer transmission patterns + +- single and multi-receiver dissemination patterns + +- full-mesh concurrent exchange behavior + +- strict separation between local-origin and received state + -SwarmPlug develops by structure, not by feature accumulation. +**Raw host runtime streams are never exchanged.** --- -## License +## Re-Exposure Principle + +SwarmPlug ver0.4 does not construct a distributed system +by directly connecting host runtimes. + +It enforces a two-step mechanism: + +1. **Normalization (ver0.3)** + Host runtime → deterministic semantic snapshot + +2. **Re-Exposure (ver0.4)** + Received snapshot → local ROS-visible interface + + +Therefore: -This repository is licensed under the -**SwarmPlug Documentation License v1.0**. +- no direct subscription to remote ROS-native topics + +- no transparent runtime mirroring across nodes + +- no leakage of host-level internal structure + -This license applies to the architectural documentation and versioned -infrastructure specifications contained in this repository only. +Instead: -Implementation systems and runtime components are not included. +- semantic state is transmitted + +- selected fields are parsed + +- local ROS topics / parameters are rewritten + +**Distributed observability is achieved through semantic rewriting, +not runtime coupling.** --- +## Scope Limitation + +SwarmPlug ver0.4 does not include: + +- Blockchain anchoring + +- Reliable delivery guarantees (ACK / retry) + +- Global coordination or scheduling + +- Task allocation or decision-making + +- Control loops + +- Direct remote ROS topic subscription + +- Full runtime federation + +- Semantic transformation beyond snapshot definition + + +**ver0.4 does not convert exchange into coordination.** +**ver0.4 does not convert re-exposure into control.** -## Contact +--- -If you are evaluating SwarmPlug for research or engineering use, -feel free to reach out at: +## Version Context -📧 **swarmplug@gmail.com** +|Version|Responsibility| +|---|---| +|ver0.1|Host attachment| +|ver0.2|Canonical identity| +|ver0.3|Semantic snapshot| +|ver0.4|Mesh exchange and local re-exposure| --- -**Note:** -This repository documents the architectural structure and version model of SwarmPlug. -It does **not** include proprietary implementation details. +## Principle + +Normalization precedes exchange. +Exchange precedes re-exposure. +Re-exposure preserves local boundaries. + +Transport follows semantics. +Distribution follows determinism. +Visibility follows controlled rewriting. + +**ver0.4 establishes distributed observability +without runtime entanglement.** +--- + +## License +This version specification is part of the SwarmPlug documentation. +Licensed under the **SwarmPlug Documentation License v1.0**. +See the **main LICENSE** file for details.