The Legates
We do not sell a tool. We send a person.
A legate of Marsovius 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 through every production deployment that follows.
Legates are not contractors. They are not labour-by-the-hour. They are members of the house, bound by the same Pact of Sovereignty as the company itself.
Latin · legatus
In Imperial Rome, the legatus Augusti pro praetore was a senatorial governor of a province, appointed with delegated imperial authority. The legate did not represent the senate from a distance. The legate was the senate, on the ground, in the province, for as long as the work required.
The protocol
D + 0
An audience is requested
The customer reaches the house through the audience desk.
D + 10
A legate is assigned
The match is the first decision. A hospital does not receive a defense legate.
D + 20
A protocol of work is signed
Scope, jurisdiction, governance, audit clauses. One page when possible.
D + 30
The first ontology is delivered
Drafted with the customer’s subject-matter experts. Versioned in the customer’s repository.
W + 12
The first production decision
A workflow runs in production. The decision is signed. The audit trail is opened.
M + 12
The legate remains
A twelve-month minimum companionship begins on day one.
The four practices
Setup
The legate installs Marsovius in your environment, connects it to your existing systems, designs the first ontology with your subject-matter experts, and stands up the first workflows. From kickoff to first production decision: six to twelve weeks.
- · installation
- · ontology design
- · connectors
- · first workflows
Training
The legate transfers every skill they use to the customer’s engineers, data teams and operators. Marsovius is not a black box and the training is not a course. Within ninety days the customer’s team runs the platform without house involvement.
- · skill transfer
- · enablement
- · operator handover
- · no black box
Counsel
The legate remains as a standing advisor for architectural decisions, ontology evolution, model selection and incident response. The counsel is not billed by the hour. It is included in the relationship.
- · architecture
- · model selection
- · incident response
- · no hourly billing
Companionship
The legate stays attached to the customer for twelve months at minimum. They attend design reviews, sit on architecture councils, and represent the house when the customer’s regulator asks how a decision was made.
- · 12 months minimum
- · design reviews
- · regulator-facing
- · permanent presence
Who legates are
Legates are engineers of the house with at least eight years of operational-platform experience. The legate sent to a customer matches the customer's institution. A hospital does not receive a defense legate. A ministry of finance does not receive a logistics legate. The match is the first decision.
A legate may be:
- —A senior platform engineer.
- —A clinical data architect.
- —A defense systems integrator.
- —An econometrician trained in tax-policy implementation.
- —A logistics operations researcher.
- —A commerce-platform engineer with EU regulatory experience.
— V —
The cost is part of the relationship.
A legate is bundled into the Pro and Sovereign editions. There is no per-legate-day billing. The pricing is per institution, not per hour. The conversation about cost begins after the audience is granted.
The code is open. The legate is sent. The work begins on the customer's premises, in the customer's ontology, under the customer's law.