swarmvault retrieval

Maintain the local retrieval index under state/retrieval/. The current stable backend is SQLite FTS, with a manifest that records freshness and indexed page counts.

Usage

swarmvault retrieval status
swarmvault retrieval rebuild
swarmvault retrieval doctor [--repair]

Commands

• status - show backend, configured hybrid/rerank behavior, manifest freshness, page count, and shard path
• rebuild - rebuild the local SQLite FTS shard from current wiki pages and refresh state/retrieval/manifest.json
• doctor - check for missing or stale retrieval artifacts
• doctor --repair - repair stale or missing artifacts by rebuilding the local index

Configuration

{
  "retrieval": {
    "backend": "sqlite",
    "shardSize": 25000,
    "hybrid": true,
    "rerank": false
  }
}

retrieval.hybrid controls semantic-page fusion when an embedding-capable provider is configured. retrieval.rerank lets the configured queryProvider rerank merged top hits before answer generation. Vaults that still use legacy search.hybrid or search.rerank can run swarmvault migrate --target 3.0.0 --apply to move those settings into retrieval.

For a broader health check that also covers graph artifacts, review queues, watch state, migrations, managed sources, and task ledgers, use `swarmvault doctor`.