Motion capture files
Baseline and subject motion files enter a selected product workflow rather than a generic black box.
Technology
A deterministic engine for movement evidence.
Kineologist is built around deterministic analysis rather than hidden judgement. Motion capture files move through a product-specific pipeline; the backend creates phase markers, crop windows, baselines, telemetry channels, plots, reports and debug artifacts; the interface then lets the reviewer inspect those outputs.
Live pipeline spine
From motion files to reviewable evidence.
The technology spine is intentionally explicit. Kineologist separates computation from presentation: the backend generates deterministic artifacts, while the GUI and report layer render those artifacts for review. This keeps the system inspectable, repeatable and easier to test across products.
Context detector
PITCH, GAIT or a custom deployment defines the phase/event logic that makes the motion meaningful.
Phase/event crop
The movement is cropped around relevant windows before the rest of the analysis is calculated.
Baseline generation
Reference clips can be normalised and averaged into a repeatable comparison authority.
Telemetry extraction
Curves, rotations, velocities, contact channels, events and deltas are exported as evidence.
Muscle proxy sequencing
Motion-derived proxy groups are created from joint rotations, motion and velocities.
Rule engine
Research-derived, context-specific rules convert persistent patterns into deterministic findings.
Reports / plots / CSV
Reports, plots, CSVs, JSON markers and debug snapshots are written as inspectable artifacts.
Review surfaces
The interface presents the generated evidence through 3D review, TrackView, reports and exports.
Sport Pack architecture
Sport Packs let one engine operate in different movement contexts.
The Kineologist engine stays shared, while movement-specific logic lives in Sport Packs. A pack can define detector behaviour, phase/event semantics, telemetry channels, rules, thresholds, report language and review outputs for a particular context. This keeps PITCH, GAIT and future custom deployments on the same artifact-driven backend while preventing one movement model from contaminating another.
Shared engine
Parsing, artifact generation, baseline handling and review surfaces stay common.
Pack-owned detectors
Movement-specific event and phase detectors live inside the relevant pack.
Telemetry schema
Each pack declares the channels that matter for its movement context.
Rules and thresholds
Pack rules process telemetry through tunable, repeatable analysis logic.
Report lexicon
Each pack owns the wording used to explain findings safely.
Deployment scaling
New contexts can be added by creating, testing and validating a new pack.
Context-specific detectors
Different movements need different truth windows.
A repeated movement only becomes useful evidence when the right moments are detected. PITCH uses baseball phase markers. GAIT uses walking events and fixed-step windows. Custom deployments can define their own detector logic, phase markers, telemetry channels and report language. This prevents repeatable movements from being forced into one generic analysis model.
PITCH phases
Baseball pitching review is anchored by P1–P4 phase markers.
GAIT events
Walking review is anchored by IC/TO events and fixed-step logic.
Custom detectors
A deployment can define its own meaningful windows.
Comparable crops
Subject and baseline use the same crop authority.
Artifact-first output
A run produces files you can inspect, not just a screen you must trust.
Every run creates tangible artifacts: cropped files, baseline-aligned files, marker JSON, telemetry CSV, plots, reports, debug snapshots and review-ready outputs. This matters because the analysis does not disappear into the interface; it leaves evidence that can be audited, shared and inspected after the session.
CSV / JSON
Telemetry, markers and debug evidence are retained as files.
Plots
Technical plot outputs support deeper inspection outside the GUI.
Reports
Coach, Master and Muscle reports translate findings into readable form.
Review surfaces
The interface presents generated outputs rather than inventing them visually.
Baseline-relative analysis
Baseline and subject can be reviewed in original and phase-locked time.
Baseline files can be cropped, length-normalised and averaged into a reference movement. Subject files are cropped with the same phase or event logic and compared back against the baseline. The system can review original timing differences and phase-locked magnitude differences, making the comparison more useful than simply placing two motions side by side.
Average reference
Multiple reference files can become a single comparison authority.
Shared windows
Baseline and subject use the same marker/event grammar.
Timing deltas
Original timing differences remain available for review.
Magnitude deltas
Phase-locked review supports shape and rotation comparison.
Telemetry and TrackView
Generated channels drive the review layer.
TrackView and plot surfaces display generated telemetry rather than visually invented values. Reviewers can inspect selected telemetry, phase lines, timing deltas, magnitude differences, baseline overlays, thresholds and channel-specific curves alongside the 3D motion.
Generated channels
The curves come from exported telemetry rather than display-only overlays.
Marker context
Phase/event lines make the timeline meaningful.
Baseline overlay
Differences can be inspected against the reference movement.
Threshold visibility
Overlay and rule settings remain inspectable by expert users.
Motion-derived proxies
Muscle proxy sequencing is derived from movement, not direct activation measurement.
Muscle proxy groups are inferred from relative joint rotations, joint motion and velocities. The system uses these motion-derived signals to visualise sequencing, contribution and baseline-relative differences across major muscle groups and individual muscles. This can support movement review, but it is not EMG and must not be described as direct measured activation.
Joint rotation and velocity inference
Proxy activity is inferred from relative joint rotations and movement velocities.
Full-body muscle mapping
Motion-derived proxy channels map across major body regions.
Flexion and extension groups
Flexion and extension families make contribution patterns easier to inspect.
Muscle activity HUD
Proxy percentages can be reviewed beside the 3D motion display.
Sequencing and contribution reports
Dedicated report surfaces summarise ordering, contribution and comparison patterns.
Clear boundary
The system does not claim EMG or direct muscle activation.
Deterministic rules
Research-derived logic creates repeatable findings.
Rule logic is built from biomechanics research cycles and product-specific review goals. Persistent detected patterns across phases or walking events can trigger context-specific findings, severity bands and report language. With the same inputs, settings and artifacts, the system should produce the same outputs.
Rule-based findings
Findings are triggered by deterministic logic, not AI guessing.
Context-aware
Rules run inside PITCH, GAIT or deployment-specific movement windows.
Severity bands
Persistent patterns can be translated into configurable severity language.
Evidence trace
Reports remain tied to markers, telemetry, debug outputs and CSV artifacts.
Reports and multilingual operation
Reports translate generated evidence into human-readable review surfaces.
Reports convert generated evidence into readable outputs. Coach reports focus on concise review language. Master reports give deeper technical interpretation. Muscle reports show motion-derived proxy sequencing and contribution in structured form. Report language can be shaped per product or deployment, and the system can operate across five language paths while stable technical identifiers remain unchanged underneath.
Coach reports
Concise applied review language for coaches and practitioners.
Master reports
Longer-form technical context for analysts and validation partners.
Muscle reports
Structured proxy sequencing and contribution tables.
Five languages
English, Italian, Spanish, Traditional Chinese and Japanese deployment paths.
Hardware agnostic
Auto Remap helps different skeleton definitions enter the same pipeline.
Different mocap systems use different skeleton naming conventions. Auto Remap inspects the skeleton definition, extracts semantic body roles and routes those roles into the product pipeline. This reduces manual setup and makes the system more practical across different capture sources, while still needing validation across new skeleton families.
Skeleton inspection
The file is inspected for meaningful body roles.
Semantic mapping
Names are mapped into the product pipeline.
No manual config
The goal is less user setup for supported skeleton families.
Validation path
New skeleton families still need real-world validation before being treated as proven.
Threshold tuning
Expert users can tune the rule layer instead of accepting one universal judgement.
Threshold controls allow product teams, coaches, facilities or validation partners to tune overlays, rule sensitivity, marker display and severity bands. This supports expert control rather than forcing one universal judgement model across every population, method or deployment context.
Visible controls
Sensitivity, marker overlays and severity bands can be inspected instead of hidden.
Validation support
Facilities can tune and test thresholds during beta/functional validation.
Product-specific
Custom deployments can define thresholds around their own protocol.
Repeatable settings
Settings can be kept stable so repeated runs remain comparable.
Plots and technical artifacts
Generated plots provide a technical inspection layer familiar to biomechanics workflows.
Plots support deeper interpretation of telemetry channels, marker timing and movement curves outside the main GUI. They are useful for technical review, documentation, validation conversations and audit trails where a reader wants to see the shape of the underlying data.
Technical review
Plots expose the shape of telemetry rather than only the written summary.
Channel curves
Selected channels can be inspected for peaks, timing, ramps and magnitude.
Marker context
Phase or event markers help align visual curves with movement structure.
Report support
Plots provide supporting evidence for report interpretation and audit trails.
Honest boundaries
Beta software, validation pathway, clear limits.
Kineologist is currently in Beta and undergoing testing at facilities and educational institutions as a pathway to functional validation. It is a movement-analysis and review tool, not a diagnostic or clinical decision system.
Beta validation pathway
Facilities, coaches, educators and analysts can help test workflows, compare outputs and shape functional validation.
Motion-derived proxies
Muscle activity views are inferred from motion, joint rotations and velocities. They are not EMG and not direct measured activation.
Readable review, not diagnosis
Reports translate deterministic analysis into human-readable review surfaces without making clinical diagnostic claims.
Next step
Want to test the engine against your movement data?
Book a demo, discuss a beta validation pathway, or explore a custom deployment built around your movement protocol.