01
The same rule, implemented three ways
Every codebase that embeds its own validation embeds its own interpretation — and they disagree in exactly the edge cases that matter.
Platform / Engine API
Run the same checks inside the workflows you already own
The Engine API puts Smartta's decision boundary inside your own products, internal tools, and integrations — submit a workforce decision, get back pass, flag, or gate with the violations and an evidence reference. One rule engine, every surface.
Same Domain Packs · same pass/flag/gate boundary · same Evidence Ledger
The problem
Every product that touches workforce data ends up rewriting the rules
Award logic in the rostering tool. A different version in the payroll integration. A third in the internal dashboard. Each one an approximation, each one drifting, each one your team's to maintain.
02
Validation without evidence
Your app checked something — but there's no decision record. When the question comes later, "the code validated it" isn't a defensible answer.
03
Every rule change is a release
When the award or policy changes, every product carrying its own logic needs a code change, a deploy, and a regression cycle — per codebase.
How it works
Three calls from governed
The API surface is deliberately small — the depth is in the Domain Packs behind it, not in the integration work in front of it.
- 1 · Submit the decision. Post the event with its domain pack and source systems — a pay period, a shift assignment, a credential exception.
- 2 · Receive the outcome. Pass, flag, or gate — with the specific violations, expected values, and remediation context attached.
- 3 · Keep the proof. Every call writes an Evidence Ledger entry; the response carries its reference, replayable later.
API Response Flow
Structured
POST /events/evaluate
200 OK
Policy outcome
Review required
Evidence reference
E-10428
Webhook dispatch
Queued
One rule engine, every surface
Build once on the governed layer
Instead of recreating workforce checks in every product and maintaining them forever, call the layer where the rules are encoded, expert-validated, and versioned once:
For product teams
Ship governed workflows without owning award logic — rule updates arrive as pack versions, not releases.
For partners
Extend Smartta into customer environments — your product gains checks and evidence customers can defend.
For AI systems
Give agents the boundary to call before acting — pass/flag/gate outcomes with evidence written either way.
Build with Smartta
Want API access or a partner conversation?
Talk to us about your use case, product architecture, and how Smartta can support your integrations, services, or developer workflows.