ruvnet--RuView

frank/ruvnet--RuView

Fork 0

mirror of https://github.com/ruvnet/RuView synced 2026-06-16 11:23:19 +00:00

Author	SHA1	Message	Date
ruv	52db398641	docs(adr-262): RuField↔RuView integration design (Proposed) 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>	2026-06-14 11:46:35 -04:00

Author

SHA1

Message

Date

ruv

52db398641

docs(adr-262): RuField↔RuView integration design (Proposed)

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>

2026-06-14 11:46:35 -04:00

Compare commits

1 Commits

v1767 .. docs/adr-262-rufield-integration

Diff Content Not Available

Compare commits

1 Commits v1767 .. docs/adr-262-rufield-integration

Diff Content Not Available

1 Commits

v1767 .. docs/adr-262-rufield-integration