dosync 0.4.1__py3-none-any.whl

dosync/validation.py

@@ -0,0 +1,98 @@
+"""
+DoSync — Parameter Schema Validation
+====================================
+Validates actuator parameter schemas (and, optionally, incoming action params)
+against JSON Schema draft 2020-12.
+
+Two distinct validations, per the design panel:
+
+1. MANIFEST validation (integrity of the standard): when a device registers, is
+   each actuator's `params_schema` itself a well-formed JSON Schema? This protects
+   the standard — a manifest claiming JSON Schema must actually be valid JSON Schema.
+
+2. PARAMS validation (execution policy, optional): when an action is about to run,
+   do the supplied params satisfy the actuator's schema? This is a per-request
+   policy — it can be disabled on the emergency path where latency matters.
+
+Graceful degradation (panel condition): the `jsonschema` library is an OPTIONAL
+dependency. If it is not installed, the hub still runs — validation is skipped with
+a visible warning, never a hard failure. The dumb device never needs this library;
+validation is the hub's responsibility.
+
+The protocol commits to JSON Schema draft 2020-12 in the spec. The library is an
+implementation choice of this reference implementation, not part of the standard.
+"""
+
+from __future__ import annotations
+import logging
+
+log = logging.getLogger("dosync.validation")
+
+try:
+    from jsonschema import Draft202012Validator
+    from jsonschema.exceptions import SchemaError, ValidationError
+    _JSONSCHEMA_AVAILABLE = True
+except Exception:  # pragma: no cover - depends on host
+    Draft202012Validator = None  # type: ignore
+    SchemaError = ValidationError = Exception  # type: ignore
+    _JSONSCHEMA_AVAILABLE = False
+
+
+def jsonschema_available() -> bool:
+    """Whether schema validation is active on this host."""
+    return _JSONSCHEMA_AVAILABLE
+
+
+def is_valid_json_schema(schema: dict) -> tuple[bool, str | None]:
+    """Check that `schema` is itself a well-formed JSON Schema (draft 2020-12).
+
+    An empty dict {} means 'no parameters' and is treated as valid.
+    Returns (ok, error_message). If jsonschema is unavailable, returns (True, None)
+    with a logged warning — degradation, not failure.
+    """
+    if not schema:
+        return True, None
+    if not _JSONSCHEMA_AVAILABLE:
+        log.warning("Schema validation skipped — jsonschema not installed")
+        return True, None
+    try:
+        Draft202012Validator.check_schema(schema)
+        return True, None
+    except SchemaError as e:
+        return False, f"invalid JSON Schema: {e.message}"
+
+
+def validate_manifest_schemas(manifest) -> list[str]:
+    """Validate every actuator's params_schema in a manifest.
+
+    Returns a list of human-readable problems (empty list = all valid). Used at
+    device registration to protect the integrity of the standard.
+    """
+    problems: list[str] = []
+    for actuator in getattr(manifest, "actuators", []):
+        schema = getattr(actuator, "params_schema", None) or {}
+        ok, err = is_valid_json_schema(schema)
+        if not ok:
+            problems.append(f"actuator '{actuator.type}': {err}")
+    return problems
+
+
+def validate_params(schema: dict, params: dict) -> tuple[bool, str | None]:
+    """Validate action params against an actuator's JSON Schema.
+
+    Returns (ok, error_message). Empty schema accepts anything. If jsonschema is
+    unavailable, returns (True, None) — degradation, not failure. This is the
+    OPTIONAL per-request validation; callers may skip it on the emergency path.
+    """
+    if not schema:
+        return True, None
+    if not _JSONSCHEMA_AVAILABLE:
+        return True, None
+    try:
+        Draft202012Validator(schema).validate(params or {})
+        return True, None
+    except ValidationError as e:
+        return False, f"parameter validation failed: {e.message}"
+    except SchemaError as e:
+        # The schema itself is broken — report distinctly from a params problem.
+        return False, f"actuator schema is invalid: {e.message}"

dosync-0.4.1.dist-info/METADATA

