# Assistant Mode Global Status Appendix

Date: 2026-03-24

## A) Verification Commands

```powershell
cd X:\1C\NDC_1C\llm_normalizer\backend
npm.cmd run build
npm.cmd run test
```

Observed result:

- TypeScript build: success
- Test suite: success (`25/25`)

## B) Retrieval Narrowing Evidence

### Case 1: bank mismatch with explicit account scope

- Session: `asst-FuRihiL5Bp`
- Query subject: `bank_settlement_mismatch`
- Source records: `262`
- Filtered after narrowing: `75`
- Semantic narrowing applied: `true`

### Case 2: generic cross-entity bank chain

- Session: `asst-j9spgqdY7k`
- Query subject: `cross_entity_breakage`
- Source records: `262`
- Filtered after narrowing: `242`
- Semantic narrowing applied: `true`

Interpretation:

- Semantic narrowing is active and effective for constrained accounting scope.
- Generic prompts still need stronger narrowing policy.

## C) Key Implementation Anchors

- Semantic profile contract and builder:
  - `X:\1C\NDC_1C\llm_normalizer\backend\src\services\assistantDataLayer.ts`
- Hybrid narrowing and enriched evidence pack:
  - `X:\1C\NDC_1C\llm_normalizer\backend\src\services\assistantDataLayer.ts`
- API regression test for semantic narrowing:
  - `X:\1C\NDC_1C\llm_normalizer\backend\tests\assistantEndpoint.test.ts`

## D) v1.1 Report Reinforcement Checklist

All 4 requested reinforcements are now explicitly present in the main report:

1. Data-loss path map (`Source -> Internal -> Lost -> Symptom -> Fix layer`)  
2. Query-class vs architecture-depth matrix  
3. Dedicated retrieval-unit diagnosis block (current vs target units)  
4. Investigation mode schema and control-policy baseline

Also added:

- symptom -> root cause -> required layer matrix
- value-impact roadmap table
- explicit “what not to do” guardrails
