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.
GOAL: given a specific SECTION of code, ONE search returns SIMILAR code across the whole forge, with {path, location/line-range, repository, associated tickets} for each hit. We already built omni-git (omni_index.db ~49MB, occ/blob tables) and a RAG/mem_graph footprint (mem_graph.db ~86MB) — heavy index, THIN usage (the query surface was broken/mis-pathed). This RFC: audit what exists and REUSE it rather than rebuild, then spec the search. nomic-embed-text is already pulled (embeddings). Spawns research; research spawns build; build spawns test. Deliverable: docs/CODE_SEARCH.md spec.
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