Evidence Review Workflow - Receipt-Bound Queue avatar

Evidence Review Workflow - Receipt-Bound Queue

Pricing

Pay per usage

Go to Apify Store
Evidence Review Workflow - Receipt-Bound Queue

Evidence Review Workflow - Receipt-Bound Queue

Turn government-data evidence receipts into deterministic review cases with customer-owned dispositions, immutable history, priority handling, and tamper-evident queue receipts. No autonomous clearance or eligibility decision.

Pricing

Pay per usage

Rating

0.0

(0)

Developer

Bryan

Bryan

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

0

Monthly active users

2 hours ago

Last modified

Share

Evidence Review Workflow

Turn CivicDataForge evidence receipts and change events into a deterministic customer-owned review queue.

The Actor provides the operational layer that a raw lookup does not:

  • stable case IDs bound to the product, subject, and evidence receipt;
  • explicit open, escalated, insufficient-evidence, confirmed-evidence, and dismissed-candidate dispositions;
  • immutable reviewer-event history with a receipt on every event, case, and queue;
  • terminal-state protection so one run cannot silently rewrite a completed review;
  • deterministic output independent of input ordering;
  • priority defaults that elevate source failure, incomplete scope, disappeared records, and restricted-party candidates;
  • up to 500 cases and 1,000 actions per run.

What it deliberately does not do

This Actor does not call an upstream government source, identify a person, decide legality, declare environmental safety, clear a transaction, or make credit, insurance, employment, housing, licensing, or other eligibility decisions. It does not send messages to arbitrary URLs. Use Apify schedules and customer-configured webhooks to route verified queue outputs into the customer's own Slack, email, ticketing, database, or case system.

Reviewer aliases and notes are customer-supplied operational metadata. Do not submit secrets or unnecessary personal data.

Example

{
"observedAt": "2026-08-23T03:00:00Z",
"cases": [
{
"reference": "supplier-001",
"productId": "cross-border-restricted-party-evidence",
"subjectKey": "supplier:001",
"decision": "POTENTIAL_MATCH_REVIEW_REQUIRED",
"evidenceReceiptHash": "sha256:76066c356142664975f19d6f9340ec9800d4bacad126d0f5c82ca966dc2f2b69",
"reasonCodes": ["PRIMARY_NAME_MATCH", "COUNTRY_CONSISTENT"]
}
],
"actions": [
{
"reference": "supplier-001",
"disposition": "escalated",
"reviewerAlias": "trade-review-1",
"at": "2026-08-23T03:00:00Z",
"note": "Agency-list confirmation required."
}
]
}

The resulting queue is a review-process receipt. It is not proof that the underlying subject is cleared, prohibited, safe, compliant, or identical to a published record.