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: Z3-optimal rebuild ORDER for the whole forge (incl. forge-itself -> forge2, carrying+extending shadow_forge)
goal
Determine the OPTIMUM ORDER to rebuild every unique forge module (the #201 enumeration) using the z3_mcp SMT/optimize solver. MODEL: nodes = unique modules; edges = build+runtime dependency (imports, package deps, tool-uses-tool); CONSTRAINTS: a module is rebuilt only after its dependencies; foundational packages (control-config lib, telemetry/logging lib per #tele) come FIRST so everything downstream is born instrumented; cycles (SCCs) are detected and an ordering/break strategy chosen. OBJECTIVE (z3 Optimize): minimize critical-path depth / maximize parallelizable batches / front-load the load-bearing packages. BOOTSTRAP: forge ITSELF is in the rebuild set — model the self-hosting order (rebuild forge2 USING the current forge, migrate, then cut over); forge2 must INCLUDE ALL data from shadow_forge/shadow_index.db AND extend it (forge2 subsumes shadow_forge). OUTPUT: an ordered, batched rebuild plan the #201 factory consumes to EMIT rewrite tickets in dependency order (not arbitrary). Deliverable: the z3 model + the ordered plan (docs/FORGE2_REBUILD_ORDER.md). Reuse z3_mcp; do not hand-roll a solver.
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