Adopt "WiFi Veil" as the product name across all user-facing surfaces, keeping VEIL (Verifiable Emission-shaping for Identity-Leakage prevention) as the technical codename it's built on. Only prose, titles, descriptions, and the console UI change — no code identifiers, file names, crate/npm `name` fields, or the deterministic proof witness are touched, so `cargo test` and the C-core host test are unaffected. - Crate & research READMEs: title + defining line now "WiFi Veil (codename VEIL — …)". - Cargo.toml / package.json / plugin.json descriptions: "WiFi Veil …". - Console UI (veil-console.html): title, brand, and copy say "WiFi Veil". - Firmware tree (README, per-provider READMEs, BUILD/INTEGRATION/MEASUREMENT): "WiFi Veil protector/core/shield". - Harness manifest: recomputed SHA-256 digests for the four changed packaged files (README, package.json, CLAUDE.md, plugin.json) — all verified consistent. Co-Authored-By: claude-flow <ruv@ruv.net> Claude-Session: https://claude.ai/code/session_01WEXNqzs7UsfNFBcP5yW21p
2.7 KiB
wifi-densepose-privshield-harness
A metaharness (contributor harness) for
wifi-densepose-privshield — 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-densepose-privshield-harness
wifi-densepose-privshield-harness doctor
Or run without installing:
npx wifi-densepose-privshield-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>(afternpm run build) — cost-optimal model routing (@metaharness/router).npm run flywheel:dry— the SYNTHETIC@metaharness/flywheeldemo (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 -p wifi-densepose-privshield.
License
MIT