zicato-index-ops

You can rebuild the derived SQLite analytical index from canonical zicato workspace files to synchronize projections after manual epoch data changes. This process repairs stale indexes and restores data integrity for cross-run analytics.

Querying tournament history and loss analysis across runs requires read-only SQLite SELECT commands against the workspace index database. This approach enables safe cross-run investigation of loss profiles, judge results, and drift metrics without consuming LLM budget.

Yes, investigating drift metrics and generation lineage requires the zicato CLI and a workspace index database. The CLI manages index rebuilding and targeted repair of promotion data when the generations table drifts.

Targeted repair fixes generation lineage drift by selectively rewriting promotion data in the SQLite analytical index. This isolates corrections to the generations table, avoiding a full database rebuild while restoring lineage integrity.

Yes, you can identify mutation points associated with rejected tournaments using read-only SQLite SELECT queries. This cross-run analytics capability compares generation outcomes and investigates recurring drift metrics without hand-editing the index.

You should avoid manual SQLite edits when investigating stale indexes or generation lineage, as hand-editing corrupts the derived analytical index. Instead, use index rebuilding or targeted repair via the zicato CLI to maintain synchronization.