Meno Overview
Bind evidence to the exact software state it observed — local verification state for humans and agents.
Meno is a local, harness-independent verification state layer. Existing tools produce evidence; Meno binds that evidence to a subject hash, preserves provenance, and evaluates proven / disproven / unknown. It owns state, not execution.
Core loop: Init → Connect → Verify → Status → Inspect
Five commands. No sixth. Agent MCP is an interface to the same core, not another command.
What it does
- Bind adapter evidence (git, command, JUnit, Playwright, human) to the current subject
- Evaluate frozen claims to
proven,disproven, orunknown - Summarize without launching tools (
meno status) - Explain a claim, including supporting, contradicting, and stale evidence
- Speak
--jsonon every command for humans and agents
Verdicts
| Verdict | Meaning |
|---|---|
proven |
Fresh supporting evidence satisfies the claim on this subject |
disproven |
Fresh contradicting evidence refutes the claim |
unknown |
Missing, stale, or conflicting evidence — never a synonym for proven |
Unknown is a first-class state. Do not describe unknown as proven.
Key concepts
| Concept | Description |
|---|---|
| Subject | Exact software state (git identity), hashed and inspectable |
| Claim | A frozen statement evaluated against stored evidence |
| Evidence envelope | Adapter output sealed to a subject, with provenance and trust |
| Adapter | git, command, junit, playwright, human — tools you already run |
| Status vs verify | status never launches tools; verify collects, then evaluates |
Tech stack
- Language: Rust (1.80+)
- Storage: SQLite under
.meno/ - Distribution: curl install script,
cargo install --git - License: Apache-2.0
- Status: v1.0 local freeze — contracts live in the Meno specs