Four verified inputs. Three recorded outputs.
The order is the architecture. Nothing is decided before the facts it depends on have been established, and nothing is decided without leaving a record.
What happens on a call
An application asks. The engine evaluates the governing policy against the verified signals. One answer comes back, and one record is written.
| decision | FAIL |
| rule | EBT Geofence (trafficking) |
| event | benefit-redemption |
| subject | demo:snap:trafficker-200 |
| when | 2026-07-31T12:31:50 |
| location | 39.46898, -99.28134 |
| reason_codes | GEO_OUTSIDE_ALLOWED_GEOFENCE |
The Trusted Execution Layer
Absolute ID consumes what your existing systems already establish and governs the decision they were never designed to make.
Nothing is replaced.
Integration
Administrators govern policy. Applications ask. Systems consume.
Endpoint reference, authentication model, request and response schemas, reason-code catalogue, SDKs and sandbox access. Likely a documentation subdomain rather than a page here.
See it run.
A demonstration evaluates a live policy and produces the record at the end of it.
Request a demonstration