The protected transition
Handing over responsibility and committing the exact approved next action happen as one step. Either both happen or neither does.
One owner, always
Try it: “Interrupt a coworker during a handoff” in the home page model.
The agentic architecture.
The rules and mechanisms that let AI agents carry business work from request to fulfillment to settlement, with controlled authority, continuous ownership and recorded evidence. MTech’s digital coworkers are built on them.
InventionPlatform-neutral
FIG. A · Work moving between agents
The problem
Agents can decide.
Acting is the hard part.
Three questions every business has to answer before it can let AI do real work. The architecture answers each one with a rule.
Authority
Who said it could?
An agent that holds the keys can do anything its credentials allow, whether or not anyone approved that specific action.
Ownership
Whose step is it?
When work passes between agents, it can be dropped, duplicated, or acted on by two agents at once.
Outcomes
Did it happen?
Suppliers, banks and other systems do not always answer. Guessing wrong means a duplicate order or a missing one.
Permission lives in the control layer, apart from the agent that asks.
Anatomy
One protected transition,
step by step.
This is the moment the architecture is built around: an agent wants to act and hand the work on. Step through what the control layer checks and what it commits.
Mechanisms
Six rules that hold
the work together.
Each rule answers one way agent-driven work goes wrong. Most can be tried in the living model on the home page.
Authority separation
The agent states what it intends to do. A control layer holds the credentials and acts only when current authority, a matching approval and the live record agree.
Permission lives in the control layer
The agent never holds supplier or bank credentials.
Approval bound to the action
An approval covers one exact, recorded action and is used once. A changed item, amount or destination is a different action.
One approval, one exact action
Try it: “Change the purchase after approval”.
Ownership and version checks
Each part of a job has one current owner and a version. Stale or competing attempts are turned away before they reach the outside world.
One owner per concern
Try it: “Have two coworkers attempt the same step”.
Reconcile before replay
An unanswered request is marked unknown, and the outside record is checked before the action is sent again.
Checked before resent
Try it: “Lose the supplier’s response”.
Evidence before money
Billing and payment depend on the state of the work. An invoice cannot move ahead of the completion evidence it relies on.
Work state governs financial state
Try it: “Receive an invoice before completion evidence”.
Where it applies
The whole commercial
lifecycle.
From the first order to the last payment, every hand-off between work and money runs under the same rules.
Procurement
Orders
Placed only under a matching approval, never resent blindly.
Inventory
Reservations
Owned by one step at a time, released when the job changes.
Field execution
Crews
Dispatched with the approved scope and evidence needs attached.
Quality control
Completion
Evidence recorded before any work is called complete.
Billing
Invoices
Issued only after verified completion, at the approved amount.
Payables
Supplier bills
Matched to what was actually received.
Receivables
Collections
Owned and tracked through to the payment.
Settlement
Closing the loop
A complete, provable chain from request to cash.
InventorThomas W. Matteson
CompanyMTech Corporation