ADR-022: Device Discovery, Bindings & Multi-Protocol Routing — Tracking

[amiable-dev]

ADR-022: Device Discovery, Bindings & Multi-Protocol Routing

Status: Draft | Whitepaper: conductor-bindings-whitepaper.md | ADR: ADR-022-device-discovery-bindings-multi-protocol-routing.md

Overview

ADR-022 extends ADR-021 (I/O Device Qualification, 90% implemented) with:

• Three-layer model: Discovery → Bindings → Mapping Rules
• Multi-protocol binding generalisation (MIDI, HID, OSC, ArtNet)
• 8 new MCP tools for binding CRUD and discovery
• LLM Canvas and Knowledge Layer integration
• Event fingerprinting for bridge device detection

Implementation Phases

• Phase 1 — Foundation (8-12h): Terminology, [[bindings]] alias, conductor_list_discovered_ports, skill rewrites
• Phase 2 — Discovery UI (10-14h): Connections view, BindingPills, Unbound Sources group
• Phase 3 — Binding CRUD (8-12h): create/update/delete/health MCP tools, Events-to-Binding bridge
• Phase 4 — Multi-Protocol (6-10h): Protocol enum, protocol badges, channel scope
• Phase 5 — Device Intelligence (10-14h): SysEx probing, USB identity, event fingerprinting
• Phase 6 — LLM Integration (8-12h): Canvas artifacts, Knowledge Layer content

Total estimated effort: 50-74h across 6 phases

Related ADRs

• Extends: ADR-021 (ADR-021: Input/Output Device Qualification — Tracking #676)
• Amends: ADR-013 (ADR-013: LLM Canvas — Artifact Projection — Implementation Tracker #627), ADR-017 (ADR-017: Unified Mapping Experience — Implementation Tracker #618), ADR-018 (ADR-018: Knowledge Layer & Retrieval Architecture — Tracking Issue #655), ADR-019 (ADR-019: Unified Workspace Filtering & Aggregate Metrics — Tracking Issue #645), ADR-020 (ADR-020: V3 Structural Rendering Migration — Tracking #667)

Reference Documents

• ADR-022-device-discovery-bindings-multi-protocol-routing.md
• ADR-022-amendments-to-existing-adrs.md
• ADR-022-implementation-sequence.md
• conductor-bindings-whitepaper.md
• whitepaper-binding-mockups.html