SILVER/NODEDC_1C
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Архитектура: ввести answer-inspection follow-up contract и закрыть phase15 replay

Browse Source
This commit is contained in:
dctouch
2026-04-18 23:04:37 +03:00
parent c605fae3a3
commit 1d48f01841
16 changed files with 575 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/ARCH/11 - architecture_turnaround/11 - continuity_stabilization_plan_2026-04-17.md
+15
View File
@@ -376,6 +376,21 @@ Still open after the accepted phase12 replay:
- this matters because `root_context_only` VAT pivots from inventory drilldown should preserve restored organization/date filters without pretending that restored scope is itself a user-selected follow-up anchor;
- targeted `assistantAddressFollowupContext` and `assistantTransitionPolicy` suites are now green after the fix, explicitly protecting the `inventory drilldown -> VAT pivot` regression where selected-item carryover must be removed while the inventory root company/date window remains intact;
- live replay `address_truth_harness_phase12_wider_saved_session_pool_live_20260418_rerun10` remains accepted `20/20`, which is the critical proof that this anchor-sanitization convergence did not reopen the flagship saved-session continuity path.
- the next replay-breadth pass now proves a different late-session contour around answer inspection and self-correction:
- a new live pack `address_truth_harness_phase15_answer_inspection_followup` validates `smalltalk -> company fixation -> historical inventory -> selected-item purchase provenance -> selected-item sale trace -> answer inspection -> VAT-on-purchase-date bridge` inside one shared session;
- the first strict replay exposed a real architecture seam rather than a wording issue:
- after a grounded selected-item sale trace, the user could ask `у тебя написано кто контрагент: рабочая станция - это ошибка?`;
- the runtime was still trying to treat that as a fresh address retrieval request, which collapsed into `unknown / unsupported` instead of inspecting the already grounded previous answer;
- the fix is now explicit in the orchestration layer:
- living-mode policy exposes a dedicated answer-inspection signal for self-correction wording;
- meta follow-up policy can now recognize `answer inspection over grounded answer` as its own follow-up class instead of leaving it to the generic address lane;
- route policy now keeps that class out of the address lane and deliberately routes it back into living-chat inspection logic;
- living-chat runtime now serves a deterministic inspection reply contract for selected-item provenance / sale-trace answers, explicitly distinguishing `selected item` from `counterparty` and preserving the next business move;
- this matters architecturally because another ambient monolith behavior is now an explicit runtime contract:
- grounded answer inspection is no longer left to accidental prompt luck;
- self-correction over a previous exact answer can now coexist with selected-object continuity instead of breaking the session into unsupported chat;
- the neighboring bridge `selected-item trace -> VAT on purchase date` remains alive after the inspection turn, which proves that answer inspection no longer tears down the active business frame;
- live replay `address_truth_harness_phase15_answer_inspection_followup_live_20260418_rerun5` is accepted `9/9`, which is the critical proof that this inspection-follow-up contour now survives as a real saved-session path instead of a one-off manual rescue.
## Next Execution Slice (2026-04-18)