docs(ADR-262): RuField↔RuView integration design — bridge crate, live adapter, privacy/provenance reconciliation (Proposed)#1069
Merged
Conversation
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: claude-flow <ruv@ruv.net>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
ADR-262 (Proposed) — researched design for integrating RuField MFS into RuView, grounded in real file:line evidence on both sides. Answers "how do we wire RuField into RuView better?" Docs-only (no code change); the implementation lands in phases per the plan.
Recommended architecture
wifi-densepose-rufieldbridge crate (anti-corruption layer) path-deps on thevendor/rufieldsubmodule — thevendor/rvcsipattern, since rufield crates are unpublished. RuField stays standalone; the bridge is the only coupling point.SensingServerAdapter(not the file-basedCsiReplayAdapter) on the hot path — taps the realSensingUpdateemit site joined withTrustedOutputtrust state, emits one signedFieldEventper cycle.CsiReplayAdapterstays for offline.csi.jsonlreplay.wifi_csiFieldEvent; rufield-fusion sits above as the cross-modality graph. They compose, not conflict.cog-ha-matterSHA-256+Ed25519 chain (already RuField's exact crypto) for theProvenanceReceipt; keep BLAKE3 engine witness as an internal hashed field.The crux — privacy/provenance reconciliation
One canonical model + a documented lossy mapping (not two parallel schemes). RuView's
effective_class(live governed cycle) is source-of-truth → mapped to RuField P0–P5 at egress.Honest finding that drives the design: RuView has two privacy enums (
PrivacyClass×4,PrivacyMode×5) and three witness mechanisms across two hash algorithms (BLAKE3 engine-cycle live, BLAKE3 BFLD dormant, SHA-256+Ed25519 cog-ha-matter standalone) — none mapping 1:1 onto P0–P5. The trap (with a dedicated test gate): RuView'sDerivedprivacy byte is1, numerically belowAnonymous=2, yet it carries identity embeddings — so a naive byte-mapping would leak identity as low-privacy P1. The bridge must map by information content (Derived → P4/P5), never by byte value.Phased plan (each independently shippable + gated)
SensingServerAdapter→ signedFieldEvents (gate: round-trip +is_fusable+ingestaccept)Derived→P4/P5 never P1, privacy monotonicity, ed25519 verify)/ws/field+ add an ingest route torufield-viewerrvcsi/mmWave) → cross-modal fusion above ruvsenseHonest scope
This is plumbing architecture, not accuracy. RuField v0.1 is synthetic by its own admission; RuView's only real-CSI rufield path is unlabeled replay + single-link
field_localizethat can't resolve true room position. The ADR claims only architecture (testable by round-trip / monotonicity / signature gates) and explicitly disclaims accuracy.Status: Proposed — opens the integration; implementation is the phased follow-up.
🤖 Generated with claude-flow