Skip to content

fix(sensing): fuse only coherent frame cohorts - #1726

Merged
ruvnet merged 1 commit into
mainfrom
codex/governed-fusion-cohort
Aug 27, 2026
Merged

fix(sensing): fuse only coherent frame cohorts#1726
ruvnet merged 1 commit into
mainfrom
codex/governed-fusion-cohort

Conversation

@ruvnet

@ruvnet ruvnet commented Aug 27, 2026

Copy link
Copy Markdown
Owner

Summary

  • Select one timestamp domain for each sensing cycle.
  • Prune active frames to the freshest cohort within the configured hard fusion guard.
  • Preserve single-node processing and engine-error audit accounting.
  • Add regression coverage for mixed ESP32-S3/C6 frame widths, frame rates, and custom guards.

Validation

  • cargo test --workspace --no-default-features
  • cargo build --release -p wifi-densepose-sensing-server --bin sensing-server --no-default-features
  • Local four-node hardware burn-in observation: 607 seconds, 4/4 active nodes, zero governed fusion errors, and 60 witness changes.
  • No firmware changes; the existing node firmware was used.

Restricted/demoted output can still occur when the soft privacy guard closes. That is intentional policy behavior rather than a fusion error.

@ruvnet
ruvnet merged commit b742eae into main Aug 27, 2026
29 checks passed
github-actions Bot pushed a commit to rajamohamedml/RuView that referenced this pull request Aug 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant