---
title: "Meno Quick Start"
description: "Install Meno and evaluate your first claims in a Git work tree."
---
## Install

Requires Rust 1.80+ for source builds. The curl installer prefers a GitHub release binary when one exists for your platform.

```bash
# curl installer
curl -fsSL https://boringinfra.company/meno/install.sh | sh

# cargo
cargo install --git https://github.com/BoringInfraCo/Meno meno
```

Installs to `~/.meno/bin` unless `MENO_PREFIX` is set.

## Initialize a work tree

Run from a Git repository:

```bash
meno init
meno connect
meno verify
meno status
```

`status` prints a subject id and each claim with a verdict:

```text
subject 9f3ac1b8e2d4

1 proven · 0 disproven · 1 unknown

C-subject-identity  proven
  Exact software state is identified.
C-unit  unknown
  Unit tests pass on the current subject.
```

## Collect evidence

`verify` is the command that launches adapters and ingests evidence. `status` never does.

```bash
meno verify
meno status --json
```

## Inspect a claim

```bash
meno inspect C-unit
meno inspect C-unit --json
```

Human confirmation is a CLI action, not MCP:

```bash
meno inspect C-policy-review --confirm
```

## Agents over MCP

Not a sixth command — the same core, over stdio:

```bash
meno connect --adapter agent --write
meno connect --adapter agent --stdio
```

Before declaring work complete, agents should inspect Meno (`meno status --json` or MCP `get_verification_state`), gather evidence with **project** tools, then re-evaluate. Never invent a verdict. Never describe `unknown` as `proven`.

## Next steps

- [Use Cases](/docs/products/meno/use-cases)
- [Meno on GitHub](https://github.com/BoringInfraCo/Meno)
- [Product page](https://boringinfra.company/meno)