Evidence for people, vendors, software, and AI

Make important digital work independently reviewable.

DAR links actions, authority, evidence, approvals, and outcomes into portable receipt chains—without replacing the systems where the work already happens.

Explore third-party verificationCreator product

DAR verifies the integrity and support behind recorded events. It does not determine truth, quality, legal compliance, ownership, or contractual acceptance.

Third-party work verification

Verify the evidence around the work—not every movement of the worker.

DAR can document milestones performed by contractors, subcontractors, employees, software, and AI agents. It captures agreed material events and packages the supporting evidence for independent review.

1

Agree on what must be proven

Define milestones, acceptable evidence, authorized actors, approval requirements, retention, and prohibited data before capture begins.

2

Reference evidence already produced

Use file hashes, commit IDs, test results, tickets, approvals, system records, timestamps, and attestations rather than recreating the workflow.

3

Generate a reviewable package

Show what evidence is verified, what is missing, who approved the result, and which limitations remain.

Non-invasive by design

DAR does not have to be installed in every system or agent.

Adoption can begin with no software installation and deepen only when stronger automation is justified.

1. Evidence upload

Secure forms, folders, email imports, or exported records. No internal installation required.

2. Read-only connectors

Limited APIs, webhooks, or service accounts scoped to specific projects, repositories, or events.

3. Local collector

An optional customer-controlled helper can hash and issue receipts without exporting sensitive raw content.

4. Native receipts

Future SDKs let platforms and AI agents issue DAR-compatible attestations directly at the source.

No default surveillance. DAR is designed for material event capture—not keylogging, continuous screen recording, unrelated message collection, or broad employee monitoring.
Transparent evidence strength

A profile is clearer than a single score.

DAR reports the components supporting an event instead of implying that a number measures truth, compliance, or quality. The example profile below is illustrative, not a current verification result.

Receipt-chain integrityLinked events have not been altered after issuance.
CHECKABLE
Independent timestampThe receipt hash existed no later than the certified time.
NOT PROVIDED
Source-system evidenceApproved references or exported records support the event.
EXAMPLE PRESENT
Counterparty attestationA customer, platform, reviewer, or collaborator independently confirms the event.
NOT PRESENT
Evidence, not judgment

DAR records controls without becoming the control authority.

A separate policy engine or customer workflow may permit, deny, or pause an action. DAR records the request, applicable authority, decision, evidence, and outcome. This preserves DAR as a neutral evidence layer.

DAR can support verification that

  • A specified event was recorded and signed
  • Evidence existed by a documented time
  • A particular artifact version was submitted
  • Tests, reviews, or approvals were reported
  • Required evidence is present or missing

DAR does not automatically prove that

  • The work was high quality or error-free
  • Every relevant action was captured
  • The vendor was truthful before timestamping
  • The work satisfied every contract or law
  • A human fully understood an approval
First product wedge

Creators remain the low-risk usability laboratory.

The initial Verified Creation Report documents prompts, generations, human edits, reviews, approvals, exports, and publication events. The same core receipt model can later support organizational and contractor evidence packages.

Verified Creation Report

A portable creation history for music, video, images, writing, and software produced across multiple tools.

  • Human and AI contribution markers
  • Evidence references and artifact hashes
  • Component-level evidence status
  • Optional timestamps and collaborator attestations

DAR complements C2PA

C2PA can carry provenance credentials with an asset. DAR preserves the broader process timeline across tools, files, people, and systems, and can record a C2PA manifest as one event in that timeline.

Intended operating models

Companies can build their own capture systems—and still use DAR.

DAR is designed to support multiple deployment and verification models as the product matures. These options describe intended operating approaches, not currently certified production services.

Hosted DAR

A future managed option for selected evidence, receipt issuance, verification, and reporting.

Customer-hosted

A future deployment model that keeps sensitive data and capture components inside the customer environment while preserving compatible receipts.

SDK and verification

Organizations may instrument their own systems using future DAR-compatible SDKs or submit compatible receipts to an independent verification service.

Deliberate sequencing

Prove value before expanding infrastructure.

NOW

Case studies, receipt integrity, secure pilot boundaries, and human-readable evidence packages.

NEXT

Read-only connectors, assisted capture, external reviewers, and paid controlled pilots.

LATER

Team workflows, contractor verification, governance exports, and customer-hosted deployment.

ROADMAP

Agent SDKs, platform co-signatures, interoperable attestations, and an independent trust network.

Make the work—and its limits—reviewable.

DAR is validating evidence packages through controlled case studies before making broader production, compliance, or legal claims.

Discuss a verification pilot View the open project