Proof
Proof and benchmarks
Volca earns trust through visible evidence: public examples, reproducible workflows, screenshots, and concrete proof points tied to real environmental data.
What you can check
- Concrete workflows using public or legally shareable data
- Search and inspection examples that can be repeated
- Screenshots showing what Volca exposes instead of hiding the data path
- Compatibility notes with explicit caveats where coverage is partial
Reproducible workflows
Step-by-step public examples help people see what Volca actually does in practice.
Benchmarks
Timing and runtime notes are most useful when they are tied to a real workflow question, dataset, and hardware context.
Inspectability proof
Screenshots, walkthroughs, and short explanations show how users inspect structures, mappings, and intermediate logic.
What strong proof looks like
Specific
Tied to a real question, a real dataset context, and a real workflow.
Reproducible
Repeatable when the data is public, or clearly marked when the data is licensed or restricted.
Honest
Shows assumptions, limits, and caveats instead of hiding them behind marketing language.
Current state
Search typo tolerance
Agribalyse search finds both spellings
In Agribalyse 3.2, searching for trellis and treillis returns the same two relevant activities. This is a small but concrete proof point: search is useful even when the user does not type the exact spelling found in the source dataset.
The public evidence is intentionally concrete and narrow. The clearest way to understand Volca today is through the live pages, current example workflows, and proof points that can be inspected directly.