Football kick
Kick sequencing, plant timing and follow-through windows.
Custom deployments
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.

Movement examples
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.
Kick sequencing, plant timing and follow-through windows.
Acceleration, contact rhythm and trunk/arm patterns.
Phase markers, rotation timing and baseline comparison.
Serve phases, shoulder/trunk sequence and release patterns.
Bowling phases, arm path and repeatability review.
Pop-up timing, stance and transition quality.
Clinic-specific movement tests and readable outputs.
Baseline-relative review for repeatable progress checks.
Teaching outputs, plots and structured evidence packages.
Deployment process
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.
Lock the movement, audience, capture requirements and success criteria.
Choose channels that expose the movement qualities worth reviewing.
Create phase or event logic that marks meaningful windows.
Translate repeated patterns into deterministic severity and language outputs.
Create Coach, Master, specialist and multilingual review surfaces.
Test with facilities, educators or performance teams as a pathway to functional validation.
Custom Sport Pack
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.
Custom event and phase detectors stay inside the pack rather than polluting the core engine.
The pack defines which channels matter for the movement context.
Context-specific rules evaluate telemetry and persistent movement patterns.
The pack owns the language used to explain findings safely and clearly.
Each pack can be tested and validated against the task it was created for.
The final pack becomes a focused product path while sharing the same Kineologist engine.
Telemetry definition
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.
Pick channels that explain the target movement rather than generic metrics.
Outputs stay connected to telemetry, CSV, plot and report artifacts.
The same engine can express baseball, gait or a new movement grammar.
Define the moments where measurement becomes meaningful.
Telemetry can be inspected beside 3D motion and reports.
The channel set can be tested with facilities or education partners.

Context-specific detectors
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.

Study the repeated protocol and the moments that matter.
Lock contact, release, peak, stable or repetition events.
Build timing windows around the selected events.
Generate curves and channels tied to those windows.
Compile persistent patterns into deterministic findings.
Inspect 3D motion, reports, plots and CSV evidence.
Custom rules
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.
Rules consume the telemetry channels generated by the custom detector and analysis path.
Findings can be evaluated inside defined P phases or movement events.
Rules can look for repeated or sustained patterns rather than one-frame noise.
Tunable thresholds can grade pattern severity for reporting and review.
Findings are expressed through language written for the deployment context.
Rule outputs feed Coach, Master and specialist report surfaces.
Report language
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.

Stable engine
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.

Next step
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.