Архитектура: централизовать inventory pivot flags и carryover target intent в continuity policy
This commit is contained in:
+5
@@ -461,6 +461,11 @@ Still open after the accepted phase12 replay:
|
||||
- the shared retarget contract is now explicitly UTF-8-safe, which matters because a broken regex encoding in the first extraction attempt silently collapsed short phrases like `покажи договоры по СВК` back into stale previous-intent carryover;
|
||||
- `assistantTransitionPolicy` no longer keeps a second local `resolveDisplayedEntityRetargetIntent(...)` owner beside the shared continuity helper, which reduces another chance that future follow-up fixes land in dead code or diverge between route retarget and anchor hydration;
|
||||
- targeted `assistantContinuityPolicy` and `assistantTransitionPolicy` suites are green after the move, and a fresh live rerun of `address_truth_harness_phase11_manual_followup_meta_quality` on `2026-04-19` is accepted `10/10`, including the short displayed-counterparty retarget step.
|
||||
- the next continuity-authority pass now centralizes one more dense decision block from the transition hot path:
|
||||
- continuity now owns `resolveInventoryFollowupPivotFlags(...)`, so inventory root pivots and explicit same-date pivots are no longer computed by a local boolean cascade inside `assistantTransitionPolicy`;
|
||||
- continuity now also owns `resolveFollowupTargetIntent(...)`, so `carryover target intent` precedence for purchase-date VAT bridge, selected-object retarget, root-context carryover, same-date pivot, displayed-entity retarget, and plain previous-intent fallback is expressed in one shared helper instead of an inline ternary tower;
|
||||
- this matters because root-pivot semantics and target-intent precedence are among the heaviest remaining orchestration decisions in the follow-up path, and keeping them under one shared continuity layer reduces another chance that future domain expansion reintroduces drift between carryover state and target route selection;
|
||||
- targeted `assistantContinuityPolicy` and `assistantTransitionPolicy` suites are green after the move, and a fresh live rerun of `address_truth_harness_phase12_wider_saved_session_pool` on `2026-04-19` is accepted `20/20`, which is the critical proof that the flagship mixed replay still survives after the decision-block extraction.
|
||||
|
||||
## Next Execution Slice (2026-04-18)
|
||||
|
||||
|
||||
Reference in New Issue
Block a user