Skip to content

Make the next technical decision with evidence.

Work with Nicholas Harris on a scoped evaluation of a scientific dataset, an agent workflow, an inference isolation design or a computational model. Remote consulting, licensing and acquisition conversations are welcome.

Choose a question we can test

  • Scientific-data audit. Trace sources, units, uncertainty and conflicting records before deciding what the dataset can support.
  • Verification and evaluation. Define an invariant, exercise adverse cases and preserve failures alongside successful runs.
  • Integration study. Test a bounded interface or model against an agreed reference and document where the comparison stops applying.

Agree on the deliverable first

Start with a short written problem statement. Together we define the inputs, access boundaries, test method, acceptance criteria and exclusions before agreeing on scope and pricing.

The proposed deliverable is a reproducible evaluation package: the agreed method, source references, runnable checks where sharing rights permit, results and limitations, and a recommendation tied to the evidence. A failed hypothesis remains a useful result.

Inspect the public work

The result pages explain what the lab demonstrated and what remains untested. The evidence and disclosure page distinguishes public artifacts from private implementation. These are examples for evaluation; they do not establish performance in your environment.

For an asset rather than a service, see the licensing and acquisition options. Ownership, dependencies, available rights and evaluation access must be confirmed in diligence before a transaction.

Bring a concrete problem

Send the technical decision you need to make, the available evidence, the intended use and any access restrictions. Please send a public summary first rather than confidential data.

Discuss an evaluationExplore an asset

nick@latticegraph.com · Nicholas Harris · Scottsdale, Arizona · Remote engagements

How we show numbers

A number you can click opens the file it comes from. How each result is checked

  • We never show a number before its file has loaded.
  • A question we have not checked yet is marked as unchecked.
  • A check that found nothing says so.
  • A file with no value for a question says so.
  • A number whose file is missing or has changed is not shown.
  • Two files that disagree about what a number describes are both flagged.
  • A number from too few samples shows its sample size.
  • Two files that give different values are both shown.
  • A file we cannot publish is listed by its fingerprint only.
  • Where a file records when it was measured, the date is in that file.
  • A question that does not apply to a page is left off it.
  • A measurement whose program failed is shown as failed.