Install & infrastructure
Getting started.
For: anyone setting Cardinal up for the first time
Cardinal has two halves to set up: a desktop host where the agents live, and an Azure backend they share. This page is the map — what you'll do, in what order, and where each detailed guide lives. If you only want to understand the system rather than run it, read How it works instead.
The big picture in a minute
The agents run on a desktop host and write to a database in Azure. The web app — Cardinal — runs in Azure too, over the same database. So setting up means: prepare the laptop, provision the cloud, then bring the agents to life. The customer-specific part is a thin slice; most of what you set up is reusable across engagements.
The path, step by step
1 · The desktop host
Install the host, restore the corpus, start the local message bus, authenticate in order, and smoke-test.
2 · The Azure backend
Stand up the shared substrate once, then onboard the engagement's thin slice; deploy the app.
3 · Bring the ring to life
Validate the config, spawn the agents, pass the three greens, and start the Ticker.