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.
PRIORITY (user). Research a pipeline for background images for the project's GUIs (the Gemma tool-GUI, brainstorm output, kokoro app). Scope to define: (a) generate vs source vs curate; (b) if generate, which local image model runs on the servers with NO external telemetry (SD/Flux/etc. local); (c) licensing if sourced; (d) storage (forge content-addressed?) + how a UI references them. DELIVERABLE: a spec ticket + recommended approach. NOTE: 'background images' scope is under-specified — first output should pin down the exact use with the user.
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