deploy / deploy (push) Successful in 30s
Centralizes fixed control intents and adds a data-driven intent_code field on kb_articles so many phrasings of the same FAQ question resolve to one stable code (e.g. VOUCHER_ACTIVATION) instead of a free-form, unvalidated string the LLM invented on the fly. - services/shared/intents.py: CONTROL_INTENTS + normalize_intent() - kb_articles.intent_code column (ORM + dev/sqlite runtime compat + migrations/sql/0034_* for postgres/sqlite) - kb_service CRUD exposes intent_code - orchestrator surfaces intent_code to the LLM and validates its intent output against control intents + the KB codes shown that turn - voice.py: _voice_early_intent_bucket renamed to _voice_ack_topic_bucket to stop it being conflated with the canonical FAQ intent
Core DB Migrations
This folder contains SQL migrations for core MVP services:
auth-servicecustomer-serviceinteraction-servicerouting-service
Files
sql/0001_core_sqlite.sqlsql/0001_core_postgres.sqlsql/0002_stage3_sqlite.sqlsql/0002_stage3_postgres.sql
Apply
python scripts/migrate_core_db.py
The runner:
- detects dialect from
DATABASE_URL - applies all
*_{dialect}.sqlmigrations in order - tracks applied files in
schema_migrations