Skip to content

Now

core 2.26.22

  • Ordinary work stays on the short path, and the loop stops when the work is done. A work-loop risk trigger that names something you can modify — a security or governance boundary, a structure or public interface, a persistent representation — now fires when a change modifies that thing. Reading it, calling it, testing it, documenting it, or regenerating a projection of it no longer routes the work to full mode. The triggers that name an act still fire on the act, even when everything they touch is unchanged.
  • The loop stops searching once the work is done. Resolve the findings the current intent requires, and do not expand the frontier unless a finding blocks correctness, security, or a stated acceptance criterion. Meeting the stop condition ends the iteration: do not continue searching for additional improvements.
  • Not knowing a file no longer sends ordinary work down the heavy path. The Unfamiliar trigger asks whether you can predict the design, not whether you know the territory. Write down the design you intend and what grounds it; the trigger fires when you cannot, or would be guessing.

Release notes for core 2.26.22