The chain · 02 Seal & Register

The auditor cannot be the audited._

sealed envelope · proof
"proof": {
  "type": "DataIntegrityProof",
  "cryptosuite": "eddsa-jcs-2022",
  "verificationMethod": "did:key:z6Mk...#key-1",
  "proofValue": "z58xkAtLcnvETu..."
}

A log says something happened — your log, your word. A sealed, registry-anchored record says what happened in a form anyone can check without asking you. That's the difference between a note to self and a receipt.

What a seal gives you_

Tamper-evident

W3C Data Integrity Proofs (eddsa-jcs-2022). Change one byte of a sealed record and verification fails — anywhere, for anyone, forever.

Registry-anchored

DeepaData-issued seals add a registry entry: discoverable and queryable by certificate ID. Re-appraisals are appended, never rewritten — never silent deletion.

Independently verifiable

Verification needs no DeepaData account and no access to the record's content. The proof is exposed; the payload is not.

Verifiable offline

Open tooling (ddna-tools, ddna-reader — MIT) verifies a sealed envelope with no network at all. Self-sealing with your own keys is free, forever.

Three conformance levels ladder up: Compliant (schema-valid) → Sealed (signed, self-service) → Certified (DeepaData-issued, registry-listed). Conformance levels · Public registry

One call to seal_

/v1/issue · seal + register
const sealed = await fetch(
  "https://deepadata.com/api/v1/issue",
  {
    method: "POST",
    headers: { Authorization: "Bearer dda_live_..." },
    body: JSON.stringify({
      artifact,                    // the extracted EDM record
      pathway: "delegated",
      authority: "app:your-platform"
    })
  }
).then(r => r.json());

// sealed.certificate_id → hand to anyone; they can verify
// without your help and without seeing the content.

Beyond observation

A trace is not a record_

Observability tools watch your system for you. A sealed record speaks for you — to people who have no reason to take your word. Keep your traces; add the record layer they were never designed to be.

The proof record does double duty: the trace your auditor reads is the one your engineers use to see what the model was actually computing over — and to make the product better.

Traces — for engineers

  • Built for debugging: latency, token counts, prompt inspection
  • Retention-limited and deletable by design
  • Unattested — no signature, no registry, no third-party check
  • Read by the team that produced them

Exactly what you want for fixing your product.

Sealed records — for regulators

  • Built for evidence: what passed between a person and an AI
  • Durable, append-only — re-appraisals appended, never rewritten
  • Signed at capture time; anyone can verify independently
  • Read by whoever has to trust them — regulator, court, insurer, the person

Exactly what you need when one interaction matters.

The same goes for memory systems: memory optimizes what a model recalls next — it compresses, rewrites, and forgets by design. A record preserves what happened, unmodified and provable. Both are natural consumers of sealed records, not substitutes for them.

Sealed records compound into a trajectory._