SPEKTRIS ASSURANCE CENTER / INTEGRATION GUIDE

Connect the task.
Inspect the action.
Verify the effect.

Build an evidence trail that connects the authority to act with the changes made in your business systems.

Use this refund example to identify the records, permissions, and control points to review for your own workflow.

Explore the reference packet

01 / AUTHORITY

The approved task

Instruction, owner, agent identity, delegation, scope, and expiration.

task.id · delegation.id

02 / EXECUTION

The tool action

Acting agent, requested operation, parameters, timestamp, and result.

taskId · correlationId

03 / SYSTEM EVIDENCE

The recorded effect

Transaction records or audit events collected from the affected system.

receipt.id · correlationId

DESIGN THE CONNECTION

Three sources.
One inspectable run.

Agree on the event boundary and identifiers before connecting a workflow. Preserve original records so an investigator can trace a finding back to its source.

Task and delegation record

Record who authorized the task, which agent can act, and the allowed tools, amounts, resources, and time window. Preserve the delegation chain when one agent hands work to another.

Example: a support reviewer authorizes one $180 refund. The support agent delegates to a payment agent with the same limit and a defined expiration.

Tool or runtime event

Capture the requested operation and parameters, agent identity, result, and event time. Carry the task and correlation IDs through the call so later evidence can be joined to the request.

Example: refund.create reports success for $180.

Business-system record

Collect receipts or audit events from the system where the change occurred. Check the actual amount, object, count, and status against the authorized task.

Example: two different posted refund IDs total $360. The action report alone does not establish this outcome.

EXPLORE THE EVIDENCE

Inspect the fields.
Change the outcome.

Compare a matched refund, a duplicate, and a missing receipt. The example distinguishes an action that was permitted from an outcome supported by collected records.

Illustrative refund packet Download JSON

Reference format

{
  "referenceFormat": "spektris-refund-example-v1",
  "illustrative": true,
  "scenario": "duplicate",
  "task": {
    "id": "EXAMPLE-1042",
    "instruction": "Refund one customer payment",
    "approvedAmountUsd": 180,
    "allowedRefundCount": 1,
    "authorizedBy": "Support reviewer",
    "authorizedAt": "2026-01-15T10:00:00.000Z"
  },
  "authority": {
    "id": "EXAMPLE-A01",
    "issuedBy": "Support reviewer",
    "delegatedTo": "Support agent",
    "scope": "One refund of $180 against payment EXAMPLE-P01",
    "taskId": "EXAMPLE-1042"
  },
  "delegation": {
    "id": "EXAMPLE-D01",
    "parentAuthorityId": "EXAMPLE-A01",
    "from": "Support agent",
    "to": "Payment agent",
    "taskId": "EXAMPLE-1042",
    "allowedTool": "refund.create",
    "maxAmountUsd": 180,
    "allowedRefundCount": 1,
    "expiresAt": "2026-01-15T10:15:01.000Z"
  },
  "toolEvents": [
    {
      "id": "EXAMPLE-T01",
      "taskId": "EXAMPLE-1042",
      "delegationId": "EXAMPLE-D01",
      "tool": "refund.create",
      "amountUsd": 180,
      "at": "2026-01-15T10:00:01Z",
      "result": "success",
      "correlationId": "EXAMPLE-CORR-1042",
      "agentId": "Payment agent"
    },
    {
      "id": "EXAMPLE-T02",
      "taskId": "EXAMPLE-1042",
      "delegationId": "EXAMPLE-D01",
      "tool": "refund.create",
      "amountUsd": 180,
      "at": "2026-01-15T10:00:03Z",
      "result": "success",
      "correlationId": "EXAMPLE-CORR-1042",
      "agentId": "Payment agent"
    }
  ],
  "agentReport": {
    "tool": "refund.create",
    "amountUsd": 180,
    "reportedStatus": "success",
    "eventId": "EXAMPLE-T01",
    "taskId": "EXAMPLE-1042",
    "correlationId": "EXAMPLE-CORR-1042",
    "agentId": "Payment agent",
    "observedAt": "2026-01-15T10:00:01Z"
  },
  "businessEvidence": {
    "source": "Illustrative payment ledger",
    "receipts": [
      {
        "id": "EXAMPLE-R01",
        "taskId": "EXAMPLE-1042",
        "amountUsd": 180,
        "status": "posted",
        "correlationId": "EXAMPLE-CORR-1042",
        "toolEventId": "EXAMPLE-T01",
        "recordedAt": "2026-01-15T10:00:01.500Z"
      },
      {
        "id": "EXAMPLE-R02",
        "taskId": "EXAMPLE-1042",
        "amountUsd": 180,
        "status": "posted",
        "correlationId": "EXAMPLE-CORR-1042",
        "toolEventId": "EXAMPLE-T02",
        "recordedAt": "2026-01-15T10:00:03.500Z"
      }
    ],
    "totalUsd": 360,
    "collectedAt": "2026-01-15T10:00:04.000Z"
  },
  "verification": {
    "verdict": "mismatch",
    "labels": "Outcome needs investigation"
  },
  "policyFinding": {
    "rule": "At most one posted refund, totaling no more than $180",
    "observedRefundCount": 2,
    "observedAmountUsd": 360,
    "result": "exception"
  },
  "investigation": {
    "decision": "Escalate the duplicate refund for review",
    "nextStep": "Review both tool calls and payment receipts before deciding on remediation.",
    "automaticRemediation": false
  },
  "correlation": {
    "id": "EXAMPLE-CORR-1042",
    "runId": "EXAMPLE-RUN-1042"
  }
}

