jev-stack

TypeSafe Jev five-layer decision stack — status & process notes.

What this is

Decision schemas and shadow-consult services for the Jev layer stack, starting with Layer 1 (injection detection). This page is informational only — it does not run, deploy, or influence anything live.

Layer status

Layer 1 — Injection merged, shadow-only

Deterministic evaluate(text) and consult-only consult(text) entrypoints. Schema: contains_instructions, claims_authority, confidence, recommended action pass | flag | hold. Kill switch JEV_INJECTION_ENABLED=false by default — while off, effective_action is always null.

Layers 2–5 not started

Planned, no implementation yet.

Process & locks

Branch off main, open a PR, review, merge only when Jason says. No direct commits to main.
No deploy, DNS change, or systemd enable/start without Jason's explicit yes.
Instinct/Jason is the sole owner of merge, live/deploy, money, and email/send. Jev only recommends — it never executes those four itself, and the kill switch defaults on.
Layer 1 injection detection resolves to one of three recommended actions — pass, flag, or hold — via JEV_INJECTION_ENABLED=false shadow consult. Nothing here is auto-enforced.
This is not Duck (:3825 / :3829) — no shared ports or auth, ever. Popstarr (:3831) stays on HOLD until Jason gives a stage yes.

CoS Jev routing

How a deliverable gets assigned and closed out, so writer lanes don't collide:

A — who/whether. Decide who (if anyone) picks this up before work starts.
B — one lane up front. A single writer lane is named for the deliverable; this is not a multi-writer race where several lanes build the same thing in parallel.
C — stage-and-close, conditional. Only if two or more clean PRs land for the same deliverable does CoS Jev stage the winner and close the losers — it's a fallback, not the default path.

This page is one such single-lane deliverable: writer_claude_box was named up front (case B), not a race entrant.

Writer lanes

Work on this stack is paced across lanes to avoid multi-writer races on the same deliverable:

cursor_cloud
pi_terra
pi_astra
codex
antigravity
grok_build
defer
writer_claude_box this page

This page was produced on the writer_claude_box lane as the sole writer for this deliverable. That lane sits outside the four core buckets above — it runs on a shared computer ("Grok Bot") under a personal Claude Pro account. The grimstarr Claude instance is kept separate and stays personal-only; it is not part of this writer roster.

Separate seats

Adjacent decision-making surfaces that this repo does not own or duplicate — each is tracked in its own place, not here:

Duck TypeSafe promote Jev — promotion path from Duck into Jev.
CoS router — the routing logic described above (who/whether, one lane, stage-and-close).
Five-layer stack — this repo's own Layer 1–5 build-out, tracked in HANDOFF.md.