Site Intelligence
Source Methodology
A public-safe methodology page for source health, connector assumptions, public/private boundaries, fallback behavior, dashboard limits, and responsible interpretation across Site Intelligence.
This page explains how Site Intelligence treats public sources, external data connectors, cached summaries, fallback values, dashboard labels, and review boundaries. It is designed for transparency and interpretation rather than professional assurance, certification, compliance, or audit reporting.
What it explains →
Source rules →
All Site Intelligence dashboards →
Site Intelligence →
Public methodology module
Source Methodology dashboard
This module summarizes the public-facing source methodology for Site Intelligence, including connector assumptions, source-health context, fallback behavior, dashboard boundaries, and interpretation limits.
Public Source Methodology
Source Notes, Fallbacks, and Public Boundaries
Loading public source methodology…
Methodology scope
What this page explains
Source Methodology explains how Site Intelligence turns external sources, public metadata, dashboard summaries, and review notes into readable public context.
Source health
Availability, status, and reliability
Source-health context helps explain whether a dashboard depends on live data, cached summaries, public metadata, fallback values, or limited source availability.
Fallback behavior
Stable public display
Public dashboards may use stable fallback summaries when external APIs are slow, unavailable, rate-limited, incomplete, or unsuitable for public display.
Interpretive limits
Context before claims
Site Intelligence presents public source context cautiously. Dashboard outputs should be read as orientation, not as complete, certified, live, or professionally validated findings.
Source rules
How Site Intelligence handles sources
Public dashboards are designed to be readable, stable, and transparent. That requires separating live source availability from public interpretation, private diagnostics, and professional claims.
Public-safe summaries
Show context, not raw payloads
Public pages summarize source context without exposing credentials, raw API responses, private diagnostics, admin endpoints, unreleased reports, or internal notes.
Conservative language
Avoid overstated claims
Dashboard copy should avoid implying certainty, completeness, professional validation, regulatory authority, certification, or real-time accuracy when those claims are not warranted.
Source separation
Public and private stay distinct
Public dashboards explain what can be responsibly shown. Private analytics, diagnostic reports, connector logs, and admin review tools remain separate.
Interpretation framework
How to read Site Intelligence dashboards
Each public dashboard should be read through source status, scope, method, public/private boundaries, and professional-use limits.
- IdentifyWhat the dashboard is summarizing
- CheckWhether sources are live, cached, limited, or fallback
- ReadLabels, notes, and boundaries before claims
- SeparatePublic summaries from private diagnostics
- AssumeExternal sources may be delayed or incomplete
- AvoidProfessional, regulatory, or certification claims
- ReviewDashboard language before public reuse
- ImproveSource coverage and clarity over time
Public/private boundary
What public dashboards exclude
Site Intelligence public pages are intentionally limited. They are designed to communicate public context without turning the site into a raw analytics console or exposing sensitive operational information.
Excluded
Private analytics and diagnostics
GA4 details, Search Console query data, raw crawl data, credentials, backend logs, admin diagnostics, and unreleased reports are not part of public dashboard pages.
Excluded
Professional determinations
Public dashboards do not provide legal, financial, medical, engineering, compliance, ESG, SDG, environmental, investment, tax, or safety-critical determinations.
Excluded
Completeness guarantees
Public summaries do not guarantee full coverage, real-time accuracy, complete source availability, exhaustive topic representation, or validated data quality.
Boundaries
Methodology, not assurance
Source Methodology is a public explanation layer. It should not be read as a professional audit, assurance report, regulatory filing, data-quality certification, or compliance review.
This page does not certify data quality, ESG performance, SDG alignment, regulatory compliance, environmental status, source accuracy, or dashboard completeness.
Methodology notes do not replace legal, financial, medical, engineering, environmental, tax, investment, compliance, safety, or professional review.
Public methodology explains source handling without exposing credentials, private analytics, API payloads, backend logs, admin diagnostics, or internal reports.