Announcement: ADR-270 Rust vendor RF provider simulator beta
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 94.5k
- Forks
- 12.5k
- Avg merge
- 21h 27m
- Merged PRs (30d)
- 43
Description
RuView and Cognitum.one have published the Rust-centric ADR-270 vendor RF provider beta.
Release: https://github.com/ruvnet/RuView/releases/tag/v0.9.3-vendor-providers-beta.1
PR: https://github.com/ruvnet/RuView/pull/1360
ADR: https://github.com/ruvnet/RuView/blob/main/docs/adr/ADR-270-vendor-rf-sensing-integration-program.md
The program now has capability-safe outcomes for Origin AI, Plume/OpenSync, Mist/Juniper, NETGEAR Insight, Electric Imp, RF Solutions, Luma/OpenWrt, Google Nest, Linksys, and Wifigarden. Eight defined contracts have deterministic JSONL/UDP simulation and strict Rust decoders. Linksys is deliberately Unsupported; Wifigarden is deliberately ContractRequired rather than fabricated.
The release includes Windows server/simulator binaries, eight 100-frame replay sets, checksums, REST/UDP/WebSocket integration, and explicit synthetic provenance. Telemetry and network inventory never masquerade as complex CSI.
Hardware/vendor-cloud validation remains open and every descriptor stays hardware_validated: false until lawful credentials, exact versions, real captures, and repeatable evidence exist. Vendor maintainers and hardware partners are invited to confirm schemas and provide test access.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading docs/adr/ADR-270-vendor-rf-sensing-integration-program.md and reviewing the referenced release and PR. The announcement describes an existing beta but does not identify a documentation change, a specific entry point, or a completion criterion, so the definition of done is currently unclear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100