Pilot design for the first observational test
What Tenuvio's first test will cover, how its catalog sample is chosen, and what it can and cannot show before a merchant authorizes a test.
Published
Protocol v0.1Kind: observationalStatus: planned, not yet run
The first test is a small pilot. Its job is to try the protocol on real product pages and find where the method breaks before any result is published. It uses public pages only, so it can show what assistants say about products but not why.
Design
| Catalog | One store, 10 products with visible prices and stock, most with a GTIN or MPN, at least one with variants and one sold elsewhere. |
|---|---|
| Prompts | One per family per product: 30 in all. |
| Repeats | 2 runs per prompt per assistant per run day (the full protocol uses 3), on 2 run days at least 7 days apart. |
| Assistants | Those whose terms allow the route used, checked against each vendor's documents before the first run. Not Perplexity's app. |
| Store named? | Only if it agrees. Otherwise described by category, country and size. |
Every prompt, capture and run record is published with the result, including empty and failed runs.
What it can’t show
Whether fixing a feed or a page changes the answers. That needs an authorized test, where Tenuvio can see the merchant’s feed and note when it changes. In an authorized test the merchant decides whether its name appears and sees the results before publication. It can correct facts about its own catalog but can’t change a score.