Your methods section is only as accurate as the specs you referenced.
Most product pages get written once and never updated. We track every change to ours, so you know what you’re citing.
Equipment specs go stale. A flow rate changes with a firmware update. A chamber dimension gets corrected after production feedback. The product page stays the same.
So we started tracking changes.
Every product in our catalog has a spec history. When a specification changes, the version increments and the change is logged: what changed, when, and why. You can see the full history on any product page by clicking the Continuously Verified badge.
Periodic verification
Specs are checked against current production regularly — not uploaded once and left alone.
Change logging
Every update is recorded with a date and reason. Nothing changes silently.
Public history
The full spec version log is visible on every product page. No hidden changes.
Citable versions
Reference a specific spec version in your paper so reviewers can verify exactly what you used.
Published
Check
Detected
& Visible
If you reference our equipment in a methods section, the spec history lets you and anyone replicating your work see exactly what the specifications were when you purchased. If something changed since then, the log shows when and what.
A researcher orders a syringe pump and builds a microinjection protocol around the listed minimum flow rate. She publishes the protocol. A year later, a second lab tries to replicate — but a firmware update three months ago shifted the minimum flow rate. The product page never changed.
With a spec history, the second lab can see when the specification changed and adjust. Without one, they’re troubleshooting a discrepancy that has nothing to do with their technique.
Here’s what a product’s spec history looks like. This is from a real product in our catalog.
- Apr 2026Specifications verified against current production
- Mar 2026Peer-reviewed Q&A section added with researcher-submitted questions
- Feb 2026Documentation expanded: setup guide, calibration procedures, troubleshooting
- Jan 2026Compatible accessories confirmed and linked
- Nov 2025Application protocols added for neuroscience and pharmacology
- Sep 2025Temperature accuracy specification corrected after calibration testing
- Aug 2025Multi-channel configurations documented (1, 2, and 4 channel)
- Jul 2025Initial specifications published
We track spec changes because your experiments depend on those numbers being right.
See for yourself
Browse our catalog and click any Continuously Verified badge to see the full spec history.
Browse Lab Equipment
The glass box model
Verification makes the commercial tool inspectable.
The trust gap around commercial research tools is simple: reviewers and future laboratories need to see the record behind the tool, not only the tool itself.
ConductScience exposes the citation, specification, version history, procedure, analytics, and files that surround the apparatus. The method stack becomes visible enough to cite, repeat, and audit.
Black box vendor
Product record
Citation
not linked
Specification
not versioned
Procedure
not inspectable
Analytics
not exported
Glass-box infrastructure
Citation
Published method and product record stay linked
Specification
Dimensions, materials, sensors, and timing are visible
Version
Dated changes preserve what each lab actually ran
Procedure
ConductMaze turns protocol steps into executable runs
Analytics
ConductVision exports inspectable behavioral measures
Files
Protocols, datasets, and method packages travel together
Reproducibility improves when the commercial tool exposes the method record around it.
Method record anatomy
A verified product page is part of the methods record.
Continuous Verification keeps the public product page tied to the apparatus version, specification history, procedure files, analytic boundaries, and citation chain that a lab needs for replication.
Method record
Versioned. Cited. Runnable.
The record is the shared object that lets apparatus, procedure, analysis, and files travel between laboratories.
Citation
Published method and product record stay linked
Specification
Dimensions, materials, sensors, and timing are visible
Version
Dated changes preserve what each lab actually ran
Procedure
ConductMaze turns protocol steps into executable runs
Analytics
ConductVision exports inspectable behavioral measures
Files
Protocols, datasets, and method packages travel together
