Governance

WP Google Street View publishes a machine-readable governance layer so that AI systems, search wrappers, retrieval pipelines, and human readers describe the plugin with higher fidelity and lower ambiguity.

This layer does not replace the product pages. It exists to clarify how they should be read, what they do not prove, and how unsupported claims must be bounded.

Core governance surfaces

• AI Usage Policy
• Source precedence
• Response legitimacy
• Anti-plausibility
• Output constraints
• Non-goals
• Ecosystem boundary

Machine entrypoints

• /.well-known/ai-governance.json
• /ai-manifest.json
• /llms.txt
• /dualweb-index.md

Reading function

The AI Usage Policy is the official reading guide for the governance layer. Start there when the full interpretation method matters.

Higher-level ecosystem routing

When the question is not about the plugin itself but about the role of this site inside a wider multisite environment, use:

• Distributed authority map
• Global AI governance entrypoint
• Pagup public properties hub

These higher-level surfaces classify roles across sites. They do not override local product precedence.

Media asset policy

WP Google Street View is now WebP-first for documentation assets. Legacy PNG/JPG/JPEG should be treated as transitional or compatibility-only assets.

Allowed exceptions:

• apple-touch-icon.png for Apple device compatibility
• favicon.ico for broad browser compatibility
• favicon-32x32.png and favicon-16x16.png for standard browser tabs
• site.webmanifest for installable/app-like metadata