Who is the LocusTrace Review Console for?
The Review Console is for analysts, counsel, strategy teams, consultants, and technical operators who need to inspect patent and litigation evidence without using the CLI.
A sober evidence-review console for analysts, counsel, strategy teams, and consultants. It routes users into decisions: what needs review, why it matters, whether the packet verified, what is covered, and what disposition to record.
The fastest path is review-first: inspect the public sample event, open the live console, record one disposition, export the evidence trail, then request a guided handoff.
Informational evidence infrastructure only. Not legal advice, not infringement analysis, not FTO.
Start with the public 90-second event walkthrough. No login, runtime, or CLI required.
Get the starter ZIP with the console, mRNA dataset, sample ledger, and reviewer packet.
Load the bundled mRNA litigation JSON from the starter examples folder.
Record one disposition, then export the reviewer packet or disposition ledger.
The download is not just a page. It includes source data, a disposition ledger sample, a reviewer-packet sample, and the static-console verification artifact so technical evaluators can verify what the reviewer saw. The starter now includes loadable mRNA litigation, sequence packet, and PTAB bundle datasets for `Load review data JSON` in the offline console, plus Dataset status, Ledger hash visibility, and a Demo complete handoff with a copyable follow-up note and hosted follow-up form link.
Browser-first guide that routes reviewers to the console and sample report.
Static non-technical queue and evidence-review workflow.
macOS launcher for opening the review console first.
Linux launcher for opening the review console first.
Data contract referenced by the console hash.
Loadable mRNA litigation review dataset.
Loadable sequence evidence-packet review dataset.
Loadable PTAB bundle review dataset.
Hash-chained reviewer decision sample.
Export shape for one reviewed event.
Compiled console verification artifact.
Use `review-console` with the current public runtime. The `locus-trace` alias is available in newer source builds and will be the public command name for the same workflow. Both route to the same immutable console data, static HTML, and verification artifact contracts.
patentchecker review-console open --input <artifact.json|artifact-dir> --out-dir <dir> --no-browser
patentchecker locus-trace open --input <artifact.json|artifact-dir> --out-dir <dir> --no-browser
The console does not ask users to browse artifacts. It asks them to review one event, inspect the evidence, understand coverage, record a disposition, export a packet, and verify that packet against the source data.
Sequence patent risk or public IP litigation intelligence.
Read what happened, why it may matter, and why it appeared.
Open the drawer for source, retrieval time, packet status, and receipt.
Load review data JSON, import a matching disposition ledger, export local decisions, or download reviewer-packet JSON.
Current release: v0.1.52
Start with who should use the console, how to inspect the workflow without local setup, and where the evidence boundary stops.
The Review Console is for analysts, counsel, strategy teams, consultants, and technical operators who need to inspect patent and litigation evidence without using the CLI.
Yes. The public sample event lets reviewers inspect the workflow in the browser first, then download the starter package when they want local datasets and export artifacts.
No. LocusTrace is informational evidence infrastructure only. The console shows source, coverage, verification, disposition, and export context; it does not provide legal advice, infringement analysis, freedom-to-operate conclusions, or investment advice.