Three pillars, one system.
Platform product name pending — the brief leaves it to be decided; “Harness” is a working title used in design only.
Data has gravity
DATA at the centre, with MODEL, HARNESS and WORKFLOWS orbiting. Hover/focus highlighting is a later enhancement.
The three pillars
Model
Choose the brain, not the hype.
- Data ontology translation
- Model portability
- Cost optimisation
- Multi-model architecture
Harness
The layer everyone underbuilds.
- Orchestration
- Agent monitoring with kill-switch
- Compliance built in
- Deterministic guardrails
Workflows
From demo to production every sprint.
- MCP, A2A and OpenAPI interoperability
- Agentic orchestration
- AI-native CI/CD
- Dev intelligence
Capabilities
A capabilities menu of 12 services across Model, Harness and Workflows, as expandable cards. Enumeration pending — the brief references 12 services but does not list them (the pillar items above total 13), and the expandable interaction is a later enhancement.
Why the harness matters
Two companies using the same model can carry materially different risk — the difference is the harness.
Trust and compliance
Data residency inside your AWS or Azure tenancy; RBI and DPDP expectations designed in; guardrails and auditability.
Reuses the approved trust posture (brief §11). §7.6 specifies a trust-and- compliance block but no platform-specific copy. Trust badges (ISO 27001 / SOC 2 / cloud partner tier) are hidden until earned.