АРЧ АП11 - Архитектура: вынести counterparty intent-family из resolveAddressIntent и обновить pre-expansion cut

This commit is contained in:
2026-04-17 19:06:14 +03:00
parent 50c66e71a8
commit 8f9364e7c9
7 changed files with 572 additions and 5 deletions
@@ -25,9 +25,9 @@ This snapshot is based on:
Latest graph rebuild:
- `5284 nodes`
- `11402 edges`
- `138 communities`
- `5287 nodes`
- `11407 edges`
- `135 communities`
Most relevant current god nodes for turnaround `11`:
@@ -126,7 +126,7 @@ This is enough to build targeted semantic packs that are not single-domain toy s
## Honest Phase Status
Estimated overall turnaround completion: `~91%`
Estimated overall turnaround completion: `~92%`
### Phase 0. Shared Baseline
@@ -163,17 +163,19 @@ Remaining debt:
### Phase 3. Capability Contracts
Status: `88%`
Status: `89%`
Reason:
- critical inventory/address capabilities are materially contract-driven;
- selected-object and root capability behavior is much more explicit than before.
- inventory intent-family now has an explicit owner in `addressInventoryIntentSignals.ts` instead of staying only as inline signal pressure inside `resolveAddressIntent()`.
- counterparty / documents / contracts / open-items intent-family now also has an explicit owner in `addressCounterpartyIntentSignals.ts`, even though legacy inline branches still remain as cleanup debt inside the central resolver.
Remaining debt:
- `resolveAddressIntent()` is still too central;
- extracted owner seams now exist for the hottest inventory and counterparty families, but the legacy inline body still keeps graph pressure high until the final cleanup pass is done;
- some business contours outside the most exercised inventory/address scenarios remain less explicit.
### Phase 4. Coverage / Evidence / Truth Gate Isolation
@@ -253,6 +255,7 @@ Compared with the pre-turnaround baseline, the system is now materially better i
- confirmed-balance and heuristic-candidate reply contracts now have explicit builders instead of repeated inline `semantics` objects in major compose branches;
- inventory factual replies are now owned by a dedicated module rather than embedded directly in the central compose body;
- inventory intent classification now has a dedicated owner instead of being only an inline segment inside the central address intent resolver;
- counterparty / contract / documents intent classification now also has a dedicated owner instead of being only an inline segment inside the central address intent resolver;
- architecture regressions can now be localized to route, transition, truth gate, coverage/evidence, boundary, or meta/memory layers.
## What Still Remains The Main Architectural Debt
@@ -47,6 +47,7 @@ What "done enough" means:
Current status:
- inventory signal-family is now delegated to `addressInventoryIntentSignals.ts`;
- counterparty / documents / contracts / open-items signal-family is now also delegated to `addressCounterpartyIntentSignals.ts`;
- this reduces ownership pressure, even though the old inline bodies still remain as cleanup debt.
### 2. Answer semantics pressure in `composeFactualReplyBody()`