{
  "schemaVersion": 1,
  "site": "https://odin-labs-ai.github.io/odin-rnd/",
  "about": "Every record this site publishes, newest first. A date is the record's own date, or the day it was first published in this repository.",
  "updates": [
    {
      "key": "exp-021-results",
      "experiment": "EXP 021",
      "title": "Kill the database mid-session, does anyone notice?",
      "kind": "Results",
      "text": "Single host: MongoDB fits four write-outage and two acknowledgement-gap scenarios; PostgreSQL two by feed gate. No acknowledged writes lost; no overall winner. Strict-ack and disturbance uncertainties remain.",
      "href": "journal/failover-results.html",
      "source": "data/failover/results.json",
      "date": "2026-11-11"
    },
    {
      "key": "exp-021-amendment-03",
      "experiment": "EXP 021",
      "title": "Kill the database mid-session, does anyone notice?",
      "kind": "Amendment",
      "text": "The counted run is complete: 48 discards reconciled; strict acknowledgements and one disturbance window remain unresolved.",
      "href": "journal/failover-results.html",
      "source": "data/failover/amendment-03.json",
      "date": "2026-11-11"
    },
    {
      "key": "exp-020-amendment-05",
      "experiment": "EXP 020",
      "title": "MongoDB on its home ground: where does it fit Odin?",
      "kind": "Amendment",
      "text": "S2's run record: the pause, all 13 discards and the report's hashes.",
      "href": "journal/mongodb-home-ground-pre-registration.html",
      "source": "data/mongodb-home-ground/amendment-05.json",
      "date": "2026-11-09"
    },
    {
      "key": "exp-021-amendment-02",
      "experiment": "EXP 021",
      "title": "Kill the database mid-session, does anyone notice?",
      "kind": "Amendment",
      "text": "The pre-registered single-copy rule fired, so the compared PostgreSQL variants are strict; ten runner fixes are recorded.",
      "href": "journal/failover-results.html",
      "source": "data/failover/amendment-02.json",
      "date": "2026-11-08"
    },
    {
      "key": "exp-020-amendment-04",
      "experiment": "EXP 020",
      "title": "MongoDB on its home ground: where does it fit Odin?",
      "kind": "Amendment",
      "text": "Both advocates settle nine readings of the S2 rules before the verdict; both veto item 8, so the report checks the disturbance windows itself.",
      "href": "journal/mongodb-home-ground-pre-registration.html",
      "source": "data/mongodb-home-ground/amendment-04.json",
      "date": "2026-10-28"
    },
    {
      "key": "exp-021-amendment-01",
      "experiment": "EXP 021",
      "title": "Kill the database mid-session, does anyone notice?",
      "kind": "Amendment",
      "text": "The runner protocol and the design draft are published.",
      "href": "journal/failover-results.html",
      "source": "data/failover/amendment-01.json",
      "date": "2026-10-25"
    },
    {
      "key": "exp-020-amendment-01",
      "experiment": "EXP 020",
      "title": "MongoDB on its home ground: where does it fit Odin?",
      "kind": "Amendment",
      "text": "S2's runner changes, the rule for which cells count, and the nine discarded cells are published.",
      "href": "journal/mongodb-home-ground-pre-registration.html",
      "source": "data/mongodb-home-ground/amendment-01.json",
      "date": "2026-10-25"
    },
    {
      "key": "exp-020-amendment-02",
      "experiment": "EXP 020",
      "title": "MongoDB on its home ground: where does it fit Odin?",
      "kind": "Amendment",
      "text": "S2 compares MongoDB with one PostgreSQL variant per scale, chosen once.",
      "href": "journal/mongodb-home-ground-pre-registration.html",
      "source": "data/mongodb-home-ground/amendment-02.json",
      "date": "2026-10-25"
    },
    {
      "key": "exp-020-amendment-03",
      "experiment": "EXP 020",
      "title": "MongoDB on its home ground: where does it fit Odin?",
      "kind": "Amendment",
      "text": "Both advocates accept the S2 pairing rule; the decision paragraph is rewritten as they required.",
      "href": "journal/mongodb-home-ground-pre-registration.html",
      "source": "data/mongodb-home-ground/amendment-03.json",
      "date": "2026-10-25"
    },
    {
      "key": "exp-021-preregistration",
      "experiment": "EXP 021",
      "title": "Kill the database mid-session, does anyone notice?",
      "kind": "Pre-registered",
      "text": "The question and how it will be scored were published before any counted run.",
      "href": "journal/failover-results.html",
      "source": "data/failover/preregistration.json",
      "date": "2026-10-25"
    },
    {
      "key": "exp-020-preregistration",
      "experiment": "EXP 020",
      "title": "MongoDB on its home ground: where does it fit Odin?",
      "kind": "Pre-registered",
      "text": "The question and how it will be scored were published before any counted run.",
      "href": "journal/mongodb-home-ground-pre-registration.html",
      "source": "data/mongodb-home-ground/preregistration.json",
      "date": "2026-10-25"
    },
    {
      "key": "note-mongodb-ai-context",
      "experiment": null,
      "title": "When a cached yes answers the opposite question",
      "kind": "Field note",
      "text": "We changed the rules behind saved AI answers and reworded questions so yes meant the opposite. Versions kept old answers out, but similar wording still caused wrong replies.",
      "href": "journal/mongodb-ai-context.html",
      "source": "journal/mongodb-ai-context.html",
      "date": "2026-10-25"
    },
    {
      "key": "note-mongodb-ai-ecosystem",
      "experiment": null,
      "title": "MongoDB beyond JSON: agents, memory and models",
      "kind": "Field note",
      "text": "We tested MongoDB for agents and memory with real Voyage embeddings. Both databases found the same nearest results; tools can repeat after a crash and cached answers can outlive a policy change.",
      "href": "journal/mongodb-ai-ecosystem.html",
      "source": "journal/mongodb-ai-ecosystem.html",
      "date": "2026-10-24"
    },
    {
      "key": "exp-019-results",
      "experiment": "EXP 019",
      "title": "Routing by our own rulebook, measured again: three fresh runs of the routed arm",
      "kind": "Results",
      "text": "Pre-registered verdict: routing beats always-Opus, within a wide replicate allowance, and does not beat always-Luna.",
      "href": "journal/router-arm-fresh-results.html",
      "source": "data/router-arm-fresh/results.json",
      "date": "2026-10-23"
    },
    {
      "key": "exp-018-results",
      "experiment": "EXP 018",
      "title": "Does routing by our own rulebook beat one fixed model on real tasks?",
      "kind": "Results",
      "text": "Eight real coding tasks, three arms, three runs each, scored by the share of hidden test cases fixed (no task was fully solved). Per case fixed, a table copied from our routing rule paid 13.3 cents (61% of cases), always Opus 5.5 paid 24.7 (65%) and always GPT-6 Luna paid 4.3 (52%). The pre-registered verdict is incomplete: one routed cell hit its spend stop.",
      "href": "journal/router-arm-results.html",
      "source": "data/router-arm/results.json",
      "date": "2026-10-23"
    },
    {
      "key": "exp-017-results",
      "experiment": "EXP 017",
      "title": "What does a defect caught in review cost, model by model?",
      "kind": "Results",
      "text": "Four models on one tool-free review seat caught between 26 and 31 of 60 defects, all within noise, at 0.06 to 8.3 cents a review. gpt-oss-120b, MiniMax M3.1 Flash and Claude Opus 5.5 are on the pre-registered frontier; Claude Sonnet 5.5 is not.",
      "href": "journal/review-frontier-results.html",
      "source": "data/review-frontier/results.json",
      "date": "2026-10-23"
    },
    {
      "key": "exp-016-results",
      "experiment": "EXP 016",
      "title": "Does the same model cost the same through every broker?",
      "kind": "Results",
      "text": "Measured on 720 identical calls: two brokers billed exactly list price for Claude Sonnet 5.5 and GPT-4o mini, the third 10% above it on both, a spread of 1.10 against a pre-registered bar of 1.05. No broker served a different model.",
      "href": "journal/broker-same-model-results.html",
      "source": "data/broker-same-model/results.json",
      "date": "2026-10-23"
    },
    {
      "key": "exp-016-amendment-01",
      "experiment": "EXP 016",
      "title": "Does the same model cost the same through every broker?",
      "kind": "Amendment",
      "text": "EXP 016's results are published with the three brokers shown as letters, not names. After this record was frozen, the lab recorded each broker's published terms (site/data/provider-terms.json, 2026-10-23). Two of the three brokers have a clause the lab owner has not yet ruled on: one bars use of its trade names without consent, the other bars systematically collecting benchmarks for competitive purposes. The lab owner decided on 2026-10-23 to publish EXP 016's results without saying which broker is which. This amendment changes only how the results are labelled. Nothing measured, counted or decided changes.",
      "href": "journal/broker-same-model-results.html",
      "source": "data/broker-same-model/amendment-01.json",
      "date": "2026-10-23"
    },
    {
      "key": "exp-019-preregistration",
      "experiment": "EXP 019",
      "title": "Routing by our own rulebook, measured again: three fresh runs of the routed arm",
      "kind": "Pre-registered",
      "text": "The question and how it will be scored were published before any counted run.",
      "href": "journal/router-arm-fresh-results.html",
      "source": "data/router-arm-fresh/preregistration.json",
      "date": "2026-10-23"
    },
    {
      "key": "exp-018-preregistration",
      "experiment": "EXP 018",
      "title": "Does routing by our own rulebook beat one fixed model on real tasks?",
      "kind": "Pre-registered",
      "text": "The question and how it will be scored were published before any counted run.",
      "href": "journal/router-arm-results.html",
      "source": "data/router-arm/preregistration.json",
      "date": "2026-10-23"
    },
    {
      "key": "exp-017-preregistration",
      "experiment": "EXP 017",
      "title": "What does a defect caught in review cost, model by model?",
      "kind": "Pre-registered",
      "text": "The question and how it will be scored were published before any counted run.",
      "href": "journal/review-frontier-results.html",
      "source": "data/review-frontier/preregistration.json",
      "date": "2026-10-23"
    },
    {
      "key": "exp-016-preregistration",
      "experiment": "EXP 016",
      "title": "Does the same model cost the same through every broker?",
      "kind": "Pre-registered",
      "text": "The question and how it will be scored were published before any counted run.",
      "href": "journal/broker-same-model-results.html",
      "source": "data/broker-same-model/preregistration.json",
      "date": "2026-10-23"
    },
    {
      "key": "exp-015-preregistration",
      "experiment": "EXP 015",
      "title": "Does Odin's cost estimate match what the brokers bill?",
      "kind": "Pre-registered",
      "text": "The question and how it will be scored were published before any counted run.",
      "href": "data/telemetry-truth/preregistration.json",
      "source": "data/telemetry-truth/preregistration.json",
      "date": "2026-10-23"
    },
    {
      "key": "note-broker-same-model-results",
      "experiment": null,
      "title": "EXP 016: Does the same model cost the same through every broker?",
      "kind": "Field note",
      "text": "Almost. Measured on 720 identical calls: two brokers billed exactly list price for Claude Sonnet 5.5 and GPT-4o mini, the third 10% above it on both, a spread of 1.10 against a pre-registered bar of 1.05. No broker served a different model.",
      "href": "journal/broker-same-model-results.html",
      "source": "journal/broker-same-model-results.html",
      "date": "2026-10-23"
    },
    {
      "key": "note-review-frontier-results",
      "experiment": null,
      "title": "EXP 017: What does a defect caught in review cost, model by model?",
      "kind": "Field note",
      "text": "Four models on one tool-free review seat caught between 26 and 31 of 60 defects, all within noise, at 0.06 to 8.3 cents a review. gpt-oss-120b, MiniMax M3.1 Flash and Claude Opus 5.5 are on the pre-registered frontier; Claude Sonnet 5.5 is not.",
      "href": "journal/review-frontier-results.html",
      "source": "journal/review-frontier-results.html",
      "date": "2026-10-23"
    },
    {
      "key": "note-router-arm-fresh-results",
      "experiment": null,
      "title": "EXP 019: Routing by our own rulebook, measured again",
      "kind": "Field note",
      "text": "Three fresh, complete runs of the routed arm on the same eight tasks, scored by the share of hidden test cases fixed. Routing paid 14.3 cents per case fixed (57% of cases), against EXP 018's 24.7 for always-Opus (65%) and 4.3 for always-Luna (52%). Pre-registered verdict: routing beats always-Opus, within a wide replicate allowance, and does not beat always-Luna.",
      "href": "journal/router-arm-fresh-results.html",
      "source": "journal/router-arm-fresh-results.html",
      "date": "2026-10-23"
    },
    {
      "key": "note-router-arm-results",
      "experiment": null,
      "title": "EXP 018: Does routing by our own rulebook beat one fixed model on real tasks?",
      "kind": "Field note",
      "text": "Eight real coding tasks, three arms, three runs each, scored by the share of hidden test cases fixed (no task was fully solved). Per case fixed, a table copied from our routing rule paid 13.3 cents (61% of cases), always Opus 5.5 paid 24.7 (65%) and always GPT-6 Luna paid 4.3 (52%). The pre-registered verdict is incomplete: one routed cell hit its spend stop.",
      "href": "journal/router-arm-results.html",
      "source": "journal/router-arm-results.html",
      "date": "2026-10-23"
    },
    {
      "key": "exp-012-results",
      "experiment": "EXP 012",
      "title": "Can a reviewer talk itself out of its false alarms?",
      "kind": "Results",
      "text": "No. Asked to name a concrete failing input for every finding or drop it, MiniMax M3.1 Flash kept 249 of 269 of its own findings. False alarms stayed at 20 and 22 of 30 clean changes, against a pre-registered bar of 2.",
      "href": "journal/self-verify-results.html",
      "source": "data/self-verify/results.json",
      "date": "2026-10-22"
    },
    {
      "key": "note-self-verify-results",
      "experiment": null,
      "title": "EXP 012: Can a reviewer talk itself out of its false alarms?",
      "kind": "Field note",
      "text": "No. Asked to name a concrete failing input for every finding or drop it, MiniMax M3.1 Flash kept 249 of 269 of its own findings. False alarms stayed at 20 and 22 of 30 clean changes, against a pre-registered bar of 2.",
      "href": "journal/self-verify-results.html",
      "source": "journal/self-verify-results.html",
      "date": "2026-10-22"
    },
    {
      "key": "exp-012-amendment-01",
      "experiment": "EXP 012",
      "title": "Can a reviewer talk itself out of its false alarms?",
      "kind": "Amendment",
      "text": "The independent review of the frozen commit (FIX-NEEDED, 2026-10-21 20:43Z) found two defects in the frozen runner. (1) The wrapper reads verify-prompt.txt from its own directory, but the record published the prompt one level up, so the published layout could not run. (2) A malformed verify reply such as {\"keep\":[null]} passed the list check, became an empty keep list and turned the verdict into SHIP with no retry and no verifyFailed mark. That contradicts the record's own failure rule, which says a verify failure leaves the alarm standing, and it would bias the result toward the hypothesis.",
      "href": "journal/self-verify-results.html",
      "source": "data/self-verify/amendment-01.json",
      "date": "2026-10-21"
    },
    {
      "key": "exp-012-preregistration",
      "experiment": "EXP 012",
      "title": "Can a reviewer talk itself out of its false alarms?",
      "kind": "Pre-registered",
      "text": "The question and how it will be scored were published before any counted run.",
      "href": "journal/self-verify-results.html",
      "source": "data/self-verify/preregistration.json",
      "date": "2026-10-21"
    },
    {
      "key": "note-flash-on-the-review-bench",
      "experiment": null,
      "title": "A free model on our review bench",
      "kind": "Field note",
      "text": "On a sealed corpus of 30 real defects and 30 clean changes, MiniMax M3.1 Flash's counts sat in Claude Opus's range at about 1.5 cents a review. No reviewer flags few enough clean changes to vote, and an agent-run reviewer can read its own answer key.",
      "href": "journal/flash-on-the-review-bench.html",
      "source": "journal/flash-on-the-review-bench.html",
      "date": "2026-10-21"
    },
    {
      "key": "note-free-model-own-bug-history",
      "experiment": null,
      "title": "Can a free model find real bugs in our private code?",
      "kind": "Field note",
      "text": "On bugs in our private fix history that can be found from the code alone, MiniMax M3.1 Flash's first guess landed within two lines of the fix 63% of the time, against 23% for our current default. Only about 1 in 10 of the small fixes we sampled could be found that way.",
      "href": "journal/free-model-own-bug-history.html",
      "source": "journal/free-model-own-bug-history.html",
      "date": "2026-10-21"
    },
    {
      "key": "note-mongodb-primitive-fit",
      "experiment": null,
      "title": "Where would MongoDB earn a place in Odin?",
      "kind": "Field note",
      "text": "99,000 requests and a separate 19,800-request repeat found two advantages over monolithic JSONB, but none over the stronger PostgreSQL alternatives, for these workloads on one machine. All seventeen outcomes and the durability amendment are retained.",
      "href": "journal/mongodb-primitive-fit.html",
      "source": "journal/mongodb-primitive-fit.html",
      "date": "2026-10-19"
    },
    {
      "key": "note-mongodb-temporal-document-fit",
      "experiment": null,
      "title": "Does flexible workflow data need MongoDB?",
      "kind": "Field note",
      "text": "Both stores passed 20,000 operations, 42 correctness checks and ten evolution suites behind Temporal activities. For this workload, a MongoDB advantage remains unresolved and flexible JSON alone gave no demonstrated reason to switch.",
      "href": "journal/mongodb-temporal-document-fit.html",
      "source": "journal/mongodb-temporal-document-fit.html",
      "date": "2026-10-19"
    },
    {
      "key": "exp-005-erratum-01",
      "experiment": "EXP 005",
      "title": "Jev as a fast gate",
      "kind": "Erratum",
      "text": "Erratum 01: the DOI link for Newcombe (1998) in the pre-registration does not resolve.",
      "href": "journal/jev-as-a-fast-gate.html",
      "source": "data/jev-gate/erratum-01.json",
      "date": "2026-10-11"
    },
    {
      "key": "exp-011-preregistration",
      "experiment": "EXP 011",
      "title": "Where does a model reviewer earn its keep?",
      "kind": "Pre-registered",
      "text": "The question and how it will be scored were published before any counted run.",
      "href": "journal/where-a-model-reviewer-earns-its-keep.html",
      "source": "data/reviewer-keep/preregistration.json",
      "date": "2026-10-11"
    },
    {
      "key": "exp-009-results",
      "experiment": "EXP 009",
      "title": "Unload leaves no trace",
      "kind": "Results",
      "text": "P1 refuted: 1 of 400 H1 trials diverged from R0 (95% Wilson upper bound 1.40%). P2 supported: 0 silent-inert and 0 false-inactive kernel configurations of 120. All 5 validity gates passed, so the record is informative.",
      "href": "journal/composable-harness-results.html",
      "source": "data/composable-harness/results.json",
      "date": "2026-10-10"
    },
    {
      "key": "exp-008-amendment-02",
      "experiment": "EXP 008",
      "title": "Hand over the cache, not the text",
      "kind": "Amendment",
      "text": "Amendment 02: the zero-prefill counter fix and a fresh counted run.",
      "href": "journal/latent-handoff-pre-registration.html",
      "source": "data/latent-handoff/amendment-02.json",
      "date": "2026-10-09"
    },
    {
      "key": "exp-007-results",
      "experiment": "EXP 007",
      "title": "Which of your gate's rules need a model at all?",
      "kind": "Results",
      "text": "Pre-registered; measured 7 Oct 2026: the premise is refuted.",
      "href": "journal/which-rules-need-a-model.html#results",
      "source": "data/blueprint-floor/results.json",
      "date": "2026-10-08"
    },
    {
      "key": "exp-007-amendment-01",
      "experiment": "EXP 007",
      "title": "Which of your gate's rules need a model at all?",
      "kind": "Amendment",
      "text": "Amendment 01: one re-call for the translator calls the client's spend limit refused.",
      "href": "journal/which-rules-need-a-model.html#results",
      "source": "data/blueprint-floor/amendment-01.json",
      "date": "2026-10-07"
    },
    {
      "key": "exp-009-preregistration",
      "experiment": "EXP 009",
      "title": "Unload leaves no trace",
      "kind": "Pre-registered",
      "text": "The question and how it will be scored were published before any counted run.",
      "href": "journal/composable-harness-results.html",
      "source": "data/composable-harness/preregistration.json",
      "date": "2026-10-07"
    },
    {
      "key": "exp-007-preregistration",
      "experiment": "EXP 007",
      "title": "Which of your gate's rules need a model at all?",
      "kind": "Pre-registered",
      "text": "The question and how it will be scored were published before any counted run.",
      "href": "journal/which-rules-need-a-model.html#results",
      "source": "data/blueprint-floor/preregistration.json",
      "date": "2026-10-03"
    },
    {
      "key": "exp-008-amendment-01",
      "experiment": "EXP 008",
      "title": "Hand over the cache, not the text",
      "kind": "Amendment",
      "text": "Amendment 01: the confirmatory analysis script.",
      "href": "journal/latent-handoff-pre-registration.html",
      "source": "data/latent-handoff/amendment-01.json",
      "date": "2026-10-02"
    },
    {
      "key": "exp-008-preregistration",
      "experiment": "EXP 008",
      "title": "Hand over the cache, not the text",
      "kind": "Pre-registered",
      "text": "The question and how it will be scored were published before any counted run.",
      "href": "journal/latent-handoff-pre-registration.html",
      "source": "data/latent-handoff/preregistration.json",
      "date": "2026-10-02"
    },
    {
      "key": "exp-006-results",
      "experiment": "EXP 006",
      "title": "nina reviews the change",
      "kind": "Results",
      "text": "Pre-registered; measured 01 OCT 2026: bar met, nina in the spotlight. Amended 01 Oct 2026, before any counted run.",
      "href": "journal/nina-reviews-the-change.html#amendment-01",
      "source": "data/nina-changes/results.json",
      "date": "2026-10-01"
    },
    {
      "key": "exp-006-amendment-01",
      "experiment": "EXP 006",
      "title": "nina reviews the change",
      "kind": "Amendment",
      "text": "Amendment 01: a digest is not a restricted term, a compound git call counts, and the client's built-in reads are disclosed.",
      "href": "journal/nina-reviews-the-change.html#amendment-01",
      "source": "data/nina-changes/amendment-01.json",
      "date": "2026-10-01"
    },
    {
      "key": "exp-006-preregistration",
      "experiment": "EXP 006",
      "title": "nina reviews the change",
      "kind": "Pre-registered",
      "text": "The question and how it will be scored were published before any counted run.",
      "href": "journal/nina-reviews-the-change.html#amendment-01",
      "source": "data/nina-changes/preregistration.json",
      "date": "2026-09-30"
    },
    {
      "key": "exp-005-results",
      "experiment": "EXP 005",
      "title": "Jev as a fast gate",
      "kind": "Results",
      "text": "Pre-registered; measured 29 Sep 2026: the claim is refuted.",
      "href": "journal/jev-as-a-fast-gate.html",
      "source": "data/jev-gate/results.json",
      "date": "2026-09-29"
    },
    {
      "key": "exp-005-amendment-01",
      "experiment": "EXP 005",
      "title": "Jev as a fast gate",
      "kind": "Amendment",
      "text": "Amendment 01: nina 0.34.0 and a pre-registered spotlight bar.",
      "href": "journal/jev-as-a-fast-gate.html",
      "source": "data/jev-gate/amendment-01.json",
      "date": "2026-09-28"
    },
    {
      "key": "exp-005-amendment-02",
      "experiment": "EXP 005",
      "title": "Jev as a fast gate",
      "kind": "Amendment",
      "text": "Amendment 02: the reviewer's file and git tools are fenced to its workspace, in two layers.",
      "href": "journal/jev-as-a-fast-gate.html",
      "source": "data/jev-gate/amendment-02.json",
      "date": "2026-09-28"
    },
    {
      "key": "exp-005-preregistration",
      "experiment": "EXP 005",
      "title": "Jev as a fast gate",
      "kind": "Pre-registered",
      "text": "The question and how it will be scored were published before any counted run.",
      "href": "journal/jev-as-a-fast-gate.html",
      "source": "data/jev-gate/preregistration.json",
      "date": "2026-09-28"
    },
    {
      "key": "tool-laya-browser",
      "experiment": null,
      "title": "Laya in your browser",
      "kind": "Tool",
      "text": "Run Laya, an open-weight typed-decision model, in your browser after a model download. Read its probabilities for a typed question. Three hand-written cases checked parity with the reference; they did not measure accuracy or calibration. Inference runs on your device without an account or API key.",
      "href": "projects/laya-browser/",
      "source": "projects/laya-browser/",
      "date": "2026-09-25"
    },
    {
      "key": "exp-004-measured",
      "experiment": "EXP 004",
      "title": "System-1 decisions without lock-in: Jev vs open-weight Laya",
      "kind": "Measured",
      "text": "Measured on one laptop, 48 hand-written rows.",
      "href": "journal/system-1-decisions-without-lock-in.html",
      "source": "data/laya-vs-jev/manifest.json",
      "date": "2026-09-24"
    },
    {
      "key": "exp-001-003-recorded",
      "experiment": "EXP 001–003",
      "title": "Three blueprint recipes",
      "kind": "Recorded",
      "text": "Each recipe applies one unchanged architectural rule to a conforming tree and to a deliberately drifted tree; the engine scored every conforming tree GREEN and every drifted tree RED.",
      "href": "experiments/#bench",
      "source": "data/experiments.json",
      "date": "2026-09-23"
    },
    {
      "key": "tool-ci-witness",
      "experiment": null,
      "title": "CI Witness",
      "kind": "Tool",
      "text": "Turn an environment-sensitive failure into an inspectable comparison: the failing assertion, a controlled reproduction and a correction that keeps the agreed checks.",
      "href": "projects/ci-witness/",
      "source": "projects/ci-witness/",
      "date": "2026-09-23"
    },
    {
      "key": "tool-migration-witness",
      "experiment": null,
      "title": "Migration Witness",
      "kind": "Tool",
      "text": "Make the acceptance decision explicit: compare the old and new component against examples you approve, with intentional changes recorded separately.",
      "href": "projects/migration-witness/",
      "source": "projects/migration-witness/",
      "date": "2026-09-23"
    },
    {
      "key": "tool-test-witness",
      "experiment": null,
      "title": "Test Witness",
      "kind": "Tool",
      "text": "A passing suite can miss a broken calculation. Inspect whether tests expose specified defects before you rely on their green result.",
      "href": "projects/test-witness/",
      "source": "projects/test-witness/",
      "date": "2026-09-23"
    },
    {
      "key": "note-a-passing-pipeline",
      "experiment": null,
      "title": "A passing pipeline was not yet a verified release.",
      "kind": "Field note",
      "text": "What a missing coverage report taught us about making “done” explainable.",
      "href": "journal/a-passing-pipeline.html",
      "source": "journal/a-passing-pipeline.html",
      "date": "2026-09-07"
    },
    {
      "key": "note-why-open-the-floor",
      "experiment": null,
      "title": "Why open the factory floor?",
      "kind": "Field note",
      "text": "Tools, experiments and a place to show work while it is still becoming something.",
      "href": "journal/why-open-the-floor.html",
      "source": "journal/why-open-the-floor.html",
      "date": "2026-09-07"
    }
  ]
}
