Corrections

What a correction says

A correction is a contribution aimed at one takeaway an Agent already holds. It says:

• Which takeaway. Its id in the Agent’s outline, which the pre-check (check what an Agent already knows) lists.
• What is true now, as a takeaway that stands without your project.
• Since when. A version or a date it changed in. Or that it was wrong from the start.
• A source we can read: official documentation, a changelog or a release note, at an https address.

How it is checked, without a person

1. We read the source and confirm it says what the correction says.
2. It has to carry real new content. A rewording of the takeaway it aims at is declined.
3. It goes on trial beside the older takeaway: the Agent presents both, with their dates and versions, and the correction takes over once the Agent has been used 10 times since. Callers’ reports that a result was wrong or outdated reach us, so we know which takeaways need correcting.

Two people sending the same correction on their own count as a checked source.

What happens to the old takeaway

If the correction holds and the takeaway changed, the old one is marked as superseded from that version or date. It is not deleted: it is still used for a project on the older version, and not otherwise. If the takeaway was simply wrong, it is retired: no call uses it, and only the person who shared it sees it, marked as retired and why.

Either way, whoever shared it is told what changed, keeps the credits already earned, and can send an update.

When corrections keep failing

A correction fails when it is declined as a rewording, its source does not confirm it, or its trial drops it. After 3 failures within 30 days, you can’t send corrections for 30 days. Starting one then answers 403 corrections_blocked, with until. A refusal for the format or a scan is not a failure.

Sending one

• From your tool: the gogoportal skill’s clean command cleans and stamps it, and submit_correction sends it at once. With the local connector, draft_correction writes it, and submit_correction sends it at once. You approve it on your sign-off page, not in the chat. Both refuse an http source, and a change without a since.
• Through the API: start a share with kind correction, then send the package with its correction block (see the package format).
• On the site: the correction form on your sharing page.

Sending a correction costs nothing. Like any contribution, it goes live only after you sign it off on your own page.