ServicesExpertiseCase StudiesKnowledgeAbout
┌─────────────────────────────────────────┐ │ EVIDENCE PROCESSING PIPELINE v2.1 │ │ STATUS: ACTIVE │ QUEUE: 12 items │ └─────────────────────────────────────────┘
╔═══════════════════════════╗ ║ STAGE 1: INTAKE ║ ╚═══════════════════════════╝
┌──────────────────────┐ │ ▓ Patent Document │ │ US 10,123,456 B2 │ │ Status: Received │ │ Pages: 47 │ └──────────────────────┘
┌──────────────────────┐ │ ▓ Source Code │ │ repo: accused-sys │ │ Commits: 2,341 │ │ Files: 892 │ └──────────────────────┘
┌──────────────────────┐ │ ▓ Tech Docs │ │ API Specification │ │ Version: 3.2.1 │ │ Format: OpenAPI │ └──────────────────────┘
╔═══════════════════════════╗ ║ STAGE 2: ANALYSIS ║ ╚═══════════════════════════╝
├── Claim Parsing │ ├── Independent: 3 │ ├── Dependent: 12 │ └── Elements: 47
├── Code Analysis │ ├── Functions: 234 │ ├── Classes: 89 │ └── Matches: 12
├── Evidence Linking │ ├── Direct: 8 │ ├── Indirect: 14 │ └── Pending: 3
╔═══════════════════════════╗ ║ STAGE 3: MAPPING ║ ╚═══════════════════════════╝
┌─────────────┬───────────────────┬──────────┐ │ Claim │ Evidence │ Match │ ├─────────────┼───────────────────┼──────────┤ │ 1.preamble │ main.java:142 │ ████████░│ │ 1.1 │ handler.py:23 │ █████████│ │ 1.2 │ classifier.py:89 │ ██████████│ │ 1.3 │ threshold.yaml │ ███████░░│ │ 2 │ conv_layer.py:12 │ █████████│ │ 3 │ embedding.java:45 │ ████████░│ │ 4 │ queue_db.sql:8 │ ██████████│ └─────────────┴───────────────────┴──────────┘
╔═══════════════════════════╗ ║ STAGE 4: OUTPUT ║ ╚═══════════════════════════╝
┌────────────────────────────────┐ │ ✓ CLAIM CHART │ │ Format: PDF + Interactive │ │ Claims mapped: 15/15 │ │ Evidence items: 47 │ │ Status: COMPLETE │ └────────────────────────────────┘
┌────────────────────────────────┐ │ ✓ EXPERT REPORT │ │ Sections: 8 │ │ Pages: 124 │ │ Exhibits: 23 │ │ Status: DRAFT │ └────────────────────────────────┘
┌────────────────────────────────┐ │ ○ INVALIDITY ANALYSIS │ │ Prior Art Found: 12 │ │ Strong Refs: 4 │ │ Status: IN PROGRESS │ └────────────────────────────────┘
════════════════════════════════════════════ Processing: claim-chart-001 Started: 2024-03-15T09:00:00Z ETA: 4h 23m remaining ════════════════════════════════════════════
┌─────────────────────────────────────────┐ │ EVIDENCE PROCESSING PIPELINE v2.1 │ │ STATUS: ACTIVE │ QUEUE: 12 items │ └─────────────────────────────────────────┘
╔═══════════════════════════╗ ║ STAGE 1: INTAKE ║ ╚═══════════════════════════╝
┌──────────────────────┐ │ ▓ Patent Document │ │ US 10,123,456 B2 │ │ Status: Received │ │ Pages: 47 │ └──────────────────────┘
┌──────────────────────┐ │ ▓ Source Code │ │ repo: accused-sys │ │ Commits: 2,341 │ │ Files: 892 │ └──────────────────────┘
┌──────────────────────┐ │ ▓ Tech Docs │ │ API Specification │ │ Version: 3.2.1 │ │ Format: OpenAPI │ └──────────────────────┘
╔═══════════════════════════╗ ║ STAGE 2: ANALYSIS ║ ╚═══════════════════════════╝
├── Claim Parsing │ ├── Independent: 3 │ ├── Dependent: 12 │ └── Elements: 47
├── Code Analysis │ ├── Functions: 234 │ ├── Classes: 89 │ └── Matches: 12
├── Evidence Linking │ ├── Direct: 8 │ ├── Indirect: 14 │ └── Pending: 3
╔═══════════════════════════╗ ║ STAGE 3: MAPPING ║ ╚═══════════════════════════╝
┌─────────────┬───────────────────┬──────────┐ │ Claim │ Evidence │ Match │ ├─────────────┼───────────────────┼──────────┤ │ 1.preamble │ main.java:142 │ ████████░│ │ 1.1 │ handler.py:23 │ █████████│ │ 1.2 │ classifier.py:89 │ ██████████│ │ 1.3 │ threshold.yaml │ ███████░░│ │ 2 │ conv_layer.py:12 │ █████████│ │ 3 │ embedding.java:45 │ ████████░│ │ 4 │ queue_db.sql:8 │ ██████████│ └─────────────┴───────────────────┴──────────┘
╔═══════════════════════════╗ ║ STAGE 4: OUTPUT ║ ╚═══════════════════════════╝
┌────────────────────────────────┐ │ ✓ CLAIM CHART │ │ Format: PDF + Interactive │ │ Claims mapped: 15/15 │ │ Evidence items: 47 │ │ Status: COMPLETE │ └────────────────────────────────┘
┌────────────────────────────────┐ │ ✓ EXPERT REPORT │ │ Sections: 8 │ │ Pages: 124 │ │ Exhibits: 23 │ │ Status: DRAFT │ └────────────────────────────────┘
┌────────────────────────────────┐ │ ○ INVALIDITY ANALYSIS │ │ Prior Art Found: 12 │ │ Strong Refs: 4 │ │ Status: IN PROGRESS │ └────────────────────────────────┘
════════════════════════════════════════════ Processing: claim-chart-001 Started: 2024-03-15T09:00:00Z ETA: 4h 23m remaining ════════════════════════════════════════════
Services

