How the open-source demo works
Instrata orchestrates a DSAR from consumer intake to an approved action. The agent handles search and reasoning; humans hold every gate that produces a side effect. Below is each layer of the pipeline.
Intake
The consumer-facing portal captures request type, identity, jurisdiction, and verification details. Each submission is normalized into a request record and placed in the operator queue with an SLA clock derived from the applicable jurisdiction.
Request orchestration
Orchestration turns a verified request into a plan of read-only steps. It decides which source systems to query, invokes the agent's tools in sequence, and collects results and reasoning — without ever performing an external action on its own.
Agent tools
Tools are the only way the agent interacts with data, and each is explicitly typed as read-only or side-effecting. Read-only tools run freely and are logged; side-effecting tools are registered as proposals that require approval.
Source-system connectors
Each connected system — billing, CRM, support, marketing — implements a small connector interface. Connectors declare their search capability and mark whether they can produce side effects, which the runtime always treats as gated.
Evidence & audit layer
Every input, tool call, result, reasoning step, and human decision is appended to an immutable audit trail keyed to the request. The evidence log is what makes a completed DSAR defensible on audit — it shows exactly what happened and who decided it.
Approval gates
A gate sits in front of every side effect. When the agent proposes an action, the operator sees the reasoning, the evidence, and the exact operation, then approves, rejects, or requests changes. Only an approval releases the action for execution.