CSE Roadmap

Core tier · about 3 hours · 12 parts

Part 7 of 12 · 1 min read

How to build it so it holds up

  • Write the outcome check first, as a state check where you can (the refund exists, with the right amount), not by reading the final text.
  • Add invariants for anything unsafe or ordered: must-verify-before, never-delete, never-call-with-these-arguments.
  • Add budgets: steps, tool calls, tokens, cost, time.
  • Check tool arguments, not only tool names.
  • Allow alternatives: use any-order sets for independent steps and several acceptable references for others.
  • Keep path similarity and milestones as diagnostics for debugging and ranking runs, not as the gate.
  • Record the trajectory in the trace (module 8) so these checks can run on production as well as test data.