Skip to content
GHOST PROTOCOL
Guide

From first file to signed conclusion.

Eight steps. Each case shows where you are and the next thing to do on its overview page. The AI can read and suggest; only people decide.

  1. 01

    Sign in

    /signin

    Type your name and pick a role. There is no password: it is a demo identity.

    Every decision, observation and signature is recorded under that name in the audit trail.

  2. 02

    Create a case

    /cases/new

    Give it a title, the scope (what it must establish, and what it must not) and the incident window.

    The window's UTC offset is used for any time recorded without one, and every event says so.

  3. 03

    Upload evidence

    Intake

    Logs (CSV, JSON, text), statements (PDF, Word), photos, audio and video, up to 50 MB each.

    Each file is checked against its contents, fingerprinted with SHA-256 and never changed.

  4. 04

    Extract events

    Extract

    Logs become events on upload. For recordings, log what you see at a timecode. For documents and photos, ask the AI to read them and accept or reject each suggestion.

    Nothing the AI proposes reaches the timeline until a named person accepts it. Quotes are checked word for word.

  5. 05

    Set clocks

    Evidence → Source clock

    Mark a source as trusted, state a known error, or pair moments it shares with a trusted source.

    Matching moments lets the engine work the error out itself (RULE-TIME-002). Original times never change.

  6. 06

    Read the timeline and decide conflicts

    Timeline · Graph · Analytics · Conflicts

    See every source on one clock, how the evidence connects, and what each rule flagged. Record a decision with a reason for every conflict.

    A conflict is a prompt for review, never an accusation. Signing waits until every conflict is decided.

  7. 07

    Write questions and claims

    Questions & claims

    Write what the case must answer. Attach claims, each citing the evidence it rests on.

    A claim's state must match its citations: nothing is called supported without a source.

  8. 08

    Conclude and sign

    Conclusion

    Answer each question as established, partly established or not established, cite the records, confirm both statements and sign.

    Established needs a supported claim. Each signature is a version; the report carries it with the doubts left in.

Tools along the way

AI assistant
A briefing that pulls the case together, and answers to questions in plain language, all cited. Claude Sonnet 5.5; it never decides.
Analytics
Activity by source, how each source holds up, claims, clock corrections, conflicts and who did what. Filters apply to every chart.
Power BI / Tableau
Analytics → Download: an Excel workbook of tidy tables that both tools open directly.
⌘K
Press ⌘K, Ctrl+K or / anywhere in the workspace to jump to any record.
Guided demo
Seven stops through the fictional case, from the home page or the dashboard.

Three rules for a sound conclusion

  1. Cite the record for everything you state.
  2. Write "not established" when the evidence cannot settle it.
  3. Never name who is responsible unless a cited record shows it.
Try it on the demo case