Files
RuView/wifi-veil/harness/README.md
Claudeandclaude-flow 5114ed183f feat(wifi-veil): add self-contained standalone repository tree
Assemble `wifi-veil/` as an extraction-ready standalone repository for the WiFi
Veil privacy shield, decoupled from the RuView monorepo. The RuView copies under
v2/, harness/, firmware/, and docs/ are left untouched; this is an additive,
self-contained tree that can be split out to its own repo (e.g. ruvnet/wifi-veil).

Optimized for a standalone identity, with all monorepo coupling removed:

- Rust crate at the repo root: renamed `wifi-veil` (lib `wifi_veil`, bin `veil`),
  workspace-metadata inheritance inlined, own `[workspace]` root, release profile.
  Dependency-free and WASM-ready — it builds and tests OFFLINE, unlike the
  monorepo copy (which needs sibling submodules). Code is byte-identical, so the
  deterministic proof witness is unchanged.
- Portable C shield core + per-provider firmware scaffolds (openwifi/openwrt/
  nexmon/esp32) under firmware/; host C-core test passes.
- npm harness renamed `wifi-veil-harness`; its guidance paths/commands repointed
  to the standalone layout; manifest SHA-256 digests regenerated and verified.
- Docs: ADR-288/289/290 and the privacy-shield research bundle; research build
  commands/links normalized to the standalone crate.
- Root scaffolding: product README, dual LICENSE-MIT / LICENSE-APACHE,
  .gitignore, CHANGELOG, CONTRIBUTING, and a GitHub Actions CI workflow
  (Rust test/clippy/fmt + wasm build, C-core host test, harness smoke).

Validated locally: cargo fmt --check, cargo clippy --all-targets -D warnings,
cargo test (43 tests + witness), cargo build --lib --target wasm32-unknown-unknown,
make -C firmware/core test, and `node harness/bin/cli.js guidance` — all green.
No telemetry, build artifacts, or lockfile committed. All defense figures remain
SYNTHETIC / L0; compliant waveform controls only, never jamming.

Co-Authored-By: claude-flow <ruv@ruv.net>
Claude-Session: https://claude.ai/code/session_01WEXNqzs7UsfNFBcP5yW21p
2026-08-09 17:06:48 +00:00

2.6 KiB

wifi-veil-harness

A metaharness (contributor harness) for wifi-veil — WiFi Veil, the compliant-waveform WiFi-sensing privacy shield (ADR-288). Defined by ADR-289.

Advanced Coding — architect → implement → review → test, plus a dependency-free WiFi Veil guidance surface. Modeled on wifi-densepose-sar-harness (ADR-286). Multi-host scaffold with a kernel that resolves native → wasm → js.

Install

npm install -g wifi-veil-harness
wifi-veil-harness doctor

Or run without installing:

npx wifi-veil-harness guidance --topic overview

Commands

Command Deps needed Purpose
init kernel + host Boot the kernel + host adapter
doctor kernel + host Verify the install end-to-end
guidance --topic <t> none Read-only WiFi Veil capability map (source-cited, evidence-labelled)
route <e0..e3> router + npm run build Cost-optimal model routing
flywheel [gens] flywheel + npm run build SYNTHETIC self-improvement demo

guidance topics: overview, threat, countermeasure, compliance, optimization, experiment. It needs no dependencies or build step, so it works offline and in CI before npm install.

What WiFi Veil is

WiFi Veil shapes a node's own beamforming feedback with keyed Givens rotations so a third-party passive sniffer cannot re-identify people, while a keyed receiver sees an essentially unchanged link. Compliant waveform controls only — never jamming. Reference results are SYNTHETIC / evidence level L0 (reproduced by cargo test), never MEASURED until a hardware witness exists. See the crate's ADR-288 and research bundle.

Darwin, router, flywheel

  • npm run evolve / evolve:dry — Darwin Mode self-mutation of the harness config (@metaharness/darwin).
  • npm run route -- <e0> <e1> <e2> <e3> (after npm run build) — cost-optimal model routing (@metaharness/router).
  • npm run flywheel:dry — the SYNTHETIC @metaharness/flywheel demo (propose → evaluate → gate → promote, signed + independently replayable).

See CLAUDE.md and the honesty notes atop src/router.ts / src/flywheel.ts for what is real wiring vs. illustrative/synthetic data.

Scope

The harness is a development aid. It does not run a WiFi Veil radio, does not emit RF, and cannot jam. It does not replace the crate's own gates — the authoritative check for a WiFi Veil change is cargo test.

License

MIT