Platform
How it works
An agent reaches the point of doing something consequential.
Submitting a payment, booking inventory, adjusting a limit, posting an entry. Instead of calling the system directly, the action goes through Coco.
Step 1
Coco receives the intended action with its parameters. Payee, amount, account, reference, whatever the action carries.
Step 2
The Action Pack declares which state the decision depends on. Coco retrieves current values from the systems holding them. This is where the engineering weight sits, because a stale vendor record produces a confident wrong answer.
Step 3
The action and the state are checked against the Action Pack.
Step 4
AUTO-EXECUTE, OBSERVE, ESCALATE, or DENY, with the reasoning attached and the decision recorded.
The action executes only on ALLOW.
Nothing reaches the downstream system before the verdict.
