March documentation
Product, integration, and reference documentation for March.
March investigates changes for downstream consequences. Give March a change, and it checks the company context you configure, records evidence, and returns either recommended updates, a conclusion that no update is needed, or a question for a person.
Start here
- Getting started — the product model and the shortest path from change to result.
- GitHub — manual PR checks, merged-PR webhooks, setup, and deduplication.
- MCP — connect an MCP client and submit source-agnostic events.
- Investigations — lifecycle, trace, evidence, and outcomes.
- Concepts — the vocabulary used across March.
- Sources and configuration — sign-in, company context, and the configuration users need.
Operator setup
Deployment and operator setup (background processing, webhooks, Netlify
Identity, and the web-context crawler) is not part of this public site. It
lives in the March repository's docs/operator/ folder.
These docs describe the behavior currently shipped in this repository. They do not describe hidden model reasoning; the investigation trace is the structured, user-visible account March records instead.