Midcore documentation overview

Midcore is an Outcome Compiler that turns high-context intent into a versioned capability graph, contract set, and evidence ledger, then reliably compiles deployable releases with deterministic gates and resumable execution. Available in the terminal, VS Code, and Desktop IDE.

Key concepts at a glance

Core ideas you'll use every day. Each links to the concept doc.

Concept	In a sentence
Outcome Compiler	Outcome Compiler — Intent → capability graph → contracts → scope lock → implementation → gates → evidence.
Gates & evidence	Gates & evidence — Deterministic checks and an append-only ledger; completion is "PASS gates", not narrative.
Agent / Plan / Debug / Ask	How Midcore works — Agent implements; Plan designs only; Debug traces failures; Ask is read-only.
Contracts first	Outcome Compiler — Freeze scope and contracts before implementation; no code before contracts.
Delivery tiers	Gates & evidence — Prototype (relaxed), Pilot (standard), Production (all gates and full hardening).
Vibe coding	How Midcore works — Agent loop with verify-after-edit, gates, and evidence; no shortcuts to production.

New to Midcore?

Follow the Learning path: Overview → Quickstart → How Midcore works → Gates & evidence → Common workflows → Best practices → Reference.

Get started

Choose your environment. Most surfaces work offline; the Desktop IDE and CLI support self-hosted or cloud LLM backends.

The full-featured CLI for compiling intent, running the agent, and managing gates from the command line. Edit files, run commands, and generate evidence without leaving your terminal.

macOS, Linux, WSL:

bash

curl -fsSL https://get.midcore.dev/install.sh | bash

Windows PowerShell:

powershell

irm https://get.midcore.dev/install.ps1 | iex

Note

Native installations can auto-update. Ensure Git is installed on Windows.

Then start Midcore in any project: midcore init and midcore agent "your intent". Continue with the Quickstart →

What you can do

Describe what you want in plain language. Midcore parses intent, builds a capability graph, freezes contracts, and compiles deployable releases. Every step is verified by deterministic gates and recorded in an append-only evidence ledger.

bash

midcore compile --intent "add user auth with JWT"

The agent edits across multiple files with full impact analysis. It runs hardening rounds, passes 33+ gates, and produces capability passports. No vibes — only machine-verifiable proof.

bash

midcore agent "add rate limiting to /api/users"

Pipe, script, and automate. Run Midcore in CI for gate checks and evidence generation:

bash

# Gate check on every PR
midcore gates run --strict

# Compile from intent in CI
midcore compile --intent "$INTENT" --non-interactive

Use Midcore everywhere

Each surface connects to the same Outcome Compiler engine. Your .maestro/ config, gates, and evidence work across CLI, VS Code, and Desktop.

I want to…	Best option
Run from the terminal	CLI / Terminal
Use in my existing editor	VS Code extension
Full IDE with agent and gates	Desktop IDE
Self-host on my infrastructure	Self-hosted deployment
Understand the compiler and gates	Outcome Compiler
Configure and troubleshoot	Settings

Next steps

Developer overview · Download · Get started free · Engineering blog

Midcore documentation overview

Key concepts at a glance

Core ideas you'll use every day. Each links to the concept doc.

Concept	In a sentence
Outcome Compiler	Outcome Compiler — Intent → capability graph → contracts → scope lock → implementation → gates → evidence.
Gates & evidence	Gates & evidence — Deterministic checks and an append-only ledger; completion is "PASS gates", not narrative.
Agent / Plan / Debug / Ask	How Midcore works — Agent implements; Plan designs only; Debug traces failures; Ask is read-only.
Contracts first	Outcome Compiler — Freeze scope and contracts before implementation; no code before contracts.
Delivery tiers	Gates & evidence — Prototype (relaxed), Pilot (standard), Production (all gates and full hardening).
Vibe coding	How Midcore works — Agent loop with verify-after-edit, gates, and evidence; no shortcuts to production.

New to Midcore?

Follow the Learning path: Overview → Quickstart → How Midcore works → Gates & evidence → Common workflows → Best practices → Reference.

Get started

Choose your environment. Most surfaces work offline; the Desktop IDE and CLI support self-hosted or cloud LLM backends.

The full-featured CLI for compiling intent, running the agent, and managing gates from the command line. Edit files, run commands, and generate evidence without leaving your terminal.

macOS, Linux, WSL:

bash

curl -fsSL https://get.midcore.dev/install.sh | bash

Windows PowerShell:

powershell

irm https://get.midcore.dev/install.ps1 | iex

Note

Native installations can auto-update. Ensure Git is installed on Windows.

Then start Midcore in any project: midcore init and midcore agent "your intent". Continue with the Quickstart →

What you can do

bash

midcore compile --intent "add user auth with JWT"

The agent edits across multiple files with full impact analysis. It runs hardening rounds, passes 33+ gates, and produces capability passports. No vibes — only machine-verifiable proof.

bash

midcore agent "add rate limiting to /api/users"

Pipe, script, and automate. Run Midcore in CI for gate checks and evidence generation:

bash

# Gate check on every PR
midcore gates run --strict

# Compile from intent in CI
midcore compile --intent "$INTENT" --non-interactive

Use Midcore everywhere

Each surface connects to the same Outcome Compiler engine. Your .maestro/ config, gates, and evidence work across CLI, VS Code, and Desktop.

I want to…	Best option
Run from the terminal	CLI / Terminal
Use in my existing editor	VS Code extension
Full IDE with agent and gates	Desktop IDE
Self-host on my infrastructure	Self-hosted deployment
Understand the compiler and gates	Outcome Compiler
Configure and troubleshoot	Settings

Next steps

Developer overview · Download · Get started free · Engineering blog