ColeWorld inc. / Orion Gateway
A clearer record.
A stronger human review.
DREDGE Studio brings child-support evidence, client explanations and human review into one working record.
Explore a child-support evidence pilot with local document OCR, source-linked timelines, discrepancy questions and independently reviewed packets. Shared Pages, AI discernment, DREDGE Case Law powered by OpenAI, public web research, client transparency, Models & tools and recorded pipeline execution remain part of the Studio. Agency data and AI use require approval. DREDGE is not connected to MACSS or endorsed by Missouri.
Explore the guided preview ↗Public architecture
From source record to reviewed casework
- Casework evidence
Original documents are preserved. Local OCR drafts require staff verification. Source-linked timeline entries retain dates, observed amounts and page references.
- Clarification and client voice
Record discrepancies as neutral questions and consider client explanations alongside the evidence. These records do not calculate official balances or authorize enforcement.
- Independent packet review
Packets retain immutable snapshots of evidence, explanations and drafts. A different authorized staff member verifies the current snapshot. Draft release and qualified legal review remain separate controls.
- Identity and roles
An enabled identity provider establishes identity. Server-assigned viewer, operator, reviewer, and admin roles control access.
- Run proposal
An operator frames the question and attaches source records. A separate reviewer approves or rejects the immutable proposal.
- Live or demonstration execution
Approved live proposals send public or fictional questions and supplied evidence to the configured Astra API with explicit consent. Demonstration mode retains the local standard or iOS pipeline. Each actual node transition records its dependencies, timing, status, and execution mode.
- Trace and evidence
The graph is built from stored node events. Source records link to their original URLs and disclose that they were supplied by a user and have not been independently verified.
- Audit and reporting
SQLite retains runs and hash-linked review events. Reliability uses completed and failed runs. Live responses retain provider-reported token usage; missing usage and actual billed cost remain explicitly unavailable.