Further Development
Inferred extensions of the framework's structure to domains outside its verified scope. Every page in this section states clearly what is inferred, what is verified, and what is out of scope. Nothing here carries the framework's verified status unless the page says so.
Pages here follow two formats. Single-topic notes that stay short are flat HTML files. Extensions that grow in depth receive their own folder with subpages.
Contents
| Page | What it covers | Status |
|---|---|---|
| Inferred high-particle-physics application | The framework's conic structure applied upward to particle scales. Three-generation 1/9 slices, the inferred particle inventory mapping, and the falsification invitation. | Inferred · open |
How Further Dev works
Every Further Dev page carries a status tag on every value and statement. The three tags used in the KB for verified work — Derived, Frame-Conditioned, Fitted — carry their usual meaning. Inferred content is stated in prose as inferred. If a Further Dev extension is later verified against empirical data, it moves into the main experiments or proofs sections and gets a canonical tag.
Further Dev content is not a claim that the framework asserts. It is an application of the framework's structure to a domain where the author's expertise does not extend. The framework's confidence stance applies: if it breaks under scrutiny, it wasn't real.
Cross-references. The verified experiments are at experiments/index.html. The framework's canonical values are at register.html.