SpecPunk uses three canonical runtime modes:
  • plot
  • cut
  • gate
These are not tone presets. They are permission boundaries.

​
Why this split exists

SpecPunk is designed to keep planning, implementation, and final acceptance distinct. That separation makes the workflow easier to inspect and reduces the chance that a single fuzzy session quietly becomes the source of truth for everything.

​
Plot

plot is the planning and inspection mode. Use it to:
  • inspect the repository
  • draft or refine a contract
  • shape scope before execution
  • prepare a bounded slice of work
plot does not:
  • change repository files as part of implementation
  • write the final acceptance decision

​
Cut

cut is the execution mode. Use it to:
  • carry out bounded implementation work
  • change repository files inside approved scope
  • run checks and produce a receipt
cut does not:
  • write the final decision
  • write proof artifacts

​
Gate

gate is the verification and decision mode. Use it to:
  • evaluate the run against frozen inputs
  • run target and integrity checks
  • write the final DecisionObject
  • write proof artifacts
gate does not:
  • act like a second implementation pass
  • replace the bounded execution flow

​
How they work together

The current public path is intentionally simple: 
goal -> draft -> approve -> cut -> gate -> proof
That flow keeps one CLI, one vocabulary, and one final decision writer.