Ahmadreza Samadi / Home

Signature ideas

Three practical ideas from Ahmadreza Samadi’s essays: start with the decision, define where AI must stop, and count cost per accepted result.

These are the principles I use to explain and design AI workflows. They are supported by the linked essays and tools, rather than claims of measured company results.

Start with the decision.

Name the decision, the person making it and the evidence it needs before choosing a model.

Why it matters

A model is a component. A useful product also needs a person, evidence, a next action and a way to judge whether the decision improved. Starting there makes the limits visible before an experiment grows.

  1. Name the decision
  2. Identify the evidence
  3. Choose the next action
  4. Then test the AI
A decision workflow for start with the decision.

Where I apply it

Use it tomorrow

  1. Write one decision as a question a person needs to answer.
  2. Name the person responsible for the next action.
  3. List the evidence and what would make it insufficient.
  4. Choose an acceptance rule before comparing tools.

Where the AI must stop.

Make the point for human checking, override or sign-off part of the product.

Why it matters

An answer and an action carry different consequences. Property identity, missing information, permissions and accountability need explicit checks. A person must be able to see the evidence and stop or override the proposed action.

  1. AI proposes
  2. Check source and limits
  3. Person accepts or overrides
  4. Authorized action
A decision workflow for where the ai must stop.

Where I apply it

Use it tomorrow

  1. Identify the error that could affect the decision.
  2. Put the human check before that consequence.
  3. Show source, date and uncertainty at the check.
  4. Specify what happens when evidence or approval is missing.

Cost per accepted result.

Include retries, failures and review when counting the cost of a result that meets an explicit acceptance rule.

Why it matters

A cheaper request may require more retries or review. Count the full workflow cost against distinct results that meet an explicit acceptance rule. The cost ledger records caller acceptance; it does not independently certify the output.

  1. All attempt costs
  2. Include tools and review
  3. Count accepted results
  4. Divide cost by results
A decision workflow for cost per accepted result.

Where I apply it

Use it tomorrow

  1. Define what counts as one distinct result.
  2. Write the acceptance rule and who applies it.
  3. Record failed attempts, retries, tool costs and review time.
  4. Report no accepted results as undefined cost per result, not zero.