mirror of
https://github.com/ruvnet/RuView.git
synced 2026-07-30 03:15:55 +00:00
e6062977c9
Some checks are pending
Continuous Integration / Code Quality & Security (push) Waiting to run
Continuous Integration / Rust Workspace Tests (push) Waiting to run
Continuous Integration / UI JavaScript Tests (push) Waiting to run
Continuous Integration / Tests (push) Waiting to run
Continuous Integration / Tests-1 (push) Waiting to run
Continuous Integration / Tests-2 (push) Waiting to run
Continuous Integration / Performance Tests (push) Blocked by required conditions
Continuous Integration / Docker Build & Test (push) Blocked by required conditions
Continuous Integration / API Documentation (push) Blocked by required conditions
Continuous Integration / Notify (push) Blocked by required conditions
Fix-Marker Regression Guard / Verify fix markers (push) Waiting to run
Security Scanning / Static Application Security Testing (push) Waiting to run
Security Scanning / Dependency Vulnerability Scan (push) Waiting to run
Security Scanning / Container Security Scan (push) Waiting to run
Security Scanning / Infrastructure Security Scan (push) Waiting to run
Security Scanning / Secret Scanning (push) Waiting to run
Security Scanning / License Compliance Scan (push) Waiting to run
Security Scanning / Security Policy Compliance (push) Waiting to run
Security Scanning / Security Report (push) Blocked by required conditions
Closes the two documentation gaps from #1456 (follow-up to #1401): - docs/calibration-guide.md: what calibrate/enroll/train-room actually enforce, grounded in v2/crates/wifi-densepose-calibration and wifi-densepose-cli source (not just ADR-135/151 aspirational prose). Covers the hard 600-frame baseline minimum, per-anchor quality gate thresholds, the unsolved pet/small-motion presence-detection gap, and what the empty-room baseline capture actually needs (steady vs silent). Flags that ADR-135's drift_score/BaselineDrift staleness system is not implemented in code — only bank.rs's baseline_id STALE check is real. - docs/trust-and-engine-errors.md: exact trigger conditions for engine_error_count vs the separate, non-sticky `demoted` privacy-class flag, where both are exposed (/health/ready and /api/v1/status share a handler), the real diagnostic gap (no per-cause breakdown, log line is the closest thing), the WDP_GUARD_INTERVAL_US recovery path for persistent clock-drift demotion, and an honest "no code path found" answer on whether a converted HuggingFace model explains engine errors. Also adds both docs to the README documentation table. No code changes. |
||
|---|---|---|
| .. | ||
| adr | ||
| archtocode-visual-overview | ||
| benchmarks | ||
| ddd | ||
| design | ||
| edge-modules | ||
| huggingface | ||
| integration | ||
| integrations | ||
| prd | ||
| qe-reports | ||
| releases | ||
| research | ||
| security | ||
| tutorials | ||
| ADR-110-BRANCH-STATE.md | ||
| ADR-110-REVIEW-GUIDE.md | ||
| build-guide.md | ||
| calibration-guide.md | ||
| proof-of-capabilities.md | ||
| readme-details.md | ||
| RELEASE-streaming-engine-v0.3.0.md | ||
| security-audit-wasm-edge-vendor.md | ||
| TROUBLESHOOTING.md | ||
| trust-and-engine-errors.md | ||
| user-guide-apple-homepod.md | ||
| user-guide.md | ||
| vendor-rf-providers.md | ||
| wifi-mat-user-guide.md | ||
| WITNESS-LOG-028.md | ||
| WITNESS-LOG-110.md | ||