Feedback and Contact

Useful feedback identifies the affected page or project concern, supplies enough evidence to understand it, and avoids sharing private or security-sensitive information through a public channel. A complete diagnosis is welcome but not required.

Feedback and contact routes

Purpose	Use this route	Include
Mathematical, physical, citation, convention, link, figure, or wording error	Email Jie Ren	Page URL, section, disputed passage or formula, expected correction, and a supporting source when available
New page, reference, exercise, figure, or maintenance improvement	Email Jie Ren	Proposed scope, canonical home, relevant plan, sources, and the checks performed
Editorial or policy concern	Editorial Standards, Citation, Reuse, and Privacy	The policy section affected, the concern, and the practical change requested
General project contact	Email Jie Ren	A short subject, the relevant route or project area, and whether a public reply is suitable

The Report Errors and Contribute guides explain how to prepare useful feedback. Send the report or proposal by email.

The contact address is shared with the parent QFT project. Do not send credentials, private keys, sensitive personal data, unpublished results, or embargoed material. For a security or rights concern, use email and describe only the category of the issue in the first message.

A compact report template

Subject:
Page or route:
Section or component:
What appears wrong or unclear:
Suggested correction or desired outcome:
Supporting source or reproduction steps:
May this report and reply be public? yes / no

For a formula or derivation, state the convention being used. For a broken route or interface problem, include the path, viewport or device class, and the action that exposed the problem. For a research-status concern, distinguish a new publication from independent confirmation or a change in expert consensus.

Sensitive reports

Do not place security vulnerabilities, private personal data, credentials, or unreleased material in a public report. Email [email protected] and identify only the category of a sensitive issue in the first message; wait for a safe follow-up channel before sending technical details.

What happens to a correction

A report should be triaged, reproduced when possible, and resolved or marked for follow-up. Corrections that materially change a formula, convention, or conclusion require a corresponding review and a correction record. The Changelog explains how changes are recorded.