
Programme structure
Visibility Monitor methodology
The planned sampling, run and annotation rules published before any result.
Read the protocolResearch library
Methods are published so readers can see what was planned, what was observed, what was excluded and what remains uncertain.

The library uses stable records for programmes, waves, prompt runs, annotations and public aggregate tables. A download may supplement the HTML record; it never replaces a readable explanation of scope, units, denominator and limitations.
The Visibility Monitor is a planned research programme. Its 12 prompts, two services, three repetitions and 20-brand panel are declared design inputs. No pilot run or research result is presented here.
Every public record should identify the research question, scope, study and wave IDs, protocol version, sampling frame, collection period, units, denominators, exclusions, review state and material limitations. Claims must link back to the method and permitted evidence. An update should revise the affected note and asset version without erasing the earlier lineage.
Read the protocol first, then inspect the example record to understand the field structure. When genuine results exist, compare only matched prompt, service and panel versions. Treat downloads as supplements to the accessible HTML table, and never interpret a missing or failed record as a negative brand observation.

Programme structure
The planned sampling, run and annotation rules published before any result.
Read the protocolSynthetic fixture
A small fictional record showing fields and states. It is not research data.
Inspect the exampleEditorial standard
Material research updates revise notes and linked assets without erasing history.
Read the editorial policy
Research context
Separate appearances, citations and verified claims without turning a sample into market share.
Read the guide