Jev Superpowers

The README labels the entire table design targets measured on the maintainer's setup, and asks you to reproduce them with scripts/test.sh plus your own Jev or Laya usage logs before quoting them. The baseline is stated loosely as roughly 14% unvetted libraries, and the comparison is against a package-vetting tool rather than a controlled study with a fixed agent and workload.

The offline suite checks skill frontmatter validity, cross-platform installers and hooks wiring. Nothing in the README documents tests that exercise a gate's judgment quality on real tasks, and no dataset, failure cases or repeated runs are published. Treat 24/24 as the harness assembling correctly rather than evidence that the decisions are right.

Largely, yes. The toolchain table points at separate repositories: jev-git for pre-commit gates, jev-scout for crate vetting, jev-axi, jev-guard, supercov, limpet and jev-seo, each with its own install command. What lives here is the five skill files and the installer layer deciding when to invoke them, plus the local Laya bridge script.

Fully offline is the documented Option B: pip install laya, run scripts/serve-laya.py --port 8000, then export TYPESAFE_BASE_URL=http://127.0.0.1:8000 and TYPESAFE_API_KEY=local so nothing leaves the machine. The 33-38 ms local gate latency and zero-egress claims come from that same maintainer-measured table rather than an independent benchmark.

jev-brainstorming, jev-writing-plans, jev-executing-plans, jev-systematic-debugging and jev-verification, built on obra/superpowers. Each gates part of the software-development flow with Jev in the cloud or Laya locally.

For the TypeSafe cloud backend set TYPESAFE_API_KEY and run `bash install.sh`; for a fully offline setup `pip install laya`, run `scripts/serve-laya.py --port 8000`, then export TYPESAFE_BASE_URL=http://127.0.0.1:8000 and TYPESAFE_API_KEY=local.

MIT, and it is a community project not affiliated with TypeSafe. The toolchain table points at separate repositories — git-jev for pre-commit gates, jev-scout for package vetting, jev-axi, jev-guard, supercov and jev-seo — each with its own install command.