Type into the four questions below. Your VALUE.md assembles live in the preview. A gate-check tells you what your draft is missing, in plain language. When the gate passes, copy the file and paste it at your project root.
Reads the Standard and the Runbook for the rules this page enforces. The gate-check is a string-match approximation, not the discipline itself. Read the result aloud and hand it to a stranger before you trust it.
The four questions
One short noun phrase. Goes in the file's first line.
One sentence: [project] gives [recipient] [the value]; [recipient] gives back [what you observe them offering].
Two or three sentences. The named person, at a specific moment, hitting the friction your project is meant to change. No counterfactual; just what you watched.
One sentence. A role plus the named individual you observed, or the class plus the observable proxy if the recipient is a population.
One sentence. What the recipient is stuck with today.
One sentence. What they now do or measure differently.
Two or three sentences. The observation a stranger could verify without you. Numbers over a window beat anecdotes.
One observation that would prove the promise false.
Inspect, Demonstrate, Test, Analyze, Judge, or Field. Pick the cheapest honest one and say where the result lives.
Things a stakeholder might want, that you deliberately won't do.
Counter-metric, threshold, re-evaluate-trigger - concrete and breakable.
Your VALUE.md
Updates as you type. Markdown only; nothing leaves this browser.
VALUE.md
(start typing above)
Six-part gate
A string-match approximation of the gate in the Standard. Catches the obvious failures; can't judge whether your Q1 is the right recipient. Use this as a draft check, not as the discipline.
Passing all six does not mean the file is right. It means it is shaped correctly enough to hand to a stranger. Read the stranger-test prompt next.