dogfood
definitionLearning a tool by actually using it on a real task, the way a real user would.
A validation modality (d): learning the tool by actually using it on a real task, as a real user. Produces a dogfood finding—the practitioner's real query, the attempts, the ranked results, the finding—which is a record (terminal on creation), not work, and feeds later hos' Think phases. Human-run; a validation modality, not verification.
The Validation Layer. The verification stack answers one question: did we build it right?—does the code match the spec. Every layer in Section 2 serves that question. It is only half of quality.
The other half is validation: did we build the right thing, and is it good? A system can pass every test, clear every linter, and survive cross-agent and human architectural review—and still be the wrong thing, or a right thing that is confusing, unpleasant, or useless in real hands. Verification cannot catch this, because verification measures conformance to a spec, and the spec itself is what validation interrogates.
This is Section 1's thesis extended. The research there—that humans overestimate AI-assisted work—was about correctness. It holds at least as strongly for goodness. An agent reporting "the feature works" is reporting that it ran; it is not reporting that the feature is good, because good is not a property the agent is positioned to judge. Validation is the antidote to overconfidence about goodness, exactly as verification is the antidote to overconfidence about correctness.