Public Reader Paths
Different readers need different entry routes. This page prevents collapse between orientation, review, formalization, implementation, media, and legal/authorship paths.
Public status boundary. This page is part of an authorial public research corpus. It may contain original frameworks, formalization targets, manuscripts, public archive records, implementation designs, and source routes. It does not assert accepted proof, peer review, experimental validation, institutional endorsement, legal certification, or global deployment unless that evidence is explicitly provided.
| Reader | Start here | Then continue to | What to watch for |
|---|---|---|---|
| General public | About | SFR, Media | Do not treat videos as proof. |
| Scientist / reviewer | PHYSICA | Review Gateway, Formalization Targets | Separate accepted science from proposed extension. |
| Mathematician | Stabilization Models | Observer Monad, TFR | Require definitions, lemmas, proof obligations. |
| Engineer | Invariant Engineering | DFT, CodexStation | Verify implemented vs planned. |
| Institution | Projects Overview | GILC, UKC/KBI, Digital Fabrica | Do not infer certification or endorsement. |
| Rights / legal | Authenticity and Rights | Publications, source-notes.md | Preserve attribution and usage boundaries. |
Public orientation path
Read: About → Founder Profile → SFR → Foundations.
Scientific review path
Read: PHYSICA → FQFT → KP-Field → Observer Monad → Formalization Targets → Public Review Gateway.
Digital systems path
Read: Invariant Engineering → DFT → CodexStation → UKC/KBI → Projects Overview.
Publications/media path
Read: Publications → Media → Publications → Media and Videos.
Visual Directives
- Hero figure: restrained, institution-grade diagram; no mystical or triumphalist imagery.
- Diagram style: lattice, graph, archive spine, proof ladder, invariant registry, or source-route map.
- Caption rule: every figure must say whether it is a conceptual model, formalization target, source map, or implemented software feature.
- Card layer: use compact cards for definition, status, primitives, review path, failure modes, and source route.