Citations that click back
Every citation is checked against your actual documents before it reaches you.
Termination requires 90 days' written notice §4.2 · 3.2 and fees are reviewed annually 3.2.1
§9.9rejected: no such source in scope
Private beta
sangrep reads the whole bundle, attachments and all, then answers with citations that click straight to the source. Checked before you ever see them.
+ 10 more files
Vendor agreement
3.2 · vendor-agreement.pdf · p4
This agreement is entered into by Meridian Systems and the counterparty identified in Schedule A, incorporating each appendix by reference.
§4.2 Either party may terminate with ninety (90) days' written notice.
Fees are set out in the pricing schedule (3.2.1) and reviewed annually each January under section 5.
What's the termination notice period?
90 days' written notice, per §4.2 of the vendor agreement.
When do the fees change?
Reviewed annually each January, per the pricing schedule.
Draft a risk summary of the appendix for the deal file.
Draft report
vendor-risk-summary.md
4 findings · every claim cited
Every citation is checked against your actual documents before it reaches you.
Termination requires 90 days' written notice §4.2 · 3.2 and fees are reviewed annually 3.2.1
§9.9rejected: no such source in scope
The model sees exactly the part you choose. Nothing else is visible to it.
1 · Overview
2 · Financials
3.2 · vendor-agreement.pdf
4 · Correspondenceinvisible
Archives inside memos inside emails. The whole package becomes one tree.
Every part of a document keeps its identity across re-parses. Old citations still land where they should.
node·3.2#a41f
↓ re-parse
node·3.2#a41f ✓
Every parse, decision, and model call is logged. Records get added, never rewritten.
+ 11:02 summarize · model
+ 11:10 override · you
supersedes ↑ · kept forever
Formats
A project holds as many files as the case needs, in any mix of formats, nested to any depth: archives inside memos inside archives. Anything sangrep can't parse yet still lands in the tree, flagged, for you to handle.
New formats ship only when they parse all the way down, embedded files and all.
Current capabilities
Upload a bundle and see everything inside it, including the spreadsheet inside the PDF inside the memo. Nothing gets lost on the way in.
For every embedded file you choose: keep it whole, summarize it, replace it with your own note, or leave it out. Your call, on the record.
Files open as formatted pages, not walls of extracted text. What you read is exactly what the model reads.
Scope a chat to the whole bundle, one appendix, or a single clause. Answers draw only from what you picked.
Every claim links to its source and gets checked against the tree first. Click through and read the original yourself.
Every step is logged as it happens. Ask why the answer says what it says, six months later, and get the whole story.
Tell sangrep what the package is about before it reads. It carries that context into every parse and answer, so it knows a schedule from a signature.
Charts, scans, and signatures are read by an image skill and cited by region, not skipped as pixels.
It follows references out to the open web, and hands you anything behind a login before it keeps going.
Human and AI, together
Auditing comes down to judgment calls, and some of those stay yours. Trim a file out of scope, summarize a section before it goes to the model, override what the parser found. Every call is on the record.
Or flip on autopilot and let sangrep make the routine calls for you, then check its work. You choose the mix, section by section. It is your review either way.
annexes.zip · 12 files
3 calls made by you · every one on the record
boilerplate-terms.pdf
40 pages, low signalscope checked · recorded
3 routine calls made · ready for review
The engine
A question does not fetch the nearest paragraph. It travels the structure to the exact node that answers it, and brings the receipt back.
Not a single vector lookup and a prayer. sangrep walks the document graph, follows references across files, and pulls in exactly what a question needs. The latest reasoning models make that navigation reliable.
The same trick coding agents use on huge repositories. sangrep keeps the whole package in reach and pages in the right sections on demand, so a 5,000-page bundle answers like a short memo.
One skill reads tables, another parses an image, another follows a link. sangrep reaches for the right tool per node instead of forcing everything through one flattener.
Skills
An image is evidence and a link is a lead. Dedicated skills read them and cite them like any clause in the document.
It reads the figure, points to the exact region, and cites the box, so a chart or a signature counts as evidence like anything else.
Open pages it reads itself. Anything behind a login it hands back to you, then picks up where it left off with the extra context.
Under the hood
Reading files is the easy part. This is the machinery that makes the answers safe to use.
01 · intake
nothing gets lost on the way in
02 · identity
citations can outlive re-parses
03 · review
your judgment, on the record
04 · ask
the model can't wander
05 · verify
made-up sources never reach you
You never touch any of this. You drop files, pick a scope, and ask. The pipeline is why the answer comes back with receipts instead of vibes.
Roadmap
Chat came first. The same engine that checks every citation is about to do a lot more.
Like the agent panel in your IDE, but pointed at a document bundle. A summarizer takes the appendix while an extractor works the contract, in parallel, each scoped and logged.
Summarizer · §3 Appendicesdone ✓
Term extractor · 3.2 vendor-agreement.pdfrunning
Figure checker · §2 Financialsqueued
Turn a package into a draft report where every claim carries its citation. Review it, click the receipts, send it on.
Draft report
Vendor risk summary
Termination requires 90 days' notice §4.2 · 3.2 and fees are reviewed each January 3.2.1
Every claim cited
An MCP server that brings the tree, scoped asks, and citation checks to the tools you already use: IDE assistants, chat platforms, internal agents.
The tree becomes a knowledge graph that follows references across contracts, appendices, spreadsheets, and links. Ask once, then see the path it took, source by source.
Save the agent, prompt, or plugin that solved a review once, then run it again on the next package. Start with a team library, then open into a marketplace for workflows teams can trust.
Vendor onboarding review
Shared workspaces for teams: one tree, live cursors, and everyone's calls on the same record. No more findings lost in email threads.
§4.2 Either party may terminate with ninety (90) days' written notice, provided that...
Fees are set out in the pricing schedule and reviewed annually.
An enterprise deployment that lives inside your walls: sangrep runs in your infrastructure, your pipelines feed it, and the models you've already approved do the answering.
Your VPC
Nothing leaves your network
Point sangrep at a whole system of record, not just an upload: SQL databases, data lakes, and browser-native docs like Google Docs that never had a filetype.
Connected sources stay live. sangrep re-reads on change and keeps every version, so you can see exactly what moved between two drafts and when.
vendor-agreement.pdfv3
+2 clauses-1 clausesince v2
FAQ
| Dimension | Chat assistantsChatGPT, Copilot, chat-with-PDF tools | Parsing APIsReducto, Unstructured, LlamaParse | sangrepthe document runtime |
|---|---|---|---|
| Your documents become | One flattened blob of text | Markdown and JSON for your pipeline | A stable, addressable tree |
| Embedded files | Ignored or silently dropped | Extracted; handling is up to you | Inventoried; you decide how each is treated |
| Citations | The model's word for it | Grounding data, if you wire it up | Checked against the tree, rejected if wrong |
| Scope control | The prompt is the scope | Build it yourself | Enforced by the system |
| Audit trail | None | Your job | Append-only, built in |
| Built for | Quick answers | Engineering teams building pipelines | Reviewers who need answers that hold up |
One email when the beta opens. Nothing else.