Technical work product for patent disputes

A patent is construed once, properly. Everything after that is repeatable: screening targets, mapping integers, and rendering the analysis for whichever forum it has to stand up in.

Every engagement is backed by the platform. 195M patent records, 926K cases, 5.76B relationships, connected. Priced as a fixed construction fee, then by the target.

What we build

Construction pack

Per patent, built once

The foundation for everything downstream. Claim integers broken out verbatim, constructions anchored to the granted specification page by page and line by line, claim differentiation analysis, and the skilled-person definition. Versioned and hashed, so every later document provably shares one construction.

Deliverables
Claim integer breakdownSpecification cross-referenceClaim differentiationWeak-integer register

Target screen

Triage before you spend chart money

The construction run against a candidate product. Integer-level pass, fail, or uncertain, the public evidence available, the jurisdictional hooks, and the pleading route that follows. The output tells you which targets are worth a full mapping and which are not.

Deliverables
Integer-level scoringEvidence sufficiencyJurisdictional hooksPleading route

Evidence of use and charts

Per target, element by element

Integer-by-integer mapping of the target product against every claim element, with a verbatim quotation from the target’s own published material behind each one, archived and timestamped at capture. Licensing grade for negotiation, filing grade for the tribunal.

Deliverables
Infringement chartsInvalidity chartsSource code reviewEvidence provenance

Filing and report support

Across the jurisdictions the family covers

One construction, rendered for each forum. Opinion requests, letters before action, and the technical annexes behind them. Expert report support under the applicable rules, working to counsel and their designated testifying expert.

Deliverables
Opinion requestsLBA technical annexesDeclaration supportExpert report support

Campaign infrastructure

Fifty targets, one position

The register that keeps a multi-target campaign coherent: target status, deadlines, downstream infringers, and product change monitoring. Amend the construction once and every document in the campaign regenerates to match.

Deliverables
Target registerDeadline trackingChange monitoringDocument regeneration

Defensive analysis

The same machinery, pointed the other way

For the party on the receiving end. Construction of the asserted patent, prior art and invalidity, non-infringement mapping, and freedom to operate against a product roadmap.

Deliverables
Prior art searchInvalidity analysisNon-infringement mappingFreedom to operate

Our knowledge section has in-depth articles on patent processes, technical analysis, and enforcement strategy.

Discuss an engagement.

Tell us about the patent, the targets, or the case. We publish no client names and no matter names.

Discuss a matter

Reader Tools

No notes yet

Select text anywhere and click
"Save" to add research notes