Job · Rung 3 · Rung 4 · Rung 5

Build a distillation or impersonation case that holds up

Collect, preserve and present a distillation or impersonation case so another expert can check every step.

For Frontier lab trust and safety, and model owners, Investigators, law enforcement and litigators. Works at Rung 3 · Investigative, Rung 4 · Forensic, Rung 5 · Evidentiary.

The situation

Business

A model owner, an AI lab, or a brand whose people are being impersonated.

Use case

Account farms query a model to train a copy, or synthetic media impersonates an executive.

Risk

A wrong attribution, or a case that falls apart when the method is examined.

Today's failure

Evidence is scattered across logs, screenshots and spreadsheets, with no custody and no reproducible method.

Silvector

Signed, chained receipts for API traffic, content hashes, replay and offline verification, with case custody planned.

Evidence

Records another expert can verify offline and a method they can rerun to the same output.

Judged on

Attributed incidents, time to attribution, and evidence that holds up.

Steps

1. Preserve first

   Before analysis, content-hash every artifact (request logs, outputs, media files) with SHA-256 and record who collected it, when and how. Analysis on an unhashed copy is analysis nobody can check.

   shCopy

   sha256sum artifacts/* > artifacts.sha256
   # record collector, time, source and method next to the hashes

2. Anchor API traffic in receipts

   When the traffic ran through Silvector, each request has a signed receipt with an action hash. Within one Worker isolate, prev links them in order. Export the receipts and hash the export like any other artifact.

3. Reconstruct lineage across accounts

   Rung 4 needs links across at least two sessions, accounts or pieces of infrastructure, each link from independent signal families. Record why each pair of signals is independent.

4. State attribution as our assessment, with its confidence

   Write attribution as an assessment with an interval and the method that produced it. A point estimate without an interval does not belong in a case file.

5. Write the methods appendix

   List every step, input hash and tool version so another expert can rerun the analysis to the same bytes. Include known error rates with denominators, or say none are known.

Guardrails

• Attribution to a person, company or country is a conclusion for counsel, not for a dashboard.
• Heavy legitimate use (evaluations, research, integrations) can look like distillation by volume. Rule it out explicitly.
• This page covers defense: preserving and presenting evidence. It does not cover evading anyone else's detection.

What works today

Receipts, replay and offline verification work today. A published log of real receipts is not built yet. Evidence packs and the console distillation card ship behind flags with synthetic demo data. Case custody, legal hold and the methods appendix are planned (AG4-400).

Next