Skip to content
Technical Actions

Technical work,
written for your system

Each action is a complete procedure: what to inspect, in what order, what counts as evidence, and what the result has to look like. Generated against your stack and your previous decisions, not against a generic example project.

Run it in your own environment · Bring back only what you choose

Seven categories

In the order the work usually happens

Understand what is there, check whether it holds, change it deliberately, prove the change worked. Two categories sit alongside that: the people who build it, and how AI is allowed to touch it.

The obvious objection

“Isn’t this just prompts?”

A prompt library

The same text for everybody, whatever they are building.

You adapt it yourself, which requires knowing what to adapt — the exact thing you were buying help with.

No memory: the twentieth prompt knows nothing about the nineteen before it.

Nothing checks the output, and nobody senior ever looks at it.

Copyable in one afternoon, which tells you what it is worth.

A technical action

Generated against your stack, your infrastructure and your previous decisions.

Carries intake questions, an evidence standard and a defined output shape — so results are comparable over time.

Remembers: each action starts from the accumulated description of your system.

Has a verification step, and a human expert available when the answer matters.

Improves as the methodology is versioned, and your past cases keep the version they ran on.

Methodology

The procedures get better; your history stays intact

Every action template carries a version. When the methodology improves, new work gets the new version — and the case you ran in March still shows exactly what it ran on.

Versioned, not silently edited

A template has a stable identifier, a version and a status. Improving it creates a new version rather than quietly rewriting what you already used.

Your past runs are reproducible

Each completed action records the version it used, so you can tell why last quarter’s audit asked different questions.

You inherit the improvements

When a better way to run an audit is found, it reaches every customer’s next action — not just the ones who thought to ask.

Pick the category that matches your worry

Describe the situation in your own words and see the procedure — and its cost — before you spend anything.