# Reference

The Mimeo contracts in full: the flow definition schema, the event contract, the manager repo's definition file formats, and how to write your own sending adapter.

The contracts, in full. Enough to author a flow, fire an event, sync a repo or write an adapter without reading source.

| Page | Covers |
| --- | --- |
| [Flow definition schema](https://mimeohq.com/docs/reference/flow-schema) | Order as routing, two-armed branches and fall-through, the id/slug/name identity rules, every node type, every condition and operator, and what the validator says. |
| [Event contract](https://mimeohq.com/docs/reference/events) | The trigger stream: the shape of an event, batching and deduplication, the events Mimeo writes itself, and how to design your own names. |
| [Definition files](https://mimeohq.com/docs/reference/definitions-repo) | Every file format, and the two rules that matter more than the formats: node ids are never rewritten, and sharing is expressed by the reference. |
| [Write your own adapter](https://mimeohq.com/docs/reference/write-your-own-adapter) | The capability declarations, the deliver contract, webhook normalization, and the conformance suite that certifies it. |

For the operating surfaces themselves: [the API](https://mimeohq.com/docs/api/), [the CLI](https://mimeohq.com/docs/cli/), and [the MCP server](https://mimeohq.com/docs/mcp/). For doing the same things by hand, [the usage guides](https://mimeohq.com/docs/usage/).