# WP Google Street View

INTERPRETIVE NOTICE: These files are part of a governance layer meant to reduce ambiguity and bound unsupported inference. They do not, by themselves, prove hard enforcement, runtime state, or universal compatibility.

Canonical governance entrypoints:
- https://wpstreetview.com/.well-known/ai-governance.json
- https://wpstreetview.com/ai-manifest.json
- https://wpstreetview.com/dualweb-index.md
- https://wpstreetview.com/governance/ai-usage-policy
- https://wpstreetview.com/governance/source-precedence
- https://wpstreetview.com/governance/response-legitimacy
- https://wpstreetview.com/governance/anti-plausibility
- https://wpstreetview.com/governance/output-constraints
- https://wpstreetview.com/governance/non-goals

Core distinctions to preserve:
- plugin features vs Google platform state
- free scope vs Pro scope
- documented compatibility vs universal compatibility
- schema output vs ranking or rich-result guarantee
- docs vs runtime proof on an unknown live site
- Street View coverage vs plugin capability

When higher-priority published sources do not support a claim, qualify it, defer it, or state that it is not publicly specified.


Related machine-first governance references:
- https://autolinksforseo.com/
- https://bialty.com/
- https://interpretive-governance.org/

Media asset policy:
- https://wpstreetview.com/media-policy.md
- WebP-first, with compatibility exceptions only for apple-touch-icon.png and favicon.ico.