DEV Community

Cover image for My Independent Open-Source Protocol Paper ("DoSync") Was Accepted at IEEE CCNC 2027
Rodrigo Giuliani
Rodrigo Giuliani

Posted on

My Independent Open-Source Protocol Paper ("DoSync") Was Accepted at IEEE CCNC 2027

Today I received the official notification: my paper, "DoSync: Governing AI-Agent Intents over Heterogeneous IoT Devices", was peer-reviewed and accepted at the Workshop on IoT Interoperability and the Web of Things (IIWOT) at IEEE CCNC 2027[cite: 1].

paper_aceptacion

For an independent developer building open-source tooling outside of an academic lab or corporate R&D budget, getting an architecture through rigorous technical peer review is a huge milestone. Three specialists in IoT and distributed systems audited the design, checked the benchmarks, and validated the core premise: we cannot let non-deterministic LLMs directly trigger physical actuation in the real world.


Why I Built DoSync

As agentic frameworks and protocols like MCP make it trivial to connect LLMs to local networks and smart devices, a dangerous gap has opened up. Language models are probabilistic they hallucinate, misinterpret context, or can be steered via prompt injection. Physical hardware, on the other hand, has irreversible consequences.

An AI agent should be able to express an intent (e.g., "prepare the living room for the night"), but a deterministic layer must govern what actually happens on the wire.


What the Reviewers Validated

The paper introduces DoSync, an open protocol and reference hub designed to sit between high level AI intents and heterogeneous IoT devices. During the review process, three core pillars of the project stood out:

  1. Nine Deterministic Guarantees (G1–G9): Formal rules enforced at runtime covering strict capability matching, hierarchical place scoping, oscillation dampening, tamper-evident hash-chained audit logging, and human-in-the-loop holds for critical actions.
  2. Standards-Native WoT Integration: Rather than inventing a closed ecosystem, DoSync maps directly to W3C Web of Things (WoT) Thing Descriptions (TD 1.1) via an extension vocabulary (dosync:), validated against hundreds of public third-party TDs.
  3. Sub-10 ms Edge Execution: The entire resolution and governance pipeline runs locally on constrained hardware (tested on a Raspberry Pi 5) with under 10 ms latency—zero cloud dependency required.

Keeping It 100% Open Source

Academic publishing often locks validated research behind expensive paywalls and conference fees. Since DoSync was built from day one as a free, community-driven project for everyone, I am keeping the full architecture, specification, and implementation completely open:

  • 📄 Read the Full Paper: Grab the pre-print PDF directly from the DoSync Protocol Repository.
  • 📱 Try DoSync App (Beta): Want to govern your smarthome devices locally using LLMs from your phone—with no accounts, no extra commercial hubs, and zero cost? Check out the DoSync App page or download the latest release from GitHub.
  • 🌐 Protocol Overview & Docs: dosync.dev

Getting peer-reviewed confirmation that an independent, open-source architecture solves a real frontier problem is the best fuel to keep building. If you're working on local AI agents, home automation, or IoT security, feel free to inspect the repo, break things, or open an issue!

Top comments (2)

Collapse
 
mansio profile image
Mikhail • • Edited

Congrats on getting into IEEE CCNC 2027! Taking an independent open-source project through peer review without an academic lab or corporate R&D behind you is no small feat.

What stood out most to me in your design is how it treats safety as a human attention budget. Putting a deterministic layer between probabilistic LLM intents and physical hardware makes total sense, especially when you factor in operator fatigue. If a human-in-the-loop system asks for confirmation too often, people start approving things on autopilot, and the whole safety net falls apart. Keeping those holds rare, specific, and sub-10 ms on local edge hardware is the exact right direction.

Looking forward to seeing how the protocol evolves!

Collapse
 
giulianiregspec profile image
Rodrigo Giuliani •

Thank you very much, Mikhail. I am truly satisfied with what has been achieved. As you rightly point out, it is difficult to work on projects of this nature while simultaneously holding down a full-time job. I am currently working on the distribution of the protocol, and I am genuinely surprised by how difficult it is.