Technical Monograph
The governed 37-chapter reference for equations, model-conditioned transfer mechanisms, uncertainty, attribution, evidence ledgers, and declared falsifiers.
Read the Technical Monograph →Content ↔ Computation
Start with the scientific argument, inspect its evidence and falsifiers, then move toward executable workflows only when an immutable provider record makes the software claim verifiable. This page is the stable bridge between AffineDrift's biomechanics library and the UpstreamDrift program repository.
This establishes a curated map among AffineDrift-owned reading,
exploratory tools, declared models, claims, and evidence. Exact source commit
85cce4d3307bb7ad3953d9fc6e583e370803515c
governs the featured computational publication.
This does not establish current installation commands, program inventory, engine support, interface compatibility, reproducibility on a reader's machine, independent scientific review, or participant-level human validation.
The proximal-to-distal collection is AffineDrift's most complete worked bridge from a long scientific argument to inspectable assumptions, counterfactuals, and model experiments. Choose the depth that fits your task; the routes reinforce one another.
The governed 37-chapter reference for equations, model-conditioned transfer mechanisms, uncertainty, attribution, evidence ledgers, and declared falsifiers.
Read the Technical Monograph →A 30-chapter plain-language journey through how a golf swing carries energy, with the same model and human-validation boundaries as the technical work.
Read the Visual Companion →A claim-by-claim field guide to observables, competing explanations, failure signatures, and the evidence that could weaken or overturn each mechanism.
Open the Falsification Atlas →Guided parameter sweeps and model comparisons for challenging the argument. Outputs are exploratory model results, not measurements from golfers.
Open the Model Workbench →Place the featured monograph alongside The Physics of Golf, The Geometry of Motion, and the four focused research-development volumes.
Browse the Long-Form Library →Build from physical intuition toward mechanics, evidence, and bounded model interpretation without treating simulation as human validation.
Follow the Golf Science Path →Connect coordinate conventions, multibody models, measurement, uncertainty, and causal limits before making claims about a golfer or population.
Follow the Biomechanics Path →UpstreamDrift remains the implementation authority. AffineDrift will publish exact commands, catalogs, screenshots, and worked examples only from its deterministic, exact-commit companion artifact. Until then, absence here means not yet verified for publication, not that a capability does or does not exist.
Waiting for provider manifest and interface authority (UpstreamDrift #9174, #9193) and the generated AffineDrift catalog (#4023, Programming Hub).
Waiting for the curated public-interface record (UpstreamDrift #9193) and generated onboarding contract (AffineDrift #4024, Engines Matrix).
Waiting for governed workflow authority (UpstreamDrift #9190), exact-commit regression (AffineDrift #4028), and interpreted examples (#4029, Workflows Catalog).
Waiting for provider capture provenance (UpstreamDrift #9191) and the AffineDrift visual-artifact pipeline (#4025).
Waiting for protected immutable publication (UpstreamDrift #9192) and provider-consumer compatibility gates (AffineDrift #4030, Provenance Ledger).
Use the Research Protocol and Data-Readiness Library to distinguish concept, simulation, pilot, ethics, and analysis states. Software readiness never authorizes participant collection, coaching, clinical use, or claim promotion.
Continue from the readiness library into the governed protocol that matches the claim you intend to test. Each route states its evidence boundary, unavailable results, and the conditions required before stronger interpretation.
These legacy guides remain available for orientation while route audit #4060 checks every capability, version, support, license, and qualification claim. Their presence here is not a statement of current UpstreamDrift support.