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

Post-F: синхронизировать статус scope и bidirectional hardening

This commit is contained in:
dctouch 2026-04-24 15:21:14 +03:00
parent bba4717dbe
commit 394eef066e
2 changed files with 7 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/ARCH/11 - architecture_turnaround/17 - post_f_semantic_integrity_hardening_2026-04-23.md
View File

@ -161,10 +161,12 @@ This phase is already active in runtime code and replay-backed.
Materially hardened in this pass:
- explicit current-turn counterparty now overrides stale organization-scoped carryover for value-flow/net asks;
- explicit one-organization open value-flow asks now stop for organization clarification instead of answering a global total under missing scope;
- incoming-vs-outgoing money comparisons now defer away from one-sided exact supplier/customer recipes into the bounded bidirectional value-flow discovery path;
- VAT exact materialization now survives period-window filtering instead of collapsing into `recipe_visibility_gap`;
- confirmed VAT tax-period turns now keep raw month extraction separate from runtime tax-quarter execution, so exact VAT routes do not lose the intended tax period;
- post-pivot receivables recovery now preserves the selected open-items recipe without weakening strict account-scope guards for risk replies;
- M23 runtime/reply integrity slice is green at `400/400`, covering VAT date-basis, stale scope recovery, open-contract as-of derivation, counterparty role replies, lifecycle labels, and value-ranking answer shape;
- M23 runtime/reply integrity slice is green at `401/401`, covering VAT date-basis, stale scope recovery, open-contract as-of derivation, counterparty role replies, lifecycle labels, value-ranking answer shape, and explicit open value-flow organization clarification;
- stale session focus no longer wins over newly grounded discovery counterparty;
- referential document follow-up no longer wakes metadata/discovery by mistake;
- `documents -> payments/contracts` and repeated pivot chains now survive year-switch and all-time continuation;
@ -179,7 +181,7 @@ Replay-backed anchors for the current layer include:
- `address_truth_harness_phase69_document_to_payments_pronoun_pivot_live_rerun3`
- `address_truth_harness_phase72_document_to_contracts_year_switch_live_rerun3`
- `address_truth_harness_phase80_payments_to_contracts_to_documents_all_time_live_rerun1`
- `address_truth_harness_phase82_human_mixed_integrity_status_dialog_live_rerun5`
- `address_truth_harness_phase82_human_mixed_integrity_status_dialog_post_m23_rerun_scope_bidirectional`
## Honest Remaining Risk

6
docs/ARCH/11 - architecture_turnaround/README.md
View File

@ -65,7 +65,7 @@ Current honest status:
- pre-multidomain readiness: `~88%`
- bounded-autonomy foundation readiness: `~86%`
- open-world bounded-autonomy readiness: `~71%`
- graph snapshot after latest rebuild: `5882 nodes`, `12746 edges`, `137 communities`
- graph snapshot after latest rebuild: `5886 nodes`, `12754 edges`, `136 communities`
- current breakpoint:
- the validated hot paths are no longer structurally broken;
- flagship continuity collapse is no longer the primary risk;
@ -90,10 +90,10 @@ Latest live proof now includes:
- `address_truth_harness_phase69_document_to_payments_pronoun_pivot_live_rerun3` accepted
- `address_truth_harness_phase72_document_to_contracts_year_switch_live_rerun3` accepted
- `address_truth_harness_phase80_payments_to_contracts_to_documents_all_time_live_rerun1` accepted
- `address_truth_harness_phase82_human_mixed_integrity_status_dialog_live_rerun5` accepted `19/19`
- `address_truth_harness_phase82_human_mixed_integrity_status_dialog_post_m23_rerun_scope_bidirectional` accepted `19/19`
- `address_truth_harness_phase11_manual_followup_meta_quality_live_rerun_vatfix` accepted `10/10`
- `address_truth_harness_phase20_continuity_stabilization_live_rerun_vatfix` accepted `6/6`
- `addressQueryRuntimeM23.test.ts` full semantic/runtime slice accepted `400/400` after Post-F VAT/date-basis, scope-recovery, and reply-shape hardening
- `addressQueryRuntimeM23.test.ts` full semantic/runtime slice accepted `401/401` after Post-F VAT/date-basis, scope-recovery, open value-flow organization clarification, and reply-shape hardening
Current architectural reading: