MaxQ EngineState, recovery, and guarded action in one runtime.

The runtime records product events, checkpoints long-running work, and enforces permission gates for state changes.

Signals map to entities, rights, and intended state changes.

Every signal lands with identity, rights, and next-state intent.

Each agent step uses current context.

Entity and workflow events refresh the Shape before the next agent step.

Events update product state.

Events update named entities, permissions, and allowed next steps for teams and agents.

Runtime boundaries define permitted transitions.

Runtime boundaries define state ownership, recovery points, and allowed actions.

State changes validate before commit.

State moves through lock, validation, commit, projection.

Long-running work resumes from saved checkpoints.

Long-running work waits on timers or signals and resumes from saved execution state.

Agent actions use scoped context, approved tools, and commit gates.

Scoped context, approved tools, committed action.

Signals update state without losing causal order.

Signals update state in recorded causal order.

Timed and signal-based work resumes from saved state.

Durable functions save state before timers or signals pause execution.

Agent actions pass the configured permission gate.

Actions stay inside the Shape and commit through the gate.

Product nodes resolve into task context.

Configured product nodes can resolve into current agent context.

Shape scopes each task.

A Shape resolves current customer state, permissions, and allowed next steps.

Each task receives scoped context.

MaxQ assembles current state, workflow position, and permissions for the task.

High-impact actions require permission before commit.

Every high-impact move meets the permission gate first.

Signals refresh stale task context.

Signals refresh context before stale work can spread.

Runtime events update state, resume work, and assemble task context.

The runtime records events, commits state changes, resumes work, and scopes task data.

Deterministic paths remain available for replay.

Deterministic transition paths remain available for inspection and replay.

Product state persists across sessions and agents.

Product state stays intact across sessions, agents, and surfaces.

Interrupted work resumes from checkpoints.

Interrupted execution returns from durable checkpoints.

Agents receive current state and scoped permissions.

Each agent run receives current state, scoped permissions, and allowed actions.

Critical actions pass approval and commit gates.

Critical actions require approval before the runtime commits the transition.

One core, five products.

The five HIKOND products listed here use the same state, workflow, and permission primitives.

The runtime checkpoints work and gates state writes.

The runtime preserves state, resumes checkpointed work, assembles current task context, and gates writes by permission.