Follow the evidence with Detective

Detective, in the web or terminal UI, keeps Cases, reviewed AI proposals, Scenario progress, and Incidentius links with the evidence. It is in development.

Detective CasesIn development

The problem

When an invoice looks wrong, how do you keep the evidence and next steps together?

A question can start with one invoice, a support message, or a handful of suspicious rows. The useful IDs, queries, and explanations quickly scatter across tabs and notes, making it hard to resume the investigation or show how a conclusion was reached.

A clearer workflow

Open a Case around the question
Choose a local or cloud project and record scalar IDs, ID sets, date ranges, the environment, and what is still uncertain. Paste a support report or ask configured AI to propose context; review every proposal before applying it.
Follow a saved investigation
Run relevant Checks or apply a Scenario to the Case. Review the timeline and evidence as you investigate, then close a Case with a reason, reopen it if work continues, or archive it when finished. A Scenario records manual query and Check steps so you can see what was completed, skipped, or still needs attention.
Connect the operational context
Create or link an Incidentius incident, or start a separate Case from an existing incident. Draft private knowledge from Case evidence, review it, then prepare a target-bound handoff for a supported local knowledge target to review; Detective does not publish directly into MeaningGraph or ModelSpec.

Illustrative workflow

Investigate a reported invoice mismatch

Starting question

How can an investigator trace a reported mismatch between an invoice and its related records?

Steps to follow

Create a private Case in a project you can access, then add the relevant record IDs, environment, and open questions to its typed context.
Use the project’s saved queries, Checks, and Scenarios to inspect the invoice and related records. Review each actual result; available definitions and outcomes depend on the project data.
Record evidence and findings as the investigation develops. If the issue is operational, link an Incidentius incident; closing the Case does not resolve that incident.

What this shows

The Case keeps typed context, evidence, findings, Scenario progress, and activity history together. Local and cloud project storage are supported; closing a Case does not resolve a linked Incidentius incident.

Open DataTug

What changes

The investigation has a place to continue, with the evidence and reasoning that support its current direction.

The case of order 11045 · Act 6 · Incident → Case

In the demo story

Maya opens her own Detective Case for order 11045, separate from Sarah’s Incident, and records the order, request and correlation IDs as its context.

The guided demo of this story is being built.