Action fusion: edit plus check

The idea

An edit can carry its planned check. The runtime runs the check as its own gated call in the same model turn.

The problem
An edit and its check cost two model round trips.
Why it matters
One turn does both, and the check still goes through every gate.
Where it stands
In production as of

A step-by-step replay of this idea is not published yet. The library adds one when a recorded run shows it.

  • Stage exit checklists and loop limits

    Each stage has an exit checklist. Code judges the clear items and System One the unclear ones. Repeated holds go to a person, and a loop guard stops the run when the same result repeats.

  • Run waste analysis

    When a run ends, the platform analyses its steps and requests for repeats, missed fusions, context growth, large outputs and long logs. It estimates the tokens each mechanism would save.

  • ObservationPack and folded results

    A tool result of 10 KiB or more is stored whole. The step keeps the head, the tail and exact diagnostic anchors. Older results fold to one recall line, and the worker can read exact pages back.

  • Engineer pipeline with stage shares

    Work follows an engineer's pipeline, and each stage gets a share of the time and cost. Review is one plan review and one holistic diff review, within about 10% of spend.

Turn the numbers into shipped work.

Crewshal runs these choices for you: a persistent AI worker with memory and rules, on your Claude and Codex subscriptions.