It checks the request
Who is asking, what are they trying to do, and why does it matter?
Passpod TASK means Trust Action Standard Kit. In plain English: it is the rule-checking engine inside Passpod.
Some digital actions are too important to happen blindly. Before an AI agent, employee, app, or company does something sensitive, Passpod TASK helps check whether the action is allowed, needs review, or should stop.
Who is asking, what are they trying to do, and why does it matter?
Is this action allowed, limited, expired, blocked, or waiting for approval?
If the action continues, Passpod can record what was checked and decided.
Passpod TASK is not the whole workflow. It is the rule-checking engine inside the workflow. It looks at the request, checks the rule, and returns a clear outcome.
Passpod TASK looks at the actor, the action, the purpose, and the requested scope.
It checks whether the action is allowed, limited, expired, blocked, or requires approval.
It returns a clear outcome so the action can continue, pause, stop, or create a receipt.
A user requests a high-risk access change. Passpod TASK checks the rule and returns “review needed” before the action continues.
Use simple scopes first. Add more later only when the workflow is clear.
Before an AI agent sends an external customer message, Passpod Action Firewall checks the action, applies policy, and returns allow, deny, needs approval, or freeze.
The request includes the actor, workspace, policy, risk context, content_hash, and a safe content_summary. The raw message body is not stored in the receipt.
A Trust Action Receipt records the decision path and limited state. DIDX Receipt State Verification exposes safe verification output only.
It is not a magic approval engine. It is not a legal guarantee. It does not make final decisions for companies.
Passpod TASK is the checkpoint. It asks the right questions before something sensitive happens.
Passpod TASK is the API layer for policy checks, decision commits, receipt states, expiry, and revocation logic.
Start with TASK Modules, then request scoped pilot access if the workflow fits your use case.