All videosOther topics0:36

Specs, plans, checkpoints, and stop conditions

A contract fixes success; the plan can change with evidence; checkpoints and stop conditions make the trajectory recoverable.

Links containing ?t= open the video at a specific second.

Video summary

The ideas to retain

01

A request is not yet a contract

Human requests usually express intent rather than every invariant an autonomous run needs.

02

Persistent instructions and a task spec solve different problems

Agentic repositories can carry persistent guidance in AGENTS.md, CLAUDE.md, GEMINI.md, or equivalent mechanisms.

03

A plan is a hypothesis, not the authority for the task

Current coding agents expose planning as an explicit operating mode. The official Codex Plan Mode template allows non-mutating actions to gather evidence and asks for a decision-complete…

Key moments

Jump directly to a section

  1. From request to observable contract
  2. Plan, evidence, checkpoint, and replan
  3. Done, recover, blocked, or escalate