Control what agents read.Verify what they change.
Mikie compiles bounded repository context, runs guarded coding work, and writes content-free Evidence to Meter—so capability, quality, and cost claims stay independently provable.
Native relay · Exactly eight read-only MCP tools · Content-free Evidence
illustrative context contract · no repository or provider call
- build_context_packet
- rank_relevant_files
- list_mikie_capabilities
- get_mikie_meter
- get_measurement_summary
- get_quality_summary
- get_business_summary
- estimate_mikie_savings
✓ selection bounded · file identities omitted
✓ line anchors bounded · values omitted
✓ content-free illustrative output
Measured on a local 5-instance accepted-patch / SWE-style suite (2026-06-25). Promising engineering evidence, not a broad benchmark or production-ROI claim. Token savings are reported separately from quality.
One customer path, explicit proof boundaries
A coding loop that fails closed.
Context, Control, verification, and Evidence share one frozen request contract without sharing raw content into telemetry.
Compile
Rank the authorized repository and build only the bounded, line-anchored context the task needs.
Guard
Freeze repository state, allowed paths, commands, model, timeout, and verifier before a Control attempt starts.
Verify
Apply one model-produced patch, verify outside the model, and permit at most one precise repair.
Prove
Sign content-free Evidence, append it to the ledger, and show only supported facts in Meter.
Three systems, one proof chain.
Compile only authorized context, run a bounded Control attempt, and project content-free Evidence into Meter.
Bounded repository context through eight read-only tools
The native relay ranks the connected repository and returns operation-scoped, line-anchored packets. It cannot expose internal recorders, evaluators, or arbitrary server paths.
One request, guarded
Freeze paths, commands, model, timeout, and verifier. Apply one patch, verify outside the model, and allow at most one repair.
- ▸immutable request manifest
- ▸one authoritative context retrieval
- ▸deterministic verifier
- ▸fail-closed Evidence gate
Content-free and signed
Eligible usage is encrypted locally, signed by the device, authenticated by the service, and appended to one ledger.
Facts with visible boundaries
Inspect provider usage, accepted work, Control status, finance, engineering, privacy, and immutable receipt projections.
Quality first. Then token efficiency.
On one local five-instance accepted-patch suite, the best v2 hybrid resolved 4/5 vs raw's 3/5 while using 71.33% fewer total tokens. Promising engineering evidence, not production ROI.
Top-right is better — high savings with high quality density.
Raw and Mikie were measured on one local five-instance suite dated 2026-06-25. Hollow competitor markers restore the prior historical illustration using only their estimated token-savings x-position; they do not share the measured y-axis and are not a head-to-head or current test. Read the Evidence Policy.
Local suite dated 2026-06-25. Provider-backed Control performance remains unclaimed.
Built for teams that need proof, not promises.
The same fail-closed rules that guard a Control attempt also guard the claims rendered in Meter.
Operation-scoped context
The relay serves only the connected repository under a signed, bounded operation lease. Ordinary telemetry never contains repository content.
Content-free Evidence
The encrypted outbox and signed ledger forbid source, prompts, model outputs, commands, credentials, and raw paths.
Missing stays unavailable
Observed, calculated, estimated, bounded, and unavailable values stay separate. No missing fact is rendered as zero.
Give agent work a contract. Then give it a receipt.
Install the native relay from npm, authenticate, bind one repository, and verify the exact eight-tool MCP surface with doctor.
Mikie Founder · $20 monthly or $192 annually · 14-day trial