A campaign answer is most useful when it identifies the configuration it describes. A statement about one setup should not automatically become an assumption about every available project option.
Add scope to your question
Record the option name exactly as it appears in the current official project information. Pair it with one question about your intended use and a link to the relevant campaign section. If the option name itself is unclear, ask for clarification instead of translating it into an assumed specification.
When an answer arrives, keep its date, source and stated scope together. Distinguish an explicit answer from your own interpretation. If an accessory or workflow is mentioned without a configuration reference, keep that dependency open until the project team clarifies it.
Recheck before making a decision
This is a planning method for reading project information, not a new specification or fulfillment announcement. The AntBelt G1 Kickstarter project remains the place to consult for project details and updates. A saved answer can help you revisit a decision, but it should not override newer official information that changes its scope.
Browse related planning notes in /updates/.