Quetrex is an enforcement-first development system for Claude Code. Every guarantee is a hook reading an artifact on disk — a real exit code, a real review verdict, a real security report. Not a sentence from a model that says it's fine.
Everything below is enforced by a deterministic hook that reads an on-disk artifact. If the artifact isn't there or the exit code is wrong, the pipeline does not advance. There is no "the agent said it was fine."
The verify-gate blocks "done" while typecheck, lint, build, or tests are red. Real exit codes, pinned to the commit under review. Green is proven, never claimed.
A separate reviewer runs in fresh context — no memory of writing the code. A clean review auto-merges. Issues go back as rework. Risk escalates to a human. Only production deploy stays manual.
Touch a sensitive path — auth, secrets, migrations, payment — and a security review is triggered automatically. You can't opt out of it. A Critical finding hard-blocks the merge. No override.
A right-size router keeps trivial work off the full pipeline. A one-line copy fix doesn't wait behind an architect and a reviewer. Rigor where it counts; speed where it doesn't.
Work moves through six stages. Between each pair sits a gate that reads a file the previous stage wrote — a verify log, a review verdict, a security report. The pipeline can't advance on a summary or a promise. It advances on the artifact, or it stops.
Quetrex installs into Claude Code as a plugin family: a stack-agnostic engine that owns the pipeline and the gates, plus a language pack that teaches it your toolchain's verify commands, conventions, and sensitive paths.
The pipeline, the hooks, the gates, the router. It knows nothing about your language and everything about enforcement. Drop in a pack and it inherits the toolchain.
Quetrex is the framework, not the model. Every run executes under each developer's own Claude subscription — no shared inference bill, no rate-limit contention, no vendor lock on the intelligence layer. You own the compute; the system owns the discipline.
Let the gates decide. Install Quetrex, point it at a task, and walk away — the code that reaches main passed typecheck, lint, build, tests, a fresh review, and, when it mattered, security. Because a hook checked, not because a model promised.