Corrections policy

What can be reported

We welcome reports of material factual errors, a citation that does not support the displayed claim, ticker or issuer mismatches, incorrect units or dates, duplicated or missing text caused by presentation, undisclosed material data limitations, unsafe investment language, privacy concerns, and content that may violate source rights.

A later price move, earnings result, filing, or news event does not by itself prove that a correctly dated report was erroneous when published. Those changes may justify new research rather than a correction.

How to request a review

Email kicoa24@gmail.com with the report URL, the exact claim or section, the reason you believe it is wrong, and a primary or otherwise reliable source when available. Do not send account passwords, payment-card data, brokerage credentials, or other unnecessary sensitive information.

Review standard

A report is compared with its stored run, snapshot, source artifacts, citation locators, content hashes, accepted claim lineage, and published payload. We distinguish source-data changes from model interpretation errors, and original research defects from later events.

The service does not currently promise a fixed response time, continuous post-publication monitoring, or acceptance of every requested change. A request may be declined when the supplied evidence does not establish a defect.

Versioned repair

Published report artifacts are not silently overwritten. The current persistence path supports an authorized repair as a newer report version derived from the prior report and authenticated workflow artifacts. The repair must use the same report and run identity, name the superseded version, carry authorization and lineage metadata, and pass the saved editorial authority and publication gate again.

The public catalog and sitemap select the absolute latest stored report version. If a newer version is incomplete or fails the required status checks, the report is not treated as an eligible current publication merely because an older version was complete.

Current transparency limits

Stocksembly does not yet provide a public correction-request form or a standalone public correction ledger. Version and lineage data are retained in the report system, but not every internal repair field is currently displayed to readers. This page will be updated if those surfaces change.