History

ruv 8eaa92cf21 feat(python): host-side decode for ADR-018 byte 18-19 (ADR-110) Python ESP32BinaryParser was using struct format '<IBBHIIBB2x' — the '2x' skipped bytes 18-19 as reserved. After the Rust-side decoder was extended to surface PPDU type + flags, the Python pipeline (which archive/v1 still uses for testing + the proof verifier) needs the same update so its consumers see the HE metadata too. csi_extractor.py: - HEADER_FMT now '<IBBHIIBBBB' (captures bytes 18-19) - New metadata fields: ppdu_type ('ht_legacy'\|'he_su'\|'he_mu'\|'he_tb'\|'unknown'), ppdu_type_raw, he_capable, bw40, stbc, ldpc, ieee802154_sync_valid, adr018_flags_raw - Class constants PPDU_HT_LEGACY..PPDU_UNKNOWN mirror the firmware test_esp32_binary_parser.py: - build_binary_frame() takes optional ppdu_byte + flags_byte (default 0) - New TestAdr110ByteEncoding class with 5 tests: - Pre-ADR-110 zeros decode as 'ht_legacy' + all-flags-false - HE-SU / HE-MU / HE-TB decode correctly - 0xFF decodes as 'unknown' - All-flags-set round-trip (0x1D) 11/11 parser tests pass (6 existing + 5 new). Backwards compat verified. Pairs with the Rust-side decoder in commit `3959fabf3`. Both pipelines now read the same wire format produced by the C6 firmware's CONFIG_CSI_FRAME_HE_TAGGING path. Ref: ruvnet/RuView#762, draft PR #764 Co-Authored-By: claude-flow <ruv@ruv.net>	2026-05-22 22:46:37 -04:00
..
v1	feat(python): host-side decode for ADR-018 byte 18-19 (ADR-110)	2026-05-22 22:46:37 -04:00
README.md	chore(repo): move v1/ → archive/v1/ + add archive/README.md (#430 )	2026-04-25 23:07:52 -04:00

ruv 8eaa92cf21 feat(python): host-side decode for ADR-018 byte 18-19 (ADR-110)

Python ESP32BinaryParser was using struct format '<IBBHIIBB2x' — the
'2x' skipped bytes 18-19 as reserved. After the Rust-side decoder was
extended to surface PPDU type + flags, the Python pipeline (which
archive/v1 still uses for testing + the proof verifier) needs the same
update so its consumers see the HE metadata too.

csi_extractor.py:
- HEADER_FMT now '<IBBHIIBBBB' (captures bytes 18-19)
- New metadata fields: ppdu_type ('ht_legacy'|'he_su'|'he_mu'|'he_tb'|'unknown'),
  ppdu_type_raw, he_capable, bw40, stbc, ldpc, ieee802154_sync_valid,
  adr018_flags_raw
- Class constants PPDU_HT_LEGACY..PPDU_UNKNOWN mirror the firmware

test_esp32_binary_parser.py:
- build_binary_frame() takes optional ppdu_byte + flags_byte (default 0)
- New TestAdr110ByteEncoding class with 5 tests:
  - Pre-ADR-110 zeros decode as 'ht_legacy' + all-flags-false
  - HE-SU / HE-MU / HE-TB decode correctly
  - 0xFF decodes as 'unknown'
  - All-flags-set round-trip (0x1D)

11/11 parser tests pass (6 existing + 5 new). Backwards compat verified.

Pairs with the Rust-side decoder in commit 3959fabf3. Both pipelines now
read the same wire format produced by the C6 firmware's
CONFIG_CSI_FRAME_HE_TAGGING path.

Ref: ruvnet/RuView#762, draft PR #764

Co-Authored-By: claude-flow <ruv@ruv.net>

2026-05-22 22:46:37 -04:00

v1 feat(python): host-side decode for ADR-018 byte 18-19 (ADR-110) 2026-05-22 22:46:37 -04:00

README.md chore(repo): move v1/ → archive/v1/ + add archive/README.md (#430 ) 2026-04-25 23:07:52 -04:00

README.md

Archive

Frozen, no-longer-active components of RuView preserved for historical reference, reproducibility, and load-bearing legacy paths the active codebase still depends on.

What lives here

Path	What it is	Why it's archived	Still load-bearing?
`v1/`	Original Python implementation of RuView (CSI processing, hardware adapters, services, FastAPI)	Superseded by the Rust workspace at `v2/`; ~810× slower in benchmarks. Kept rather than deleted because the deterministic proof bundle (`v1/data/proof/`) is part of the pre-merge witness verification process per ADR-011 / ADR-028.	Yes — for the proof bundle only. Active code lives in `v2/`.

What "archived" means

Do not add new features here. New work goes in v2/.
Do not refactor or modernize the archived code beyond what is strictly necessary to keep the load-bearing paths working. The Python proof bundle is intentionally frozen so that its SHA-256 reproducibility holds across releases (per ADR-028's witness verification requirement).
Bug fixes inside archived code are allowed when the bug affects a still-load-bearing path (currently: only the Python proof). All other "bugs" in archived code are out-of-scope — they are part of the historical record and any fix would unnecessarily churn the witness hashes.
CI continues to verify the load-bearing paths. .github/workflows/verify-pipeline.yml runs the Python proof on every push and PR; if you change anything inside archive/v1/src/ or archive/v1/data/proof/, expect the determinism check to flag it.

Quick reference for the load-bearing paths

# Run the deterministic Python proof (must print VERDICT: PASS)
python archive/v1/data/proof/verify.py

# Regenerate the expected hash (only if numpy/scipy version legitimately changed)
python archive/v1/data/proof/verify.py --generate-hash

# Run the full Python test suite (legacy, still maintained)
cd archive/v1&& python -m pytest tests/ -x -q

Why we keep `v1/` rather than delete it

Trust kill-switch. The proof at v1/data/proof/verify.py feeds a known reference signal through the full pipeline and hashes the output. If the active code's behavior drifts, the hash changes and CI fails. This is what stops accidental regression in the science layer of the codebase.
Witness verification. ADR-028's witness-bundle process bundles the proof, the rust workspace test results, and firmware hashes into a tarball recipients can self-verify. Removing v1 would break that chain.
Historical reference. ADR-011 documents the "no mocks in production code" decision; the original violations and their fixes live in this Python codebase. The ADRs reference these paths.

If the time comes to retire the proof bundle (e.g., a Rust port of the proof exists and the Python version is no longer canonical), the right move is a single follow-up that simultaneously: ports the witness-bundle process, updates verify-pipeline.yml, and either deletes archive/v1/ or moves it to a separate read-only repository. That decision belongs in its own ADR.

README.md Unescape Escape