fix: harden v1.2 trajectory disposal matching
This commit is contained in:
@@ -77,6 +77,12 @@ Use `阶段 x` only as a workflow stage inside the same `v1.1 优化改造` batc
|
||||
- 轨迹诊断必须记录 active、emitted、rejected、expired,方便现场调参。
|
||||
- 后续 YOLO 模型只作为 evidence 增强输入,不能修改 `BatchEngine` 的业务语义。
|
||||
|
||||
## Final Review Findings
|
||||
|
||||
- Evidence and generic trash fallback must share the same count budget: one matched `disposal_evidence` consumes one observed trash deposit signal when `trash_deposit_count` is also present, but extra trash deposits must still fall back to pending batches.
|
||||
- A trajectory candidate must not append source-zone-external motion before source motion has been seen. If outside motion appears first and is later followed by source noise, the candidate is rejected with `motion_started_outside_source` instead of producing evidence.
|
||||
- Runtime diagnostics on the deployed host should be checked for schema only, not by printing config, because the remote config may contain RTSP credentials and calibration.
|
||||
|
||||
## Backend Planning Notes
|
||||
|
||||
- `EngineSettings.zone_ids` should remain config driven; numeric zones are preferred for new configs, but old `r1c1` style IDs should continue loading.
|
||||
|
||||
Reference in New Issue
Block a user