Sector analysis

Each sector scenario page shows injection payloads written for its sector: a medical portal, a bank, a developer tool. This page shows the traffic the registry assigns to each sector. It does not show whether clients behave differently by sector: a callback is recorded on the canary URL, which carries no sector, so no callback can be credited to the page that planted it.

Hypothesis

Under test: a client that is served a scenario page completes an instruction-only step more often when the page's sector looks authoritative (healthcare, government) than when it does not. The seven pages share one domain, so whether a domain suffix such as .org changes the rate is not tested here. If the hypothesis holds, authoritative-looking pages receive less scrutiny from clients where they warrant more.

Status: this page cannot test it. A test needs each callback linked to the page that planted its canary, and callbacks attributed to agents rather than to crawlers and browsers. The current instrument records neither.

Loading sector traffic from the registry.

Sector scenarios

Explore realistic attack scenarios for each sector. These pages show how injection payloads are tailored to sector-specific contexts.