docs: karpathy-pattern wiki built from the spec, plan, design contract and decisions ledger

kb/ is its own wiki root: 34 pages across 7 categories, index.md catalog, log.md, AGENTS.md schema layer, and raw/ holding copies of README, the spec, the 13-task plan, the design master and the SDD ledger.

Every page cross-references 3 to 6 others and all 107 wikilinks resolve except two [["list"]] artefacts inside JSON snippets in the copied plan.

Kept separate from the repository root on purpose: its generated graph lands in kb/.ua/ instead of overwriting the code graph.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

kb/Jev scoring.md

@@ -0,0 +1,18 @@
+# Jev scoring
+
+Jev is a separate typed judgment model, not a second opinion in prose. `lib/jev.ts` asks it four questions per
+option, gets a value plus a confidence for each, and combines them through `WEIGHTS` into one composite score.
+
+Three flags come out of the scores:
+
+- `verify_semantics` when semantic safety falls below 0.45, or below 0.6 for an option whose `option_type` is
+  `rewrite`. Live Jev scores an index create around 0.57 ("probably equivalent, no stated proof"), so keying the
+  soft floor on the option type rather than on "has SQL" is what keeps the warning useful.
+- `low_confidence` when any dimension's confidence drops under the floor.
+- `change_control` when an action is marked as needing change control.
+
+When Jev is unreachable or abstains, `jevFallback` returns the composite order and marks the source
+`jev_unavailable`, so the report prints "composite order — Jev did not decide" rather than implying Jev chose.
+A real run on the 2.7 MB production plan hit exactly this path and stayed honest.
+
+Related: [[Analyst model]], [[Option type and sql to run]], [[Jev goal gate]].