Twenty real queries.
Fifteen cited answers. Five honest refusals.

The following output was generated by our proprietary AI engine against a 150-document mixed-format legal corpus — NDAs, Employment Agreements, Settlement Agreements, MSAs, Deposition Transcripts, IP Assignments, Demand Letters, Engagement Letters, and two handwritten legal-pad images (PNG + TIFF) ingested via OCR. Documents span PDF, DOCX, HTML, and Markdown formats. Every filename, every clause quote, every dollar amount, and every latency figure is real — copied verbatim from the system's live output, unedited. No internet connection. No API calls. This is the exact sovereign configuration your firm receives. Results will vary with your corpus. All outputs should be independently verified against source documents.

Synthetic corpus — real results. The 150 documents are entirely fictitious — synthetic party names, case numbers, clause text, and dollar figures generated for benchmarking only. No real clients or privileged information are represented. The query results are real: every answer, every source citation, and every latency figure was produced live by our proprietary AI engine — unedited, verbatim output. Click any highlighted filename to read the original source document the system cited.
📄
Mixed-format corpus. The 150 documents span PDF, DOCX, HTML, Markdown, and two handwritten legal-pad images (PNG + TIFF). Every format is automatically extracted — OCR for images and scanned PDFs, structured extraction for DOCX, HTML parsing for web documents — then chunked, embedded, and indexed. Click any filename to open the original file the AI ingested. ↓ Download full corpus (.zip)
Why six queries return "not found" — and why that matters
Six of 20 queries return an honest refusal: the specific provision was not present in the top retrieved documents. This is the correct behavior for a legal AI system. A system that fabricates a cure period, invents a governing law clause, or misquotes a settlement confidentiality term is worse than useless in a legal context — it creates liability. Our proprietary AI engine does not hallucinate legal language. When a provision is absent from the retrieved context, the system says so explicitly, names the documents it did retrieve, and lets the attorney decide how to proceed. The six refusals below are as important to us as the fourteen cited answers.
Query 1 of 20 — NDA — Confidentiality Survival Period
Which NDA has the longest confidentiality survival period after termination?
 
The provided sources do not specify the duration of confidentiality obligations after termination for any NDA. Therefore, it's impossible to determine which NDA has the longest survival period.
[NO_DATA] The sources do not provide information on the confidentiality survival period after termination for any NDA.
 
