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.
Build: code.search tool (CLI + MCP) — snippet/path -> similar code with paths, repos, tickets
goal
Build the search: input a code SECTION (raw text) OR a path:line-range; embed it (nomic-embed-text via litellm); ANN over the index (#b_index) + omni-git lexical match; return ranked hits, EACH with {path, line-range, repository, associated tickets, score}. Expose as a CLI AND an MCP tool (so agents can call it). Ticket association: join hit location -> ticket_works/memgraph edges. ACCEPTANCE: paste a known function, get its near-duplicates across repos with correct paths+repos, and at least one correct associated ticket where one exists.
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