A demonstration usually starts with the correct file already selected. For repeat projects, it is also useful to understand how someone would recognize that design among several similar saved versions later.
Request an ordinary retrieval example
Ask the demonstrator to explain which record identifies the intended artwork, which revision was approved and how the file is distinguished from an earlier draft. A visible filename may be sufficient for one workflow; another may need a separate job record. Evaluate the clarity of the process rather than assuming every system includes the same library features.
Include one realistic ambiguity in your question: two designs with the same name but different dates, for example. Ask what information resolves it. Do not assume a thumbnail reveals small text changes.
Compare what you can document
Keep notes on demonstrated behavior and questions that remain unanswered. Separate manual organization from functions actually shown in the software. A polished demonstration is not evidence of an unshown feature.
When considering AntBelt G1, confirm current software and configuration details through project sources. This buying checklist does not promise revision tracking, automatic backups or any particular file-management feature.
Explore related AntBelt preparation notes at /updates/.