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

Four ways to read a pack — ordered by what leaves your network

A pack is files on your disk, so the reader is your choice and the privacy answer follows from that choice, not from us. Each path below states what actually leaves your network. On all four, Citenda receives nothing at read time — we are not in the read path at all.

Four ways to read a pack — ordered by what leaves your network The corpus files sit on disk inside your own network, as plain, portable files. Path 1, Sovereign mode, is an open-source model you self-host on hardware you control: it stays inside the network, nothing leaves it, and it runs with no connection at all. Paths 2, 3 and 4 — Claude Code, Cowork, and any other stack — read the same files from the same disk, but send to your model provider, whether that is Anthropic or one of your own. What leaves your network on those three is your question and the passages the tool reads. Citenda receives nothing on any path, and is never in the read path. Your network Corpus files plain, portable files Path 1 — Sovereign mode Open-source model, self-hosted on hardware you control Leaves your network: nothing. Runs with no connection. Paths 2, 3 & 4 — hosted models Claude Code · Cowork · your stack reads the same files, same disk Your model provider Anthropic, or yours Paths 2–4 — what leaves: your question, and the passages the tool reads Citenda receives nothing on any path — never in the read path
One corpus, four readers — the privacy decision is the reader you pick, not the pack

Path 1 — Sovereign mode (an open-source model on hardware you control)

  1. Unzip the pack on a machine you own — a workstation or a server inside your own network.
  2. Run an open-source model on that hardware and point it at the unzipped folder.
  3. Ask the pack's own control questions with the network cable out, if you want to prove it.

Retrieval and inference both happen on your hardware, so there is no API call to make and nothing to take on trust about what happens after a question leaves the room. This is the strictest answer available, which is why it is listed first: the paths below are conveniences you choose knowingly, not the default.

Leaves your network: nothing. This path runs with no connection at all.

Path 2 — Claude Code (zero runtime, retrieval on your disk)

  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 on disk.
Leaves your network: your question, and the passages the agent reads. Zero runtime is true and stays true — no Citenda service runs anywhere, and no index of your files is built off your disk. But the passages the agent selects are sent to Anthropic's API as the context for its answer, so this is not a zero-egress path. If nothing at all may leave your network, use Path 1.

Path 3 — 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.
Leaves your network: your prompts, and the files you attach to the workspace — whole files, not only the passages a reader selects. The pack content is our product, so sending it is fine; your own confidential material may not be. If nothing may leave your network, use Path 1.

Path 4 — any other 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.

Leaves your network: whatever that stack sends. Self-hosted end to end, that can be nothing; pointed at a hosted API, it is whatever that API receives. The pack does not constrain the choice either way — it is your call, not ours.

Verification

Verify your download

  1. Compare the zip's SHA-256 with the checksum in your delivery email.
  2. Run verify.py for a full offline re-check — per-file hashes, unit counts, every citation resolved.
  3. Run verify.py --acceptance to re-run the pack's own 16 acceptance questions, published in ACCEPTANCE.md.

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 → verify.py --acceptance → email. Firm and Group buyers get a named support contact.

Support email: boris.marchand@citenda.com

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 →