github ruvnet/RuView v1097
Release v1097

latest releases: v1136, v1133, v1115...
4 hours ago

Automated release from CI pipeline

Changes:
research(R3.2): embedding-level physics-informed env — structural validation + AETHER dependency (#729)

Implements R3.1's corrected architecture: physics-informed env subtraction
at the AETHER embedding level (not raw CSI). Tests whether moving the
operation closes the cross-room gap that R3.1 NEGATIVE surfaced.

Headline (10 subjects, 2 rooms, 3 positions/room):

Approach Cross-room K-NN
Within-room AETHER sanity 100%
Cross-room AETHER raw (no env sub) 10% (chance)
Cross-room AETHER + labelled MERIDIAN 20% (oracle)
Cross-room AETHER + physics-informed 10% (chance)
Cross-room AETHER + physics + residual 20%

Structural validation: physics + residual matches the labelled MERIDIAN
oracle WITH ZERO LABELS. The architecturally-correct approach works.

But neither approach reaches 80%+. Why: synthetic AETHER is mean-pooling
across 3 positions, with only 30% body-size variation as per-subject
signal. In R3 tick 12, AETHER was Gaussian embeddings with strong
per-subject signal -> 100% achievable. Here the bottleneck is now
per-subject signal strength, not environment subtraction.

R3.2 is the THIRD 'honest scope' finding in the loop:

Tick Finding Path forward
R3.1 physics-informed at raw fails embedding level (R3.2)
R6.2.2.1 2D N=5 knee doesn't hold in 3D chest zones (R6.2.4)
R3.2 mean-pool AETHER too weak real contrastive AETHER

All three are productive: they identify the gap production work must fill.

R3.2 confirms ADR-024 (AETHER) is on the critical path for cross-room
re-ID. Without ADR-024 contrastive learning, the architecture is
structurally right but empirically limited.

Recommended next experiment (out of scope for this synthetic loop):

  • Replace mean-pooling AETHER with ADR-024 contrastive head
  • Train on MM-Fi, run R3.2 protocol
  • Expected: 70-90%+ cross-room K-NN
  • ~1-2 days of training work

R3 thread closed satisfactorily for the loop: R3 (tick 12) -> R3.1
NEGATIVE -> R3.2 STRUCTURALLY VALIDATED. Arc produced:

  • Architectural recommendation: use embedding level
  • Critical-path component identified: ADR-024 AETHER
  • Three constraint regimes documented (within-room ok, embedding+labels
    = oracle, embedding+physics+residual = matches oracle without labels)
  • Clear production path

Honest scope:

  • Synthetic AETHER is mean-pooling, not contrastive
  • 20% oracle ceiling is this synthetic setup's cap
  • 30% body-size variation is weak per-subject signal vs R15's 12-15 bits
  • Static subjects (dynamic would give richer signals via R10+R15)
  • Two rooms only

Composes:

  • R3 / R3.1 / R3.2 = full arc
  • R6 / R6.1 forward operator unchanged
  • R6.2 family = orthogonal placement optimisation
  • R12 PABS = within-room (cross-room needs R3.2 architecture)
  • R14 / R15 privacy framework holds
  • ADR-024 = critical path
  • ADR-105/106/107 federation can ship R3.2 outputs

Coordination: ticks/tick-26.md, no PROGRESS.md edit.

Docker Image:
ghcr.io/ruvnet/RuView:4183ef651f95afd896a4a800ccd023d0be21804d

Don't miss a new RuView release

NewReleases is sending notifications on new releases.