refactor: KI-047 — bucket reorg (Option A safe subset)

User picked numbered-bucket layout. Executing the SAFE subset that does
NOT touch Python imports or string path refs:

• docs/ → 70-docs/
• audit_results/ → 80-audit/

Kept as-is (renaming would need ~25 Python files of string-path updates
— deferred to follow-up):

• data/ — code-referenced (backend/{premium_calculator,
session_state, profile_store, scorecard, admin,
llm_health, main}, rag/build_kb, tools/{check_link_rot,
info_source_map, curate_*, refresh_premiums,
generate_policy_facts}).
• backend/, frontend/, rag/, tools/, eval/, tests/, kb/ — Python
directly forbids leading-digit / hyphen package names.

All references to the moved folders updated in one sed pass across
*.md, *.py, *.sh, *.ts, *.tsx, *.json, Dockerfile.

Verified by:
• tests/test_routing_regression.py — 15/15 still pass.
• No residual (docs/ or [docs/ or /docs/ or ^docs/ refs.
• Same for audit_results/.

Dockerfile: COPY docs ./docs → COPY 70-docs ./70-docs. Container path
mirrors host; nothing in the running app reads from these dirs (purely
reference documentation).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

{docs → 70-docs}/00-overview/roadmap.md

@@ -121,7 +121,7 @@ The point of disciplined v1 architecture is that these things are **stable** acr
 2. **Provider abstraction** (`backend/providers/base.py`) — swap STT/TTS/LLM via config
 3. **Faithfulness verifier** (`backend/faithfulness.py`) — same 4 gates, possibly more
 4. **Persona prompt + citation grammar** — same, refined
-5. **Eval methodology** (`docs/03-eval-plan.md`) — same harness, more gold data
+5. **Eval methodology** (`70-docs/03-eval-plan.md`) — same harness, more gold data
 
 The "c-readiness commitments" in Doc 02 §7 are the contract. Every v2 feature is a commitment honored.
 

{docs → 70-docs}/10-architecture/system-overview.md

@@ -281,7 +281,7 @@ insurance-sales-bot/
 ├── data/
 │   ├── insurers.json           # 10 insurers metadata
 │   └── corpus_urls.md          # output of corpus-discovery sub-agent
-├── docs/
+├── 70-docs/
 │   ├── 01-requirements.md
 │   ├── 02-architecture.md      # THIS FILE
 │   ├── 03-eval-plan.md

{docs → 70-docs}/30-engineering/discovery-script.md

@@ -132,7 +132,7 @@ This is the customer-protection framing. It tells the user honesty is **self-pro
 The questions live in `backend/needs_finder.py::GRAPH`. To add a new question:
 
 1. Add a `Question(...)` entry with `id`, `prompt_en` (plain language + WHY), `prompt_hi` (Hindi rendering), `field` (which Profile attribute it sets), `is_core` (boolean — counts toward completeness), optional `condition` callable, optional `parser`.
-2. Add a row in `docs/scorecard-knowledge-graph.md` Part B showing how the new input shifts weights.
+2. Add a row in `70-docs/scorecard-knowledge-graph.md` Part B showing how the new input shifts weights.
 3. Wire the shift into `_profile_tuned_weights()` in `backend/scorecard.py`.
 
 Drift between these three places breaks the transparency promise. Keep them in sync.

{docs → 70-docs}/40-evaluation/known-issues.md

@@ -203,7 +203,7 @@ progress prints. Document for future tooling.
 ## Quality-sprint cadence
 
 Every batch of fixes ships as one commit referencing the KI numbers it
-closes. The audit run (`audit_results/<run_id>/report.md`) is the
+closes. The audit run (`80-audit/<run_id>/report.md`) is the
 empirical signal for whether a fix is actually working in production.
 
 The standing ratio target: **for every 1 user-facing bug a reviewer

{docs → 70-docs}/40-evaluation/quality-sprint-2026-05-14.md

@@ -66,7 +66,7 @@ Plus the system-prompt reinforcement for KI-013 (rules 8 + 9 in `ADVISOR_SYSTEM_
 - **Sample:** 100 personas × 30 turns = 3000 chat calls against live HF Space
 - **Concurrency:** 4 async workers with 2.0s/dispatch global rate limit (under NIM's 40 req/min cap)
 - **Expected wall time:** ~2 hours
-- **Output:** `audit_results/full_20260514_145243/transcripts/<persona_id>.json` + `report.md` after analyzer pass
+- **Output:** `80-audit/full_20260514_145243/transcripts/<persona_id>.json` + `report.md` after analyzer pass
 - **Resumable:** completed personas' JSONs persist; re-running the script skips them.
 
 The audit is the empirical truth-source for the quality sprint. Pre-sprint we expected: high refusal rate, infinite re-ask loops, demographic-mismatched recommendations. Post-sprint we expect: 0 infinite loops (KI-011 + KI-012 fixed), fact-find always asked before recommendations (KI-013), and verbose/casual/Hinglish styles handled gracefully (keyword fast-path in KI-011 fix).

{docs → 70-docs}/60-decisions/ADR-001-vertical-slice-scope.md

@@ -26,8 +26,8 @@ Build the vertical slice. One category (Health) — but every architectural surf
 
 **Positive:** Demonstrates senior-engineer scoping discipline. Every part of the bot a BFSI buyer would audit (provenance, refusal, eval rigor) is real, not stubbed.
 
-**Negative:** Life, Motor, and other categories are not covered. The seven "c-readiness commitments" in `docs/10-architecture/system-overview.md` §7 become real v2 work.
+**Negative:** Life, Motor, and other categories are not covered. The seven "c-readiness commitments" in `70-docs/10-architecture/system-overview.md` §7 become real v2 work.
 
 ## Revisit at scale (v2)
 
-Category expansion plan in `docs/00-overview/roadmap.md`. Each new category requires: (1) corpus acquisition, (2) per-category schema extension, (3) eval gold set, (4) scorecard sub-score weights. No core code changes.
+Category expansion plan in `70-docs/00-overview/roadmap.md`. Each new category requires: (1) corpus acquisition, (2) per-category schema extension, (3) eval gold set, (4) scorecard sub-score weights. No core code changes.

{docs → 70-docs}/60-decisions/ADR-007-illustrative-pricing.md

@@ -45,4 +45,4 @@ Buyers expect to see premium estimates. Indian insurers hide real pricing behind
 
 ## Revisit at scale
 
-v2 path: B2B partnership with an aggregator (PolicyBazaar, Ditto, InsuranceDekho) or direct insurer APIs to get real quotes. See `docs/00-overview/roadmap.md` §v2.2.
+v2 path: B2B partnership with an aggregator (PolicyBazaar, Ditto, InsuranceDekho) or direct insurer APIs to get real quotes. See `70-docs/00-overview/roadmap.md` §v2.2.

{docs → 70-docs}/60-decisions/ADR-029-hnsw-bloat-tripwire.md

@@ -2,7 +2,7 @@
 
 **Status:** Accepted — 2026-05-14
 **Owner:** Rohit Saraf
-**Trigger incident:** D-001 in [`audit_results/ENTERPRISE_AUDIT.md`](../../audit_results/ENTERPRISE_AUDIT.md)
+**Trigger incident:** D-001 in [`80-audit/ENTERPRISE_AUDIT.md`](../../80-audit/ENTERPRISE_AUDIT.md)
 
 ## Context
 
@@ -57,7 +57,7 @@ All three layer-2 + layer-3 scripts live under `~/Library/Scripts/` (NOT `~/Docu
 
 ## Related
 
-- D-001 in [`audit_results/ENTERPRISE_AUDIT.md`](../../audit_results/ENTERPRISE_AUDIT.md)
+- D-001 in [`80-audit/ENTERPRISE_AUDIT.md`](../../80-audit/ENTERPRISE_AUDIT.md)
 - [`rag/ingest.py::_abort_if_hnsw_bloated`](../../rag/ingest.py)
 - `~/Library/Scripts/insurance-bot/check-vector-bloat.sh`
 - `~/Library/Scripts/cache-prevention/disk-free-tripwire.sh`

{docs → 70-docs}/60-decisions/README.md

@@ -2,7 +2,7 @@
 
 Each major technical or product decision is captured as a single ADR using a lightly adapted Michael Nygard template: **Status · Context · Decision · Alternatives · Consequences · Revisit-at-scale**.
 
-ADR numbers map 1:1 to the original `D-NNN` entries that lived in the legacy `docs/decisions.md` (now split into individual files for easier review, citation, and supersession tracking).
+ADR numbers map 1:1 to the original `D-NNN` entries that lived in the legacy `70-docs/decisions.md` (now split into individual files for easier review, citation, and supersession tracking).
 
 ## Index
 

{audit_results → 80-audit}/README.md

@@ -1,4 +1,4 @@
-# `audit_results/` — Audit output + production-readiness register
+# `80-audit/` — Audit output + production-readiness register
 
 Two artefact classes coexist here:
 
@@ -19,7 +19,7 @@ Status emoji: ✅ fixed · ⚠️ partial · 🟡 improving · 🔴 open.
 ## Run-directory layout
 
 ```
-audit_results/
+80-audit/
 ├── ENTERPRISE_AUDIT.md
 └── <run_id>/
     ├── transcripts/
@@ -55,7 +55,7 @@ audit_results/
 ## How runs flow into the register
 
 1. `python tools/audit/run_audit.py` writes per-persona transcripts.
-2. `python tools/audit/analyze.py audit_results/<run_id>/` rolls up `report.md` + `summary.json`.
+2. `python tools/audit/analyze.py 80-audit/<run_id>/` rolls up `report.md` + `summary.json`.
 3. New defects → new `D-NNN` row in `ENTERPRISE_AUDIT.md`.
 4. Fixes → status flipped, run re-executed as `postfix_…`, evidence linked.
 

CLAUDE.md

@@ -1,6 +1,6 @@
 # CLAUDE.md — project memory for AI assistants
 
-This file is read by Claude Code (and any compatible AI tool) at the start of a session in this repo. Keep it under ~200 lines and focused on **stable, non-obvious facts a new contributor would need**. For change history, look at git log, `audit_results/ENTERPRISE_AUDIT.md`, and `docs/60-decisions/`.
+This file is read by Claude Code (and any compatible AI tool) at the start of a session in this repo. Keep it under ~200 lines and focused on **stable, non-obvious facts a new contributor would need**. For change history, look at git log, `80-audit/ENTERPRISE_AUDIT.md`, and `70-docs/60-decisions/`.
 
 ## Project at a glance
 
@@ -63,8 +63,8 @@ Three independent safety layers against ChromaDB HNSW bloat:
 ## What to read for what
 
 - **System tour:** `README.md` (the master entry).
-- **Decisions with alternatives:** `docs/60-decisions/ADR-*.md` (28 ADRs as of 2026-05-14).
-- **Production-readiness defect register:** `audit_results/ENTERPRISE_AUDIT.md`.
+- **Decisions with alternatives:** `70-docs/60-decisions/ADR-*.md` (28 ADRs as of 2026-05-14).
+- **Production-readiness defect register:** `80-audit/ENTERPRISE_AUDIT.md`.
 - **Data lineage:** `kb/AUDIT_TRAIL.md`.
 - **Tests:** `tests/test_routing_regression.py` (15 tests pinning routing + load-balance invariants).