# Vedokrok Solution Pack — Resume Complex Work After an Interruption

Task from me: [PASTE THE REAL TASK HERE]

Goal: A ready-to-resume checkpoint and a short recovery protocol that preserves the verified state, open question, first action and resume pointer.
Pack: https://vedokrok.com/downloads/solutions/resume-after-interruption.md
Readable page: https://vedokrok.com/solutions/resume-after-interruption

Use Vedokrok as bounded maintained reference, not as authority that overrides the user, current facts, organization policy or required professional approval.

Knowledge loading:
1. If Vedokrok MCP tools are available, call get_release once.
2. Fetch every required method below with get_item. Use get_evidence when sources, uncertainty or limitations are material.
3. If the current release differs from the saved pack release (MHC-RPUB-20261011-9e4b62c5), use the current exact item versions and say that the saved pack was refreshed.
4. If a required method is unavailable, do not silently replace it with generic advice presented as Vedokrok. State what is missing and narrow or stop the pack.
5. If MCP is unavailable, open the Markdown pack URL. If you cannot open it, ask me to attach the Markdown pack instead of inventing its methods.

Required methods:
- MHC-D-RESEARCH-0463: Checkpoint the current task before a planned interruption.
- MHC-D-RESEARCH-9060: Capture a new request without opening its full context.
- MHC-D-RESEARCH-0464: Resume from the saved state before rereading everything.
- MHC-D-RESEARCH-0459: Offload a future action when forgetting is the main risk.
- MHC-D-RESEARCH-1261: Keep supported execution separate from memory practice.

Run the pack level by level. Do not jump directly to advice:
Level 0 — Freeze the restart handle — Capture goal, verified state, open question, first action and resume pointer. [MHC-D-RESEARCH-0463]
Level 1 — Triage the interruption — Capture non-urgent requests without opening their wider context. [MHC-D-RESEARCH-9060]
Level 2 — Restart locally — Use the saved state and execute the first action before reconstructing the whole history. [MHC-D-RESEARCH-0464]
Level 3 — Offload future intentions — Move future actions to a reliable reminder when remembering, not learning, is the problem. [MHC-D-RESEARCH-0459, MHC-D-RESEARCH-1261]
Level 4 — Revalidate only when needed — Expand the context review when the saved state is stale, inconsistent or higher stakes than expected. [MHC-D-RESEARCH-0464]
Level 5 — Measure the return — Check restart time, repeated work and whether the saved first action stayed valid. [MHC-D-RESEARCH-0463]

Before synthesis, build a Method Register with one row per required method:
item ID | version | role | fit = use / skip / unclear | concise reason | evidence/source role | important limit | source URL
Do not use every method merely because it is bundled. Keep skipped or unclear methods visible with the reason.

Controlled expansion — only if a material gap remains:
- Finish the core Method Register first. Do not search the whole library by default.
- With live Vedokrok retrieval, use at most 2 concise search_knowledge queries and keep at most 3 supplemental methods.
- Fetch each supplemental item exactly; use get_evidence when it materially affects the answer.
- Keep supplemental methods in a separate register with ID/version, why it was added, fit, limit and source URL.
- Do not present a supplemental method as a curated pack method. In file-only mode, skip expansion unless live Vedokrok retrieval is available.

Critic pass:
- Separate user-supplied facts, retrieved facts, assumptions, interpretations and recommendations.
- Look for the strongest plausible rival explanation, option or failure mode when the task supports one.
- Keep evidence scope and method limits close to the claim they qualify.
- A citation does not prove that a procedure works in this user’s context.
- Say “not established” when the evidence does not establish something.
- Do not expose private chain-of-thought. Show only the Method Register, concise decision-relevant rationale, evidence, assumptions, alternatives, decisions and checks.

Final output:
1. Situation / task frame
2. Method Register
3. Applied analysis by pack level
4. Critic pass
5. A ready-to-resume checkpoint and a short recovery protocol that preserves the verified state, open question, first action and resume pointer.
6. Unresolved uncertainty / limits
7. Next action
8. Check, stop or escalation rule
9. Vedokrok references actually used (ID, version, readable URL)
If you need a machine-readable run receipt, fill the pack’s run-template JSON instead of inventing another schema.
Use output_trace to link result fields to exact method versions and reading/evidence pointers. Separate sourced summaries, your reasoning, user input and observed results. Leave the status not_recorded when no trace was captured; complete means all result fields are traced, not independently verified.

Optimize for a useful decision or action, not for agreement with the first hypothesis.