A feature you would like to see can gradually feel like a promised feature after several planning conversations. Keep a personal wish list separate from the project details you can currently verify.
Use two clearly labeled records
In the confirmed-information record, save the official source, the date checked, and the exact scope of the statement. In the wish list, describe what you hope to do and why it matters to your project. Leave an unanswered question open until an official source addresses it.
For example, confirmed support for cylindrical engraving does not answer every question about a particular object or a final accessory configuration. Record those as separate questions instead of extending a general capability statement into a specific compatibility promise.
Decide which unanswered questions matter
Mark a question as essential if its answer could change your decision. Keep optional preferences separate so they do not obscure the practical requirements of your project. Review official campaign details again before making a commitment, especially when a saved screenshot lacks a date or context.
This is a personal evaluation method for AntBelt G1 followers. It does not announce new features, a delivery schedule, or a change in campaign terms.
Browse related AntBelt project notes in /updates/.
Review current AntBelt G1 project details on Kickstarter: