# Evidence Review Workflow - Receipt-Bound Queue (`civicdataforge/evidence-review-workflow`) Actor

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.

- **URL**: https://apify.com/civicdataforge/evidence-review-workflow.md
- **Developed by:** [Bryan](https://apify.com/civicdataforge) (community)
- **Categories:** Developer tools, Automation
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-usage

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## 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

```json
{
  "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.

# Actor input Schema

## `observedAt` (type: `string`):

Optional ISO-8601 time used to make the queue receipt reproducible.

## `cases` (type: `array`):

One to 500 evidence cases. Every case must reference a canonical sha256 evidence receipt.

## `actions` (type: `array`):

Optional review decisions. Terminal dispositions cannot be silently overwritten.

## Actor input object example

```json
{
  "actions": []
}
```

# Actor output Schema

## `results` (type: `string`):

API URL for the case records produced by this run.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("civicdataforge/evidence-review-workflow").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("civicdataforge/evidence-review-workflow").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call civicdataforge/evidence-review-workflow --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,civicdataforge/evidence-review-workflow"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/FcGODT92pjDfNSKLc/builds/fsLLZ2MoVkqyYDwD9/openapi.json