Paradigm-as-code
Scientific test types (MWM, Open Field, EPM, Rotarod) are defined in code as SOLID specs as a read-only catalog. Labs create named environments from them and fill in apparatus values per environment.
Mişko
Behavioral test management for laboratory mice. Plan studies, track subjects, run paradigms, and keep summary results — while computer vision stays an independent service.
What is Mişko?
Section titled “What is Mişko?”Mişko is an internal, on-prem SaaS for biology labs that run behavioral tests on mice. It is the system of record for the lab workflow — subjects, environments, scenarios, tests and summary results — while the heavy computer-vision work (frame telemetry, tracking, video) lives in a separate, independent service.
Scenario-centric domain
A scenario bundles one or more environments (and their paradigms’ metrics), so an experiment is defined once and a test is just pick a subject and run it environment by environment. Results are data, not pass/fail.
Two independent systems
Mişko keeps summary metrics + artifact URLs. The CV service owns raw telemetry and video in its own database. One thin contract connects them.
Internal SaaS, single-tenant
One laboratory per installation. No public sign-up — the superadmin is bootstrapped at startup and manages users from inside.
Where to next
Section titled “Where to next”- Overview: what the system does and who it is for.
- Installation: get Mişko running with Docker or locally.
- Usage: the day-to-day workflow from login to running tests.
- Architecture: layers, stack, and the system boundary.
- Domain model: the lean, scenario-centric data model.
- Measurement architecture: paradigm specs, metric definitions, MWM normalization, and quality control.
- Integration: the Mişko / CV service contract.
- Roadmap: the phased plan.