Corrections

What should be corrected

Corrections cover factual errors, descriptions that no longer match the app, broken or misleading source links, incomplete attribution, unclear rights statements, accessibility barriers, unsafe framing, and missing AI disclosure.

A disagreement with an interpretive prompt may instead lead to clearer framing or source context. The project does not present one card meaning as universally authoritative.

Review and record

• Check the report against current code, tests, provenance snapshots, and a primary source where one exists.
• Correct the source content and regenerate the static page rather than patching built HTML.
• Update the affected page’s review date. Record material public-facing corrections in the changelog.
• Do not remove attribution or weaken a rights restriction while a source question remains unresolved.

Current reporting gap

The project does not yet publish a correction email address, issue tracker, or in-product report form. Until the owner chooses a durable public contact route, this page documents the review standard but cannot offer a public submission channel.