Meno Use Cases

Don’t ship on stale tests

Yesterday’s green CI does not prove today’s tree. Meno binds JUnit or command evidence to the current subject hash. Change the commit and that evidence goes stale.

meno verify
meno status
# checkout another commit
meno status
# C-unit is unknown until you verify again

Agent “done” that you can inspect

Coding agents should not declare work complete from prose. Point them at Meno:

meno status --json
# gather evidence with project tests
meno verify --json

Unknown claims stay unknown until evidence exists. MCP cannot freeze-bypass, weaken, or delete frozen claims.

Playwright against this subject

Ingest browser results the same way as unit tests. A failing suite is disproven, not a shrug.

meno connect
meno verify
meno inspect C-browser

Human confirmation stays human

Policy or review claims that require a person use meno inspect --confirm. That is not available over MCP.

meno inspect C-policy-review --confirm
meno status

Export a bundle

Hand someone the evidence pack, not a screenshot of a terminal:

meno inspect --export ./meno-bundle

Pairing with Pico and Harnie

Meno does not map attack paths (that’s Pico) and does not hand off agent sessions (that’s Harnie). It answers a narrower question: for this exact software state, what is proven?

pico scan
harnie import pi session.jsonl
meno status --json