Product
One indexed record set. Six ways to read it.
CaseSignal reads each record once and keeps the exact place every passage came from — page, sheet and row, section or timecode. Everything after that is a different reading of the same index, and each one carries its citations with it.
The record set · Source library & viewer
Records go in whole, and stay openable.
A case begins as a pile of files, links and notes. CaseSignal turns that pile into an indexed library without asking you to rename, reformat or re-key anything.
Four ways in
Upload files, point at a public webpage, paste a transcript, or type a note. All four become first-class sources that can be cited the same way.
Processing you can watch
Each record moves through queued, extracting, indexing and analyzing to complete. A record that extracts poorly is marked “needs review” rather than being quietly indexed as empty.
A viewer that lands on the passage
Opening a citation opens the record at that page, sheet row or section, with the cited passage highlighted in place — not a copy of it in a sidebar.
Deleting is complete
Removing a source removes its stored file, its excerpts and every citation that pointed at it, so nothing in the case can outlive the record behind it.
- Indexed
Procurement Request.pdf
3 pages
- Indexed
Vendor Proposal.pdf
5 pages
- Indexing
Invoice Register.xlsx
Sheet “Invoices”
- Extracting
County procurement page
Public webpage
- Queued
Signed receipt.png
Vision extraction
- Indexed
Interview notes
Typed note
| Claim | Status | Cites |
|---|---|---|
| The vendor proposal commits to delivery on September 10, 2024. | =Supported | +1 −0 |
| The quantity invoiced matches the quantity recorded as received. | ≠Contradicted | +0 −2 |
| A revised delivery date was communicated to the committee. | ≈Partial | +1 −1 |
| The 12 back-ordered units were subsequently delivered. | ?Unresolved | +0 −0 |
01 · Claim ledger
Every checkable assertion, with the evidence for and against it.
A claim is a statement the records make that could be checked. CaseSignal extracts them from the excerpts themselves, then derives a status from the citations attached — never from a guess about who is credible.
Status is computed from counted supporting, conflicting and context citations, so a status and its evidence can never drift apart. Change the evidence and the status follows; set the status yourself and it is recorded as an analyst decision that later analysis will not overwrite.
- =Supported
- Directly evidenced by at least one cited source excerpt, with no cited excerpt against it.
- ≈Partially supported
- Some elements are evidenced; other elements are not established by the cited sources.
- ≠Contradicted
- At least one cited source excerpt is inconsistent with the claim as written.
- ?Unresolved
- The case sources do not settle this point in either direction.
- ·Context only
- Background that frames the record without asserting a contested fact.
02 · Verified timeline
A chronology that admits what it does not know.
Dated events are pulled from the records with the citation that dates them. The hard part of a chronology is not ordering events — it is being honest about which dates are actually established.
Every event carries a precision, so a date inferred from context never reads like a date stated in a filing, and two records that disagree produce one event marked as disputed rather than two events that look like a sequence.
- ●Exact
- A specific date stated in a cited source.
- ◐Estimated
- Inferred from surrounding context; not stated directly.
- ▭Range
- Occurred somewhere inside a stated window.
- ⚠Conflicting
- Sources give different dates for the same event.
Jun 14, 2024
Purchase request submitted
S1 p. 1
Aug 2, 2024
Notice of award issued
S3 p. 1
Sep 10, 2024
Delivery date committed in proposal
S2 p. 4⚠ Sources differ
Sep 18, 2024
Delivery date stated to committee
S4 p. 14⚠ Sources differ
Sep 21, 2024
Delivery received — 228 of 240 units
S6 p. 1
03 · Evidence graph
Who appears where, and how the records connect.
Named parties, organizations, documents, locations and transactions are extracted with the excerpt that names them, then drawn as one connected picture of the case.
Relationships are typed rather than generic — authored by, sent to, paid, occurred at, precedes, supports, contradicts — and a contradicting edge is drawn as a contradiction rather than hidden. Selecting any node or edge shows the excerpts that produced it, so the graph is an index into the records rather than a summary that has floated free of them.
04 · Discrepancy matrix
Where the records disagree with each other.
CaseSignal compares stated values across records and reports the difference. It describes what each record says and stops there — it does not decide which one is right, and it does not characterise a difference as an error or as wrongdoing.
These records appear inconsistent regarding the reported delivery date. No record in this case documents an agreed change to the contract schedule.
Stated value
September 10, 2024
Halvorsen Office Systems commits to delivery of all 240 units on September 10, 2024.
Stated value
September 18, 2024
The Facilities Manager stated that delivery of the 240 workstations is scheduled for September 18, 2024.
| Row | Invoice | Vendor | Qty | Amount |
|---|---|---|---|---|
| 219 | INV-4469 | Meridian Facilities | 30 | $21,900.00 |
| 220 | INV-4470 | Northstar Print | 48 | $3,264.00 |
| 221 | INV-4471 | Halvorsen Office Systems | 240 | $178,080.00 |
| 222 | INV-4472 | Halvorsen Office Systems | 1 | $0.00 |
Compared across records
- Date
- Time
- Amount
- Count
- Name
- Title
- Location
- Procedure
- Status
- Sequence
Each difference opens as a side-by-side comparison: the stated value in each record, the verbatim excerpt it came from, and its exact location. Differences carry a review state, so one that has been explained by a further record is closed with a reason rather than deleted.
05 · Case copilot
Ask the case. Inspect the evidence.
The copilot answers from this case's records and nothing else. It has no access to the open web, to other cases, or to anything the model happens to remember about the subject.
- Every factual sentence carries a citation you can open at its exact location.
- When the records conflict, the answer says so and gives each side with its own citation.
- When the records are silent, the answer says the sources do not establish the point rather than filling the gap.
- Any answer can be promoted into a claim in the ledger, carrying its citations with it.
Which records disagree about the delivery date?
The available sources conflict on this point.
The vendor proposal commits to delivery of all 240 units on September 10, 2024 S2 p. 4.
The committee minutes record delivery as scheduled for September 18, 2024, and record that no formal amendment was approved S4 p. 14.
The receiving report records the delivery arriving on September 21, 2024 S6 p. 1.
3 citations verified against the retrieved excerpts. Unverifiable citations are removed before an answer is shown.
Key findings
- The receiving report records 228 units received, with 12 units back-ordered S6 p. 2
- The invoice register records 240 units invoiced S5 Sheet “Invoices,” row 221
- The award was made on August 2, 2024 in the amount of $178,080 S3 p. 1
06 · Brief & evidence room
Publish the trail, not just the conclusion.
A brief is assembled from the case itself. Narrative sections are drafted from the cited material and are fully editable; inventory sections are compiled from what you marked for inclusion.
Export as Markdown or PDF, or publish a read-only evidence room at a link you name — with an expiry date, an optional password, analyst notes hidden and downloads disabled if you prefer. Sharing is off until you turn it on, each item is opted in individually, and the link can be revoked at any time.
Traceability
How a citation stays honest.
Answers are produced in four steps, and the fourth is the one that matters. Nothing reaches you until its citations have been checked against the excerpts that were actually retrieved.
Plan
Your question is turned into a retrieval plan: which sub-questions to ask of the index, and which records or date ranges are in scope.
Retrieve
The plan runs against this case's excerpts using full-text search, and semantic retrieval where embeddings are configured. The retrieved set is fixed before anything is written.
Generate
An answer is drafted from the retrieved excerpts alone, with a citation required on every factual sentence.
Verify
EnforcedEach citation is resolved back against the retrieved set. Anything that does not resolve is stripped from the answer before you see it.
When nothing survives verification
The drafted answer is discarded and replaced with a single sentence: “The available case sources do not establish this.” A confidently worded answer with no surviving citation is treated as a failure, not as a result.
The passage you read in a citation is the stored excerpt, shown verbatim — never a paraphrase, and never text regenerated at display time. That is what makes it possible to check the product against the record instead of taking its word for it.
Claim
All 240 workstations were delivered to Building C in September 2024.
- Supporting
- 2
- Conflicting
- 1
- Context
- 1
“Expected quantity: 240 units. Quantity received: 228 units. Quantity back-ordered: 12 units.”
Shown verbatim from the stored excerpt — the passage displayed is the passage that was indexed.
Supported formats
What CaseSignal can read, and what it keeps.
Uploads are validated by extension and content type before anything is stored, and each file may be up to 25 MB. Filenames are reduced to a safe basename on the way in.
| Format | Extensions | Preserved for citation |
|---|---|---|
| Page numbers, and the section heading each passage sits under | ||
| DOCX | .docx | Heading hierarchy and paragraph order |
| Text | .txt | Line ranges, and timecodes where a transcript contains them |
| Markdown | .md · .markdown | Heading hierarchy and list structure |
| CSV | .csv | Column headers and row numbers |
| Spreadsheet | .xlsx | Sheet names, column headers and row numbers |
| Image | .png · .jpg · .jpeg · .webp | Vision-extracted text with a confidence value per region |
| Webpage | public URL | Page title, canonical URL and section headings |
| Note | typed or pasted | Your own text, stored verbatim and citable by paragraph |
Both signals must agree
An upload is accepted only when its extension and its content type both resolve to the same known format. Clients that send a generic content type fall back to the extension; a mismatch is rejected with a message that names the problem.
Webpages are fetched carefully
URL imports run server-side against a protocol and port allowlist, with private and link-local addresses blocked and every redirect re-checked. The page is reduced to readable text and sanitized before it is stored.
Scanned pages are flagged
A PDF with no machine-readable text is detected during extraction and marked “needs review” with a low confidence score. Adding the page as an image lets vision extraction transcribe it, marking illegible passages rather than guessing them.
Built for questions that require receipts.
Start with one record set. CaseSignal will show you what it says, where it disagrees with itself, and what is still missing.