VALUE.md -

<the opening scene that names your build trap - one short paragraph, 3-6 sentences. Delete this line if you skip the opening.>

Value Statement

<one sentence: [project] gives [recipient] [the value]; [recipient] gives back [what you observe them offering - describe the exchange shape, do NOT promise their behavior].>

Q1: Who it's for?

<the one specific person this is for - one sentence>

Q2: What changes for them?

Before: <what the recipient is stuck with today - one sentence>

After: <what they now do or measure differently that they couldn't before - one sentence, verb on their side>

Q3: How will you know the change happened for them?

<one short paragraph - 2 or 3 sentences. What proof would tell you the change landed, and how a stranger could check it without you?>

Breaks if: <the one observation that would prove the promise false - a number over a window is strongest>

Check: <Inspect | Demonstrate | Test | Analyze | Judge | Field - pick the cheapest honest one, and say where the result lives (a file, a dashboard, a CI job, a survey, paired runs)>

Status: <Proposed | Promised | Proven | Broken>. <one short sentence on why this status, and what would move it to the next state>

Last verified: <YYYY-MM-DD or "not yet"> · Re-verify by: <YYYY-MM-DD - empty if status is not Proven>

Promises

P1 - <one promise, one screen - start with "you", not "the system">

Status: <Proposed | Promised | Proven | Broken> · Recipient:

Last verified: <YYYY-MM-DD or "not yet"> · Re-verify by: <YYYY-MM-DD - empty if status is not Proven>

<the promise, from the recipient's seat - what they get, in their own words>

Breaks if: <the observation that would prove this broke - an event a stranger could check without asking you>

Check: -

What we don't promise

What we don't break