Jev votes in shadow mode under Decision Buddy’s pilot DB-2026-011: Jev makes the call below, the reasoning model still makes the actual decision, and agreement is kept score of. This batch is a decidability pre-screen — is each queue item ready to be decided at all? The pilot stays with Decision Buddy until Dave transfers it; this page is the fleet’s window into the log.
Latest batch: Mon Oct 26, 2026 · 11:57 PM PT · use case: queue-decidability · guard passed all 7 (operational text only). Verdicts were pre-registered in the manifest before any Jev vote existed. Gate scores are Jev’s per-gate probabilities; the source gate is the story of this batch — 0.03 on every item with no link attached, 0.99 on the one that had them.
The register cannot say what decision this names — fails the options, source, and owner gates.
The batch’s positive control: both drafts linked, the call (review / approve / edit) stated, owner clear. Criteria soft but present — Jev scored criteria_stated 0.25 against the model’s ‘soft but present’; logged as a divergence for the Nov 25 review.
Fails everything: no options, no source, no owner. The register calls it underspecified in its own words — Jev’s firmest call of the batch.
The three surfaces are concretely named (genuinely pickable), but no links to any of them are attached — fails the source gate. Expected closest call in the batch.
A clean binary with the verdict text quoted in the register, but no link to the verdict document travels with the item — fails the source gate. Jev read owner_named at 0.41 (‘Astro builds if approved’ as weak ownership); logged as a divergence for the Nov 25 review.
Options defined and owner named, but no source link attached, and the register itself marks it not-yet-decidable until the phone arrives.
Options and owner are defined, but no source link travels with the item in the register — fails the source gate under the pilot’s strict composite.
Two sub-verdict divergences are logged for the Nov 25 review: Q15 criteria_stated (Jev 0.25 vs model “soft but present”) and Q12 owner_named (Jev 0.41 — “Astro builds if approved” read as weak ownership). Honest read on the batch: encouraging but weak evidence — the negatives were telegraphed by the register; borderline items are the real test. The log itself lives in the decision-buddy repo (jev-pilot/shadow-log.jsonl) and stores only the item ref + a hash of the state — never the raw text. A separate one-off connector check on Oct 26 (415 tokens, routed a test note to “records” at confidence 1.0) is not part of this tally. Draft bands are recorded, never acted on, in shadow mode.
Dump what's on your mind about Jev Buddy — raw and unfiltered. Each dump lands in the buddy's repo (docs/ingest.md) as a timestamped entry — or saves on this device until a repo is linked and a token is connected.
🔒 Connect GitHub to unlock dumping. Paste a token once — it stays on this device only.
Enter dumps it · Shift+Enter for a new line
The markdown files in Jev Buddy's repo. Tap a file name and its contents open right below it — open as many as you like at once. Edit inside an opened file and the save goes straight back to GitHub. The repo is private, so nothing here — not even the file names — is shown until GitHub is connected on this device.