Flow
Select a scenario, run it, then inspect the receipt and API response tabs.
Expected outcome: review_required
The demo includes a weak security-readiness signal, so the API correctly refuses a blind green result.
Authentic ≠ Active
The receipt stays authentic. Its lifecycle status can change.
Before revocation
valid = true
status = active
signature_valid = true
After revocation
valid = false
status = revoked
signature_valid = true
1
Create requestEnterprise asks for work-readiness before sensitive access.
Waiting
2
Record consentConsent is granted, missing, or expired depending on scenario.
Waiting
3
Submit signalsIdentity, work authorization, and security-readiness signals are submitted.
Waiting
4
Run policyPolicy evaluates source, strength, expiry, and consent context.
Waiting
5
Verify receiptThe signed receipt is checked through the public verification endpoint.
Waiting
Decision receipt
Run a scenario to generate a signed Remote Worker TrustPass receipt.
Not run
Decision
—
Lifecycle status
—
Signature
—
Current validity
—
Request ID
—
Receipt ID
—
Expected
—
Reason
—
Evaluated signals
Waiting for scenario run.
Dynamic API responses
Idle
{ "status": "ready_to_run" }
Endpoint trace
Each completed step appears here with method, protection boundary, endpoint, status, and timing.
READY
WAITING
Waiting for scenario run.
—