Act on it together

Stateful Object Lifecycle

One record. Every actor. Always in sync.

Stateful Object Lifecycle keeps a single shared record — case, ticket, deal, claim — as it passes through hands over days or weeks. Every actor sees the same current status, owner, and history. SLA timers run in the background. The object can only move to states you've permitted from where it is now.

Shape

Operational dimensions

Human supervisor

Person oversees and intervenes by exception.

Event-triggered

Fires when an upstream condition occurs.

Medium data gravity

Holds working state that compounds over runs.

Two-way integration

Reads from and writes to external systems.

Inputs

object identifier (case ID, ticket ref, deal ID)
transition request (actor, target-state, attached evidence/notes)
state machine definition (states, permitted transitions, SLA config)
actor identity and role

Outputs

updated canonical state (current status, owner-of-record)
transition history entry with actor + timestamp
SLA status and breach alerts
permitted-next-transitions list for current state

Mechanism

Maintains a per-instance state machine over a long-lived case / record / transaction object — tracks status, owner, history, SLAs, and permitted transitions across the object's life.

Why this is a primitive

Cannot be decomposed: the per-instance state machine (states, transitions, owner-of-record, history log) is a single operation — progress-the-object's-state. Without it the primitive collapses to an unstructured document store. It does NOT decide who-acts-next (that's workflow-routing) and does NOT compute task dependencies (that's schedule-and-plan); it simply owns and progresses one object's lifecycle.

Where it shows up

Insurance claims management — claim moves from Submitted → Triaged → Under Assessment → Approved/Declined, with each transition locked to the right handler role and SLA timers running per stage

Customer support ticketing — ticket state (Open → Assigned → In Progress → Pending Customer → Resolved → Closed) owned by support case lifecycle, multiple agents hand it between them

B2B deal management — sales deal progresses through pipeline stages with owner reassignment at each stage, full history retained for handoff to account management on close

Regulatory permit application — application state machine enforces review stages with mandatory evidence attachments before state progression is permitted

Related primitives

Composes with

Workflow Routing & Gating →Coordinated Multi-Party Sequencing →Temporal Dependency Scheduling →Multi-Role Live Operational Surface →Structured Submitter-Side Form Intake →Inbound Document Intake →Classificatory Inference →Explanatory Inference →

Alternative to

Workflow Routing & Gating →Temporal Dependency Scheduling →