Every ticket as the root of its provenance graph — goal, patch, approval, runs and (as the ticket-class build lands) mandate, manifestations, guarantees, journey, artifacts and children. Rendered through the <<<TicketGraphList>>> tag.
Research: audit omni-git + RAG/mem_graph footprint vs ACTUAL usage — reuse or rebuild?
goal
Measure the existing indices: omni_index.db (occ/blob) and mem_graph.db (~86MB) — what do they contain (files, blobs, symbols, embeddings?), are they QUERIED anywhere or just built, how stale, and can they back a code-similarity search AS-IS? Determine: does a vector/embedding store already exist (migrations 0019_vector_store/0020_multi_axis_search) and is it populated? OUTPUT: a footprint-vs-usage table + a REUSE decision (which existing index backs the search; what must be added). Explicitly answer the operator's question: have omni-git and the RAG system been used at all?
patch
none
approval
unapproved
runs
no runs recorded
mandate (clauses)
not yet recorded — lands with the ticket-class build
manifestations
not yet recorded — lands with the ticket-class build
guarantees
not yet recorded — lands with the ticket-class build
journey (blunders & successes)
not yet recorded — lands with the ticket-class build
artifacts (forge)
not yet recorded — lands with the ticket-class build