Science Library

Behavioral apparatus, organized around the work.

Use this as the scientific map of ConductScience: apparatus families, paradigms, scored endpoints, species constraints, disease models, and methods that help a lab choose the right equipment path.

Apparatus libraries for the full behavioral suite

Each library should read like a scientific buying map, not a thin category page. It should explain what the apparatus is for, what it measures, what design details matter, and where adjacent tools or products fit.

Open current index
Boundaries

Keep separate projects separate.

/science is the cross-suite scientific library. Product-specific acquisition, automation, support, and graph-discovery surfaces can be linked when useful, but they should not be the primary sections here.

Software workflows

Acquisition, tracking, scoring, and analysis stay in the software product surfaces.

Executable schedules

Automated protocol runners and task files stay with the automation product surface.

Post-purchase support

Warranty, installation, repair, and service plans stay in the support surface.

Funding graph

Investigators, institutions, grants, and research discovery stay in the dex surface.