Working with a legate

A legate is a senior engineer of the house, dispatched to the customer's premises with delegated authority to install the platform, design the first ontology, train the operators, and remain as counsel. The brand page is at /legates — this doc covers the practical week-by-week reality.

Before the legate arrives

You will be asked to prepare three things:

1. A point of contact — a single named individual who can decide.
2. Read access — to the three or four source systems that matter most.
3. A signed protocol of work — one page, jurisdiction and scope.

Week 1 — Listening

The legate spends the first week not deploying anything. They sit with operators, read existing documentation, walk the warehouse or the floor of the hospital, and read the legal frame the institution operates under.

By the end of the week the legate proposes the first seven to twelve ontology types. The customer's lead architect signs them or argues them.

Week 2 — Installing

The platform is brought up on the customer's hardware from a clean clone of the marsovius-platform repository. The compose stack starts. The first Hermes connector pulls a sample of production data into a staging ontology. The customer's operators see a working workspace by the end of the week.

The full installation procedure is at /docs/installation.

Weeks 3 to 6 — Building

The legate pairs with the customer's engineers to write the first three pipelines, the first two workflows, and the first dashboards. Every change is reviewed in code by the customer.

Weeks 7 to 12 — First production decision

A workflow runs in production. A decision is signed. The audit trail is opened. The customer's operators now use Marsovius for at least one operational task that previously lived in a spreadsheet.

Months 4 to 12 — Counsel

The legate steps back. They remain on call for architectural decisions, ontology evolution, model selection, incident response, and regulator-facing meetings. They are not billable by the hour during this period — the cost is part of the relationship.

After 12 months

The customer's team operates the platform without house involvement. The legate remains reachable. For Sovereign customers, the legate stays on premises for as long as the engagement requires it.