TRACE / 01VERIFIABLE PROCESS PROOF

One process crossed five systems. Where is the proof of the whole thing?

A vendor approval, AI agent run, or regulated decision leaves evidence scattered across logs, files, model records, and queues. Traces binds the signed records to one process ID, preserves their order, and seals the complete sequence into one independently verifiable proof.

Create your first trace View trace docs

One trace ID across your workflow Events, files, and AI records JSON, PDF, and public verification

LIVE TRACE ASSEMBLY

app.invoance.com/dashboard/traces/3a889ca5

3a889ca5Vendor onboarding · Acme Corp

open

onboarding.startedProcurement · 09:12:04

5f61a420a521030d0e…

Records attach with the same trace_id until your process is complete.

01OpenCreate a trace around the real process

02AttachAdd records as your systems produce them

03SealLock the complete ordered evidence set

04VerifyShare one proof outside your stack

02THE EVIDENCE GAP

The process finished in minutes. Proving it later takes weeks.

Each system can show its own record. None can prove the complete sequence, what was included, or whether the evidence changed after the process ended. That gap becomes your problem when a customer, auditor, or regulator asks one simple question: “Show me exactly what happened.”

WITHOUT A TRACE

APPLICATION LOGDOCUMENT STOREMODEL GATEWAYCASE QUEUEPAYMENT PROVIDER

No single artifact proves the items belong to the same process or stayed in order.

WITH INVOANCE TRACES

E signed eventD anchored documentA AI attestationE signed outcome

One composite hash. One signed seal. One ordered proof bundle.

03ONE EVIDENCE THREAD

Follow the work across systems. Seal the proof at the finish line.

Your application decides what belongs in the process and when it is complete. The trace simply gives each signed record a shared context and a provable order.

Who approved this supplier, using which checks and documents?

ProcurementDocument vaultScreeningAI review

01EVENT

Onboarding started and sanctions check passed

02DOCUMENT

The exact W-9 and contract that were reviewed

03AI

Signed risk summary, model, and approval context

04EVENT

Final approver, policy version, and timestamp

One sealed vendor file that answers the review without rebuilding the story.

04FOUR API MOMENTS

Create. Attach. Seal. Verify. No workflow engine required.

Traces fits around the process you already run. You choose the boundary; Invoance preserves the evidence inside it.

Create a trace

Open one trace for the business process and keep your own case, order, run, or workflow identifier beside it.

trace_id: trc_01KXV84C2QY7P6D9

Attach signed records

Pass the trace ID when you record an event, anchor a document, or create an AI attestation. Nothing else in the workflow changes.

event · document · attestation

Seal the sequence

When the process is complete, Invoance hashes the ordered item set and signs the composite result. The sealed trace cannot accept new items.

status: sealed · items: 5

Verify one proof

Export JSON for machines, PDF for reviewers, or share a verification page. One check covers every item and its order.

signature: valid · order: intact

05WHAT GOES INSIDE

Three proof primitives. One complete process record.

Every item remains independently verifiable. Sealing a trace adds the proof that those exact items formed this exact sequence.

Events

Approvals, state changes, payments, tool calls, handoffs, and outcomes from the Event Ledger.

approval.granted · refund.issued · shipment.releasedExplore events

Documents

The exact files the process used or produced, anchored by hash without forcing you to move storage.

contract.pdf · decision-notice.pdf · invoice.jsonExplore documents

AI attestations

Signed model inputs, outputs, rationale, tool context, and human approvals from AI-powered decisions.

risk-summary · agent-decision · human-reviewExplore ai attestations

06SHIP THE WHOLE LIFECYCLE

One trace ID. Your language, your workflow.

Use the official SDK that already fits your stack. Create a trace, attach records on the ingest calls you already make, seal it when the process completes, and retrieve the proof bundle.

Nine SDK and HTTP examples
No event bus or pipeline migration
Async sealing for reliable processing
Offline verification support

Read the Traces API docs

TRACE LIFECYCLE

POST /v1/traces

PythonCREATE → ATTACH → SEAL → PROVE

trace = await client.traces.create(
    label="Vendor onboarding: Acme Corp"
)

await client.events.ingest(
    event_type="onboarding.started",
    payload={"vendor": "acme"},
    trace_id=trace.trace_id,
)

await client.traces.seal(trace.trace_id)
proof = await client.traces.proof(trace.trace_id)

Your workflow stays in place. The trace ID follows the records that matter.

07WHAT CHANGES

Less reconstruction. More evidence that travels.

Traces turns the evidence you already produce into a portable record of the whole process, without turning Invoance into your workflow system.

Shorter evidence hunts

Stop asking four teams to rebuild one process from exports, screenshots, and ticket comments.

Cleaner control evidence

Hand auditors one ordered proof bundle instead of granting access to every source system.

Defensible AI workflows

Connect what the model decided to the documents, approvals, and downstream action around it.

Portable process trust

Let a customer, partner, or regulator verify the trace without trusting your dashboard or your word.

YOUR APPLICATIONRuns the process

INVOANCE TRACESPreserves the proof

08SEAL THE WHOLE STORY

The next time someone asks what happened, send one proof.

Start with one workflow and one trace ID. Keep your systems, your storage, and your process exactly where they are.