Implement Manticore fully and re-theme
This commit is contained in:
@@ -59,6 +59,10 @@ Memory/wiki search helpers:
|
||||
- `MEMORY_SEARCH_BACKEND` (`django` or `manticore`)
|
||||
- `MANTICORE_HTTP_URL`
|
||||
- `MANTICORE_MEMORY_TABLE`
|
||||
- `MANTICORE_EVENT_TABLE`
|
||||
- `MANTICORE_METRIC_TABLE`
|
||||
- `COMPOSING_ABANDONED_WINDOW_SECONDS`
|
||||
- `CONVERSATION_EVENT_RETENTION_DAYS`
|
||||
- `MANTICORE_HTTP_TIMEOUT`
|
||||
|
||||
For XMPP media upload, configure one of:
|
||||
@@ -238,6 +242,9 @@ Performance defaults now applied in GIA:
|
||||
|
||||
- Batched Manticore reindex writes (`REPLACE ... VALUES (...)` in chunks) for lower ingest latency.
|
||||
- Cached table-ensure checks to avoid `CREATE TABLE IF NOT EXISTS` overhead on every query.
|
||||
- Behavioral event dual-write uses `MANTICORE_EVENT_TABLE` (default `gia_events`) when event ledger flags are enabled.
|
||||
- Behavioral metrics are written by `python manage.py gia_analysis` into `MANTICORE_METRIC_TABLE` (default `gia_metrics`).
|
||||
- ORM shadow copies can be pruned with `python manage.py prune_behavioral_orm_data`; defaults are driven by `CONVERSATION_EVENT_RETENTION_DAYS`.
|
||||
- Runtime table maintenance available through MCP (`FLUSH RAMCHUNK`, `OPTIMIZE TABLE`) for steady query responsiveness.
|
||||
|
||||
### F) MCP server for task + memory tooling (VS Code)
|
||||
|
||||
Reference in New Issue
Block a user