VerooMethodology and example provenance
How Veroo’s public examples are recorded, reviewed, and kept honest.
Veroo’s recorded examples come from versioned public scenarios run through the real product in a local development environment. They are not customer records. The AI writes chat replies and proposes State updates; repository validation and human review check provenance, visible claims, scenario consistency, and current product boundaries before publication.
Source
Real local product flows, exported by the repository’s recording workflow.
Data
Purpose-built public scenarios, never private customer conversations.
Review
Automated validation plus human review of claims, boundaries, and page context.
1. Start with a versioned public scenario
A scenario defines the user messages and whether each turn is expected to change the saved State.
- Scenario files live with the marketing recording source in the repository.
- Names and circumstances are constructed for product demonstration, not copied from customers.
- The scenario states the planning or decision behavior the example is meant to test.
2. Run the scenario through the real local product
Each turn is sent through the same chat and State-update chain used by Veroo’s product flow.
- The recording captures model identifiers, prompt versions, messages, State versions, and change summaries.
- Answer-only turns remain visible when the saved State correctly does not change.
- Recordings are exported and validated by repository scripts rather than written by hand.
3. Separate what AI produced from what people reviewed
The product AI generates the recorded replies and State patches. Human review does not rewrite those recorded outputs.
- Reviewers check that the page description matches the recording and does not invent a product capability.
- Reviewers check sensitive boundaries such as medical, legal, financial, safety, booking, and real-time data claims.
- Page copy may summarize the recording, but the full Example page remains the source for the complete transcript and State progression.
4. Preserve versions and real update dates
A recording stores when it was captured and which prompt and model versions were used.
- Material recording changes require a new real run, export, and validation.
- Page `lastmod` changes only when the public content changes materially.
- Use Case pages show representative excerpts; complete transcripts and State changes stay on Example pages.
What these examples do not prove
A successful recording demonstrates one product flow. It is not a customer testimonial, benchmark, guarantee, or substitute for professional judgment.
- Examples do not prove accuracy for every input or situation.
- Veroo does not claim live bookings, maps, calendars, imports, active monitoring, or interactive checklist completion unless those capabilities are actually shipped.
- External facts, prices, schedules, laws, health guidance, and contractual terms still require current authoritative sources.
Report an error or outdated example
Send the page URL and the specific statement or recording turn that needs review. Veroo will verify the source and update the public page or rerun the scenario when necessary.