Docs & install guides

Docs

Everything needed to install, verify and get help. Docs-first support: most answers live on this page before they are ever emailed.

Choose your path

Three ways to run a pack — only one of them leaves your network

Three ways to run a pack — only one of them leaves your network Pack files on disk (Plain, portable files) and Claude Code / any stack sit inside Your perimeter. Cowork path: Path 1 — Cowork: your prompts and the attached files leave your perimeter to Anthropic cloud. Paths 2 & 3 — nothing leaves your perimeter. Your perimeter Pack files on disk Plain, portable files Claude Code / any stack Reads the files directly Cowork path Anthropic cloud Cowork processing Path 1 — Cowork: your prompts and the attached files leave your perimeter Paths 2 & 3 — nothing leaves your perimeter
The Cowork path is a convenience, and it is the one path that crosses the boundary

Path 1 — Cowork (convenience)

  1. Download the pack zip from your delivery email and unzip it.
  2. In Claude's Cowork, attach the pack folder to your workspace.
  3. Ask questions; answers cite the pack's stable citation keys.
Honest note: on this path, your prompts and the attached pack files are processed in Anthropic's cloud. The pack content is our product — fine to send; your own confidential material may not be. If nothing may leave your network, use Path 2.

Path 2 — Claude Code (zero runtime, zero egress of your data)

  1. Unzip the pack inside your project workspace.
  2. Point Claude Code at the unzipped pack — it reads the files directly from disk.
  3. Work as usual — retrieval happens locally against the files.

Path 3 — any agent stack

Packs are tool-agnostic: plain, portable files with stable citation keys. Works with Claude out of the box; LangChain, LlamaIndex, your in-house RAG — anything that reads files — consumes the same artifact, and the pack documents how to read it.

Verification

Verify your download

  1. Compare the zip's SHA-256 with the checksum in your delivery email.
  2. Run the included verification tool for a full offline re-check (per-file hashes, unit counts).
  3. Run the self-test to confirm the corpus answers its own control questions.

Editions are immutable. If a checksum ever mismatches, stop and contact us — we never silently re-upload an artifact.

Support

How support works

Docs-first, email-only. Order of escalation: the notes shipped with the pack → this page → the self-test → email. Firm and Group buyers get a named support contact.

Support email: [email protected]

Lost your download links?

Links expire minutes after they are issued — that is deliberate. A self-service resend form, keyed on your purchase email, is on the way.

Pending: the self-service resend form goes here. Until then, email us from your purchase address and we will re-issue your links.

After purchase: your pack spend counts

If you later bring us your own document estate, 100% of what you have spent on packs in the trailing 12 months credits into the first engagement signed within 12 months. (It never credits against the Estate Assessment, which everyone pays in cash.)

What we do with your own documents →