Mission runtime

Work you can verify,
not chat you have to trust.

NAVIG turns operations into missions: typed, durable, auditable units of work that end in a receipt. A node does the work, a mission tracks it through a strict state machine, and a receipt proves what happened.

Node → Mission → Receipt

Three contracts. One auditable path from intent to proof.

Step 1

Node

A machine that can do work — registered with the runtime, carrying its capabilities and status. Your laptop, a VPS, a homelab box.

Step 2

Mission

A unit of work with a strict lifecycle: queued → running → succeeded, failed, cancelled, or timed out. Only legal transitions are accepted, failed and timed-out missions can retry, and state survives a restart.

Step 3

Receipt

Terminal proof. Every mission that finishes records an execution receipt — outcome, duration, error — inspectable from the Deck or the API.

queuedrunningsucceeded|failed|cancelled|timed_out

Only legal transitions are accepted · failed and timed-out missions can retry · state survives a restart

Rails first, autonomy second

The runtime is wrapped in the same safety layer as everything else NAVIG does.

Approval gates that fail closed

Gate any action pattern behind human approval — from the Deck, Telegram, or the API. Timeout or error means denied.

Everything audited

Every privileged decision lands in a structured audit log; every operation lands in a hash-chained, tamper-evident ledger.

Honest reversibility

Operations are labeled green, yellow, or red before you need to care. navig undo replays the last green one — with drift detection.

Full safety capability list in the matrix →

Start operating

Four commands from zero to mission control. Everything runs on your machine.

1 · Install

# Any platform with Python 3.10+
pip install navig

# Linux / macOS one-liner
curl -fsSL https://navig.run/install.sh | bash

# Windows (PowerShell)
irm https://navig.run/install.ps1 | iex

2 · Set up

# Interactive onboarding — providers, workspace, bot
navig init

# Check what's configured at any time
navig init --status

3 · Bring the brain online

# Start the local gateway (the runtime lives here)
navig gateway start

# Verify the install end-to-end
navig doctor

4 · Open mission control

# The Deck cockpit → Mesh Explorer → Missions
navig deck open

# Proof on demand: recent operations, chain-verified
navig ledger show --tail 20

Prefer a guided path? The first-mission guide walks every step with tips.

First mission guide See the capability matrix

Work you can verify,not chat you have to trust.