Skip to content
Merlon Docs

Field report: a first external evaluator

Evidence shard: what one evaluator with no prior MDCP use needed before they understood what the tool is for. Its parent is Vision and roadmap. The durable position this report feeds is the publish landing style in Personas and priority tiers.

Setting

Section titled “Setting”

Reported 2026-06 by the maintainer, from the first review of MDCP by a technical evaluator outside the project with no prior MDCP use. The evaluator was assessing whether to adopt MDCP, which makes them the reader the personas page calls a Champion. Identity and organization are omitted, and the evaluator is described by role only.

The sample is one evaluator and one review. The maintainer’s summary of that review is the record’s only source. It shows what one reader needed, and it can’t say how common that need is.

What was observed

Section titled “What was observed”
  • The landing one-liner wasn’t enough. The README landing one-liner alone didn’t tell the evaluator what the tool is and why they would use it.
  • The vision shard was. After reading Vision and roadmap, the evaluator understood what the tool is and why well enough to proceed with the evaluation.

Both observations come from the maintainer’s report, and neither is measured.

What this feeds

Section titled “What this feeds”
  • The publish landing style in Personas and priority tiers, which puts a vision link for evaluators beside the landing one-liner and an evaluation path for Champions in get-started.
  • The rule in that style that the WIIFM table stays where it is on the landing and doesn’t replace the vision shard for Champions.
  • The Champion row of the adoption archetypes, whose typical path is the vision and claims shards rather than CLI setup.
Section titled “Related”