About
Mission and operating principles
CPT Physics is a research and software project. This page explains the mission, how the project started, why the rollout is staged, and the principles that govern how findings are communicated.
Mission
Build it right before building it public
Build a computable, reproducible implementation of the Confined Photon Topology framework, and release it responsibly through a staged validation process that earns trust before claiming it.
Project background
CPT began as a private theoretical investigation into whether photon confinement topology could provide a coherent geometric basis for physical constants and nuclear structure predictions. The initial question was simple: can the observed value of the fine-structure constant be derived from a geometric constraint rather than measured and accepted as a brute fact?
As the theoretical work matured, a deliberate decision was made to build software alongside theory from the beginning—not as a later add-on, but as a first-class part of the research process. This means that no theoretical claim exists without a corresponding, testable software implementation. The two tracks are not independent; they are coupled by design.
The result is a dual-implementation codebase in TypeScript (primary) and Python (secondary), with a validation pipeline that gates every release. The website you are reading is the public-facing layer of this private validation work—not a marketing exercise, but an honest account of where the project stands.
Why a staged rollout
Physics frameworks are most credibly disclosed when they have passed reproducibility checks that others can verify. Rushed disclosure of incomplete or partially validated work creates noise, damages credibility, and wastes the time of potential collaborators who engage in good faith only to find the work is not yet ready for scrutiny.
The staged rollout is not secrecy—it is discipline. The distinction matters: secrecy withholds information indefinitely; discipline withholds it only until it meets a defined standard. The standard here is reproducibility, traceability, and documented limitations.
When Phase 03 (public package release) is reached, the disclosure will be complete and substantiated. Until then, controlled early access allows the project to gather structured feedback without exposing unfinished work to general scrutiny it is not yet prepared to withstand.
Research communication principles
Scope claims precisely
State what is known with precision, and explicitly avoid extending claims beyond validated results. Vague language that implies broader certainty than the evidence supports is treated as an error, not a rhetorical convenience.
Separate established from under-test
Every piece of public-facing content distinguishes between results that have cleared internal validation and those that remain under active investigation. This separation is not optional.
Respond to qualified interest
Early-access requests from researchers and developers with relevant backgrounds receive prompt, honest responses. We do not gatekeep access to maintain mystique—we gate it to avoid wasting collaborators' time with incomplete work.
Acknowledge limitations without apology
Known limitations are documented openly because acknowledging them is the only intellectually honest position. A limitation that is documented is a boundary the project is working within; an undocumented limitation is a credibility risk.