Docs · Omnis LocusTrace

LocusTrace docs for evaluation, verification, and delivery risk

Use this lane for buyer evaluation, evidence verification, self-hosting, adapters, coverage scope, and the delivery-system surfaces behind vector and sequence IP review.

Patent IPDelivery riskVerificationSelf-serve
Need another page?
Search the docs

Jump to buyers, verification, demos, self-hosting, or adapters without opening the full docs tree first.

Mobile navigation
Jump to section
Open
Omnis LocusTrace is verifiable patent-sequence drift monitoring. It produces offline-verifiable Evidence Packets that show how public patent-sequence coverage changes around a biotech program over time.
Use this page when you want the shortest path from "I found the product" to "I can verify the artifact and start an evaluation."
Informational evidence infrastructure only. Not legal advice, not infringement analysis, not FTO.

What you can do first

Most users should start in this order:
  1. Download the current runtime bundle.
  2. Verify the runtime checksum.
  3. Run patentchecker info to confirm the contract and schema digests.
  4. Verify the public demo Evidence Packet.
  5. Start the free 2-week LocusTrace trial when you want scoped watchlists and buyer-specific packets.
The public product name is Omnis LocusTrace. The runtime binary is still named patentchecker for backward compatibility.

Open the Review Console locally

The browser-first Review Console is the easiest way to understand LocusTrace before using company-specific inputs. In the current mirrored runtime, use the stable internal command name:
BashRunnable example
./patentchecker/patentchecker review-console open \
  --input examples/evidence-packet.sample.v0.1.json \
  --out-dir /tmp/locus-review-console \
  --no-browser
The command writes review-console.html, review_console_data.v0.1.json, and static_review_console.v0.1.json, then prints a local file_url. Newer source builds also accept the public alias locus-trace for the same workflow; review-console remains supported for compatibility.

Download the runtime

Use the website download links so the asset path stays pinned to the current public release:
Linux:
BashRunnable example
BASE="https://omnisgenomics.com/patent-checker/downloads/v0.1.52"

curl -L "$BASE/patentchecker-linux-x64.tar.gz" -o patentchecker-linux-x64.tar.gz
curl -L "$BASE/patentchecker-linux-x64.tar.gz.sha256" -o patentchecker-linux-x64.tar.gz.sha256
sha256sum -c patentchecker-linux-x64.tar.gz.sha256
tar -xzf patentchecker-linux-x64.tar.gz

./patentchecker/patentchecker info
macOS:
BashRunnable example
BASE="https://omnisgenomics.com/patent-checker/downloads/v0.1.52"

curl -L "$BASE/patentchecker-macos-universal.tar.gz" -o patentchecker-macos-universal.tar.gz
curl -L "$BASE/patentchecker-macos-universal.tar.gz.sha256" -o patentchecker-macos-universal.tar.gz.sha256
shasum -a 256 -c patentchecker-macos-universal.tar.gz.sha256
tar -xzf patentchecker-macos-universal.tar.gz

./patentchecker/patentchecker info
Expected result: the checksum command prints OK, and patentchecker info prints contract and schema digest metadata.

Verify a public Evidence Packet

Download the demo packet and checksum:
BashRunnable example
BASE="https://omnisgenomics.com/patent-checker/downloads/v0.1.52"

curl -L "$BASE/demo_offline_packet.zip" -o demo_offline_packet.zip
curl -L "$BASE/demo_offline_packet.zip.sha256" -o demo_offline_packet.zip.sha256
sha256sum -c demo_offline_packet.zip.sha256
Then lint the packet with the runtime you unpacked above:
BashRunnable example
./patentchecker/patentchecker packet lint \
  --packet demo_offline_packet.zip
Expected result: the packet validates without modifying the packet. Treat any checksum mismatch or lint failure as a stop condition and re-download from the website release path.

What a LocusTrace Evidence Packet contains

An Evidence Packet is designed to be reviewed by humans and verified by software.
Core artifacts:
  • report.md: human-readable monitoring or posture report
  • alerts_summary: machine-readable triage summary
  • run_packet_index.v0.1.json: packet file index with stable references
  • index.json: counsel-facing artifact index
  • *.sha256: checksums for offline verification
  • receipts and manifests: release, runtime, and run provenance
The packet should answer:
  • what input scope was declared
  • what public corpus or source snapshot was used
  • what changed between comparable runs
  • which artifacts support the finding
  • which claims are deliberately not being made

Start the free 2-week trial

Use the free trial when you want Omnis to scope a buyer-specific evaluation instead of only verifying the public demo.
Trial shape:
  • 1 to 3 scoped LocusTrace Watchlists
  • one concrete sequence-heavy review problem
  • deterministic Evidence Packets
  • weekly review loop
  • production-key decision only after proof

Choose the right next page

Common failure modes

If sha256sum -c or shasum -a 256 -c fails, delete the downloaded file and checksum, then download both again from the website path.
If ./patentchecker/patentchecker info is missing, confirm the archive was extracted and that you are running the command from the directory that contains the unpacked ./patentchecker folder.
If packet lint fails, keep the failing packet unchanged and capture the command output. The packet and output are useful debugging artifacts during a trial or support handoff.