# Vedokrok Solution Pack — Clarify an Unclear Work Task

Task from me: [PASTE THE REAL TASK HERE]

Goal: A minimum working brief with a checkable result, facts, assumptions, unknowns, competing explanations and one discriminating next check.
Pack: https://vedokrok.com/downloads/solutions/clarify-unclear-work.md
Readable page: https://vedokrok.com/solutions/clarify-unclear-work

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-0610: Separate known, unknown and assumed states.
- MHC-U-9C0A00000004: Choose a test or question that could prove the working explanation wrong.
- MHC-D-RESEARCH-0362: Hand off the uncertainty, owner and decision boundary rather than a vague status.

Run the pack level by level. Do not jump directly to advice:
Level 0 — Name the requested result — Rewrite the request as an observable result, audience or decision and completion condition.
Level 1 — Separate evidence from guesses — Label facts, assumptions and unknowns before they silently become requirements. [MHC-D-RESEARCH-0610]
Level 2 — Create a real alternative — Keep at least two plausible interpretations or explanations when the uncertainty matters. [MHC-U-9C0A00000004]
Level 3 — Choose a discriminating check — Pick the smallest question, sample or test whose result can change the plan. [MHC-U-9C0A00000004]
Level 4 — Make the handoff executable — Name the owner, time boundary, important uncertainty and what answer would unblock the work. [MHC-D-RESEARCH-0362]
Level 5 — Decide whether to start — Start when the remaining uncertainty no longer changes the next bounded step; otherwise escalate the exact unresolved decision. [MHC-D-RESEARCH-0362]

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 minimum working brief with a checkable result, facts, assumptions, unknowns, competing explanations and one discriminating next check.
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.