Football kick
Kick sequencing, plant timing and follow-through windows.
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.
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.
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. It also defines analysis depth: full-body, torso-only or another controlled capture corridor. We define what matters, detect when it happens, create rule logic and test the outputs in the real environment.
Define protocol
Lock the movement, audience, capture requirements and success criteria.
Define telemetry
Choose channels that expose the movement qualities worth reviewing.
Build detectors
Create phase or event logic that marks meaningful windows.
Create rules
Translate repeated patterns into deterministic severity and language outputs.
Shape reports
Create Coach, Master, specialist and multilingual review surfaces.
Validate
Test with facilities, educators or performance teams as a pathway to functional validation.
Research to rules
Deep movement research becomes a deployable rule system.
A custom deployment starts by understanding the movement sequence: phases, timing windows, meaningful telemetry, common technique patterns and context-specific caution states. That research is converted into detector logic, telemetry definitions, rule thresholds, severity grading and report lexicons. The result is a sport pack that can repeatedly turn captured motion into structured findings rather than generic visual playback.
Research model
The movement is studied until its phases, events and review priorities are explicit.
Telemetry design
Only channels that explain the movement context are promoted into the pack.
Rule logic
Research assumptions become deterministic conditions and persistent-pattern tests.
Tunable thresholds
Severity bands can be adjusted during expert review and validation.
Lexicon mapping
Graded findings select safe language written for the deployment context.
Report generation
Rules feed Coach, Master and specialist reports using the shared Kineologist engine.
Detector examples
Different sport packs can use different detector grammars.
Custom deployments do not force every movement into one detector model. PITCH is built around a baseball phase grammar that uses local wrist positional trace, wrist speed and wrist rotation to understand key throw phases. GAIT uses a walking-event grammar, starting with local foot positional trace and speed, then refining IC/TO timing with motion-derived muscle analysis. The shared engine stays the same; the sport pack defines the evidence that makes the movement meaningful.
PITCH detector grammar
Local wrist trace, wrist speed and wrist rotation help identify baseball phase moments.
GAIT detector grammar
Local foot trace and speed establish walking IC/TO event candidates.
GAIT post-process precision
Motion-derived muscle analysis refines walking events after the first detector pass.
Custom pack freedom
A new deployment can define its own detector mix, telemetry and report language.
Custom Sport Pack
A custom deployment becomes a controlled evidence product.
A deployment can define its own analysis modes, full-body or reduced-sensor profiles, phase-warp policy, evidence-quality grading, semantic report schemas, editable client terminology and multilingual report assets while sharing the stable Kineologist engine.
Context-owned detectors
Custom events and phases remain inside the deployment pack.
Evidence profiles
Whole-chain or focused capture profiles define which measurements are authoritative.
Evidence-quality grading
Strong, limited and invalid evidence states can be made explicit.
Semantic reports
Coach and Master surfaces share one deterministic evidence profile.
Editable terminology
Client language can be adapted without changing the analysis.
Multilingual assets
Report and Lexicon assets can be packaged per deployment language.
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 throwing-arm position and 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.
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.
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 evidence profiles can connect a whole movement chain.
A custom deployment can combine detector events, phase-relative telemetry, whole-chain sequence logic, exact timing and magnitude differences, evidence-quality grading and report claim boundaries into one deterministic product path.
Exact timing
Frames and seconds under native timing authority.
Exact geometry
Degrees and distance under the correct aligned authority.
Native magnitude
Speed and acceleration retain their physical scale.
Evidence quality
Strong, limited or invalid evidence is stated explicitly.
Claim boundary
The report states what the result can and cannot prove.
Report integration
The same evidence drives Coach, Master and specialist surfaces.
Report language
Clients can adapt substantially all report language across five languages.
Headlines, interpretations, labels, evidence templates, action plans, review priorities, section headings and claim boundaries can be adapted to the organisation while the underlying evidence remains locked.
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.
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.