EVIDENCE LANE / REFERENCE
Troubleshooting
Identify which state failed before retrying the work.
The observer is disconnected
Studio may display its last received state. Open it from the supported launcher and inspect the persistent engine and client connection. A visible window is not proof that the selected project is bound.
A capability is listed but not ready
Read the selected operation’s requirements, configured provider, dependencies and measured readiness. Check required credentials, licensing, models and device compatibility. Catalogue presence alone is not execution proof.
Sources or results look stale
Compare the selected source identities and current bytes with the recorded snapshot. Use source refresh for changed material. Historical receipts do not reverify today’s files.
An operation has uncertain effects
Preserve the operation identity and reported observations. Use the owning result/recovery path to determine committed effects before replay. An uncertain operation is not an automatic retry.
The Plan changed while work was running
Read the current revision and the worker’s task contract. Semantic steers checkpoint affected work; stale worker completion must not be promoted into the new Plan.