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

АРЧ АП11 - Архитектура после регресса: Архитектура: сделать counterparty и contract ranking-ответы business-first без отчетного preamble

Browse Source
This commit is contained in:
dctouch
2026-04-18 15:32:05 +03:00
parent a51fc2a70d
commit 0c6440fc5e
4 changed files with 35 additions and 40 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
+5 -1
View File
@@ -252,7 +252,11 @@ Latest continuity-authority convergence evidence after the current route pass:
- `vat_payable_forecast` and `vat_liability_confirmed_for_tax_period` now open with a business-first `Коротко: ...` lead, while the detailed calculation stays in the secondary block;
- service-flavored top lines like `Собран прогноз...`, `Режим результата...`, and `Строк агрегата...` are removed from the first screen of the reply, which makes VAT answers read like user-facing guidance instead of an engine report;
- VAT reply tests now explicitly protect this top-block shape, so future changes cannot silently reintroduce the same mechanical preamble;
- this is still not the end of shaping work: some ranking families and long evidence-heavy replies still need the same cleanup;
- the next human-answer-shaping cleanup pass is now applied to counterparty ranking/profile replies:
- `counterparty_activity_lifecycle`, `contract_usage_overview`, `customer_revenue_and_payments`, `supplier_payouts_profile`, and `contract_usage_and_value` now open with business-first wording instead of service-flavored `профиль собран / строк агрегата / строк источника`;
- ranking and contract replies now preserve user wording better in the visible heading layer, including `минимальный бюджет` phrasing for low-turnover active contracts;
- targeted ranking/profile tests now protect the new top-block shape, so these families are less likely to regress back into report-like wording during later route/domain work;
- this is still not the end of shaping work: some long evidence-heavy replies and residual catalog-style blocks still need the same cleanup;
- this pass does not yet finish full single-owner continuity, but it narrows one of the remaining seams where route arbitration and scope memory could disagree about whether the session was still grounded.
## Next Execution Slice (2026-04-18)