Use the synthetic examples to explore the fields, up to 100,000 characters. Checks run in your browser; this inspector sends no packet contents to a server.

REFERENCE CHECK

The receipts reveal a mismatch.

Reference structure Checked

Tool-action sequenceOutside example scope

Authorized total$180.00

Collected receipts2

Recorded total$360.00

A successful tool response can coexist with a different business result. Compare the source records before closing the run.

These checks compare fields, scope, and amounts in an illustrative packet. Production verification also needs authenticated sources, reliable collection, and appropriate evidence coverage. This reference format is not a production API contract.

ACCESS AND CONTROL POINTS

Observation and enforcement
need different connections.

Set access around the evidence you need and the action you intend to control.

Observe and investigate

Start with the minimum read-only access needed to inspect task records, runtime events, and downstream audit or transaction records.

Scope service identities to the selected workflow and record types.
Preserve source identifiers, event times, and collection times.
Track collection gaps and late records before declaring an outcome verified.
Agree on sensitive-field redaction before evidence leaves a source.

Control a consequential action

Enforcement requires a supported interception point before the action executes. A read-only audit connection cannot stop a write.

Identify the gateway, tool wrapper, or runtime hook that receives the action first.
Define allow, block, and human-review decisions for that boundary.
Decide how approval expiry, retries, and unavailable controls behave.
Verify bypass paths and downstream effects separately.

The sources and hooks above are integration requirements to assess for your environment. Supported connections and the exact enforcement boundary are agreed for the selected workflow.

PLAN THE EVALUATION

Give your technical team
a concrete starting point.

Bring one workflow, its runtime, and the business system it changes. Use the review to establish a connection plan and measurable acceptance criteria.

Evaluate Spektris

Connection and ownership01

Identify the workflow owner, agent runtime, systems of record, available APIs or event exports, and service accounts. Establish correlation IDs, collection frequency, expected volume, and who maintains each connection.

Deployment and identity02

Agree where collectors and controls will run, the required network paths, and how service credentials are issued, scoped, rotated, and revoked. Confirm supported deployment options against the selected environment.

Data handling and retention03

Identify the exact fields collected, where evidence is processed and stored, who can inspect it, and the required retention, export, and deletion rules. Define treatment of secrets and sensitive records before collection begins.

Acceptance and failure modes04

Test matched outcomes, unexpected effects, missing records, duplicate delivery, expired delegation, and unavailable controls. Measure evidence coverage, investigation time, human-review effort, and operational overhead against the existing workflow.

Connect the task.Inspect the action.Verify the effect.