Kineologist

Custom deployments

Turn a repeatable movement into a dedicated analysis product.

A custom deployment defines the movement grammar, telemetry, phase markers, detector rules, reporting language and validation pathway for a specific sport, clinic, education or performance workflow.

Custom deployment movement grid

Movement examples

Repeatable protocols become product paths.

Custom Deployments are for movements where the same pattern is captured repeatedly and the review layer can be made meaningful with custom telemetry, windows, rules and reports.

Football kick

Kick sequencing, plant timing and follow-through windows.

Sprint mechanics

Acceleration, contact rhythm and trunk/arm patterns.

Golf swing

Phase markers, rotation timing and baseline comparison.

Tennis serve

Serve phases, shoulder/trunk sequence and release patterns.

Cricket bowling

Bowling phases, arm path and repeatability review.

Surf pop-up

Pop-up timing, stance and transition quality.

Rehab screen

Clinic-specific movement tests and readable outputs.

Return-to-play

Baseline-relative review for repeatable progress checks.

Education lab

Teaching outputs, plots and structured evidence packages.

Deployment process

From protocol to product.

The deployment process converts movement research into a working product path. We define what matters, detect when it happens, create rule logic and then test the outputs in the real environment.

01

Define protocol

Lock the movement, audience, capture requirements and success criteria.

02

Define telemetry

Choose channels that expose the movement qualities worth reviewing.

03

Build detectors

Create phase or event logic that marks meaningful windows.

04

Create rules

Translate repeated patterns into deterministic severity and language outputs.

05

Shape reports

Create Coach, Master, specialist and multilingual review surfaces.

06

Validate

Test with facilities, educators or performance teams as a pathway to functional validation.

Custom Sport Pack

A custom deployment becomes a plug-in pack for the engine.

A custom Sport Pack is essentially a plug-in context for the Kineologist engine. It isolates the detectors, telemetry definitions, rule sets, report lexicon and language used for a specific movement task. Creating a custom deployment means defining the pack, integrating it with the shared engine, testing the outputs, validating the review surfaces and then deploying it as a focused product path.

Detector isolation

Custom event and phase detectors stay inside the pack rather than polluting the core engine.

Telemetry definition

The pack defines which channels matter for the movement context.

Rule sets

Context-specific rules evaluate telemetry and persistent movement patterns.

Report lexicon

The pack owns the language used to explain findings safely and clearly.

Validation path

Each pack can be tested and validated against the task it was created for.

Deployment boundary

The final pack becomes a focused product path while sharing the same Kineologist engine.

Telemetry definition

A custom product starts by defining what should be measured.

The telemetry layer translates a movement into inspectable channels. For baseball pitching, channels can include root speed, hips and pelvis position, trunk separation, trunk separation velocity, forearm lag, elbow flexion velocity, foot-centre channels, front-knee angle, hip-centre speed, hip rotation, stride distance, head displacement, arm displacement, spine displacement and cocking elbow/hand-depth channels.

Channel selection

Pick channels that explain the target movement rather than generic metrics.

Evidence traceability

Outputs stay connected to telemetry, CSV, plot and report artifacts.

Context-specific logic

The same engine can express baseball, gait or a new movement grammar.

Phase windows

Define the moments where measurement becomes meaningful.

Review surfaces

Telemetry can be inspected beside 3D motion and reports.

Validation pathway

The channel set can be tested with facilities or education partners.

Custom telemetry channel definition

Context-specific detectors

Custom detectors turn movement into automatic phases.

Detector logic creates the timing windows that make a review meaningful. A deployment may define phases, contact events, release points, stable windows, repetitions or sport-specific review moments, then expose them in the same inspectable review layer used by PITCH: motion, curves, markers and evidence together.

Full-screen TrackView 3D and curve review proof

Observe movement

Study the repeated protocol and the moments that matter.

Define events

Lock contact, release, peak, stable or repetition events.

Create crop logic

Build timing windows around the selected events.

Export telemetry

Generate curves and channels tied to those windows.

Run rules

Compile persistent patterns into deterministic findings.

Review outputs

Inspect 3D motion, reports, plots and CSV evidence.

Custom rules

Custom rules turn telemetry into graded review findings.

Bespoke deployments require custom rule sets so telemetry can be processed through rule-based analysis. Tunable rules flag persistent patterns during defined phase windows, then grade the severity of each pattern. That severity grading drives report language through a context-specific lexicon, so the final outputs remain repeatable, reviewable and specific to the movement task.

Telemetry inputs

Rules consume the telemetry channels generated by the custom detector and analysis path.

Phase-aware windows

Findings can be evaluated inside defined P phases or movement events.

Persistent pattern flags

Rules can look for repeated or sustained patterns rather than one-frame noise.

Severity grading

Tunable thresholds can grade pattern severity for reporting and review.

Context lexicon

Findings are expressed through language written for the deployment context.

Report integration

Rule outputs feed Coach, Master and specialist report surfaces.

Report language

Reports can be shaped around the deployment audience.

The report layer can be tuned for intended users and language. A Japanese report surface, coach report, master report or specialist deployment report can present the same deterministic backend evidence in the right voice.

Custom report language example

Stable engine

One stable engine, custom movement meaning.

The shared engine keeps artifacts, baselines, telemetry, 3D review, plots and report generation stable while the deployment layer defines what the movement means and how it should be interpreted.

Custom movement pack architecture

Next step

Have a repeatable movement that deserves its own product?

Tell us the movement, the capture setup, the review audience and the evidence you need. We can discuss whether it fits a custom Kineologist deployment path.

Discuss a deployment