About this Site
A short operational guide to navigating, searching, inspecting, citing, and contacting the Observatory.
What this site is
The Panta Rhei Research Program is an independent open research program publishing a coherent theory of reality alongside the formal machinery used to check it. This site is the program’s public observatory — every monograph, paper, note, prediction, formalization, and dataset is reachable here, with the reasoning visible.
It is not a marketing page, not a closed peer-review repository, and not a wiki. It is an inspectable record of an active research program. The standard you should hold it to is the standard you hold a published research artifact to.
The eight lanes
Top-level navigation is organised into eight epistemic lanes. Each lane answers a different reader question:
- Discover — first orientation. Where is this program, what is it claiming, where do I start?
- Program — what kind of research program this is, how it is governed, who runs it.
- Agenda — what we are actively working on, what we have publicly committed to.
- Corpus — the construction itself. Mathematical structures, derivations, conceptual scaffolding.
- Results — discharged predictions and named results, with provenance.
- Verify — how each result is checked. Lean proofs, falsification packs, audit posture.
- Impact — where the program’s predictions touch the wider scientific landscape.
- Engage — how to read with us, write to us, or work with us. Includes the contact route.
Lanes are stable. URLs are stable. A link to a lane page is a citable surface.
How to choose a route
Pick the lane that matches what you are trying to do:
- “I want to understand what this program claims.” → start at Discover, then Corpus.
- “I want to check whether a specific prediction holds.” → start at Results, follow the link to the matching entry in Verify.
- “I am writing about this program and need verifiable facts.” → start at Media Kit → Journalist FAQ.
- “I want to read the books.” → start at Publications → individual book pages carry the Zenodo DOI + PDF.
- “I want to inspect the formal machinery.” → start at Verify → the TauLib section.
If none of those match, use Search (next section).
Search and quick access
Press / anywhere on the site (or Cmd/Ctrl+K) to open the search modal. The search is powered by Pagefind, which indexes the full site content at build time and runs entirely in your browser — nothing is sent to a server.
Before you type, the modal shows three short orientation lists:
- Quick access — direct chips to FAQ, Latest Publications, Research Log, Publications, Construction Spine, Verify, Cite, and Contact.
- Common starting points — four first-contact-shaped questions that route to the right page.
- Site help — links to this page and to the Colophon.
As soon as you start typing, the orientation lists collapse and Pagefind results appear in their place. The result list supports lane filter chips (All / Corpus / Results / Verify / Program) for narrowing.
If Pagefind misses what you are looking for, the modal also offers a one-click “Broader site search with Google” link that runs site:panta-rhei.site <your query>.
Page tools
Most pages carry a small set of page tools, visible either in the right rail (desktop) or in the “page tools” drawer (mobile):
- Share page — copy the page’s permalink to your clipboard.
- Copy citation — copy a pre-formatted citation string for the current page.
- Reviewer note — open a pre-filled email to the program with the page URL and a short context block, for sending a reviewer comment.
- Download PDF dossier — where available, a print-ready PDF version of the page.
- Download Markdown dossier — where available, the page’s source content as portable Markdown for offline reading or quoting.
- Related routes — a small list of adjacent surfaces (sibling pages, parent lane, cross-linked entries).
- Right-rail identifiers — on publication pages, the right rail also carries the publication’s DOI, ORCID(s), GitHub repository, and any other persistent identifiers (full pattern shipped in Wave 6).
Page tools are an inspection convenience, not a separate navigation system. Everything they expose is also reachable through the page itself.
PDF / Markdown dossiers
Every Monograph and most long-form research artifacts ship both as a rendered web page and as a portable dossier:
- PDF dossier — typeset for print and archival reading.
- Markdown dossier — the page’s source content as Markdown with stable headings and embedded math, suitable for offline reading, quoting, or re-rendering.
Dossier links appear in the right rail of pages that have them. If a page does not expose a dossier link, none has been generated for it yet — most non-publication pages do not need one.
Publications, Research Log, Changelog
Three near-adjacent surfaces, distinct in scope:
| Surface | Records | When to read it |
|---|---|---|
| Publications | Finished and citable works — Monographs, Hinge Papers, Research Notes, Dossiers. | When you want to read or cite a finished artifact. |
| Research Log | Dated public ledger of research activity — what was worked on, what landed, what was reframed. | When you want to know what the program has been doing recently. |
| Changelog | Site and release changes — what shipped on the site itself. | When you want to know what changed on this website. |
The Research Log is the public progress journal. The Changelog is the site’s release notes. The two intentionally do not overlap.
How to inspect a claim
Every named result in Results carries a verification panel that links to:
- the formal proof (Lean source in TauLib, with the exact theorem name and a permalink to the source line),
- the falsification pack describing what observation or measurement would refute the claim,
- the provenance trail — which monograph chapter or paper the claim originates from, and which corpus entries it depends on.
The Verify lane carries the cross-cutting machinery: the proof-assistant stack, the audit posture, the custom axiom inventory, and the release manifest. If you want a single page that explains how the program is checked, Verify · How to verify is that page.
How to cite the program
The full citation guidance is on the Cite page. The short version:
- Cite an individual Monograph by its Zenodo DOI (on the book’s individual page).
- Cite the program as a whole using the canonical URL
https://panta-rhei.site. - Cite a specific result, prediction, or note by its canonical page URL plus the named result identifier shown on the page.
- Cite TauLib by its repository URL plus the theorem name.
The Cite page also has BibTeX templates for each of the above.
How to contact or report corrections
Use the Contact page. Three routes:
- General correspondence — use the contact form.
- Reviewer note on a specific page — use the “Reviewer note” page tool, which pre-fills the page URL and a short context block.
- Erratum or correction — email the program directly (address on the Contact page). All errata are recorded openly in the Changelog and, where they affect a published artifact, linked from the artifact’s page.
We read every message. We do not always reply quickly, but corrections are taken seriously and recorded openly.
Colophon
The Colophon page records how the Observatory is built — the static-site stack, the search index, the metadata pipeline, the design system, and the site-facts snapshot from the most recent build.
If you want to understand the construction of this site (not the construction of the underlying program), the Colophon is the page for you.
Research Graph
The Research Graph page is the program’s authority and provenance layer. It records, for every Monograph, Paper, Note, person, repository, and dataset, which persistent identifiers (DOI, ORCID, OSF, GitHub, Wikidata) describe it.
If you want to understand how this program connects to the wider scholarly-identifier graph, or you want machine-readable provenance for citation tooling, the Research Graph is the page for you.