Engage Engagement Route Canonical engage, corrections, corpus-changelog, feedback, scrutiny, errata How to submit corrections, prior-art references, claim-boundary concerns, formalization concerns, publication errata, and private review feedback.
Engagement RouteCanonical

Corrections

How to submit corrections, prior-art references, claim-boundary concerns, formalization concerns, publication errata, and private review feedback.

Concrete is best
Name the page, result, registry object, theorem, module, publication, or route under review.
Meaning is traceable
Substantive corrections are handled through controlled corpus updates and public changelog entries.
Privacy respected
Private or sensitive feedback can be summarized publicly without exposing private correspondence.

Correction posture

Corrections and review are part of the research process. Meaningful changes to the corpus are logged publicly rather than silently absorbed.

Panta Rhei invites corrections, prior-art references, technical objections, formalization concerns, and domain-specific review. Public feedback is triaged, evaluated, and, where accepted, implemented through controlled corpus updates. Substantive changes are recorded in the Corpus Changelog.

Where To Send What

Concern Best route
Public question, critique, or prior-art suggestionGitHub Discussions
Broken link, route, metadata, or reproducible site defectSite Issues
Formalization concern or Lean-source mismatchTauLib Issues
PDF, checksum, timestamp, DOI, or artifact metadata concernPublications Issues
Concrete wording, metadata, documentation, or code fixPull Request to the relevant public repository
Private review, sensitive concern, institutional context, or media correctionEmail via Contact

What To Include

  • the exact public URL, registry ID, result ID, theorem, TauLib module, PDF, or publication route;
  • the correction or concern;
  • why it affects meaning, correctness, scope, priority, or interpretation;
  • references, reproduction steps, counterexamples, or suggested wording where available;
  • whether you are comfortable being named publicly if the correction is logged.

What Happens Next

Substantive feedback is triaged by domain, severity, affected surfaces, privacy constraints, and propagation needs. If accepted, the semantic correction is made in Corpus or the appropriate source repository, propagated outward, verified, and recorded in the Corpus Changelog when it affects public meaning.

GitHub Issues and Discussions are useful working surfaces. The curated public history of meaningful semantic changes is the Corpus Changelog.

Publication Errata

If a correction affects a released publication or monograph, the publication record may also receive an erratum. Publication-specific errata remain under Publication Errata and should link back to the Corpus Changelog when the correction affects the semantic corpus.

Save or share this page for inspection

Download a portable dossier, copy a reviewer note, or send this page to someone who can inspect it.

Email to expert