Investigative software for WindowsMac & Linux planned next week · Downloads & access →
Documentation

Understand the work before importing the files.

These website guides explain the current product roles and demonstration workflow. Version-specific installed manuals and accepted download instructions remain tied to the released edition.

Product guides

Start with the application you are evaluating.

ProofDesk: source to claim

  1. Create a local case and preserve the originals separately.
  2. Record each source’s origin, exact locator and limitations.
  3. Link evidence as support, contradiction or context.
  4. Review chronology, source ancestry and unresolved claims.
  5. Inspect the private report and approved export scope.

Back up plaintext project files securely. A completed integrity check is not a truth verdict.

Inspect ProofDesk →

Field System: repeatable case work

  1. Choose a template suited to the research question.
  2. Keep case IDs and original source locators consistent.
  3. Record review decisions and stress-test questions.
  4. Inspect any edition-specific exchange before accepting it.

The 110-template catalogue and private exchange QA do not establish universal device or cross-product acceptance.

Inspect Field System →

Research Edition: cited report review

Choose the report path and inspect its input/provider requirements. Review cited passages, uncertainties and extraction limits. Fusion combines related report work; bounded Autopilot requires consent and supported execution scope. Human approval remains necessary.

Browse all 20 workflows →

Studio: draft to output preparation

Organize the draft, source notes, revisions and editorial checks. Prepare the project JSON or website HTML export supported by the exact edition. Review file permissions, citations and private material before using any output. No automatic CMS publication is promised.

Inspect Studio →
Shared practices

Keep review, publication and permission separate.

Our fictional Harbor Grant example follows SRC-001–004 and CLM-014–017 throughout. Preserve those relationships when preparing a handoff; inspect the receiving application and supported format instead of assuming lossless automatic transfer.