Repository navigation
DoSync Protocol v0.3.0
What's new in v0.3.0
New components
MQTT transport adapter — Layer 1 HAL via Mosquitto broker. Devices register, send events, and receive commands over MQTT. Authenticated via DOSYNC_MQTT_SECRET. Includes LWT, QoS 1, exponential backoff, and retained message cleanup on device DELETE.
ExternalResolver — HTTP wire protocol (RESOLVER-SPEC v0.3 §5) for language-independent resolver implementations. Auto-fallback to CapabilityMatchingResolver on error. HTTPS support via DOSYNC_RESOLVER_CA_CERT.
Protocol improvements
Severityenum separated fromUrgency— event classification and response priority are now distinct typesbypass_on_emergencyconfigurable per policy —BlockIntentPolicysetsbypass_on_emergency=False; operator blocks are absolute and cannot be overridden by emergency urgencyDeviceActuatorRateLimitPolicy— DB-backed persistence viarate_limit_logtable; rate limit windows survive hub restarts- Enriched
intent_blockedaudit entries withurgency,source,emergency_overridefields; distinctemergency_intent_blocked_by_policytype
Operational
- Hub version bumped to
0.3.0 - Heartbeat endpoint exposes MQTT transport status (
transports.mqtt.*) purge_rate_limit_events()on startup — prevents unbounded DB growthconfig/mosquitto-secure.conf— secure Mosquitto configuration example in repo- Systemd secrets file enforced
chmod 600
Certification
| Tier | Tests | Status |
|---|---|---|
| Basic | 10/10 | ✅ |
| Standard | 32/32 | ✅ (was 22) |
| Emergency | 35/35 | ✅ (was 32) |
Independent implementation
dosync-node — Node.js implementation, Standard 32/32, own CI, own repo.
CI/CD
GitHub Actions workflow on every push and PR — 6 steps (syntax, imports, Severity regression, resolver scoring, hub startup, policy engine), ~41s.
Full specification: spec/DOSYNC-SPEC-v0.1.md
Resolver spec: spec/RESOLVER-SPEC-v0.3.md