v1767

ruvnet/RuViewv1767Jun 14, 2026by github-actions[bot]

AI Summary

Documents the integration design for RuField↔RuView in ADR-262, defining the architecture and privacy mapping strategy.

Key Highlights

Documented the integration design for the wifi-densepose-rufield bridge crate.
Defined the canonical privacy/provenance model mapping RuView effective_class to RuField P0-P5.
Identified the 'Derived byte=1' trap and defined mapping by information content.

New Features

Updated ADR-262 documentation to Proposed status with P1 implementation details.
Updated CI configuration to support recursive submodules.

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`