docs: define progressive person fusion route
This commit is contained in:
+6
-2
@@ -19,6 +19,7 @@ recall, without hurting addressed responses or yield behavior.
|
||||
|
||||
| Need | Authoritative file |
|
||||
|---|---|
|
||||
| Progressive feature-fusion implementation route | [docs/progressive_feature_fusion_route_2026-09-02.md](docs/progressive_feature_fusion_route_2026-09-02.md) |
|
||||
| Current hypotheses, experiment gates and stopping rules | [`docs/omni_speaker_floor_experiment_plan_2026-08-30.md`](docs/omni_speaker_floor_experiment_plan_2026-08-30.md) |
|
||||
| Novelty boundary and claim restrictions | [`docs/multiparty_egocentric_floor_gap_audit_2026-08-30.md`](docs/multiparty_egocentric_floor_gap_audit_2026-08-30.md) |
|
||||
| Code/data map and current blocker | This file |
|
||||
@@ -60,10 +61,13 @@ semantic event ground truth.
|
||||
2. **P1:** probe aggregate activity and per-person active-speaker grounding;
|
||||
compare correct, wrong-person and time-shifted visual inputs.
|
||||
3. **P2:** re-evaluate `G`, `G+A`, `G+A+pooled-V` under the frozen event protocol.
|
||||
4. **P3:** train an anonymous person-wise causal side branch with matched
|
||||
temporal-capacity controls.
|
||||
4. **P3:** begin the progressive person-fusion route with Frame-set Attention,
|
||||
then add spatial or track-temporal structure only after its controls pass.
|
||||
5. **P4:** attempt person-memory adapter/Thinker LoRA only if P1/P3 pass.
|
||||
|
||||
The detailed architecture, controls and stopping gates for P3 are frozen in
|
||||
[the progressive feature-fusion route](docs/progressive_feature_fusion_route_2026-09-02.md).
|
||||
|
||||
## Stable data contracts
|
||||
|
||||
### Time and labels
|
||||
|
||||
Reference in New Issue
Block a user