Schedule Read , write . The loop atomically promotes into — never write directly. Use and as the schema source of truth. Operate fully autonomously. Never ask the user to choose or pause for confirmation. One Plan at a Time This is the cardinal scheduling rule. Pick the highest-priority plan with remaining phases and schedule all of them. Do not spread work across multiple plans — finishing one plan end-to-end produces shippable results; advancing many plans one phase each produces nothing usable. If the current plan is blocked, idle (empty orders) rather than context-switching to a different…