Legacy Python Implementation (v1)
Relevant source files
The following files were used as context for generating this wiki page:
The Legacy Python Implementation (v1) represents the original reference pipeline for the RuView WiFi sensing system. Although the project now utilizes a Rust-based workspace in v2 for production, the archive/v1/ directory remains a load-bearing component of the repository. It serves as the primary source for the system's deterministic proof of reality, ensuring that behavioral drifts in newer implementations are detected during verification.
Sources: archive/README.md:4-10, AGENTS.md:12
This implementation includes the original CSI processing logic, hardware adapters, and FastAPI-based services. It is intentionally frozen to maintain SHA-256 reproducibility for the Witness Verification process required by ADR-028.
Sources: archive/README.md:12-18, CLAUDE.md:8
Architecture and Components
The v1 implementation follows a sequential pipeline to translate radio frequency perturbations into human pose data. It consists of hardware adapters that ingest Channel State Information (CSI), signal processing modules, and a neural network inference layer.
Core Processing Pipeline
The pipeline processes raw CSI data through the following stages:
- Ingestion: Hardware adapters collect CSI packets from WiFi routers.
- Signal Processing: The system applies filters to the raw amplitude and phase data.
- Inference: The processed signal passes through a neural network to estimate human poses.
- API Service: A FastAPI implementation exposes the sensing data to external clients.
Sources: archive/README.md:10-15, harness/ruview/src/guidance.js:46-52
The diagram shows the top-down flow of data from physical radio hardware to the end-user interface in the v1 implementation.
Sources: archive/README.md:10-15, harness/ruview/src/guidance.js:46-52
Deterministic Proof (Trust Kill Switch)
The v1 implementation houses the "Trust Kill Switch," a deterministic proof located at archive/v1/data/proof/verify.py. This utility validates the science layer by feeding a reference CSI signal through the production pipeline and hashing the output. If any changes in the project cause the behavioral output to drift, the SHA-256 hash changes, and the verification fails.
Sources: archive/README.md:37-42, plugins/ruview/skills/ruview-verify/SKILL.md:15-18
Verification Workflow
The verification suite utilizes synthetic data to ensure cross-platform consistency.
| Component | Description | Default/Seed |
|---|---|---|
verify.py | Main execution script for the proof | N/A |
expected_features.sha256 | The target hash for comparison | N/A |
sample_csi_data.json | 1,000 synthetic frames used for testing | seed=42 |
This sequence illustrates how the verify.py script acts as a gatekeeper for the scientific integrity of the sensing pipeline.
Sources: archive/README.md:37-45, plugins/ruview/skills/ruview-verify/SKILL.md:15-28
Maintenance and Legacy Support
Code within archive/v1/ is under a strict maintenance policy to prevent churn in witness hashes.
- No New Features: All active development occurs in the
v2/Rust workspace. - Limited Refactoring: Modifying archived code is permitted only to maintain existing load-bearing paths.
- Bug Fixes: Fixes are only authorized if a bug directly impacts the deterministic proof.
- Performance: The Python implementation is benchmarked at approximately 810x slower than the v2 Rust implementation.
Sources: archive/README.md:20-30, archive/README.md:13
Summary
The Legacy Python Implementation (v1) remains critical for RuView's trust model. It provides a frozen, verifiable baseline for the CSI processing logic. By maintaining this implementation, the project ensures that its "Trust Kill Switch" can detect regressions in the science layer across different releases and hardware architectures.
Sources: archive/README.md:44-50, harness/ruview/src/guidance.js:154-165