Roadmap

Phased development plan

The project advances through four phases, each gated by defined entry and exit criteria. No phase is entered before its predecessor meets exit criteria. Key risks are documented openly per phase.

Local Stabilization and Gating

Current

Establish a reliable local validation pipeline where all core tests pass deterministically and packages can be cleanly built and smoke-tested in isolation.

Entry criteria

›Core package source code exists with initial test coverage
›Basic release-pipeline infrastructure is in place

Exit criteria

›All internal validation suites passing without exception
›Automated local release pipeline active and green
›No blocking issues in local package build and smoke test
›Both TypeScript and Python implementations confirmed passing

Key risks

›Chiral pattern investigation may surface inconsistencies requiring framework revision
›Test coverage gaps in pro tier may delay gate clearance
›Pro-tier TS/Python parity issues may require additional remediation cycles

Controlled Early Access

Distribute packages to a small set of qualified external collaborators under a controlled confidentiality agreement. Gather structured feedback. Identify gaps in documentation and usability.

Entry criteria

›Phase 01 exit criteria fully met

Exit criteria

›1–3 qualified external pilots completed without blocking findings
›Documentation reviewed and validated by at least one pilot participant
›All known limitations documented in the public record
›No open critical issues from pilot feedback

Key risks

›External feedback may reveal conceptual gaps requiring framework-level revisions
›Documentation may prove insufficient for independent use without significant supplementation
›Finding and qualifying suitable pilot participants may take longer than expected

Public Package Release

Publish packages to npm and PyPI. Launch full public documentation. Open community engagement channels.

Entry criteria

›Phase 02 exit criteria fully met
›Independent reproducibility check completed by at least one external party

Exit criteria

›cpt-core and cpt-physics published to npm and PyPI respectively
›Public documentation site live with complete API reference
›Community support channel (e.g., GitHub Discussions) open and staffed
›Pro-tier packages staged for follow-on release after core stabilizes publicly

Key risks

›Unanticipated scale of public interest may outpace available support resources
›Novel runtime environments may surface validation issues not seen in controlled testing
›Community expectations may diverge from the project's current validation posture

Open Ecosystem and Public Deployment

Publish all packages to npm and PyPI under open licenses. Launch the community submission platform. Establish CPT Physics as the definitive public encyclopedia for A-GEOM framework physics.

Entry criteria

›Phase 03 stable — core packages publicly available with acceptable support load
›Community submission pipeline tested and operational

Exit criteria

›All packages available as open-source under CC-BY or equivalent
›Community platform accepting and publishing peer-reviewed submissions
›cpt-physics.com established as the canonical public reference

Key risks

›Community submissions may require significant curation resource
›Scope of framework may grow faster than documentation capacity

Learn more about the project’s mission, background, and operating principles.

About the Project →