User Guide

Consortium treats a multi-processor product as one buildable system. The normal workflow is deliberately short:

1. describe the topology and resource ownership in Consortium.toml;
2. define boundary-safe message types in a shared crate;
3. write application and firmware logic against the generated Context;
4. run csti build; and
5. integrate the resulting dist/ tree with the target image.

The chapters follow that sequence:

• Getting Started tours the workspace and runs the first checks.
• System Architecture explains how the crates and generated code fit together.
• Project Manifest documents the current Consortium.toml schema.
• Generated Runtime shows the endpoint entry points and IPC surface.
• Build and Deployment explains csti build, its artifacts, and the packaging boundary.

The development notes later in the book record design work and hardware bring-up. They are useful context, but they are not the authoritative API reference.