Mock engagement: discovery

Overview

Module	field.01 · practice · docs · Pass 11 · 1 to 2 h
You build	docs/engagement/discovery.md
Tests	course/tests/field.01 (named below, with why each exists)
Needs	none
Used by	no code call site; this is an independent artifact
Milestone	MS-P11

Key Takeaways

• Tie each claim to the exact platform evidence that Mock engagement: discovery produces.
• State the owner, success condition, and recovery action before declaring the work complete.
• Record unresolved assumptions so the next review can test them.

How to work this chapter

ol start field.01
ol tests field.01
ol check field.01

---

1. Why now

A useful engagement begins with the customer’s operating problem and decision process, not with a product tour. Discovery establishes context before anyone promises a solution.

2. Principles

Ask open questions, separate stated symptoms from measured impact, identify stakeholders and data restrictions, and agree on a written definition of success.

3. Worked example

Interview a mock platform team reporting slow inference. Ask for request mix, baseline, users affected, error budget, deployment constraints, and acceptable evidence. Reflect back the problem and ask them to correct your summary.

4. The artifact and its check

Test	KIND	Checks	Why it matters downstream
test_artifact_paths_are_declared	artifact	Confirms the submitted paths and required evidence exist, so a plausible narrative cannot pass without the reviewable deliverable.

5. Pitfalls

#	Pitfall	Symptom	Caught by
1	The deliverable records a conclusion without its customer evidence	Another engineer cannot reproduce the sizing or recommendation.	test_artifact_paths_are_declared
2	An assumption is written as a measured fact	The engagement plan can promise capacity or security the system has not demonstrated.	test_artifact_paths_are_declared
3	The next owner and decision gate are missing	Work stalls at handoff even when the technical work is complete.	test_artifact_paths_are_declared

6. Where it’s used next

Direction	Module	Connection
Back	craft.09	Read this declared prerequisite before producing the artifact; use it to verify the relevant contract or evidence.
Back	review.03	Read this declared prerequisite before producing the artifact; use it to verify the relevant contract or evidence.

Going further

Resource	What to inspect
Mock engagement sequence	Carry the evidence and open decisions into the next customer-facing artifact in the sequence.