UK-based independent AI efficiency projectEvidence before claims · 2026

Token Optimisation

AI efficiency · measured
Discuss a diagnostic

Heartbeat vs Progress: Four Different Workflow Signals

INCIDENT REPORT + SEPARATE CHECK · SCOPE KEPT DISTINCT

Heartbeat vs Progress: Four Different Workflow Signals

A long-scroll visual companion to the article. It summarizes the article’s evidence boundary and method; it does not extend the underlying result.

At a glance

Heartbeat vs Progress: Four Different Workflow SignalsFour-step visual: PROCESS ALIVE?; PROVIDER ACTIVE?; STAGE CHANGED?; VERIFIER ACCEPTED?. The later check did not establish the earlier call’s outcome. The exact earlier duration and result remain unknown.INCIDENT REPORT + SEPARATE CHECK · SCOPE KEPT DISTINCT1PROCESS ALIVE?2PROVIDER ACTIVE?3STAGE CHANGED?4VERIFIER ACCEPTED?Evidence labels and limits travel with the visual.
A heartbeat is evidence about process liveness; it does not by itself establish provider activity, semantic progress, or accepted work.

Evidence in scope

  • User-reported wait: >60 minutes
  • Later bounded check: 120 seconds, succeeded
  • The events are separate

Evidence boundary: The later check did not establish the earlier call’s outcome. The exact earlier duration and result remain unknown.

How to use the diagram

Record independent timestamps for process, provider state, durable stage change, and verifier result.

What this visual explains: A heartbeat is evidence about process liveness; it does not by itself establish provider activity, semantic progress, or accepted work.

What it does not establish

No root cause, production detector accuracy, or universal timeout is measured.

← View article · Return to source article