Decision patterns from the community (with fit verdicts)

TL;DR 37 decision shapes people published for Jev, digested from curated X posts and the repos they link. This page is the index: find the rows that look like judgments your project already makes, then open the ONE domain page that holds them for the full state / ask / code / fit / map detail. Pattern IDs are permanent.

Route by project type

Spans two? Read the one holding most of your candidate rows; open the second only for a specific Pxx.

Route by where Jev sits

A second way in, from Nate B. Jones's member guide (used with his permission): four placements of a classifier in a system. He also publishes a build-ready recipe-card prompt for each, plus a read-only audit prompt; they are his paid material, so follow the link rather than expecting them here.

All patterns

Fit is our verdict against Jev 1.13 jaggedness: known failure modes and System One Models: strong = bounded options, semantic judgment, code owns the rest; workable = real, with a stated mitigation; poor = a documented weakness (numbers, dates, time series, generation, huge state) sits in the middle of it. strong* = strong only in the narrow per-item form; the domain page says which form is poor. Page: agents = Patterns: agent internals, context and coding agents, interface = Patterns: browser, computer use, voice and product UI, data = Patterns: judging, search, documents, real-time and markets, business = Patterns: marketing, sales, GTM, content, support and ops.

Retrofitting an existing agent

• Start order (@k2sbhai): smallest repeated decisions first — context pruning (P07), model routing (P02), tool/skill selection (P08), supervision (P04), review gates (P10), browser/computer actions last (P12, P14). Measure cost, latency and error rate before and after; cheaper with more bad decisions is a failed optimisation.
• Business workflows: find the expensive queue of incoming information and put Jev at the front of it (Ryan Vogel / Greg Isenberg, @startupideaspod) — P22, P19.
• Vet community repos first: see the caveats in Community repos: what people built and how they use Jev.
• Read-only audit prompt for an existing codebase: The typesafe-ai agent skill and Claude Code plugin.

Anti-patterns seen in the wild

• "It can't hallucinate." It cannot break your schema; it can still pick a wrong valid option confidently — Jev 1.13 jaggedness: known failure modes, Confidence vs probability.
• Asking Jev for its own confidence. confidence comes back on Choice and Score; Noul has none. Walkthroughs also invent the types boolean/categorical and a context field; the real fields are state and questions — HTTP API: POST /v1/systemone and GET /v1/models, OpenAPI component schemas.
• One global threshold, or a Noul threshold reused on a Choice. Structural invariants between question types are not guaranteed — Jev 1.13 jaggedness: known failure modes.
• Overlapping Choice options. @cyrilXBT reports about a third of answers were inconsistent until four overlapping categories were rewritten — criteria, not model (Writing instructions and criteria that Jev reads correctly).
• Review velocity, "last 30/60/90 days", settlement windows. Date ordering is a documented failure mode; extract parts, compute in code (Cookbook: Date extraction).
• Dumping a session, sitemap or corpus into one state. 64k per request, 32k for state plus the longest question, and accuracy falls as irrelevant detail grows (State: what you send Jev).
• Asking it to explain, summarise or write the reply. Not trained to generate; chaining choices to fake it is slow and bad (Jev 1.13 jaggedness: known failure modes).
• Counting. "How many of these failed or mention X" — one question per item, add up in code.

Related

• Consult guide: could Jev help this project? — running the "could Jev help this project?" conversation
• Patterns: agent internals, context and coding agents, Patterns: browser, computer use, voice and product UI, Patterns: judging, search, documents, real-time and markets, Patterns: marketing, sales, GTM, content, support and ops — the patterns themselves
• Field reports: independent evaluations, critiques, open replicas — independent measurements behind the numbers quoted in patterns
• Community repos: what people built and how they use Jev — index of the repos named in Seen lines; Ideas section overview — what this tier is
• Patterns overview, Cookbooks overview, Use-case map by industry, Choosing between Choice, Score, Noul

Sources

Post and repo links are inline in each pattern's Seen line on the domain pages; each domain page lists its raw captures in frontmatter (raw/x/, raw/x-repos/ in the private repo; indexes raw/x/INDEX.json, raw/x-repos/INDEX.json).