Resume from evidence

What you'll do

Prepare an evidence-based restart note for an interrupted synthetic BI task. Distinguish the Analytical Spine qualification workflow from general Agent Spine setup orchestration. Your output identifies the last supported claim, the current gap and one bounded next action.

Start from retained state

A conversation summary is useful context, but it is not the authority for what executed. On resume, inspect the approved project's status and selected receipt history. Identify the current definitions, required scenarios, observation times and any superseding retry or changed dependency.

Do not initialise a new proof over a retained project merely because the agent has lost conversational context. The existing project has its own catalogue, frozen expectations and history. Recreating those artifacts can erase the distinction between a real continuation and an unrelated new exercise.

Keep the two Spine meanings clear

Analytical Spine is the qualification and evidence workflow for the documented source/Fabric/Power BI chain. General Agent Spine setup orchestration concerns repository context and agent workflow setup. Their names are similar, but one cannot substitute for the other's evidence.

A healthy agent-memory setup does not prove a sales measure reconciled. A qualified report query does not prove repository onboarding or agent configuration is complete. Ask which workflow owns the status before treating a summary as an action instruction.

Synthetic resume note
Task: explain the selected Sales report qualification
Last established: retained query observation for the named state
Current gap: new model definition invalidated dependent evidence
Next: inspect the changed binding and plan current observations
Human decision: deployment consent remains pending

Use this structure to make the continuation reviewable. Keep references local and authorised. The academy copy should use synthetic descriptions rather than private paths, run identifiers or screenshots of customer evidence.

Prefer the newest supported state

Suppose yesterday's selected gate passed, then today's retry failed because a required rendered observation was missing. The newer failure supersedes the old success for that retry. A restart that chooses the older green result because it is easier to explain would misrepresent the retained history.

Likewise, a stale atlas or handoff does not become current because an agent reads it today. Follow the observed change and identify the owning producer. The local ledger is not an always-on watcher of every remote asset, so record whether current remote observations have actually been obtained.

Choose one safe next action

Separate local inspection from an effect requiring consent. You may be able to review a definition, explain a mismatch or prepare a current plan while source access remains pending. Make that independent progress without pretending the blocked observation happened.

If a retained file no longer matches its binding, do not edit the receipt or re-sign history. Investigate the original evidence and obtain a new observation through the owning workflow where required. If expectations need review, keep the original lock and identify the explicit new epoch work rather than silently refreezing.

Your expected output is a concise restart note a fresh reviewer can verify. It records what was established, what is historical or stale, what remains unknown and the exact next action. It does not certify a pipeline or authorise a background schedule, deployment or Hosted push merely to restore momentum.

Check your understanding

1. Why is a conversation summary insufficient evidence that an operation completed?
2. How would confusing general Agent Spine setup with Analytical Spine qualification mislead a restart?
3. Which retained result should guide a restart after a newer retry failed?