Frequency
Does this step repeat often enough for automation to remove meaningful work?
Guides
A practical framework for choosing between deterministic automation, AI-assisted steps, and human decisions in a service-business workflow.
Guide by Ian Kirs · ARCHKIRS
Automate work that is repetitive, rule-based, and expensive to repeat manually. Keep judgement, exceptions, commercial commitments, and high-consequence decisions under human control.
Use deterministic logic when the rule can be stated exactly. Use AI only where the input is genuinely unstructured - language, conversations, or documents - and where the output can be checked or bounded. AI is not a reason to automate a process.
| Task | Best default | Why |
|---|---|---|
| Store submitted form fields | Deterministic automation | The data and destination are known. |
| Send routine notifications | Deterministic automation | The trigger and recipient can be defined exactly. |
| Calculate known prices or quantities | Deterministic automation | Repeatable arithmetic should not depend on a language model. |
| Approve scope, price, or contract terms | Human decision | These are commercial commitments and may require judgement. |
| Summarize a long project discussion | AI-assisted | Natural-language compression can save time if the original remains available. |
| Translate project messages | AI-assisted | Language is unstructured; preserving the original keeps the result auditable. |
| Enforce project access and isolation | Deterministic automation | Security boundaries must be explicit and testable. |
| Handle an unusual exception | Human with system support | Exceptions are where rigid automation can create the wrong outcome. |
Does this step repeat often enough for automation to remove meaningful work?
Can you explain the trigger, inputs, output, and exceptions clearly?
What happens if the system makes the wrong decision or sends the wrong result?
Can a person later understand what happened and correct it?
Related proof
ARCHKIRS.SITE uses deterministic structures for enquiries, client and project records, commercial calculations, document versions, and protected private data.
Project Workspace uses server-side AI for tasks such as translation, summaries, transcription, and repository-grounded questions, while authorization, project isolation, evidence boundaries, and final owner decisions remain explicit system controls.
Take one repeated workflow and mark each step as data transfer, fixed rule, human judgement, or unstructured interpretation.
That usually makes the right split between ordinary automation, AI-assisted work, and human control much clearer.