Intention → Action → History
Outcomes Are
State Changes
Who carries an intention through to the consequential state change?
An invoice has been generated. It has been sent. It has been opened. The money has not arrived.
There is no shortage of artifacts. There is a document, a delivery record, perhaps a notification. Each records something that happened. Yet if the intention was to collect payment, the consequential condition remains unchanged.
This is the distinction I want us to make precise: an artifact is something an action leaves behind; an outcome is the realized change that action brings about. To judge completion, we must specify which change fulfills the intention.
These categories can overlap. A finished manuscript can be both an artifact and the fulfillment of a writing assignment. A generated invoice can complete an instruction to prepare an invoice. But the existence of either object does not automatically complete the larger undertaking in which it participates.
For students of the Reality Equation, this opens a deeper question. We have spent considerable time examining the relation between Actual and Expectation. Now we need to examine the passage by which an intention becomes history available to subsequent Actual.
First, say what must become true.
A state change needs a before and an after. A successful outcome also needs a criterion. Without that criterion, we can count activity indefinitely while leaving the intended condition untouched.
Let s describe the task-relevant state. For a simple invoice example, track whether the invoice has been drafted, sent, and paid. These are bookkeeping coordinates for this example, not new terms in the Reality Equation.
Task-level state
s = (drafted, sent, paid)
Each coordinate is 0 before the condition is met and 1 afterward.
If the instruction is to collect payment, define a completion criterion c(s) that equals 1 when payment has been received and 0 while it has not. Generating and sending the invoice change the first two coordinates. They do not yet change the third.
Successful completion of the chosen intention
c(sbefore) = 0
c(safter) = 1
Sending the invoice is a real state change. It may be a necessary step. We should not deny either fact. We should locate it correctly: it is an intermediate outcome relative to the intention to collect payment.
Change the intention, and the point of completion changes.
State laboratory
Same history.
Different finish line.
The events stay fixed. Watch which states satisfy the selected intention.
State 01
Drafted
(1, 0, 0)
The document exists.
It has not been sent.
Criterion satisfiedStill incomplete
State 02
Delivered
(1, 1, 0)
The recipient has the invoice.
Payment has not arrived.
Criterion satisfiedStill incomplete
State 03
Paid
(1, 1, 1)
Payment has been received.
The collection condition is met.
Criterion satisfiedStill incomplete
Completion first occurs at State 01. The document is itself the requested outcome. The later states continue to satisfy that criterion.
Completion first occurs at State 02. A prepared document was insufficient; delivery was the intended state change.
Completion first occurs at State 03. Preparation and delivery were intermediate outcomes. Payment fulfills the chosen intention.
An artifact’s existence and an intention’s fulfillment are different questions.
Locate the change in the equation.
Retain the established entity index:
RX = AXPX + iIX
EX = PX + iIX, with EX ≠ 0.
PX is the resolved prediction supplied by the prediction machine. The imaginary term represents the entity’s relationship to ideas. Together they form Expectation. Actual supplies the numerator; Reality is the quotient.
We can therefore distinguish a change in Actual from a change in the predictive or imaginary component of Expectation. Reality can change through either side of the relation. It is derived from those terms, not a fourth independently adjustable control.
This matters because “things feel different” does not by itself establish that the external condition changed. A revised expectation can alter the quotient. A new interpretation of an unpaid invoice does not make it paid.
For the present inquiry, hold the entity, its observable, and its nonzero Expectation fixed. Then a change in its indexed Actual gives:
With Expectation held fixed
ΔRX = ΔAXEX
If the denominator changes as well, we must evaluate the full before-and-after quotient. Changes can reinforce or offset one another. We cannot infer the resulting change in Reality from the numerator alone under every condition.
The point of holding Expectation fixed is to isolate the contribution we are examining. Something has happened. The settled conditions available to the relevant observable are different. The desired condition has become part of settled history.
History is shared. Indexing is particular.
When I say that Actual is shared, I mean that we inhabit one history. The squirrel storing nuts, the human making a payment, and the agent repairing a system do not create private universes in which their actions settle.
The formal distinction remains:
One source, entity-specific projection
AX = OX(A*)
A* denotes the common settled history. OX denotes the observable associated with entity X.
A shared source does not require identical numerical inputs for every entity. A restaurant operator, a caller, and a software agent can encounter different projections of the same operational change. A repair can enter the agent’s observable through a successful test before it enters the operator’s observable through a report.
Nor does every event change every entity’s indexed Actual immediately. What enters depends on the observable and on when evidence becomes available.
We must also preserve the word Immutable. Action does not revise an already settled event. It produces a subsequent event. Later settled history includes what has now happened; earlier history has not been rewritten.
The temporal passage
Reality → Action → Subsequent history → Later Actual
This is where actualization belongs. The human is a history maker among other history makers. Within this framework, an actualizer is an entity participating in the production of settled change. The category is broader than deliberate human intention; intention gives a particular course of action a chosen direction and a completion criterion.
A repair changes what the next caller encounters.
Consider the repair behind “Somebody Handled It.” Aki, an AI receptionist, needed to retain a usable callback number when a requested time slot was full. Another AI agent, working on the software behind Aki, reported interpreting my request, changing the live system, testing the phone and text paths, and removing its test records.
The code was an artifact. The deployment record was an artifact. The completion message was an artifact. They traced a passage through the work.
The intended outcome was a changed operational condition: the relevant turn-away flow would now preserve a usable callback number. A caller taking that path would encounter the repaired behavior.
Receiving a code suggestion would have left the passage unfinished. Somebody would still have needed to apply it, deploy it, and establish that the condition held. In the reported repair, the agent carried those intermediate steps.
That is the specific sense in which something else was actualizing. The system was coupled to machinery that could act. Its contribution extended through deployment and checks of the resulting state.
We should identify the entity at that operative boundary: the agent together with its authorized tools and execution environment. A model’s ability to describe a repair is not sufficient to produce the repair. Access, permissions, and functioning action paths matter to what can become history.
Software automation has long changed the world. A scheduled payment, for example, already has consequences beyond producing a document. The distinctive feature of this case is the agent’s reported use of context and feedback to carry a multi-step assignment without my supplying each intervening instruction.
Who carries the intention?
A reminder stores something that should later influence action. A note on the door changes the state of the door and the information available there. But if the intention is to return a borrowed book, putting up the note has not returned the book.
The reminder can preserve the intention while leaving its actualization assigned to you.
Many familiar workflows have this structure. A document is produced, then a person must interpret it. A notification arrives, then a person must choose the next step. The tools preserve and transform information, while the human repeatedly reconnects that information to consequential action.
In that arrangement, the human carries the intention across the gaps. This is the operational meaning of being the glue.
Delegation changes where that continuity resides. An agent can retain the objective, inspect intermediate results, choose a permitted next action, and continue until the criterion is satisfied or a real boundary requires a human decision.
It need not control every cause. An agent following up on an invoice cannot guarantee that a customer will pay. A counterparty remains an actor. Carrying the intention means sustaining the authorized work toward the condition and reporting its actual status, including an unresolved dependency.
This distinction also prevents us from calling any busy system successful. A system may create many artifacts, make many changes, and still fail to produce the intended outcome. It may even produce an unwanted outcome. Actualization describes consequential participation; success requires the chosen condition to be met.
Who carries an intention through to the consequential state change?
The question directs our attention to the whole passage. We look for the continuity between what is sought, the actions taken, and what has become true.
The change can precede your knowledge of it.
Suppose the repair is complete, but I have not yet received the report. The operational condition has changed. I may still be carrying it as unfinished.
Then evidence reaches me. In the terms of the framework, new evidence enters my indexed Actual and participates in the quotient that supplies my Reality. I do not consciously inspect a naked numerator outside that relation. I encounter a condition in which the repair can now be recognized as completed.
This is why the breadcrumbs matter. The artifacts let me inspect what happened, connect it to the original intention, and determine whether the completion claim is warranted. A confident report without a corresponding state change would give me an unreliable account of the outcome.
But the artifacts alone do not explain the relief. The recognition has two parts: the intended condition has changed, and I was not required to maintain every connection that brought it about.
I was involved in the larger undertaking. I supplied direction and authority. I remained accountable for decisions assigned to me. What ceased to be necessary was my continuous intervention in the middle.
That is the deeper significance of “somebody handled it.” Another operative entity carried an intention through actions that became history. Evidence of that history returned to me.
Replace the output inventory with a state description.
Take one current task. Write the condition before the work, then the condition that would establish completion. Identify the artifacts that can help produce or verify the transition. Finally, identify who must keep the work moving between those artifacts.
If completion still depends on you noticing every intermediate result and supplying every next instruction, you remain the carrier. If another authorized entity can sustain the passage and return a verifiable result, the organization of actualization has changed.
The invoice makes this easy to see. The document can be beautifully generated, correctly addressed, and successfully delivered while the collection intention remains unfulfilled. Payment changes the condition. The evidence lets you know.
The same discipline applies to the repaired receptionist, the delivered publication, the reconciled account, and the returned book. Begin with what must become true. Then follow the action all the way there.
The world was never waiting for human beings alone to make history.
Now an intention you once had to carry can travel through another actualizer.
1 thought on “Outcomes Are State Changes”