@@ -0,0 +1,372 @@
+Metadata-Version: 2.4
+Name: dosync
+Version: 0.4.1
+Summary: The semantic layer between AI agents and physical devices
+Author-email: Rodrigo Giuliani <rgiuliani@dosync.dev>
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://dosync.dev
+Project-URL: Repository, https://github.com/giulianireg-spec/dosync-protocol
+Project-URL: Specification, https://github.com/giulianireg-spec/dosync-protocol/blob/main/spec/DoSync-SPEC-v0.1.md
+Project-URL: Issues, https://github.com/giulianireg-spec/dosync-protocol/issues
+Keywords: iot,ai-agents,protocol,semantic,orchestration,audit,governance,mcp,home-automation,robotics
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: System Administrators
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Home Automation
+Classifier: Topic :: System :: Distributed Computing
+Classifier: Topic :: Software Development :: Libraries :: Application Frameworks
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: fastapi<1.0,>=0.115.0
+Requires-Dist: uvicorn<1.0,>=0.23.0
+Requires-Dist: pydantic<3.0,>=2.7.0
+Requires-Dist: jsonschema<5.0,>=4.18
+Provides-Extra: wiz
+Requires-Dist: pywizlight>=0.5.0; extra == "wiz"
+Provides-Extra: mqtt
+Requires-Dist: paho-mqtt>=2.0.0; extra == "mqtt"
+Provides-Extra: ha
+Requires-Dist: aiohttp>=3.8.0; extra == "ha"
+Provides-Extra: ble
+Requires-Dist: bleak>=0.21; extra == "ble"
+Provides-Extra: sms
+Requires-Dist: twilio>=8.0.0; extra == "sms"
+Provides-Extra: mavlink
+Requires-Dist: pymavlink>=2.4.0; extra == "mavlink"
+Provides-Extra: mcp
+Requires-Dist: mcp>=1.0.0; extra == "mcp"
+Provides-Extra: all
+Requires-Dist: pywizlight>=0.5.0; extra == "all"
+Requires-Dist: paho-mqtt>=2.0.0; extra == "all"
+Requires-Dist: aiohttp>=3.8.0; extra == "all"
+Requires-Dist: bleak>=0.21; extra == "all"
+Requires-Dist: twilio>=8.0.0; extra == "all"
+Requires-Dist: pymavlink>=2.4.0; extra == "all"
+Requires-Dist: mcp>=1.0.0; extra == "all"
+Provides-Extra: dev
+Requires-Dist: pytest>=7.4; extra == "dev"
+Requires-Dist: pytest-asyncio>=0.23; extra == "dev"
+Requires-Dist: httpx>=0.27; extra == "dev"
+Dynamic: license-file
+
+# DoSync Protocol
+
+> The semantic layer between AI agents and physical devices.
+
+[![License](https://img.shields.io/badge/license-Apache%202.0-blue.svg)](LICENSE)
+[![Protocol](https://img.shields.io/badge/protocol-v0.4-green.svg)](spec/DoSync-SPEC-v0.1.md)
+[![PyPI](https://img.shields.io/pypi/v/dosync.svg)](https://pypi.org/project/dosync/)
+[![Python](https://img.shields.io/pypi/pyversions/dosync.svg)](https://pypi.org/project/dosync/)
+[![CI](https://github.com/giulianireg-spec/dosync-protocol/actions/workflows/ci.yml/badge.svg)](https://github.com/giulianireg-spec/dosync-protocol/actions/workflows/ci.yml)
+[![Certification](https://img.shields.io/badge/certification-Conformance%2052%2F52-orange.svg)](dosync/certify.py)
+[![MCP](https://img.shields.io/badge/MCP-compatible-purple.svg)](dosync/mcp_server.py)
+
+---
+
+## The problem
+
+Today's IoT protocols speak the language of commands. AI speaks the language of goals.
+
+```python
+# Existing protocols
+lock.unlock()
+light.set_brightness(100)
+thermostat.set_temperature(21)
+
+# What an AI actually expresses
+"there is an emergency at home"
+"nobody is home — save energy"
+"good morning"
+```
+
+Someone has to translate. Today, that translation is custom code written per-device, per-platform, per-scenario. It breaks when you add a new device. It completely fails in emergencies where milliseconds matter.
+
+**DoSync is the bridge.**
+
+---
+
+## What it does
+
+DoSync is an open protocol (Apache 2.0) that lets AI systems interact with physical devices using **semantic intent** — expressing *what they want to achieve*, not *how to achieve it*.
+
+When the hub receives `"ensure_safety / emergency"`, every registered device figures out its own role automatically based on its declared capabilities — no hardcoded rules, no manual configuration.
+
+---
+
+## Scope and safety boundaries
+
+DoSync coordinates **non-safety-critical systems** — lighting, access, climate, notifications, logging — and produces a tamper-evident record of every action. It is infrastructure for coordination and auditability, not a certified safety system.
+
+DoSync is **not** certified to IEC 61508 / IEC 62304 / ISO 13849 and must not be the sole or primary mechanism for:
+
+- Primary control of medical devices or life-support systems
+- Fire suppression, gas detection, or emergency shutdown of SIL-rated machinery
+- Any function where a failure could cause injury or loss of life
+
+In regulated or industrial environments, DoSync **complements** the certified safety systems already in place — coordinating the peripherals around them and recording what happened — but never replaces them. The certified safety system remains in charge of safety.
+
+See [Protocol Specification §12.3](spec/DoSync-SPEC-v0.1.md) for the full operational boundaries.
+
+---
+
+## Is DoSync for you?
+
+DoSync earns its place in specific situations — and honestly gets in the way in others. A quick filter:
+
+**It probably fits if you:**
+- Are building an **AI agent that acts on physical devices** and need an auditable record of what it did, when, and why.
+- Coordinate **heterogeneous devices** (different brands / transports) and want one semantic layer — express a goal, devices resolve it — with a tamper-evident audit trail.
+- Work in **robotics or physical automation** and want a policy + safety layer (emergency preemption, confirmation policies) *between* the AI and the actuators.
+- Keep hand-writing per-device command sequences and wish you could just say *"secure the space."*
+
+**It's probably not for you if you:**
+- Want home automation (schedules, motion → light). [Home Assistant](https://www.home-assistant.io/) and its automations — and its MCP server — already do that better; DoSync would be overhead.
+- Have a single device or one brand's ecosystem — you don't need a coordination layer.
+- Don't need auditability or a policy layer.
+
+**If the first list is you:** the fastest way in is the **[20-minute device tutorial](TUTORIAL.md)** — build a device that senses, expresses a goal, and acts, with the full audit trail. Or open an [issue](https://github.com/giulianireg-spec/dosync-protocol/issues) describing what you're trying to coordinate and we'll tell you honestly whether DoSync fits.
+
+---
+
+## Demo
+
+[![DoSync Demo](https://img.shields.io/badge/▶_Watch_Demo-YouTube-red?style=for-the-badge)](https://youtu.be/2czAqoIrd08)
+
+**What you'll see:** Claude AI triggers a physical emergency protocol in real time — 10 Philips WiZ bulbs at full brightness, SMS notification sent, audit log updated. No commands. No rules. No cloud.
+
+---
+
+## How it works
+
+```
+User / AI says:  "there is an emergency at home"
+                          │
+                    DoSync Hub v0.3.0
+                          │
+          ┌───────────────┼───────────────┐
+          ▼               ▼               ▼
+   💡 All lights      📱 SMS sent     🚨 Alarm
+   at maximum       to family        activated
+   (10 WiZ bulbs)   immediately
+          │               │               │
+          └───────────────┴───────────────┘
+                          │
+                  Audit log updated
+              (SHA-256 tamper-evident)
+```
+
+The **Capability-based Resolver** matches the intent against every device's **Capability Manifest** — what it can sense, what it can do, whether it's emergency-capable. No rules to write. Add a new device and it participates automatically.
+
+Benchmark (Raspberry Pi 5, Python 3.11.2):
+
+| Devices | Mean | p99 | Within 500ms limit |
+|---|---|---|---|
+| 38 (production) | 0.076ms | 0.097ms | ✓ |
+| 1000 | 1.336ms | 5.690ms | ✓ |
+| 5000 | 9.163ms | 24.541ms | ✓ (20× margin) |
+
+---
+
+## Protocol architecture
+
+| Layer | Name | Role |
+|---|---|---|
+| 5 | **Intent** | AI expresses semantic goals |
+| 4 | **Semantic** | Resolver maps intent → device actions |
+| 3 | **Registry** | Devices self-declare capabilities on join |
+| 2 | **Secure channel** | mTLS, local PKI — no internet required |
+| 1 | **Transport (HAL)** | Reference: WiFi/HTTP-WS · MQTT. Via bridge: Zigbee · Z-Wave · Thread · Matter (Home Assistant). Native BLE/radio bindings: roadmap |
+
+---
+
+## Quick start
+
+### Install and run — five minutes, no hardware
+
+```bash
+pip install dosync
+dosync-hub
+```
+
+That is a working hub on `http://127.0.0.1:47200`. It starts with a simulated
+executor, so you can drive the whole protocol — register devices, fire intents,
+read the audit chain — before you own a single smart device.
+
+Register something and give it a goal:
+
+```bash
+# 1. A device declares what it CAN DO (not what commands it takes)
+curl -X POST http://127.0.0.1:47200/v1/devices/register \
+  -H 'Content-Type: application/json' -d '{
+    "device_id": "siren-hall", "device_name": "Hall Siren",
+    "manufacturer": "acme", "model": "S1", "firmware": "1.0",
+    "category": "actuator", "tags": ["alarm", "emergency"],
+    "emergency_capable": true, "cert_tier": "basic",
+    "sensors": [], "actuators": [{"id": "alarm", "type": "alarm",
+                                  "description": "audible alarm"}]}'
+
+# 2. An AI expresses a GOAL — not a command, and it names no device
+curl -X POST http://127.0.0.1:47200/v1/intent/async \
+  -H 'Content-Type: application/json' \
+  -d '{"intent": "ensure_safety", "urgency": "emergency", "context": {}}'
+
+# 3. Ask WHY those devices were chosen
+curl http://127.0.0.1:47200/v1/intents/ensure_safety/explain
+
+# 4. Read the tamper-evident record of what happened
+curl http://127.0.0.1:47200/v1/audit?limit=10
+```
+
+Step 3 is the one worth pausing on: the hub tells you which devices it
+evaluated, which it included, and the score breakdown behind each decision.
+Step 4 is the other: every action leaves a SHA-256-chained entry, so what the
+system did is provable after the fact rather than merely logged.
+
+Install only the adapters you need:
+
+```bash
+pip install 'dosync[wiz]'      # Philips WiZ bulbs
+pip install 'dosync[ha]'       # Home Assistant bridge
+pip install 'dosync[mqtt]'     # MQTT devices
+pip install 'dosync[all]'      # everything
+```
+
+### Docker
+
+```bash
+docker run -p 47200:47200 dosync/hub        # published image
+# or, from a clone:
+docker compose up
+```
+
+### From source (development)
+
+```bash
+git clone https://github.com/giulianireg-spec/dosync-protocol
+cd dosync-protocol
+python3 -m venv venv && source venv/bin/activate
+pip install -e '.[dev]'
+pytest                                  # 667 tests
+dosync-hub --reload
+```
+
+---
+
+## What's built today
+
+| Component | Status |
+|---|---|
+| REST API (12+ endpoints) | ✅ |
+| WebSocket real-time events | ✅ |
+| Web dashboard | ✅ |
+| API key authentication + SHA-256 audit log | ✅ |
+| Capability-based resolver | ✅ |
+| Certification CLI — Standard 33/33 · Emergency 44/44 (signed reports) | ✅ |
+| Philips WiZ adapter (UDP local) | ✅ |
+| Home Assistant bridge (10 domains) | ✅ |
+| Native MCP server (Claude, ChatGPT, any LLM) | ✅ |
+| GPIO adapter — Raspberry Pi 5 (PIR + DHT22) | ✅ |
+| SMS notifications via Twilio | ✅ code (requires an active Twilio plan) |
+| MQTT transport adapter (Mosquitto) | ✅ |
+| Shelly adapter (HTTP local, Gen1 + Gen2) | ✅ code, not hardware-tested |
+| Matter adapter (via HA bridge / python-matter-server) | ✅ code, not hardware-tested |
+| External Resolver Protocol (HTTP wire format) | ✅ |
+| SQLite persistence (survives restarts) | ✅ |
+| CI pipeline (GitHub Actions) | ✅ |
+| Multi-hub assisted failover (Phase A — operator-in-the-loop) | ✅ |
+| Long-running operations + telemetry reconciliation (state machine) | ✅ |
+| Drone / MAVLink adapter — full AI→intent→mission loop in ArduPilot SITL | ✅ software (physical flight pending) |
+
+---
+
+## MQTT transport
+
+DoSync supports MQTT as a Layer 1 transport for devices that can't use HTTP. Requires Mosquitto and proper authentication. See [config/mosquitto-secure.conf](config/mosquitto-secure.conf) for secure setup.
+
+```bash
+# Enable MQTT in the hub service
+Environment="DOSYNC_MQTT_BROKER=localhost"
+Environment="DOSYNC_MQTT_USER=dosync-hub"
+Environment="DOSYNC_MQTT_PASSWORD=<password>"
+Environment="DOSYNC_MQTT_SECRET=<registration-secret>"
+```
+
+---
+
+## Certification
+
+Self-certifiable with the CLI:
+
+```bash
+python3 certify.py --host <hub-ip> --port 47200 --tier standard
+# Output: dosync-cert-standard-*.json
+```
+
+| Tier | Tests | What it validates |
+|---|---|---|
+| **Basic** | 10 | Connectivity, auth, device manifest |
+| **Standard** | 33 | Protocol conformance, events, health, version headers |
+| **Emergency** | 44 | Everything in Standard + emergency override, policy engine, audit log integrity |
+
+---
+
+## Implementations
+
+| Language | Location | Author | Certification |
+|---|---|---|---|
+| Python (reference) | `server.py` | this project | Standard 33/33 · Emergency 44/44 ✅ |
+| Node.js (companion) | [giulianireg-spec/dosync-node](https://github.com/giulianireg-spec/dosync-node) | this project | 33/33 Standard ✅ |
+
+The Node.js implementation is a **companion** port that validates the protocol
+is implementable in a second language against the same certification suite —
+both share the same author. A genuinely **independent** implementation
+(different author or organization) is a tracked milestone for v1.0: a protocol
+needs multiple independent implementations to become a standard. See the
+[roadmap](ROADMAP.md).
+
+---
+
+## Works with Home Assistant — a layer on top, not a replacement
+
+Home Assistant already solved the hardest problem: talking to thousands of devices, and since 2025 it ships an MCP server so an AI can control them directly. DoSync doesn't reinvent that — it reads devices from HA through a bridge already in the repo and adds **one thing**: it turns a semantic goal (`ensure_safety`, `away_mode`) into a coordinated, **auditable** set of actions across *any* source (HA, WiZ, GPIO, MQTT, BLE).
+
+The honest version: for everyday automation ("porch light when I get home") you **don't need DoSync** — HA's automations and its MCP cover that completely. DoSync earns its place only when **coordination and traceability matter at once** — e.g. a fall-response that unlocks the door, lights the house, and messages family, with a tamper-evident record of exactly what fired and when. Full reasoning: [Home Assistant Already Talks to Your Devices. So What Would DoSync Add?](https://dev.to/giulianiregspec/home-assistant-already-talks-to-your-devices-so-what-would-dosync-add-1iei)
+
+---
+
+## Beyond the home
+
+Nothing in DoSync assumes a house — the same 5-layer stack coordinates physical systems anywhere an AI needs to act: retail cold-chain, hotels, factory peripherals (alongside certified safety systems, never replacing them).
+
+The proof: we took it to the hardest device, an **autonomous drone**. From a single plain-language sentence, an AI model (Claude Haiku, via DoSync's MCP server) fired an `inspect_area` intent and the drone flew the full mission in ArduPilot SITL — every step confirmed by real telemetry. When the AI guessed coordinates 11,000 km away, the supervisor didn't fake success: it waited for a confirmed arrival, none came, and it aborted with a clear diagnosis. **The AI can be wrong; the protocol doesn't have to be.** [Full build log](https://dev.to/giulianiregspec/i-gave-an-ai-one-sentence-a-drone-flew-the-mission-and-when-the-ai-guessed-wrong-the-system-2h3m) · *(validated in SITL; physical-hardware flight is the next step, not a claim made today.)*
+
+---
+
+## Contributing
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for development workflow, including the CI pipeline that runs on every push.
+
+---
+
+## Specification
+
+- [spec/DoSync-SPEC-v0.1.md](spec/DoSync-SPEC-v0.1.md) — full protocol specification
+- [spec/RESOLVER-SPEC-v0.3.md](spec/RESOLVER-SPEC-v0.3.md) — resolver interface + external resolver protocol
+- [DESIGN-PRINCIPLES.md](DESIGN-PRINCIPLES.md) — architectural decisions and rationale
+- [COMPATIBILITY.md](COMPATIBILITY.md) — backward compatibility guarantees
+
+---
+
+## License
+
+Apache 2.0 — free to implement, free to extend, no royalties.
+
+---
+
+*DoSync Protocol v0.3.0 · © 2026 Rodrigo Giuliani · rgiuliani@dosync.dev*

dosync-0.4.1.dist-info/RECORD

@@ -0,0 +1,46 @@
+dosync/__init__.py,sha256=SMw2W4Y5dqQ3Stubn5O4qcSGXAr4hsbI2Bz6qNz0vqs,839
+dosync/audit_backup.py,sha256=44C45gWI5MrnMkI_ZtOnkU-LdL3ADjRradMq_IBjeKE,7581
+dosync/auth.py,sha256=vZDSKLyOgKJruJCzbe9cLCV5RHL0KTmfwDFK9Cdu-Gw,7404
+dosync/auth_fastapi.py,sha256=xrpNYzGyqJyhgb_4_eoJcafbI9EDm2HDoOJBM9y4hG4,2719
+dosync/cert_signing.py,sha256=6MlGb8hvABBFidgVAwwCavrQpGoaIaOlKRo9ofZ_bT8,4625
+dosync/certify.py,sha256=Plsl5G9Hz_XJOIeE3Gaf7zyoUBq0zUkbkzbv-LB77NQ,50427
+dosync/cli.py,sha256=rYFTV7ZGGo50FYGszNsGXJJxYVmHz7ADct1QvnSJhiw,2840
+dosync/composite_operations.py,sha256=z65zZZTC9KRDaPDTWC3-ztV93Rz-r0FmYXPBahDfnwk,14247
+dosync/db.py,sha256=dKGdbjH45gOeArHqWFAn3a8zTtmna1vWC7KWIHkKuTY,36007
+dosync/device_arbiter.py,sha256=YdTo06lq8AUjzx55fTivZZmrSW0xax2n8pMsICstIws,12553
+dosync/discovery.py,sha256=CTB6ckJLusUWZbI20h-YD3EHUwlVMRyIHy-mFfzPmnw,6885
+dosync/ed25519_pure.py,sha256=LoxGYUbbtDrkdIDK9sLQn3MC313_yC3fB8lYQwh4ARQ,6189
+dosync/executor.py,sha256=URxZeshp0ftF2jhOD5gRszzZ0Ivw0L9r45IgE1eIx9s,4060
+dosync/geo.py,sha256=k9b0exTcfFf766apWtbfRbJro8pRCcUc_Pokb_TnyTI,2827
+dosync/hub.py,sha256=I8Mr_sKEkcTULzWT6zGEN2JB7TAUOOUroy4-3KDFOIw,142321
+dosync/hub_monitor.py,sha256=xsxwsRws36x3UG4F4E25IbHubL8phwaD2p4WXIsEC5M,6345
+dosync/manage.py,sha256=oEDwattBfU68RAL2tqdjZJ3IIDvEuw6ncNt25j0fChc,36058
+dosync/mcp_server.py,sha256=nvO7Fx6_tlrHCtwoOEWRqxMxMSgKMiiqXUq2kXaxjA4,33153
+dosync/metrics.py,sha256=g749tzyF5uMecscGxz9ERrtybmQqYE_rn9OhLf90p7U,10333
+dosync/models.py,sha256=swxnC0nXAU2KNCWfyCHM7BbP3ybToJnY1R-g4vGvXhs,23628
+dosync/operation_guards.py,sha256=noIKu9flKJ56L8mbFPc8MQ4DEb7IQ9OZNT2GeJI2xKQ,9926
+dosync/operation_supervisor.py,sha256=NjHI0l_zsCx6z9W9Nw8uXWXUOu6-1vFbENjpKLzNqQc,10727
+dosync/operations.py,sha256=Oqpqe8469HBAHZG1EFA5gnCA6SmgTUNYfmFJGxXUDak,15976
+dosync/policies.py,sha256=YLPeVQUgN_2fpzXht7IiF8An09fH-IU2dMZfsaQ9feU,47356
+dosync/policy_config.py,sha256=-PYnn26390ixP7O5IAiBEeX6tkezMBo7dPRzg5yTZi0,10565
+dosync/py.typed,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
+dosync/reconciler.py,sha256=rEebPlNqjF_fbKjh8hSGAijCQhWXWSawzmvtA4iplAo,10003
+dosync/route_composer.py,sha256=gqKtwTKPonKX1VUdGfO_uMHVuls5WqecbhwH1Z0-QOk,8934
+dosync/security.py,sha256=kuQme0o0FfJUNpv5Ath9emV9V55bRq-K31fZXy61moQ,22825
+dosync/server.py,sha256=lbSYxlj8sq28QDWj4aCt6RYZfsFhhnZ-h0lN0II40yI,83838
+dosync/validation.py,sha256=CTgomrgP9VWoeitr365h3F1d8znDoUUSZfyIL31LnPU,3940
+dosync/adapters/__init__.py,sha256=RXaAuYZuGxZtJMyWgqUQBWPa7X1zcl_Mbxc9EisBcAY,9809
+dosync/adapters/ble.py,sha256=0vTbuldxDTBTRYvhVkLKiyMo1vgednormqnseAd7bm4,7754
+dosync/adapters/homeassistant.py,sha256=_s0I_VY_fc28LQ6ugDJi6ngpcWoNCMFjOJwheM7uqgo,27843
+dosync/adapters/matter.py,sha256=fli6jLfNE_-8RTLOnVQ-NX3rh3SRjQY7_vJu6Z7BEkQ,12432
+dosync/adapters/mavlink.py,sha256=Z8r33JIlQe2md4fScMJboKPb0wULVrG-v5LFhBs0fPE,62496
+dosync/adapters/mqtt.py,sha256=eQNtTFd2ypwV1tlQ-JLybfZ57y-SV74wpD_PXKe5GL0,17974
+dosync/adapters/notifications.py,sha256=TXQRwg8XeV6Hw3jrqAGZrDOctZNRpsGV_6k_2kcfnE4,5896
+dosync/adapters/shelly.py,sha256=yfIf8wKw-VWDU_P2UxaPFHpqI5mqb6VIZzp632pnsxk,13286
+dosync/adapters/wiz.py,sha256=4s9-CxydsJ-YN47r49CuRpIAEYXQEtSVUBPlU0aObWk,13157
+dosync-0.4.1.dist-info/licenses/LICENSE,sha256=CrztwUlJbww0ayaNDlD7F6Io8aNlvj_epa8K7PQ5HzA,11346
+dosync-0.4.1.dist-info/METADATA,sha256=KW52OblR7lWdvrg7FX5x6g0mFEvFnh3XPwCa2nZT0bw,16666
+dosync-0.4.1.dist-info/WHEEL,sha256=K260EYznzXsJYBQGqmI8VTxEdiZYNvDZwW9cBh9-_MA,91
+dosync-0.4.1.dist-info/entry_points.txt,sha256=abiGvO_Xvos_ggjM2eVX7JCyK32guaOlV10E7ADFBR0,118
+dosync-0.4.1.dist-info/top_level.txt,sha256=Tm-0WJ9qFe_yTHjuE2QGdtGAGuBeY-QbF-Hbn_Mu6XQ,7
+dosync-0.4.1.dist-info/RECORD,,

dosync-0.4.1.dist-info/WHEEL

@@ -0,0 +1,5 @@
+Wheel-Version: 1.0
+Generator: setuptools (83.0.0)
+Root-Is-Purelib: true
+Tag: py3-none-any
+

dosync-0.4.1.dist-info/entry_points.txt

@@ -0,0 +1,4 @@
+[console_scripts]
+dosync-certify = dosync.certify:main
+dosync-hub = dosync.cli:hub
+dosync-manage = dosync.manage:main