OMK CLI proposes evidence-gated verification for coding agents
u/Fabulous-Lobster9456 is building OMK, a local-first CLI control plane that prevents coding agents from declaring completion without recorded evidence, and is seeking feedback from agent builders on whether the approach is useful or over-engineered.
Score breakdown
OMK introduces a structured, evidence-gated completion check for coding agents, directly addressing the problem of agents falsely reporting task success without verifiable proof.
- 01OMK is a local-first CLI control plane for coding agents, currently pre-1.0 and not stable.
- 02Core principle: coding agents cannot declare a task complete without recorded evidence.
- 03Execution pipeline follows the structure: Goal → DAG → Route → Verify → Replay.
u/Fabulous-Lobster9456 is building OMK, a local-first CLI control plane for coding agents built around a single core constraint: agents cannot declare a task "done" without recorded evidence. The system structures execution as a five-stage pipeline — Goal → DAG → Route → Verify → Replay — and captures proof bundles, decision traces, provider fallback behavior, and replay/inspect artifacts at each stage.
The project is explicitly pre-1.0 and described as not yet stable.
The current development branch extends this with a regression proof matrix, which verifies that hardening algorithms are backed by tests, proof bundles, decision traces, and reachable CLI/runtime surfaces. The project is explicitly pre-1.0 and described as not yet stable. The post is a call for feedback from agent builders, asking whether proof bundles and replayable verification would genuinely increase trust in coding-agent runs, or whether the architecture is over-engineered for practical use.
Key facts
- 01OMK is a local-first CLI control plane for coding agents, currently pre-1.0 and not stable.
- 02Core principle: coding agents cannot declare a task complete without recorded evidence.
- 03Execution pipeline follows the structure: Goal → DAG → Route → Verify → Replay.
- 04The system records proof bundles, decision traces, provider fallback, and replay/inspect artifacts.
- 05A current branch adds a regression proof matrix checking hardening algorithms against tests, proof bundles, decision traces, and reachable CLI/runtime surfaces.
- 06The author is seeking feedback from agent builders on whether the verification model is useful or over-engineered.
Topics
Summary and scoring are generated automatically from the original article. We always link back to the publisher and never republish images or paywalled content. Last processed Jun 11, 2026 · 08:34 UTC. How this works →