Glossary
Definition
A model-agnostic platform runs on foundation models from multiple providers and lets the customer choose or change the model without rebuilding anything.
Model-agnostic platforms separate the application layer (workflows, tools, data access, guardrails) from the model layer. The customer selects which provider and model each workspace uses, subject to region and compliance constraints, and can change it as models improve or prices move. Evaluation sets make the change safe by showing behavior differences before they reach production.
The design also allows routing: general language tasks to a frontier model, domain-specific reasoning to a model tuned on the domain, and sensitive workloads to a provider under the right agreement. The customer's data is never used to train any of them.
Meridian is model-agnostic. Customers bring frontier models from leading providers, and Meridian routes HR and finance domain reasoning to its own tuned models.
Read next
Long-form explainers and frameworks that use this term, dated and signed.
Governance
A seven-part framework for governing AI agents in HR: scope statements, least-privilege data permissions, approval tiers, audit trail, model choice, employee communication, and works council and GDPR alignment.
Marcus Feld7 min read
Explainers
MCP explained without jargon: how agents discover and call tools, where tool permissions must be enforced, why the gateway pattern matters, and how OpenTelemetry makes agent runs observable.
Owen Gallagher6 min read
Get started
Start with one workflow, one approver, and one number to move. Most design partners were live in five weeks.