A correction should repair the public claim without quietly rewriting the evidence trail that made the mistake visible.
Corrections: fix the claim, keep the trail
How Ptichi treats factual, source, translation and interface corrections, including the current reporting-channel limitation.
Ptichi treats factual errors, broken or mismatched sources, misleading evidence language, translation errors, inaccessible interaction and broken public links as correction-worthy problems.
What to identify
A useful correction report should identify:
- the canonical page URL and language;
- the sentence, field or interface state that is wrong;
- what is wrong with it;
- a source or reproducible observation when one is needed to establish the correction.
Do not send confidential work material, voice recordings, credentials or personal medical information to demonstrate a public-site problem.
How Ptichi should change a corrected page
The fix should update the smallest source of truth that owns the error. When the change affects evidence, the source/proof registry and the visible page must remain consistent. When it affects a localized representation, equivalent locale pages should be checked rather than assuming one wording change transfers cleanly.
A review date may change when the page is substantively re-reviewed. It should not be bumped merely to make content look fresh.
Material corrections
For a material factual or methodological correction, the page should make the new state clear and preserve enough repository history or public explanation to understand what changed. Tiny spelling fixes do not need a ceremonial errata entry.
The goal is traceability, not a museum of commas.
Current reporting limitation
Ptichi does not currently publish a private correction form or support inbox. The contact page is the canonical place to check current contact availability.
Until a real reporting route is published, this page defines the correction policy but does not pretend that a private submission channel exists. If a future channel is added, this page and the Agent-Ready Web Profile must change with it.
