A useful project answer should show what is known, what is still being checked, and where the final detail will appear. That structure is more helpful than expanding an uncertain answer into a promise.
Start with the narrow question
Restate the question without adding assumptions. Link the answer to current prototype evidence or published project information when available. If the answer depends on final configuration, testing, or campaign terms, label that dependency clearly.
Keep the correction path open
Date the note and identify where readers should look for the latest version. If the evidence changes, update the project information rather than leaving two conflicting answers in circulation.
The /updates/ archive collects practical AntBelt project notes; Kickstarter remains the place to review current campaign information.
Follow the AntBelt G1 project and review the latest details on Kickstarter: