Skip to main content
Operations begins from persisted truth. A model response, log line, Pub/Sub delivery, or external API response is not by itself proof that a job advanced or an effect succeeded.

Operating model

Understand workers, outboxes, retries, and ownership.

Operational control plane

Use the needs-you inbox, resumable job shells, durable controls, and batch execution.

Recover failures

Classify failures and resume safely.

Audit authority

Trace digest-bound human decisions.

Inspect telemetry

Correlate jobs, operations, traces, and usage.
Use State ownership when two systems disagree and Record and replay when validating idempotency or reproducing an execution.

Bounded autonomy and operational KPIs

Where Harmonia reasons, where deterministic code controls execution, where humans retain authority, and how the demo is measured.

Operational control plane

Operator attention, resumable live state, durable job controls, connector capabilities, and large-batch execution.

Failure and recovery reference

Typed failure categories, retry limits, escalation, replay, and fail-closed recovery behavior.

State ownership and retention

The authoritative owner, scope, lifetime, writers, readers, and retention boundary for every Harmonia state store.

Authenticated record and replay

Capture, sanitize, review, and replay authenticated runs without fabricating evidence or mutating durable state.
Last modified on August 28, 2026