create-evda 0.1.0

package/templates/hypotheses.md

@@ -0,0 +1,70 @@
+---
+type: ledger
+evda: 1
+created: {{date}}
+---
+
+# Hypothesis Ledger
+
+Claims about the owner of this record, each with where it came from, what would kill it, and what happened when the owner pushed back. Append-only. Falsified entries are kept: the chain is the product.
+
+## The entry
+
+Every entry has exactly this shape. Copy it, fill it, and append it at the end of this file. IDs are sequential and zero-padded to four digits; the next ID is one more than the last entry in the file, and the first is H-0001. Separate entries with a line holding only `---`.
+
+    ### H-0042: <the hypothesis in one line>
+
+    **Status:** open | standing | refined | falsified | retired
+    **Domain:** <a word for the area of life this is about>
+    **Raised:** YYYY-MM-DD, by <the agent | the owner>, in <where>
+    **Supersedes:** H-0041          (omit if none)
+    **Superseded by:** H-0043        (written when it happens, never in advance)
+
+    **Hypothesis:** the claim, stated so that it could be wrong.
+
+    **Origin:** quote. "<the owner's exact words>" (`path/to/where/they said it.md`)
+       or    **Origin:** path. `path/to/the/file.md`
+       or    **Origin:** reasoning: <what it was derived from>   (agent-raised only)
+
+    **Falsifier:** what observation would kill it. If this cannot be written so it could come
+    back false, the hypothesis is not yet a hypothesis and says so.
+
+    **Test:** how it gets checked.
+
+    **Due:** YYYY-MM-DD             (optional, only when a real date exists;
+                                     omit it and the claim is parked, which is normal)
+
+    **Pushback:**
+    - YYYY-MM-DD, the owner: "verbatim" -> what it changed
+
+    **Evidence:**                   (when a finding arrived without the owner)
+    - YYYY-MM-DD: what was found (source)
+
+    **Outcome:** written only when the test resolves. Empty until then, and an empty
+    outcome is a fact about the ledger, not a gap to fill.
+
+One more line, directly after `**Test:**`, and every open entry with a Test has it: `**Due:** YYYY-MM-DD` when the test has a date, or `**Due:** none, because <why no date can exist>` when it genuinely cannot be dated. An open entry with a Test and no Due line is a claim nothing will ever surface, and it is a failure. The file `.evda/due.jsonl` is derived from the Due line and from nothing else; a date that appears only in the prose of a test is invisible to it, and a bare `none` with no reason is a refusal to think.
+
+## Rules, each with the failure it prevents
+
+1. **Never edit a hypothesis in place.** A refinement is a new entry that supersedes. This is the ruling on spec decision #11 (history), made 2026-09-15: append-only, because overwriting destroys the evidence the audit runs on, and he still has to be able to change his mind.
+2. **Origin is one of three kinds, and it says which.** A paraphrased origin cannot settle a later disagreement about what was actually claimed, which is the only thing an origin is for.
+   - `Origin: quote` followed by the owner's verbatim words.
+   - `Origin: path` followed by a file path that must exist.
+   - `Origin: reasoning` followed by what it was derived from. **For a hypothesis the agent raised, and only then.** There is no quote because the owner did not say it, and the hypothesis field is itself the claim being recorded. The grounds must still be named and checkable.
+2b. **Refutation has more than one source, and the entry says which.** The owner pushing back is the common case and the highest-value one, but a hypothesis can also be killed by evidence that arrived on its own.
+   - `Pushback:` the owner's verbatim words.
+   - `Evidence:` a finding from outside the conversation, with its source. H-0028 ("Write with Siri is Apple's dictation product") was refuted by web research on the day it was raised, not by the owner, and the ledger had nowhere to put that.
+   An entry with `Evidence:` and no `Pushback:` is fine and is worth noticing: it is the loop working without the owner having to be present, which is what an always-on record is for.
+3. **A falsifier that cannot come back false is not one.** Same contract as `verify.mjs --expect`. Where one cannot be written, say so on the entry rather than inventing one.
+4. **Pushback is quoted, not summarised.** The correction is the highest-value thing in the ledger and it is the thing most often lost.
+5. **Status `standing` means it was tested and survived. It never means true.** A hypothesis that has not been tested is `open`, not `standing`, and the difference is the whole value of the word.
+   What the first version was protecting is still right and is kept: **nothing in here graduates to a fact.** A standing hypothesis survived one test. It remains falsifiable forever, and a later refutation is a normal outcome rather than a reversal.
+   So: `open` is proposed and untested. `standing` is tested and survived, and therefore carries an Outcome saying what the test found. `falsified` is tested and failed. `refined` is superseded by a sharper version. `retired` is no longer worth testing.
+6. **A falsified hypothesis is kept, never deleted.** The chain is the product; a ledger holding only surviving claims is a ledger that has learned nothing.
+
+The only lines of an existing entry that ever change: `Status`, `Superseded by`, a new bullet under `Pushback` or `Evidence`, and `Outcome` when the test resolves. Everything else is a new entry.
+
+---
+
+<!-- Entries begin below this line. Append at the end; never insert above an existing entry. -->