A personal campaign change log can help an AntBelt G1 follower distinguish a newly noticed detail from a documented change. The key is saving the source and date before drawing a conclusion.
Record the detail in context
Choose only the questions that affect your project, such as the information available about a proposed workflow or package. For each entry, record the page address, the date you checked it, and the relevant wording or a private screenshot.
On the next visit, compare the same section. A different page may have a different purpose, so a shorter description elsewhere is not automatically evidence that a feature or condition changed.
Leave room for an unresolved comparison
Use a note such as “earlier wording not saved” when you lack the old source. If a difference is clear but its meaning is unclear, formulate one specific question and consult the current official project information.
This article is a method for organizing a follower's own notes. It does not announce a campaign change, new specification, or delivery commitment. Keep personal interpretations visibly separate from confirmed project statements, and use the current Kickstarter page for the details on which you intend to rely.
Browse related AntBelt project notes in /updates/.
Review current AntBelt G1 project details on Kickstarter: