design-time → runtime
Forms × Dimensions
Presence
Gravity
Persistence
Form One
User Task
Live state in every worklist item
Not a document assembled at
request time — the human opens
current variable store, not a snapshot
Record summons the human
Task obligation generated by
the instance — not a scheduler,
not a manager, not an email
Work survives mid-task events
Service restart, personnel change —
the instance holds the human's
in-progress contribution intact
Form Two
Service Task
Agent receives live work object
Structured input assembled from
the running instance — not a
reconstructed payload
Service call fires by obligation
The record generates the call —
no scheduler, no human decision,
no email required
Output logged; instance outlasts call
Structured result written to event log
with performer identity, timestamp,
and confidence score
Form Three
Ad-Hoc Subprocess
Agent reasons against live state
Each tool invocation queries the
current instance — the running
record is always authoritative
Orchestration layer orbits record
Agent proposes; engine governs.
Every tool call passes through
the record — not through the agent
most consequential
Context window ends.
Instance continues.
The Work Record holds the thread
the agent cannot hold.
Persistence is the structural answer.
The forms are design-time assignment decisions. The dimensions are runtime properties every form inherits from the running object.