Build against a decision.
Not a guess.
Otarx gives applications and agents one contract for proposing consequential change and one signed result that downstream systems can enforce.
Propose a consequence.
Receive a decision.
The integration model is intentionally small. A caller submits an action claim describing the target object, requested operation, actor context, current-state reference, and proposed consequence.
Otarx resolves the applicable Reality Contract, determines which enterprise perspectives are required, evaluates observer claims and evidence, establishes the bounded reality relevant to the consequence, and returns a signed ADMIT or DENY decision.
{
"claim_id": "clm_...",
"state_ref": "S0",
"target": {
"type": "protected_object",
"id": "..."
},
"operation": "UPDATE",
"actor": {
"principal": "...",
"delegate": "..."
},
"context": {
"purpose": "...",
"session": "...",
"device": "..."
},
"evidence_refs": [
"..."
],
"requested_consequence": {
"proposed_state": "S1"
}
}The caller can provide evidence references. The caller does not decide what evidence is sufficient. The Reality Contract does.
Make the consequence
portable.
A Reality Decision contains the claim reference, Reality Contract reference, outcome, bounded reality context, decision timestamp, validity window, and cryptographic signature.
Protected systems can verify the decision without reproducing the admission process.
{
"decision_id": "rxd_...",
"claim_id": "clm_...",
"contract": "rc_...",
"outcome": "ADMIT",
"bounded_reality": {
"target": "...",
"operation": "UPDATE",
"actor": "...",
"state_ref": "S0"
},
"scope": {
"object": "...",
"operation": "UPDATE"
},
"issued_at": "...",
"expires_at": "...",
"signature": "..."
}
Thin clients.
Central admission.
SDKs help callers construct valid action claims, attach evidence references, verify signed Reality Decisions, and invoke enforcement adapters.
Reality Contract evaluation, observer resolution, evidence convergence, bounded reality construction, and admission remain inside the Otarx Runtime.
Every application does not need to become its own reality policy engine.
Create valid consequence proposals.
Reference available enterprise evidence.
Validate signed ADMIT or DENY results.
Invoke protected mutation boundaries.
Start where consequence
becomes durable.
The first useful integration point is usually the final mutation boundary of a consequential workflow.
Transfers, balances, settlements, and financial state.
Privileged modifications to production systems.
Code and configuration entering canonical environments.
Changes to enterprise systems of record.
High-consequence approval and authorization workflows.
Privilege, role, entitlement, and authority mutations.
A caller can compute, reason and propose upstream.
The protected consequence becomes canonical only when accompanied by a valid Otarx Reality Decision.