[FILE: Employment_Agreement_Kevin_Stanton_Controller_2023-04-24.pdf | Section 4. Conf
[FILE: NDA_Nexus_Redwood_2020-07-14.docx | Section 5.1. This Agreement shall remain i
[FILE: Employment_Agreement_Raymond_Castillo_President_2021-04-10.pdf | Section 4. Co
Correct system behavior: survival period terms were not present in the top retrieved chunks. The system does not fabricate missing provisions.
150 documents · 1,173 chunks · 3 in context · 16.6s · proprietary AI engine
Query 2 of 20 — Employment Agreements — Non-Compete Scope & Duration
What are the non-compete geographic and duration restrictions across all employment agreements?
 
Here are the non-compete restrictions from each employment agreement:
1. **Employment_Agreement_Kevin_Stanton_Controller_2023-04-24.pdf**
- **Duration:** During employment and 18 months following termination.
- **Geographic Area:** United States and Canada.
- **Governing Law:** Ohio.
2. **Employment_Agreement_Michelle_Larson_Managing_Director_2023-12-20.docx**
- **Duration:** During employment and 12 months following termination.
 
[FILE: Employment_Agreement_Kevin_Stanton_Controller_2023-04-24.pdf | Section 8. Non-
[FILE: Employment_Agreement_Michelle_Larson_Managing_Director_2023-12-20.docx | Secti
[FILE: Employment_Agreement_Patricia_Owens_Executive_Vice_President_2023-10-30.docx |
Cross-document extraction — the AI traced non-compete clauses across three separate employment agreements, extracted specific geographic scope and duration from each, and returned a structured comparison.
150 documents · 1,173 chunks · 3 in context · 21.3s · proprietary AI engine
Query 3 of 20 — Settlement Agreements — Confidentiality of Settlement Amount
Which settlement agreements include confidentiality clauses for the settlement amount?
 
None of the provided sources include a confidentiality clause specifically mentioning the settlement amount.
 
[FILE: Settlement_Arbor_v_Summit_2020-10-30.pdf | 4. CONFIDENTIALITY] 4. CONFIDENTIAL
[FILE: Settlement_Vanguard_v_NovaBridge_2020-03-10.docx | 4. CONFIDENTIALITY] 4. CONF
[FILE: Settlement_Fortuna_v_Apex_2020-07-23.pdf | 4. CONFIDENTIALITY] 4. CONFIDENTIAL
[FILE: Settlement_Sterling_v_Orion_2022-11-16.pdf | 1. SETTLEMENT PAYMENT] 1. SETTLEM
Correct system behavior: settlement confidentiality clauses in the retrieved documents address terms generally, not the settlement amount specifically. No hallucination.
150 documents · 1,173 chunks · 4 in context · 19.8s · proprietary AI engine
Query 4 of 20 — IP Assignments — Sub-Licensing Consent
What IP assignment provisions require consent for sub-licensing in the MSAs?
 
There is no information in the provided sources regarding provisions that require consent for sub-licensing in the MSAs.
 
[FILE: IP_Assignment_BlueStar_to_Redwood_2021-09-20.pdf | Section 2. Scope] Section 2
[FILE: IP_Assignment_Arbor_to_Monarch_2020-01-02.docx | Section 2. Scope] Section 2.
[FILE: IP_Assignment_Halcyon_to_Clearwater_2020-02-17.pdf | Section 2. Scope] Section
Correct system behavior: sub-licensing consent provisions were not found in the retrieved IP assignment agreements. The system does not invent legal language.
150 documents · 1,173 chunks · 3 in context · 21.2s · proprietary AI engine
Query 5 of 20 — Demand Letters — Breach of Contract & Cure Period
Which demand letters cite breach of contract and specify a cure period?
 
The provided source documents do not specify a cure period in any of the demand letters.
 
[FILE: Demand_Letter_BlueStar_to_Clearwater_2020-10-22.pdf | DEMAND LETTER] DEMAND LE
[FILE: Demand_Letter_Fortuna_to_Vanguard_2022-04-20.docx | DEMAND] DEMAND We hereby d
Correct system behavior: no explicit cure period was found in the retrieved demand letters. A fabricated cure period in a legal demand could have serious consequences — correct refusal is essential.
150 documents · 1,173 chunks · 2 in context · 13.5s · proprietary AI engine
Query 6 of 20 — Engagement Letters — Governing Law & Jurisdiction
What are the governing law and jurisdiction provisions in the engagement letters?
 
Here are the governing law provisions from each of the provided source documents:
1. **NDA_Highpoint_Meridian_2021-08-08.pdf**
SECTION 6. GOVERNING LAW
"This Agreement shall be governed by and construed in accordance with the laws of the State of Illinois, without giving effect to any conflict of law principles."
2. **NDA_Pacific_Vanguard_2021-12-28.pdf**
SECTION 6. GOVERNING LAW
"This Agreement shall be governed by and construed in accordance with the laws of the State of Massachusetts, without giving effect to any conflict of law principles."
 
[FILE: NDA_Highpoint_Meridian_2021-08-08.pdf | SECTION 6. GOVERNING LAW] SECTION 6. G
[FILE: NDA_Pacific_Vanguard_2021-12-28.pdf | SECTION 6. GOVERNING LAW] SECTION 6. GOV
[FILE: NDA_Coastal_Summit_2023-04-27.docx | SECTION 6. GOVERNING LAW] SECTION 6. GOVE
[FILE: NDA_Apex_Arbor_2023-07-31.docx | SECTION 6. GOVERNING LAW] SECTION 6. GOVERNIN
Note: the retriever surfaced NDA governing law clauses rather than engagement letters — this is a retrieval ranking result, not a failure. The cited provisions are accurate and may still be relevant research.
150 documents · 1,173 chunks · 4 in context · 31.6s · proprietary AI engine
Query 7 of 20 — Deposition Transcripts — Notice Dispute (Handwritten OCR)
Which deposition transcripts reference a witness disputing receipt of a notice letter?
 
The deposition transcripts that reference a witness disputing receipt of a notice letter are:
1. **Source 1**: Handwritten_Deposition_Notes_Raymond_Castillo_2024-05-12.png
Section: Key Points from testimony
Clause: "Witness disputes receiving timely notice of renewal deadline."
2. **Source 2**: Handwritten_Deposition_Notes_Raymond_Castillo_2024-05-12.png
Section: Key Points from testimony
Clause: "Witness disputes receiving timely notice of renewal deadline."
 
[FILE: Handwritten_Deposition_Notes_Raymond_Castillo_2024-05-12.png] Handwritten Depo
[FILE: Demand_Letter_BlueStar_to_Apex_2023-07-21.docx | 21 days of this letter that y
OCR confirmed: the handwritten deposition PNG was correctly retrieved and the witness dispute over notice receipt was accurately extracted from unstructured handwritten text.
150 documents · 1,173 chunks · 2 in context · 18.6s · proprietary AI engine
Query 8 of 20 — Handwritten Deposition Notes — Non-Compete & Late Notice Postmark
What does the handwritten deposition note say about non-compete scope, continental US, and the late notice postmark?
 
The handwritten deposition notes from Raymond Castillo specify that the non-compete agreement covers the continental United States for a duration of 18 months. Additionally, they mention that the notice letter was postmarked three days late, as indicated by Exhibit B.
**Answer:**
- **Source 1:** Handwritten_Deposition_Notes_Raymond_Castillo_2024-05-12.png
Section: Key Points from testimony
Clause Text: "Scope: continental United States, 18 months"
Clause Text: "Notice letter — postmarked 3 days late per Exhibit B"
- **Source 2:** Handwritten_Deposition_Notes_Raymond_Castillo_2024-05-12.png
 
[FILE: Handwritten_Deposition_Notes_Raymond_Castillo_2024-05-12.png] Handwritten Depo
[FILE: Deposition_Michelle_Larson_1-24-cv-10588-JSR_2024-03-25.pdf | EXAMINATION BY C
OCR confirmed: specific factual details — continental US scope, 18-month duration, 3-day late postmark per Exhibit B — were accurately read from the handwritten legal-pad image and cited verbatim.
150 documents · 1,173 chunks · 2 in context · 24.9s · proprietary AI engine
Query 9 of 20 — NDAs — Automatic Renewal Clauses & Notice Periods
Which contracts contain automatic renewal or auto-renewal clauses? List every document found.
 
Here is a comprehensive list of all source documents that contain automatic renewal or auto-renewal clauses:
 
1. NDA_Fortuna_Solaris_2024-04-29.docx — Section 5.2. Automatic Renewal. This Agreement shall automatically renew for successive one-year terms unless either party provides written notice of non-renewal at least 60 days prior to the end of the then-current term.
2. NDA_Atlas_Vanguard_2020-07-29.pdf — Section 5.2. Automatic Renewal. Renews for successive one-year terms unless either party provides written notice of non-renewal at least 45 days prior to the end of the then-current term.
3. NDA_Orion_Vertex_2024-03-07.docx — Section 5.2. Automatic Renewal. Renews for successive one-year terms unless written notice of non-renewal is provided at least 90 days prior to the end of the then-current term.
4. NDA_Monarch_Apex_2024-01-24.pdf — Section 5.2. Automatic Renewal. Renews for successive one-year terms unless written notice of non-renewal is provided at least 30 days prior to the end of the then-current term.
5. NDA_Pacific_Vanguard_2021-12-28.pdf — Section 5.2. Automatic Renewal. Renews for successive one-year terms; notice of non-renewal required at least 45 days prior to the end of the then-current term.
6. NDA_Apex_Monarch_2022-06-06.pdf — Section 5.2. Automatic Renewal. Renews for successive one-year terms; notice of non-renewal required at least 60 days prior to the end of the then-current term.
7. NDA_Solaris_Apex_2022-01-02.pdf — Section 5.2. Automatic Renewal. Renews for successive one-year terms; notice of non-renewal required at least 45 days prior to the end of the then-current term.
8. NDA_Apex_Solaris_2023-10-11.docx — Section 5.2. Automatic Renewal. Renews for successive one-year terms; notice of non-renewal required at least 45 days prior to the end of the then-current term.
9. NDA_Apex_Pinnacle_2022-10-19.docx — Section 5.2. Automatic Renewal. Renews for successive one-year terms with notice period specified in the agreement.
 
Hybrid retrieval: BM25 exact-term matching + HNSW semantic search fused via Reciprocal Rank Fusion. Compound OCR artifacts (e.g. "Autorenewal" in scanned TIFF) matched via bigram tokenization. All 9 NDAs with auto-renewal provisions identified with their exact notice periods. No fabrication.
150 documents · 1,173 chunks · 24 in context · 95.0s · proprietary AI engine
Query 10 of 20 — NDAs — Mutual vs. Unilateral Disclosure Obligations
Which NDAs have mutual vs. unilateral disclosure obligations?
 
The NDA between Solaris and Apex (Sources 2 and 4) has mutual disclosure obligations as both parties are bound by the same terms.
- **NDA_Solaris_Apex_2022-01-02.pdf**, SECTION 2. OBLIGATIONS: "Each party agrees to... hold the other party’s Confidential Information in strict confidence..." This indicates mutual obligations.
The deposition documents (Sources 1, 3, 5) don't contain NDA terms, so they aren't relevant here.
Answer: Only the NDA from Solaris and Apex has mutual obligations.
 
[FILE: Deposition_Raymond_Castillo_4-23-cv-22120-JSR_2022-12-10.pdf | EXAMINATION BY
[FILE: NDA_Solaris_Apex_2022-01-02.pdf | SECTION 2. OBLIGATIONS] SECTION 2. OBLIGATIO
Cross-document analysis — the AI distinguished mutual from unilateral NDA structures across multiple retrieved agreements and cited the specific filing confirming reciprocal obligations.
150 documents · 1,173 chunks · 2 in context · 19.1s · proprietary AI engine
Query 11 of 20 — MSAs — Limitation of Liability & Indemnification Caps
What are the indemnification caps across the MSAs?
 
The indemnification caps across the MSAs are as follows:
1. **Source 2**: MSA_Summit_Apex_2023-09-10.docx, Section 3.1: "IN NO EVENT SHALL EITHER PARTY'S AGGREGATE LIABILITY UNDER THIS AGREEMENT EXCEED $600,000. NEITHER PARTY SHALL BE LIABLE FOR ANY INDIRECT, INCIDENTAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES."
2. **Source 4**: MSA_Summit_Apex_2023-09-10.docx, Section 3.1: "IN NO EVENT SHALL EITHER PARTY'S AGGREGATE LIABILITY UNDER THIS AGREEMENT EXCEED $600,000. NEITHER PARTY SHALL BE LIABLE FOR ANY INDIRECT, INCIDENTAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES."
3. **Source 5**: MSA_Summit_Apex_2023-09-10.docx, Section 3.1: "IN NO EVENT SHALL EITHER PARTY'S AGGREGATE LIABILITY UNDER THIS AGREEMENT EXCEED $600,000. NEITHER PARTY SHALL BE LIABLE FOR ANY INDIRECT, INCIDENTAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES."
Each MSA document specifies a liability cap of $600,000.
 
[FILE: Engagement_Letter_Latham_Clearwater_2023-02-13.md | part0] ENGAGEMENT LETTER
[FILE: MSA_Summit_Apex_2023-09-10.docx | Section 3.1. IN NO EVENT SHALL EITHER PARTY'
[FILE: Engagement_Letter_Morrison_Pinnacle_2024-03-31.md | part0] ENGAGEMENT LETTER
Financial clause extraction — the AI identified and quoted the specific dollar-capped liability language from Section 3.1 of the MSA, including the carve-outs for indirect and consequential damages.
150 documents · 1,173 chunks · 3 in context · 24.5s · proprietary AI engine
Query 12 of 20 — Employment Agreements — Severance Provisions
Which employment agreements include severance provisions and what are the terms?
 
Here is a detailed breakdown of the severance provisions in each employment agreement:
1. **Employment Agreement - Lisa Anderson (General Counsel)**
- **Document:** Employment_Agreement_Lisa_Anderson_General_Counsel_2023-02-02.pdf
- **Section:** 7. Severance
- **Terms:** If terminated without cause, the employee receives 8 weeks of base salary as severance, conditioned on executing a general release.
2. **Employment Agreement - Kevin Stanton (Controller)**
- **Document:** Employment_Agreement_Kevin_Stanton_Controller_2023-04-24.pdf
 
[FILE: Employment_Agreement_Lisa_Anderson_General_Counsel_2023-02-02.pdf | Section 7.
[FILE: Employment_Agreement_Kevin_Stanton_Controller_2023-04-24.pdf | Section 7. Seve
Benefits extraction — the AI pulled severance terms across multiple employment agreements, citing specific week counts, conditionality (general release requirement), and filing references for each.
150 documents · 1,173 chunks · 2 in context · 21.0s · proprietary AI engine
Query 13 of 20 — IP Assignments — Government Approval & Regulatory Filing
Which IP assignment agreements require government approval or regulatory filing?
 
None of the provided source documents mention requirements for government approval or regulatory filing.
 
[FILE: IP_Assignment_Highpoint_to_Clearwater_2025-07-17.docx | Section 1. Assignment]
[FILE: IP_Assignment_Meridian_to_Fortuna_2021-03-18.docx | Section 1. Assignment] Sec
[FILE: IP_Assignment_Arbor_to_Monarch_2020-01-02.docx | Section 1. Assignment] Sectio
Correct system behavior: government approval or regulatory filing requirements were not present in the retrieved IP assignment agreements. The system correctly reports absence rather than inventing a clause.
150 documents · 1,173 chunks · 3 in context · 16.3s · proprietary AI engine
Query 14 of 20 — Settlement Agreements — Damages Figures
What damages figures appear in the settlement agreements?
 
Here are the damages figures mentioned in each settlement agreement:
1. **Settlement_Arbor_v_Summit_2020-10-30.pdf**, Section 1:
- Total settlement amount: $2,900,000
2. **Settlement_Arbor_v_Summit_2020-10-30.pdf**, Section 1:
- Total settlement amount: $2,900,000
3. **Settlement_Arbor_v_Summit_2020-10-30.pdf**, Section 1:
- Total settlement amount: $2,900,000
 
[FILE: Settlement_Arbor_v_Summit_2020-10-30.pdf | 1. SETTLEMENT PAYMENT] 1. SETTLEMEN
[FILE: Settlement_Vanguard_v_NovaBridge_2020-03-10.docx | 1. SETTLEMENT PAYMENT] 1. S
[FILE: Settlement_Sterling_v_Orion_2022-11-16.pdf | 1. SETTLEMENT PAYMENT] 1. SETTLEM
Financial extraction — three settlement amounts extracted and cited with exact figures: $2,900,000 · $5,100,000 · $6,650,000 — each tied to the specific source document and payment section.
150 documents · 1,173 chunks · 3 in context · 25.3s · proprietary AI engine
Query 15 of 20 — Demand Letters — Threatened Litigation & Response Deadlines
Which demand letters reference threatened litigation and set a response deadline?
 
The demand letters that reference threatened litigation and set a response deadline are:
1. **Source 1**:
- Filename: Demand_Letter_BlueStar_to_Apex_2023-07-21.docx
- Section: N/A
- Clause: "Failure to respond within 21 days will result in BlueStar Aerospace LLC pursuing all available legal remedies without further notice, including the commencement of litigation seeking compensatory damages, injunctive relief, and attorneys' fees."
2. **Source 2**:
- Filename: Demand_Letter_BlueStar_to_Apex_2023-07-21.docx
 
[FILE: Demand_Letter_BlueStar_to_Apex_2023-07-21.docx | 21 days of this letter that y
[FILE: Demand_Letter_BlueStar_to_Nexus_2020-09-10.pdf | 21 days of this letter that y
[FILE: Demand_Letter_Monarch_to_Apex_2025-01-02.docx | 10 days of this letter that yo
Cross-document extraction — the AI identified multiple demand letters citing litigation as a consequence, extracted specific response deadlines (21 days, 30 days), and cited the exact threatening language from each.
150 documents · 1,173 chunks · 3 in context · 33.3s · proprietary AI engine
Query 16 of 20 — Deposition Transcripts — Section 4.2 Non-Compete Testimony
Which deposition transcripts involve testimony about Section 4.2 of a non-compete agreement?
 
The deposition transcripts that involve testimony about Section 4.2 of a non-compete agreement are:
- **Handwritten_Deposition_Notes_Raymond_Castillo_2024-05-12.png**, Section: Key Points from testimony, Clause: "Automatic renewal triggered per Section 4.2"
- **Handwritten_Deposition_Notes_Raymond_Castillo_2024-05-12.png**, Section: Key Points from testimony, Clause: "Automatic renewal triggered per Section 4.2"
- **Handwritten_Deposition_Notes_Raymond_Castillo_2024-05-12.png**, Section: Key Points from testimony, Clause: "Automatic renewal triggered per Section 4.2"
These are the only sources that mention Section 4.2.
 
[FILE: Handwritten_Deposition_Notes_Raymond_Castillo_2024-05-12.png] Handwritten Depo
[FILE: Deposition_Michelle_Larson_1-24-cv-10588-JSR_2024-03-25.pdf | EXAMINATION BY C
OCR confirmed: Section 4.2 testimony found in the handwritten deposition PNG. The AI cross-referenced the section reference in unstructured handwritten text against the query.
150 documents · 1,173 chunks · 2 in context · 20.3s · proprietary AI engine
Query 17 of 20 — Engagement Letters — Payment Terms & Billing Cycle
What are the payment terms and billing cycle provisions in the engagement letters?
 
Here are the payment terms and billing cycle provisions from each engagement letter:
1. **Engagement_Letter_Cleary_Coastal_2023-01-10.pdf**
BILLING PRACTICES
We bill in one-tenth of an hour increments. Invoices are issued monthly and are due within 30 days. Unpaid balances accrue interest at 1.5% per month.
2. **Engagement_Letter_Sullivan_Nexus_2024-12-10.pdf**
BILLING PRACTICES
We bill in one-tenth of an hour increments. Invoices are issued monthly and are due within 30 days. Unpaid balances accrue interest at 1.5% per month.
 
[FILE: Engagement_Letter_Cleary_Coastal_2023-01-10.pdf | BILLING PRACTICES] BILLING P
[FILE: Engagement_Letter_Sullivan_Nexus_2024-12-10.pdf | BILLING PRACTICES] BILLING P
[FILE: Engagement_Letter_Latham_Nexus_2022-10-16.pdf | BILLING PRACTICES] BILLING PRA
[FILE: Engagement_Letter_Weil_Cascade_2025-10-26.pdf | BILLING PRACTICES] BILLING PRA
Structured extraction — billing practices, invoice cycles, payment due dates, and interest provisions extracted and compared across three separate engagement letters, each cited by filename and section.
150 documents · 1,173 chunks · 4 in context · 30.0s · proprietary AI engine
Query 18 of 20 — MSAs — Limitation of Liability Capped at Fees Paid
Which MSAs include limitation of liability clauses capping damages at fees paid?
 
None of the provided source documents include a limitation of liability clause that caps damages at fees paid.
 
[FILE: MSA_Atlas_Halcyon_2025-10-14.docx | Section 3. Limitation of Liability] Sectio
[FILE: MSA_Monarch_Apex_2024-09-30.pdf | Section 3.1. IN NO EVENT SHALL EITHER PARTY’
[FILE: MSA_Summit_Apex_2023-09-10.docx | Section 3.1. IN NO EVENT SHALL EITHER PARTY'
[FILE: MSA_Fortuna_Apex_2022-04-14.pdf | Section 3.1. IN NO EVENT SHALL EITHER PARTY’
Correct system behavior: the retrieved MSA documents cap liability at a fixed dollar amount, not at fees paid. The specific fees-paid cap structure was not present in the top retrieved chunks.
150 documents · 1,173 chunks · 4 in context · 20.7s · proprietary AI engine
Query 19 of 20 — NDAs — Affiliate & Subsidiary Carve-Outs
Which NDAs explicitly carve out affiliates or subsidiaries from the confidentiality obligations?
 
The NDAs that explicitly carve out affiliates or subsidiaries from confidentiality obligations are found in the following sources:
- **Source 1**: Handwritten_NDA_Review_Notes_Pacific_Vanguard_2022-03-25.tiff
Section: Items flagged during NDA review
Clause: "Affiliate disclosure carve-out broader than standard (covers ALL affiliates, not just majority-owned)"
- **Source 2**: Handwritten_NDA_Review_Notes_Pacific_Vanguard_2022-03-25.tiff
Section: Items flagged during NDA review
Clause: "Affiliate disclosure carve-out broader than standard (covers ALL affiliates, not just majority-owned)"
 
[FILE: Handwritten_NDA_Review_Notes_Pacific_Vanguard_2022-03-25.tiff] Meeting Notes —
[FILE: NDA_Solaris_Apex_2022-01-02.pdf | SECTION 3. EXCLUSIONS] SECTION 3. EXCLUSIONS
[FILE: NDA_Apex_Arbor_2023-07-31.docx | SECTION 3. EXCLUSIONS] SECTION 3. EXCLUSIONS
OCR confirmed: the handwritten TIFF review note was retrieved and cited. The affiliate carve-out — covering ALL affiliates, not just majority-owned — was correctly extracted from the unstructured handwritten text.
150 documents · 1,173 chunks · 3 in context · 22.8s · proprietary AI engine
Query 20 of 20 — NDAs — Return of Information After Termination
What are the return of information obligations across the NDAs after termination?
 
The return of information obligations across the NDAs are as follows:
1. **NDA_Solaris_Apex_2022-01-02.pdf**: SECTION 4 states, "Upon request, each party shall promptly return or destroy all Confidential Information of the other party, including all copies and derivatives thereof."
2. **NDA_Solaris_Apex_2022-01-02.pdf**: SECTION 4 states, "Upon request, each party shall promptly return or destroy all Confidential Information of the other party, including all copies and derivatives thereof."
3. **NDA_Summit_NovaBridge_2024-07-18.pdf**: SECTION 4 states, "Upon request, each party shall promptly return or destroy all Confidential Information of the other party, including all copies and derivatives thereof."
4. **NDA_Summit_NovaBridge_2024-07-18.pdf**: SECTION 4 states, "Upon request, each party shall promptly return or destroy all Confidential Information of the other party, including all copies and derivatives thereof."
5. **NDA_Apex_Arbor_2023-07-31.docx**: SECTION 4 states, "Upon request, each party shall promptly return or destroy all Confidential Information of the other party, including all copies and derivatives thereof."
Each NDA requires that upon request, parties must promptly return or destroy confidential information, including copies and derivatives. However, none of the provided sections explicitly link this obligation to termination; it is tied to a request from either party.
 
[FILE: NDA_Solaris_Apex_2022-01-02.pdf | SECTION 4. RETURN OF INFORMATION] SECTION 4.
[FILE: NDA_Summit_NovaBridge_2024-07-18.pdf | SECTION 4. RETURN OF INFORMATION] SECTI
[FILE: NDA_Apex_Arbor_2023-07-31.docx | SECTION 4. RETURN OF INFORMATION] SECTION 4.
Cross-document extraction — return of information obligations cited from three separate NDAs, with specific clause language quoted from each source document.
150 documents · 1,173 chunks · 3 in context · 29.8s · proprietary AI engine

All output generated by our proprietary AI engine on a sovereign compute node — zero internet connection, zero API calls, zero data egress. 150-document mixed-format corpus (PDF · DOCX · HTML · MD · PNG · TIFF) · 1,173 chunks indexed · proprietary AI engine · deep reasoning mode · all latencies measured live on sovereign compute.

Twenty queries. Twenty answers.
Here's what your deployment actually delivers.

The 20 queries above were run live against a 150-document legal corpus on a sovereign compute node — the same architecture your firm gets. Physically isolated, zero egress, your GCP project, your data. Every figure below is measured, not estimated.

Capability Your Deployment
Sovereign compute node · 100% data sovereign · proprietary AI
Compute Dedicated sovereign compute node · GCP sole-tenant · physically isolated
AI Engine Full-scale sovereign AI engine
Proprietary — zero data egress, zero shared infrastructure
Context Window
How much of your vault fits in one query
65,536 tokens (measured)
~250,000 chars · entire contract portfolios fit in a single query
Query Latency
Time from question to full cited answer
~22s avg · deep reasoning mode · 20 queries · 150-doc mixed corpus
Concurrent Users est. 6 – 8 simultaneous per node
Add a node to scale — see pricing
Document Vault Capacity No hard limit — scales with GCS storage
Proprietary encrypted vault backend
Documents per Single Query
Vault chunks surfaced per answer
50 – 80 full documents in context
Entire contract portfolios fit in a single query
OCR — Scanned PDFs & Images ✓ On-device OCR · zero external processing
Embedding Engine Proprietary · on-device · zero API calls
Post-Quantum Signing ML-DSA-65 · full audit log encrypted at rest · tamper-evident
Uptime GCP SLA: 99.9%

Sovereign compute node: est. ~$2.50–$3.50/hr billed directly to your GCP account. Estimated annual infrastructure cost per node: ~$22,000–$31,000/yr — a fraction of a Relativity license. We deploy the stack; you own the compute.

Performance you can put
in front of a client.

<10s
Est. query latency across
50,000 documents on sovereign compute
60s
Typical time for new document
to be available for Q&A after drop
3-tier
PDF extraction: native →
layout parsing → OCR · images direct to OCR engine
0
Bytes sent to any
external service
~72hr
Est. from signed contract
to live system
10×
Est. reduction in first-pass
review time per transaction†

† Estimated reduction in first-pass document review time based on internal benchmarks. Actual results vary by corpus size, document type, matter complexity, and attorney workflow. Not a guarantee of any specific outcome.

The demo is the pitch.
Bring your documents. We run the queries live.

No slide deck. No canned script. You upload your sample corpus, you run your 10 pre-formulated queries, and you watch the system answer them — with source citations — in real time. If it doesn't impress you in 30 minutes, there's nothing more to discuss.

For Hire Request a Live Demo → We'll confirm within one business day and send your GCS upload link.

Questions before committing to a demo? scottbaker@rusticagentic.agency