NODEDC_1C/docs/ARCH/11 - architecture_turnaround/21 - current_status_canon_2026-05-01.md

21 - Current Status Canon (2026-05-01)

Purpose

This note is the short source of truth for current module wording after the Post-F and Planner Autonomy closure work.

It exists to prevent stale percentage drift in planning discussions.

If another document says 78%, 87%, 92%, or 85% for a module that is now closed, read that value as a historical snapshot unless this note explicitly repeats it as current.

Current Module Map

• Post-F Semantic Integrity Hardening: 99%, operationally closed as a hardening slice and now used as a regression gate.
• Inventory Stock Open-World Breadth Proof: 100% for the declared inventory-stock scenario pack, not for arbitrary inventory questions.
• Planner Autonomy Consolidation: 100% for the declared phase83 planner-brain slice, including catalog alignment, live-readiness gating, checked-source sanitation, and accepted mixed replay.
• Active next module: broader Open-World Bounded Autonomy Breadth over unfamiliar 1C asks, while keeping Post-F and phase83 as regression gates.
• Completed active slice: Business Overview Evidence Fusion, tracked in 22 - open_world_bounded_autonomy_breadth_2026-05-01.md.
• Current active slice: Business Overview Catalog Route Fabric: the route is reviewed in catalog/data-need/planner contracts, while fresh multi-probe runtime execution remains a pending bridge.
• Active module progress: ~18% (Open-World Bounded Autonomy Breadth).

Reporting Rule

Use these labels when reporting progress:

• Прогресс модуля: 99% (Post-F Semantic Integrity Hardening, operationally closed/regression gate) when discussing the Post-F slice itself.
• Прогресс модуля: 100% (Planner Autonomy Consolidation, declared phase83 slice closed) when discussing the planner-autonomy slice that was just completed.
• Прогресс модуля: X% (Open-World Bounded Autonomy Breadth, active slice: <name>) for new breadth work after this point.

Do not report Post-F as 78%, 87%, or 92%.

Do not report Planner Autonomy as still open unless the discussion is about the next broader module, not the declared phase83 closure target.

What Is Actually Closed

Post-F closed the acute semantic-integrity rescue layer:

• stale organization scope must not beat explicit current-turn counterparty meaning;
• stale focus objects must not hijack newly grounded entities;
• VAT and exact materialization must not self-filter confirmed rows away;
• repeated pivots must keep subject, lane, and time continuity honest;
• business-answer review remains the primary acceptance surface.

Planner Autonomy closed the declared planner-brain slice:

• reusable catalog chain templates are first-class planner objects;
• selected chains expose catalog-template matches and alignment status;
• replay artifacts surface catalog alignment as an acceptance invariant;
• phase83 proved selected-counterparty, open-organization money flow, broad-evaluation continuity, metadata drilldown, and off-domain safety together under live-readiness gating.

What Is Not Closed

The project is not yet a universal arbitrary-1C agent.

Remaining work belongs to the next breadth module:

• implement the fresh multi-probe business_overview runtime bridge behind the reviewed route-fabric contract;
• broader dynamic schema traversal for unfamiliar 1C asks;
• more primitive descriptors where live evidence proves a real gap;
• more replay-backed domain packs that start from user business meaning, not from route convenience;
• continued pressure reduction around central intent seams such as resolveAddressIntent();
• preservation of Post-F and phase83 canaries as regression gates during breadth expansion.

Graphify Rule

graphify-out/GRAPH_REPORT.md is the current graph snapshot.

Older graph counts inside historical validation bullets are evidence-at-the-time, not the current graph size.

After any code or documentation sync that changes the map, rebuild graphify and treat the new report as the navigational source.

Canonical Reading Order

For current planning, read:

1. README.md
2. this document
3. 22 - open_world_bounded_autonomy_breadth_2026-05-01.md
4. 20 - planner_autonomy_consolidation_2026-05-01.md
5. 19 - inventory_stock_open_world_breadth_proof_2026-05-01.md
6. 17 - post_f_semantic_integrity_hardening_2026-04-23.md
7. 16 - data_need_graph_and_open_world_mcp_plan_2026-04-22.md

Documents 01 through 15 remain valuable, but mostly as the historical architecture trail.