Архитектура: централизовать organization carryover precedence в continuity policy и transition glue

This commit is contained in:
2026-04-19 10:23:23 +03:00
parent ca71335499
commit 0a423288b9
6 changed files with 89 additions and 36 deletions
@@ -434,6 +434,12 @@ Still open after the accepted phase12 replay:
- this matters because navigation date scope and continuity temporal scope are now merged through one owner before transition decides pivots, instead of being backfilled ad hoc inside the hot path;
- targeted `assistantContinuityPolicy` and `assistantTransitionPolicy` suites are green after the move, with direct helper coverage for navigation-first temporal precedence and for non-applicable intent families staying untouched;
- a fresh live rerun of `address_truth_harness_phase12_wider_saved_session_pool` on `2026-04-19` stayed semantically stable and again failed only on the already-known date-sensitive `today` expectations, not on the new shared temporal carryover authority.
- the next continuity-authority pass now centralizes organization carryover precedence for follow-up filters:
- transition no longer owns a local cascade of `historical organization -> shared authority -> continuity snapshot -> navigation organization -> clarification selection`;
- shared continuity now owns that merge through `applyOrganizationCarryoverFilters(...)`, so organization hydration in follow-up filters has a single explicit precedence contract;
- this matters because `previous_filters.organization` is now aligned with the same continuity authority story that already drives route, living-chat, and data-scope, instead of keeping one more hot-path-only merge order inside transition glue;
- targeted `assistantContinuityPolicy` and `assistantTransitionPolicy` suites are green after the move, with direct helper coverage for organization precedence and for preserving an already grounded organization value;
- a fresh live rerun of `address_truth_harness_phase12_wider_saved_session_pool` on `2026-04-19` remained semantically stable and again failed only on the already-known date-sensitive `today` expectations, not on the new shared organization carryover authority.
## Next Execution Slice (2026-04-18)