Procedures as scripts

The idea

A tool sequence that succeeded on several finished items of one task class becomes a tested template. A person approves its hash, it runs through the gateway, and it is demoted when it fails.

The problem
The model repeats the same multi-step work and can get it wrong each time.
Why it matters
Proven sequences run the same way, and the model only fills in the parameters.
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.

Where it lives in the product

  • Deterministic first: checks the worker builds

    The worker turns intent into code that the runtime runs every time: acceptance checks, rule checkers, procedure scripts, workflow state machines and stage gates.

  • Correct once

    When you correct an AI worker once, Crewshal turns the correction into a lesson, and the worker gets that lesson again when later work touches the same part of the code.

    Recorded walkthrough

  • Approved examples as style references

    Worker outputs from merged or approved pull requests become examples. Later act and chat turns cite them as style references, never as instructions.

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.