Support support_page canonical Layer 2 — coverage questions for journalists and editors.
support pagecanonical

Journalist / Editor Due Diligence — FAQ

Layer 2 — coverage questions for journalists and editors.

Layer 2 · Journalist / Editor Due Diligence

Journalist/editor coverage questions: what to write, what to avoid, what to cite, which experts to call.

18 entries · last reviewed 2026-05-09 · version v0.1-pilot

Can a journalist write about this before expert review?

Yes, if the story is framed around inspectability, open-research infrastructure, and the public burden the program accepts — not around validated scientific truth.

Coverage before expert review is responsible only if status is clear. The story should be about public research form and inspection surfaces, not about acceptance of the scientific claims.

What is the responsible first story?

The responsible first story is the inspection architecture: what a serious high-scope research program exposes before asking anyone to believe it.

The first story should be architectural and epistemic, not triumphalist. The site is a case study in obligations, Corpus, Results, TauLib, Release Manifest, predictions, falsification, errata, and assessment protocols.

What should I avoid writing?

Do not write that the framework is proven, peer-reviewed, externally accepted, or that Lean proves the physical claims.

Avoid collapsing status boundaries. Do not present internal results as externally accepted conclusions, do not call it a theory of everything, and do not treat Lean compilation as empirical truth.

Are external institutions endorsing Panta Rhei?

No. External organizations and references are cited as context, standards, or background, not as endorsement, validation, review, or acceptance.

Citations to open-science, standards, philosophy, repository, or reporting resources are contextual. They must not be converted into institutional endorsement.

Is the work peer-reviewed or covered elsewhere?

Not yet by traditional journals; the program is published openly for scrutiny.

The work is independent open research, not settled peer-reviewed consensus. If there is no current third-party press or review, say so and frame the piece as a first-contact inspection story.

How should I describe the work accurately?

Use: “Panta Rhei is an independent open research program dedicated to building a coherent theory of reality, published as an inspectable research observatory.”

This phrasing identifies the scope, independence, public-release form, and inspection posture without claiming validation. Use Panta Rhei Research Program for the program and Category τ for the framework where appropriate.

What should I link first?

Link the Journalist FAQ or Media Kit for framing, then Verify or the Release Manifest for inspection status, and only then route readers to specific Results or papers.

Do not link only a striking result without status context. A good link stack starts with framing and verification, then points to the specific Corpus, Result, paper, Registry, or TauLib artifact.

How do I cite a specific result, paper, or registry object?

Cite books and papers through DOI/citation pages, cite results by stable URL and status label, and cite registry objects by stable object ID and permalink.

Use the publication artifact for citable works, stable Result URLs for claims, Registry IDs for atomic objects, and the Release Manifest/TauLib for formalization claims.

What are the most third-party-checkable artifacts?

TauLib, the Release Manifest, Registry, Results status pages, prediction timing, falsification pack, errata, research papers, and assessment protocols.

Checkability comes from public source, stable IDs, explicit status, reproducible builds, named falsification routes, and correction behavior. These artifacts are the best first links for experts.

What should an editor ask before assigning a story?

Ask whether the piece is about inspection architecture or validated science, what claims are being checked, which experts will be called, and which status labels must be preserved.

A responsible assignment picks a bounded path: inspection architecture, master constant, TauLib formalization, prediction timing, falsification surface, or a domain-specific claim. Avoid a broad “new theory proves X” pitch.

Which experts should I call first?

Call a formal-methods reviewer for TauLib, a mathematician for kernel hinges, a physicist for prediction bridges, and a philosopher of science for scope and framing.

Match experts to claim layers. Formal build, mathematical hinge, physics bridge, prior art, philosophical interpretation, life-sector adequacy, and impact translation require different reviewers.

What should I ask outside experts?

Ask whether the artifact is inspectable, whether the specific claim is well-typed, whether the derivation is forced, whether prior art overlaps, and what would falsify it.

Do not ask an expert to judge the entire program in one quote. Ask them which artifact they inspected, what layer they can judge, and what would change their assessment.

How should I cover predictions and falsification claims?

Cover them as public accountability commitments, not as validated confirmations. Preserve timing categories, precision tiers, and failure conditions.

Some prediction records are post-dictions, some tension-side commitments, and some forward tests. A responsible piece links prediction timing and falsification surfaces and does not imply numerical agreement validates the whole framework.

How should I cover public-good or impact claims?

Cover them as conditional impact pathways, not as deployed products, institutional adoption, or proven applications.

Impact pages map what could matter if upstream Results survive review, translation, and uptake. Coverage should name upstream dependencies, translation assumptions, required domain validation, and governance risks.

What funding or conflicts should I disclose?

Disclose that the program is independently authored and self-funded, with no institutional funder, grant sponsor, or corporate backer stated on the site.

Report funding status neutrally. Independence may explain the publication route, but it is not evidence that the claims are correct.

Can I quote or interview the authors?

Yes. The Journalist FAQ says direct quotes, interviews, podcasts, and background briefings are available on request through the listed media contact route.

Journalists should include outlet, angle, audience, format, length, and deadline. Current public material has no embargo unless the authors specify otherwise for drafts or upcoming releases.

What if I find an error?

Report it. Corrections, errata, and bounded critique are part of the research architecture, not an embarrassment.

Errors may include broken proofs, stale numerical values, wrong scope labels, citation issues, broken links, or misleading framing. Report before publication where possible and describe unresolved discrepancies clearly.

What if outside experts disagree?

Report the disagreement by claim layer: form, formalization, bridge adequacy, prior art, empirical prediction, or interpretation.

A useful article does not flatten disagreement into one yes/no verdict. It identifies the layer being disputed, the artifact inspected, the expert domain, and remaining uncertainty.