CivicDataForge › Directory › Evidence review workflow
Every evidence result becomes a case you can prove.
Feed receipt-bound results from supported CivicDataForge products into one deterministic queue. The workflow assigns stable case IDs, preserves the upstream evidence decision, records customer-owned dispositions as immutable events, and binds the whole queue to a reproducible SHA-256 receipt.
Live now: the public Actor passed deterministic, hostile-input, terminal-state, packaging, cloud-build, and customer-facing Store readback gates. Run it on Apify or connect it through Apify MCP.
The operational loop
| Step | What the workflow preserves |
|---|---|
| 1. Ingest | Product ID, subject key, upstream decision, reason codes, source time, and canonical evidence-receipt hash. |
| 2. Prioritize | Explicit caller priority or conservative defaults that elevate source failures, incomplete scope, changes, and screening candidates. |
| 3. Review | Customer-owned dispositions: confirmed evidence, dismissed candidate, escalated, or insufficient evidence. |
| 4. Prove | Stable case ID, immutable event hashes, case receipt, queue receipt, and deterministic output ordering. |
Built for portfolios, rosters, and recurring checks
The queue accepts one to 500 receipt-bound cases and up to 1,000 explicit review actions per run. Terminal dispositions cannot be silently overwritten. Re-running the same normalized evidence and actions produces the same case identities and receipt structure, making the result suitable for export, reconciliation, and independent verification.
What this replaces: loose spreadsheets, screenshots, copied source snippets, and undocumented reviewer judgment. The output keeps evidence, workflow state, and integrity separate so a reviewer can see exactly what changed and who—not the software—made the disposition.
Responsible-use boundary: the workflow does not approve, deny, clear, certify, or determine legal, environmental, employment, insurance, housing, payment, licensing, or other eligibility outcomes. It preserves evidence and human review state. Consequential facts must be verified with the issuing authority.
Run the live Actor · Use the public Postman workspace · Open the machine catalog · Check source health