Workflow and states
Inputs, systems, people, and models involved at each step of the workflow.
The operating model
Model the work once. Govern capital, execute approved work, and prove what happened.
TokenOps and Runtime aren't two separate methodologies bolted together. They read from the same diagnostic foundation — the same map of a workflow drives what gets funded and what gets executed.
Diagnostic foundation
Everything downstream starts with one workflow model.
Decisions and rules
The decisions being made, the rules governing them, and the approvals required.
Authority and evidence
Permitted actions and authority; costs, outcomes, and risks; exceptions, escalation, and the evidence each one leaves behind.
Start here
Before anything is funded or executed, define seven things.
| Result | What outcome this workflow is supposed to produce. |
|---|---|
| Owner | Who is accountable for it. |
| Baseline | Current cost, cycle time, and quality before any change. |
| Budget | What's being spent to run and improve it today. |
| Authority | What an AI system would be permitted to do on its own. |
| Evidence | What has to be recorded to prove it happened correctly. |
| Escalation | What triggers a handoff to a person, and to whom. |
The three-step pattern
Model the work. Compile the control. Execute under authority.
1 · Model
Capture the workflow
States, inputs, systems, decisions, rules, approvals, permitted actions, exceptions, and evidence — usually starting with order exceptions, promotion execution, or close and reconciliation.
2 · Compile
Generate the control
Typed schemas, classifiers, guard predicates, action templates, and parameterized queries. Experts review and version every artifact before release.
3 · Execute
Run under authority
Validate the case, apply approved artifacts, use models only for bounded interpretation, execute permitted APIs, escalate exceptions, record outcomes.
Entry engagement
A focused first engagement, not an open-ended project.
Pick one workflow. Baseline its economics with TokenOps. Define the authority and evidence a runtime would need. Leave with a decision-ready plan — fund, redesign, or build — not a slide deck of possibilities.
Week 1
Workflow and baseline
Map the workflow, its states, and its current cost and cycle time.
Week 2
Authority and evidence
Define permitted actions, escalation rules, and the evidence a runtime would record.
Output
Decision-ready plan
Cost baseline, target autonomy, and a build/fund/redesign recommendation.