Development Roadmap

Evidence-bounded development states and live planning authorities for AffineDrift

Development Roadmap

Evidence-bounded states and live planning authorities

Status Authority

This page is an evergreen map, not a schedule or progress meter. Live scope, ownership, dependencies, and delivery state reside in the GitHub issue tracker and pull requests. Protected merge history is the authority for delivered changes. Dates, percentages, and promises are intentionally omitted because a hand-maintained forecast cannot establish readiness.

The repository’s content-review process is documented in content-development/:

State Contract

State	Meaning	What it does not mean
Available	A linked page, source, or program exists and can be inspected.	Peer reviewed, experimentally validated, or suitable for a decision.
Validated	A specific claim names its validation evidence, revision, population or model, and limits.	The whole page or neighboring claims inherit that result.
Experimental	Work is available for exploration but remains under qualification.	Stable API, cross-engine parity, human validation, or production readiness.
Planned	A tracking issue or explicit proposal exists, but the deliverable is not available.	Active work, a promised date, or guaranteed delivery.
Deprecated	Material remains only for compatibility or historical reference.	Recommended use.
Opinion	Editorial interpretation, priorities, or hypotheses.	Empirical evidence or organizational commitment.

Status is claim-specific. A readable book can be Available while some of its claims remain Experimental. A software engine can be Extended in its own support contract without making every analysis workflow validated.

Public Content Workstreams

The site-wide scientific trust review is tracked by #4021. Its child issues partition the rendered site without treating publication as review:

An open child issue means the corresponding review gate is not protected-closed. The generated Scientific Claim-Audit Inventory is the route-level status report; an inventory record is not itself scientific evidence.

Reading and Contribution Surfaces

Available: Article Index, The Physics of Golf, The Geometry of Motion, and the book series. Availability says only that the reader-facing material exists.
Experimental: Tangent-Space Series and Daydreams & Doodles, subject to their local scope notes.
Planned: Book Reviews; no review text is currently represented as delivered.
Available submission channels: Collaborate and Contact, without an acceptance or response-time promise.

UpstreamDrift Software Boundary

UpstreamDrift is the runtime and computational repository. This roadmap does not duplicate its live backlog. The capability statement reviewed here is pinned to protected UpstreamDrift commit 8cc236c6879e7535bb6bd15aecbe3396fb6dbb36:

Supported: MuJoCo, exercised by required pull-request CI.
Extended: Drake and Pinocchio, exercised by scheduled or targeted validation.
Experimental: OpenSim and MyoSuite, outside the required release gate.

See the pinned engine support contract and getting-started guide. A support tier is a software-test boundary, not a statement of biomechanical validity or cross-engine numerical equivalence.

How to Choose Work

Check the relevant issue and its dependencies.
Verify that no active lease or pull request already owns the same files.
State the evidence and falsifier before strengthening a public claim.
Change canonical sources test-first and use an ordinary protected pull request.
Treat the work as delivered only after protected merge and exact-main verification.

For corrections, open a GitHub issue. For private questions, use the Contact page.

Authority snapshot reviewed: 2026-08-29. Follow the linked repositories for live state.