Three Dimensions the Running Object Acquires
WORK RECORD
CPP-TX-2026-004821
State: In Force
Identity · State
History · Obligations
Presence
Gravity
Persistence
Running Instance
Governed Lifecycle
Presence
what does the agent actually get?
Where? · What happened? · What's next?
engine delivers
RAG / prompt snapshot
Where?
node 5 of 9 ✓
✗unknown ✗ → guessed ✗
History?
8 events ✓
partial ✗ → truncated ✗
Next?
→ Bind ✓
indeterminate ✗ → opportunistic ✗
The instance IS the work. It occupies memory.
Engine delivers → live truth: position · history · next step.
RAG / prompt → snapshot:
guessed slice of history under context‑window limits.
A snapshot cannot hold weight.
Gravity
structural obligations — the instance summons the organization
Work
Record
Worklist
task assigned
Service Call
fires
Timer Event
schedules
Message Event
waits
Workers orbit the record.
It coordinates — not a container they fill.
Persistence
the instance outlasts every component
Service restart
✓ instance persists
Personnel change
✓ instance persists
Regulatory update
✓ instance persists
New AI deployed
✓ instance persists
Engine: passivate · serialize · rehydrate on next event
Agent: context window boundary →
✗ thread lost
The token survives.
The running object exists in memory, summons the organization, and persists from instantiation through final discharge.