Spaces:
Sleeping
Sleeping
Commit History
-
docs: stale-references sweep — align legacy docs with ADR-044 + 8-gate state
11 files fixed per 2026-05-27 docs-audit (P0 / P1 / P2 / one P3): P0 — Upload pipeline most-likely-to-mislead: - 70-docs/20-data-pipeline/ingestion-policy.md: wholesale §"Exception — user uploads" rewrite; dual-write table row; date bumped + ADR-044 cross-ref - kb/security/INDEX.md: "5 gates" → "8 gates" with full table extension P1 — Status inversions: - 70-docs/60-decisions/ADR-003-curated-corpus.md: "Locked" banner now says "partially superseded by ADR-044"; counts 190/19 → 148/21; quarantine-only framing flipped to dual-write - 70-docs/60-decisions/README.md: ADR-003 status row updated - 70-docs/10-architecture/safety-architecture.md: F-13 "Not applicable — D-003" → "LIVE per ADR-044, mitigated by 8 gates" (resolved internal contradiction) - 70-docs/00-overview/problem-statement.md: §5.4 qualified as v1 intent + ADR-044 update; §7 non-goal bullet replaced with cross-session-retrieval caveat P2 — Architecture summaries omitted dual-write: - ARCHITECTURE.md: explicit…21e4b2a
-
feat(llm+docs): KI-177 + KI-179 + KI-183 + ADR-040 docs cascade
THREE-TIER LLM CHAIN — Google Gemini PRIMARY, NIM Tier 1, OR Tier 2. Live audit (KI-178) of OpenRouter's free-tier catalog killed my earlier recommendation: gemini-2.0-flash isn't in OR's catalog, llama-3.3-70b- :free and hermes-3-405b:free don't expose response_format. So OR's free-with-JSON pool is only nemotron-3-super-120b / qwen3-next-80b / gemma-4-31b. User obtained a Google AI Studio key, set up billing ($0 historical spend, $10 cap, free 1500/day quota active), confirmed working live on gemini-2.5-flash + gemini-2.5-flash-lite. NEW MODEL TIERS: Brain Fast (sales_brain): Tier 0 Google gemini-2.5-flash-lite (KI-183 — 2.0-flash retired) Tier 1 NIM qwen3-next-80b → mistral-large-3 → llama-4-maverick Tier 2 OR nemotron-3-super-120b:free → qwen3-next-80b:free → gemma-4-31b:free Last NIM nemotron-super-49b (only when all else dies) Brain Main (orchestrator): Tier 0 Google gemini-2.5-flash Tier 1+ same NIM/OR cascade Judg…132a829
-
docs: KI-101..KI-107 — audit + CLAUDE.md + ADR sync
Document the seven KIs landed today across the production-readiness register, project memory, and affected ADRs: - KI-101 (66eb4ed) — drop 6 function-local `import logging` lines from orchestrator.py; module-level import is the sole binding so the asyncio wait_for TimeoutError branch no longer raises UnboundLocalError. - KI-102 (4bb8da0) — profile RAG cross-session isolation. session_id stamped on every chunk; main retrieve() excludes doc_type=profile; per-session lookup triple-checks meta.session_id == session_id in Python; legacy chunks without session_id fail-closed. ADR-022 extended with a session-isolation subsection. - KI-103 (8ef5c43) — _canonical_fallback no_trailer loop-breaker. New session._ff_failed_attempts + _ff_skipped_slots; after 2 failed attempts on the same slot, mark skipped and advance. - KI-104 (407f2a1) — voice_format.tts_preprocess strips chain-of-thought leakage: <think> blocks, **Reasoning:** labels, [INTERNAL] blocks, sentence-anchored CoT…1d10432 -
fix(admin): KI-096 + KI-097 — public /api/version + password-only admin
KI-096: add unauthenticated GET /api/version (git SHA + uptime). Lets any caller verify which commit HF Space is serving without admin auth. KI-097: rip out admin IP allowlist. ADMIN_IP_ALLOWLIST env, _ip_allowed(), and the dual-gate 404-to-hide-existence behavior are gone. _check_admin now only verifies the X-Admin-Password header; bad/missing password → 401 Unauthorized. Operational rationale: changing networks locked the operator out without adding meaningful security beyond a strong password. ADR-023 superseded; ADR-010 secret count 8 → 7. Also includes test_name_persistence.py (4 deterministic regression cases pinning KI-091/094/095) and the KI-094 mistakes-log entry. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>d37a6cf -
docs: KI-091 + KI-094 — extractor gates + None-guard added to audit + CLAUDE + ADR-032
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>d547d5a -
docs: final sync — backend/README post-KI-070 + ADR-032 cross-links in README §4.3 + ENTERPRISE_AUDIT KI-080 row
Three small completeness fixes surfaced by the end-of-session audit: - backend/README.md — `needs_finder.py` row now correctly described as "safeguard fallback only" post-KI-070 (was still labelled the primary fact-find driver, pointing to ADR-027). Added new row for `fact_find_brain.py` (the actual KI-070 driver). Marked `question_paraphraser.py` as deleted. - README.md §4.3 — opening sentence reframed from "fallback chain" to "candidate pool with probe-driven sticky primary election"; ADR-031 + ADR-032 cross-links added inline so a reviewer can jump straight to the architecture reference. - ENTERPRISE_AUDIT.md KI-080 row — added inline link to ADR-032 so the audit table's KI-080 entry routes through to the end-to-end architecture spec (was already linking ADR-031, now both). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>088ff0b -
docs: KI-088 + KI-089 + KI-090 — audit rows + CLAUDE.md sync (semaphore / test-fix / lenient parser)
2e5de93 -
docs: ADR-032 LLM chain architecture reference + KI-080..KI-087 doc sync
Adds new architecture reference ADR consolidating KI-079..KI-087: - 70-docs/60-decisions/ADR-032-llm-chain-architecture.md (NEW, 435 lines) - TL;DR + ASCII data flow diagram - Component reference (every ModelHealth field) - Election algorithm pseudo-code + score formula - Probe loop cadence + OpenRouter credits polling - Per-provider credit signal table (Groq headers / OR endpoint / NIM rate-meter) - Per-phase httpx timeout justification - Failure classification table - KI-079 escalation path - Telemetry surface (brain_used variants) - Performance characteristics + operational runbook Updated docs: - CLAUDE.md "LLM stack" section: KI-080..KI-087 full coverage + NIM-first preference (KI-087), credit gating (KI-085), per-phase timeouts (KI-084), admin tab (KI-086), HF Space secrets (KI-081) - 80-audit/ENTERPRISE_AUDIT.md: 5 new rows (KI-081, KI-084, KI-085, KI-086, KI-087) appended to "Fixes shipped today" table - backend/provi…6a47549 -
docs: KI-080 — sync CLAUDE.md + ENTERPRISE_AUDIT + new ADR-031 + 11 stale KI-025/50-50 surface sweep
Documents the KI-080 architectural shift from "iterate every chain candidate per call" (ADR-026 / KI-025 50/50 NIM ↔ Groq rotation) to "probe-elected sticky primary with cross-provider backup" (ADR-031). Files updated: - CLAUDE.md — "LLM stack" section rewritten for KI-080 election; KI-025 rotation marked deprecated. - 80-audit/ENTERPRISE_AUDIT.md — KI-078/KI-079/KI-080 rows added to "Fixes shipped today" table; executive-scorecard UX-latency + test- coverage rows updated to cite KI-080 (supersedes KI-025). - 70-docs/60-decisions/ADR-031-sticky-primary-election.md — NEW. Full ADR following ADR-030 shape: Context, Decision, Alternatives, Consequences, Files touched, Revisit at scale. - 70-docs/60-decisions/ADR-026-provider-load-balancing.md — header updated to "Superseded by ADR-031"; body retained as historical record per ADR convention. - 70-docs/60-decisions/ADR-030-llm-driven-fact-find.md — pointer to ADR-026 swapped for ADR-031. - README…c592055 -
docs: sync KI-071..KI-077 to ENTERPRISE_AUDIT + CLAUDE.md (post-KI-070 safeguards + Name field)
After KI-070 shipped the single-LLM-call fact-find, six follow-up KIs landed to make the experience robust under real-world LLM degradation and to surface the captured profile in the UI. Recording them in canonical docs so they're traceable across the repo. ENTERPRISE_AUDIT.md "Fixes shipped today" — added 7 rows: - KI-071 — 12-file docs reconciliation against actual code reality - KI-072 — P0 fallback captures user's answer to last-asked slot - KI-073 — Clear chat resets profile-completeness chip synchronously - KI-074 — P0 greedy multi-slot capture + slot-trigger guards - KI-075 — Brain timeout 12s → 25s (root cause of "still robotic") - KI-076 — HF Dataset viewer disabled (CastError gone) - KI-077 — Name field + profile-panel pre-fill from chat state CLAUDE.md "Fact-find loop" section extended with two new bullets documenting the safeguards added since KI-070: - KI-072/074 — fallback path no longer dead-ends; greedy multi-slot capture with trigger guards - KI…dd6172a -
fix(fact-find): KI-072 — canonical fallback now captures user's answer + doc sync (CLAUDE.md / ADR-030 / ENTERPRISE_AUDIT)
═══════════════════════════════════════════════════════════════ KI-072 — P0 fallback wedge fix (backend/fact_find_brain.py) ═══════════════════════════════════════════════════════════════ Live user screenshot showed the bot stuck asking "First — what should I call you? I'll save your profile so the next time you visit, you won't have to answer all this again." FOUR times in a row while the user answered "I am Don" / "Don" / "Don Jon". Every answer dropped on the floor. Root cause: when KI-070's `drive_fact_find()` brain call fails (timeout, malformed JSON trailer, chain exhaustion), it falls back to a canonical question via `next_question(profile).prompt_en`. But the original fallback just returned the question text — it never tried to APPLY the user's current message to whichever slot was last being asked. So under any sustained LLM degradation (NIM rate limit / pool timeout), fact-find wedges into an infinite re-ask. Fix: `_canonical_fallback` now takes `session` + `user_text`, re…e098e1b -
refactor + feat: KI-050b/053/054 — rename completeness + eval speed + tax questions
Combines three logically-related changes into one push-clean commit (rewrites the prior 67bdd3a + 866fb24 to drop accidentally-swept-in binaries + runtime state that tripped HF Space's pre-receive hook). KI-050b — data/ → 40-data/ rename completeness across docs: • 40-data/ internal docs (README, corpus_urls.md, info_source_map, illustrative_premiums.json, llm_health.json, profiles/README, reviews/icici-lombard.json) • kb/ — AUDIT_TRAIL, INDEX, all 218 kb/policies/*.md mirror sheets, kb/research/corpus_acquisition.md, kb/reviews/* leaderboards • tools/ — info_source_map.py, build_kb_mirror.py, full_pipeline.sh, README, ~12 other scripts touching data/ paths in prose • eval/info_source_map.json (2772 source-provenance entries) + README entrypoint.sh preserved — its `/data/` paths are absolute HF Space persistent-disk mounts, NOT references to the repo folder. KI-053 — eval/run.py --no-extract flag. Skips the orchestrator's free-form profile_extractor LLM call …57ef382 -
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/. Doc…e2d09f9