ARCHIVIST

Centennial Defense Systems

Turn scattered source material
into evidence another reviewer can check.

Turn documents, web captures, and AI conversations into reviewable evidence packages.

Keep core archive work on the operator's Mac.

See the verification proofSee reviewer outcomes

macOS · Local archive processing · Tamper-evident export · Source-linked review

[00] hero · sha:51fc02cfe00d

[01] how-it-works · sha:3e733a4ae6be

How It Works

Four steps from evidence to reviewable case package

1. Capture

Bring documents, web captures, and AI conversations into one review workflow.

2. Investigate

Triage evidence into cases. Map entities and relationships. Annotate sources with integrity-chained notes, tags, and flags.

3. Correlate

Search across all case evidence by entity, document, time window, or keyword. See connections the manual way would miss.

4. Export

Build evidence packages with chain-of-custody notes, integrity verification, PDF reports, and a standalone verifier.

[02] different · sha:80df92f4af58

What Makes It Different

Content-addressed integrity by architecture

  • Trace findings back to source material and detect post-export changes.
  • Annotations are integrity-chained separately from source evidence.
  • Evidence packages include verification metadata for detecting changed source files.
  • Keep core archive work on the operator's Mac.

[03] proof · sha:2bfb8aa9224a

Proof

Don’t take our word for it. Run the verifier.

Every exported case package carries a SHA-256 manifest of its own contents and a standalone verifier. Anyone who receives the package — opposing counsel, a client, a court’s technical staff — can re-run that check without installing Archivist and without taking your word for anything.

What ships in the package

Package contents
evidence_package_sample-matter_20260725/
├── README.md
├── INTEGRITY_MANIFEST.json      SHA-256 of every file
├── CHAIN_OF_CUSTODY.json        who did what, when
├── PROCESSING_PROVENANCE.json
├── evidence/
│   ├── sources/
│   ├── findings/
│   └── annotations/
├── report/case_report.pdf
├── verification/verify.py       standalone, no install
└── viewer/index.html            offline case viewer

Integrity manifest (excerpt)

INTEGRITY_MANIFEST.json
{
  "schema_version": "archivist-evidence-manifest/v1",
  "created_at": "2026-07-25T19:38:34.313674+00:00",
  "package_id": "evidence_package_sample-matter_20260725",
  "file_count": 9,
  "files": {
    "CHAIN_OF_CUSTODY.json":
      "sha256:4158116a4507b139b22bc0d6a5e4456347e8069f…",
    "evidence/findings/f-sample-matter-001.json":
      "sha256:9525213cb882ac19ddd27ace86c43a196bf3153d…",
    "README.md":
      "sha256:e4562d701dabdb2413b625843cc205dc44c7018b…"
  }
}

Untouched package verifies clean

Verification passed
$ python3 -m investigator verify evidence_package_sample-matter_20260725
INTACT: All files verified.
$ echo $?
0

Change one value and it refuses, loudly

Tamper detected — exit 1
$ # change one severity value inside one finding file
$ python3 -m investigator verify evidence_package_sample-matter_20260725
FAILED: Integrity check failed.
  Tampered: evidence/findings/f-sample-matter-001.json expected=sha256:9525213cb882ac19… got=sha256:9fec60c2a15f2d5f…
$ echo $?
1
Standalone verifier, same package
$ python3 verification/verify.py
Verifying evidence package: evidence_package_sample-matter_20260725
============================================================
  [Package signature] PASSED
  [Manifest integrity] FAILED
    - TAMPERED: evidence/findings/f-sample-matter-001.json expected=sha256:9525213cb882ac19… got=sha256:9fec60c2a15f2d5f…
  [Chain of custody] PASSED
  [Annotation chain] PASSED
============================================================
RESULT: TAMPERED
One or more verification checks failed.

Transcripts above are real output from Archivist v6.1.0 against a demo case generated locally, not a client matter. Archivist is tamper-evident: it detects that a file changed after export. It does not prevent someone from changing a file. Integrity is not authorship: Archivist runs with no account and no signing keys, so the operator recorded in CHAIN_OF_CUSTODY.json is a stated identity, not a cryptographically proven one. And it makes no claim about admissibility, which is a question for your jurisdiction and not a property of any tool.

[04] outcomes · sha:ce004e6e9302

Buyer outcomes

A review trail that travels with the work

Archivist keeps the source trail, integrity record, and verification path together from capture through handoff.

Reviewable package

Turn documents, web captures, and AI conversations into reviewable evidence packages.

Source traceability

Trace findings back to source material and detect post-export changes.

Local-first handling

Keep core archive work on the operator's Mac.

Independent verification

Hand a package to another reviewer with a standalone verifier, without requiring them to trust Archivist's word.

[05] personal · sha:882393773481

Personal archives

Search your own archive on your Mac

Archivist includes local-first workflows for reviewing your own exported conversations and documents. Preserve the source trail, search the material, and detect changes after export without moving the core archive workflow off your Mac.

Import

Work with exported conversations, documents, and PDFs.

Search

Review imported material through local-first search workflows.

Keep

Preserve versioned, tamper-evident archive records on your Mac.

See the verification transcript →

Verify the boundary

Know what is proven before you rely on it

Review current product availability, support delivery, and attestation facts in one source-controlled record.

Request access by emailRead Trust & Status