Qualixar Jev Decision Layer 1.0.11 — Approve Once, Every Harness

Qualixar Jev Decision Layer 1.0.11 — Approve Once, Every Harness

Qualixar Jev Decision Layer lets a coding agent hand small, consequential choices (which tool, which task, which files matter, whether an extraction matches its source) to TypeSafe Jev, then continue through the host's own permissions. It is part of Qualixar's AI Reliability Engineering work: typed, gated, advisory decisions instead of an agent guessing.

1.0.11 is about the layer working without being babysat. This release note also covers 1.0.9 and 1.0.10, which shipped as tags only.

Approve once, every harness

• One approval covers a whole folder tree, in every harness. Run setup on a parent folder, such as /jev-setup ~/Documents in Claude Code, and every project under it is covered in Claude Code, Codex, VS Code, Antigravity and Hermes. The setup wizard now says so, pre-selects child coverage for a parent folder (never for a single project), and defaults to 365 days. You still confirm coverage on a separate review screen, and a folder you revoke stays off.
• An expired project grant no longer switches off a folder its parent covers. A revoke or refusal still does.
• Hierarchical enrollment itself arrived in 1.0.9. In 1.0.10 the Codex session-start hook began naming a local service that cannot start, instead of staying silent.

Claude Code uses Jev more, and more correctly

• Session guidance now names the exact workspace_path, data_classification and provider your grant accepts, and lists typed tools only when your grant enables them, so the agent stops guessing arguments and making calls that cannot succeed.
• Subagents get the same guidance through SubagentStart. Previously every subagent ran without knowing Jev was available.
• A folder with no active grant gets one line at session start saying so, instead of silence.
• jev host-register now upgrades its own previous-release entry, so the Claude desktop app stops launching an old version after an upgrade.

Other hosts

• Hermes now looks at the folder Hermes is actually working in (worktree and messaging-gateway sessions included), using the same order Hermes itself uses.
• No change to Codex, Antigravity or VS Code hook behavior.

Reliability of the release itself

• The test suite no longer writes grants into the developer's own state directory, and the coverage gate now fails if any test does.
• Every per-module coverage floor holds again, with new tests that assert exact refusals on error paths. Code that could never run was removed.

Platform scope: supported and verified on macOS. Linux remains experimental and unverified. Windows hosted runtime entry points stay disabled. Native host sessions are not yet independently verified for every adapter; see the host guide.

Upgrade

Claude Code: claude plugin marketplace update qualixar, then claude plugin update qualixar-jev-decision-layer@qualixar, then restart. For the desktop app, quit it fully and run jev host-register --host claude-desktop --write from the new plugin cache. Codex: follow the getting-started guide.

A child project whose own grant had already expired starts using its covering parent's grant as soon as 1.0.11 is installed. Run jev revoke on that project first if it must stay off.

Full detail: CHANGELOG.