Supported Behavior | Midfleet Docs

Capability matrix

Capability	Assurance	Control point	Failure behavior
Workflow resolution and preflight	Enforced	Midfleet Hub	Returns typed blockers without creating a draft, invocation, or run.
Invocation idempotency	Enforced	Workflow API	Replays the original logical request; changed content under the same key conflicts.
Stage ownership and allowed transitions	Enforced on the Hub-routed path	Workflow and handoff lifecycle	Rejects a transition that is absent from the current allowed actions.
Required evidence before completion	Enforced on the Hub-routed path	Governance and completion gate	Completion remains blocked until required evidence is present and accepted.
Agent heartbeat	Observed	Agent presence telemetry	Stale presence is unavailable or unknown, not proof of workflow failure.
Agent-reported progress	Attested	Agent or adapter report	Consequential claims require corroborating repository, CI, review, or deployment evidence.
Direct repository or cloud action outside Midfleet	Uncovered	External system	Midfleet cannot reject or roll back an action that bypasses its supported control point.

Interpret the matrix narrowly

An assurance level applies to the named action and control point, not to the whole product or surrounding infrastructure. A visible claim coordinates ownership but does not lock a file. A green heartbeat proves recent liveness but not progress. A recorded CI URL proves that a reference was attached, not that the test was correctly designed.

Review the boundary before automation

Identify the action that can cause impact.
Name the Midfleet or external control point that can prevent it.
Define the failure behavior and the owner of recovery.
Choose an authoritative evidence source.
Keep uncovered actions under explicit external ownership.