SolaVeritas.ai mark

Engineering deep dive

System & moat.

How the system works. Why it gets harder to copy over time.

Scope

Scope.

  • Domain: multi-document due diligence
  • Input: heterogeneous document sets
  • Output: structured, traceable findings
  • Goal: reproducible evaluation across datasets

The goal is not summarization — but consistent, reproducible evaluation.

Problem surface

Same fact — told three different ways.

📄 Articles · 2024 · p.4
Authorized capital:
$2,400,000
Issued shares: 1,000,000
📄 Audited financials · p.12
Net revenue:
$2,237,800
Issued shares: 1,250,000
📄 Investor deck · slide 6
FY2023 revenue:
~$2.4M
Issued shares: not stated

No shared schema. No canonical source. Consistency must be inferred — not assumed.

Input constraints

Input constraints.

  • OCR noise (scans, handwritten documents)
  • Fuzzy entity names
  • Layout-dependent meaning
  • Style variability

Inputs are noisy and inconsistent. Extraction is probabilistic — and must be validated.

System objective

Convert unstructured documents into structured findings.

01 · Extract
Entities & facts
LLM-assisted, source-bound
02 · Normalize
Shared form
canonical representation
03 · Reconcile
Cross-document
conflicts surfaced
04 · Validate
Rule-bound output
verifiable findings

Model produces text. System produces structure.

System model

System model.

Multi-stage pipeline. Each stage produces a structured intermediate state — the input to the next stage.

EXTRACTLLM-assisted
NORMALIZEcanonical form
RECONCILEcross-document
VALIDATErule-bound
Intermediate stateTyped entity list
Intermediate stateNormalized graph
Intermediate stateReconciled claims
OutputVerified findings

Every intermediate state is inspectable, testable, replayable.

Execution model

Execution model.

  • Stage dependencies
  • Schema-bound outputs
  • Validation gates
  • Retry / fallback paths

Each stage depends on validated outputs from previous stages. Execution is controlled — non-linear when needed.

Control layer

Control layer.

  • Deterministic rules (if / then)
  • Schema constraints
  • Pass / fail logic
  • Validation before progression

Rules define what must be true. Models assist — they do not decide correctness.

Replicable components

Replicable components.

  • UI / document viewer
  • LLM-based extraction
  • Basic pipelines
  • Simple rule checks

Straightforward to implement. They do not provide defensibility on their own.

Complexity drivers

Complexity drivers.

  • Entity normalization across documents
  • Cross-document reconciliation
  • Second-order validation
  • Missing-data inference
  • Consistency across datasets

Complexity arises from interactions across documents — and the need for consistent behavior.

Core capabilities

Core system capabilities.

01 · Citation lineage
Bind every claim to its source.
claim → source → region → evidence
02 · Contradiction detection
Trace inconsistency chains.
mismatch and inconsistency chains across documents
Validation core
Verification, not analysis.
deterministic rules · cross-document checks · pass / fail
03 · Negative assurance
Detect what's missing.
expected ≠ present — harder than detecting what is present
04 · Section rules
Binary outputs, not probabilities.
deterministic pass / fail logic per section

Four primitives. Each feeds the validation core.

Language & jurisdiction

A separate axis — wrapping the pipeline.

Language & jurisdiction layer
EXTRACT
NORMALIZE
RECONCILE
Multi-language entities
"ABC Corp" / "ABC AŞ" / "ABC GmbH" — same entity
Structural divergence
Turkish "Esas Sözleşme" ≠ Delaware Articles of Incorporation — similar function, different structure
Rule variation
Same risk surface, different jurisdiction-specific rules

Affects meaning — not just data. Where local complexity lives.

Feedback & learning

Feedback & learning structure.

Each transaction extends the explicit knowledge base around the model.

Real deal
Transaction
System runs
Findings produced
Expert review
Law firm / VC feedback
Captured edge case
Transaction memory
Update
Rule + schema
Improved
System hardened

Compounding loop. Not training on data — extending structure around it.

Failure modes

Failure modes.

  • Extraction errors
  • Entity mismatch
  • False conflicts
  • Missed inconsistencies
  • Missing-data errors

Errors propagate across stages. They must be monitored — and reduced over time.

What becomes hard

What becomes hard.

  • Stability across datasets
  • Reducing false positives / negatives
  • Handling edge cases
  • Maintaining behavior under change

The challenge is maintaining consistency — under real-world variability.

Learning mechanism

Learning mechanism.

  • Iteration from real cases
  • Rule refinement
  • Schema updates
  • Error correction loops

Learning occurs at the system level — not model training.

Distribution + learning

Distribution + learning.

  • Design partners (law firms)
  • VC case execution
  • Real dataset exposure
  • Feedback-driven iteration

Distribution drives system improvement. Each use case contributes to refinement.

Resulting advantage

Resulting advantage.

  • Increased reliability
  • Accumulated edge cases
  • Improved consistency

Advantage builds gradually — through iteration.

Boundary conditions

Boundary conditions.

  • Replicable at early stages
  • No static moat
  • Not protected by model access

The system is not inherently uncopyable. Defensibility develops over time.

System overview

AI reasons. System verifies. Expertise compounds.

Language & jurisdiction layer · spans the entire pipeline Multi-language entities · legal terminology variation · structural differences · semantic mapping · rule variation by jurisdiction

Input

Document set · PDF / DOCX / scans
  • OCR noise / handwritten
  • Fuzzy names
  • Different styles
  • Missing / inconsistent data
Unstructured · unreliable

System pipeline

INGESTION
EXTRACTION (LLM-assisted)
NORMALIZATION
RECONCILIATION
VALIDATION (CORE) verifies before output
deterministic rules · cross-document checks · comparison of comparisons · missing detection
OUTPUT ASSEMBLY

Moat primitives → into validation

  1. Citation lineage (claim → source → region)
  2. Contradiction detection (mismatch chains)
  3. Negative assurance (expected ≠ present)
  4. Section rules (pass / fail)

Output

Structured findings
  • Confirmed
  • Conflicts
  • Missing
  • + traceable references
Not answers — verifiable outputs
Outer loop · learning & feedback Real deals → system execution → law firm / VC feedback → rule + schema update → edge case library (transaction memory) → improved system → more deals

AI reasons. System verifies. Expertise compounds.

Rotate your phone

This deck is designed for landscape view. Turn your device sideways for the best experience.

TR EN · 1 / 20