v1767
KlingAIResearch/LivePortraitv1767Jun 14, 2026by github-actions[bot]
AI Summary
Documents the architectural integration design for RuField and RuView, focusing on privacy model consistency and cross-modal fusion architecture.
Key Highlights
- Research document for RuField↔RuView integration design (ADR-262).
- Defines vertical fusion composition between ruvsense and rufield.
- Identifies privacy mapping challenge: Derived byte value vs. information content.
Full Release Notes
Automated release from CI pipeline **Changes:** docs(adr-262): RuField↔RuView integration design (Proposed) (#1069) Researched integration ADR: thin wifi-densepose-rufield bridge crate (rvcsi pattern), live SensingServerAdapter emitting signed FieldEvents, vertical fusion composition (ruvsense within-WiFi → rufield cross-modal), and ONE canonical privacy/provenance model (RuView effective_class → RuField P0-P5 at egress; reuse cog-ha-matter SHA-256+Ed25519 receipt). Key finding: RuView has 2 privacy enums + 3 witness mechanisms; the Derived(byte=1)<Anonymous(byte=2)-but-carries-identity trap means the bridge must map by information content, not byte value. Plumbing architecture, not accuracy (real-CSI is unlabeled replay today). Co-authored-by: ruv <ruvnet@gmail.com> **Docker Image:** `ghcr.io/ruvnet/RuView:faca0530defc1599ae0be96308046740d466f509`