Docs · OGN platform
GPU-native genomics operating system
From raw reads to GIAB-validated variant calls in a continuous GPU pipeline. This is the control surface for the engine: CLI, pipelines, benchmarks, and deployment runbooks.
CUDA 12+Hopper · AmpereGIAB-validated flowsSchemas stable
Viewing
PatentChecker coverage scope
PatentChecker Coverage Scope
PatentChecker is strongest today when it is positioned as a deterministic evidence workflow, not a generic patent search portal.
This page explains what is covered now, what gets scoped during evaluation, and what we do not claim by default.
Current strongest path
The strongest current workflow is:
- WIPO/PCT-first sequence and patent-text review
- deterministic evidence bundles
- offline verification of artifacts and receipts
- buyer-run paid
2-weekevaluation in the buyer's own environment
That is the path we recommend for first evaluations because it is the most proven, the easiest to verify, and the least likely to overstate product breadth.
What PatentChecker does well today
- turns monitoring output into signed, reviewable evidence instead of a black-box report
- preserves hashes, provenance, and verification receipts
- supports buyer-run paid evaluation and production-key conversion after proof
- scopes watchlists, cadence, and coverage declarations around a specific review problem
What "coverage" means here
Coverage is not a marketing label. It is the declared scope of the run:
- jurisdictions
- sequence types
- made-public cutoff
- source and adapter path
Those declarations are part of the artifact trail, so buyers and counsel can see what was and was not checked.
Expansion path
PatentChecker can widen beyond the default WIPO/PCT-first lane through approved adapters and buyer-specific corpus scope.
That means:
- private-corpus or customer-specific data sources can be scoped during evaluation
- office-specific workflows can be added behind the adapter boundary
- production deployment can be matched to the buyer's environment and controls
The first evaluation should stay narrow. Expansion happens after the workflow proves useful.
What we do not claim by default
PatentChecker does not claim all of these out of the box:
- full native office-specific coverage for every jurisdiction
- legal opinions
- freedom-to-operate determinations
- infringement conclusions
- practitioner-led prosecution support unless a practitioner partner is explicitly involved
If your workflow depends on office-specific coverage, private corpora, or deployment restrictions, scope that during the evaluation instead of assuming it.
International buyers
PatentChecker can be evaluated by global teams today, but the default buyer path is still:
- English-first
- WIPO/PCT-first
- deterministic evidence first
If your team needs region-specific data handling, office-specific source expansion, or a more restrictive deployment model, raise that during the evaluation scoping step.
Recommended first step
Start with the
2-week evaluation and one concrete review problem:- one watchlist
- one sequence-centered question
- one recurring monitoring workflow
That gives the fastest answer to the real question: can your team get to a first verified bundle quickly enough for the workflow to matter.