A campaign answer can be accurate while addressing a different project from the one you intend to make. Keep your intended use beside the answer before treating it as a buying decision.
Write the use case in plain language
Describe the object type, intended design and the question you need answered. Avoid supplying guessed specifications. If a material identity or accessory requirement is unknown, say so directly.
Then record the source and date of the answer. Ask whether it addresses that object and workflow, or only describes a broader capability. For example, confirmation of cylindrical engraving support does not by itself identify which configuration suits an individual object.
Keep decisions conditional where evidence is missing
Use three fields in your private note: what the answer confirms, what remains unclear and what evidence would resolve it. A missing answer is a reason to retain the question, not to fill the gap with a similar-looking demonstration.
For AntBelt G1, consult the current Kickstarter project for applicable details. This article offers a backer research method and does not announce new specifications, included accessories or delivery commitments.
Explore related AntBelt preparation notes at /updates/.