Sustainable Catalyst Site Intelligence
Public Observatories
Public Observatories brings together the evidence, geography, events, country profiles, comparisons,
thematic dashboards, source records, briefing outputs, saved research paths, release history, and audit
records that make Site Intelligence inspectable as a public knowledge system.
Each observatory supports a different form of inquiry while preserving source identity, reporting period,
geographic scope, data state, methodology, limitations, lineage, and responsible-use boundaries. The
observatories remain connected without collapsing unlike evidence into one universal score.
to artifact to workspace. Integrity records can support change detection and reproducibility, but they do
not prove that a claim is factually correct.
Public observatory directory and trust layer
Auditable Public Observatory
Sources, methods, evidence, artifacts, releases, and digests
Integrity and lineage, not factual certification
Observatory directory
Eight connected public observatory environments
Each observatory answers a different public research question while sharing source records,
methodology conventions, export structures, data-state labels, and responsible-use rules.
Auditability
Auditable Public Observatory
Inspect evidence records, source–method–artifact lineage, release history, schema references,
verification levels, canonical digests, public audit packets, and integrity contracts.
Geospatial research
Earth Observation Studio
Explore supported satellite, map, environmental, infrastructure, and event layers with temporal
context, source records, spatial limits, and interpretation guidance.
Public events
Live Event Intelligence
Review supported earthquake, environmental, disaster, humanitarian, displacement, and conflict-event
records with source identity, event windows, geographic linkage, and delivery state.
Country research
Country Intelligence
Review a source-aware profile for one country across environmental, development, infrastructure,
humanitarian, human-security, economic, and institutional evidence.
Comparative research
Cross-Domain Comparison
Compare two country contexts while keeping units, definitions, reporting years, source methods,
data states, missing evidence, and compatibility rules visible.
Thematic analysis
Thematic Intelligence
Explore climate and environment, human development, human security, and infrastructure through
source-aware indicators, trends, events, methods, and exports.
Transparency
Source + Methodology Studio
Inspect public publishers, connector state, coverage, freshness, transformation rules, limitations,
feature usage, and the methods used throughout Site Intelligence.
Documentation
Public Briefing Studio
Turn selected evidence into a structured investigation manifest containing claims, sources,
limitations, gaps, notes, and portable JSON, CSV, HTML, or print-ready outputs.
Signature observatory layer
Auditable Public Observatory
The Auditable Public Observatory registers supported public research artifacts and connects them to
source records, methodology records, workspaces, release history, schema references, limitations, and
canonical integrity digests.
Evidence ledger
Registered public records
Supported evidence products receive stable identifiers, schema references, source links, method
links, verification levels, data states, limitations, and canonical digests.
Lineage graph
Source → method → artifact → workspace
Lineage records show which source and method records support a public artifact and where that
artifact appears in the application.
Canonical records
Stable representations for change detection
Canonical UTF-8 JSON, deterministic field ordering, normalized values, and explicit digest scope
support reproducible integrity checks.
Integrity digests
SHA-256 change detection
A canonical digest can show whether a supported payload changed relative to an expected digest while
excluding volatile fields where the verification contract requires it.
Release lineage
Track public product evolution
Release records connect versions, public features, schema changes, verification behavior, migration
notes, and known limitations across the development history.
Audit packets
Portable public verification records
Export structured packets containing artifact metadata, source and method links, limitations,
verification state, digest information, and release context.
Public artifact classes
What the observatory can register and trace
Site Intelligence treats public-facing records, dashboards, briefs, exports, source summaries, and
methodology products as artifacts that can be identified, versioned, linked, and reviewed.
Evidence records
Indicators, events, layers, and observations
Register supported public evidence with identifiers, source references, time and geography fields,
units, definitions, data states, and known limitations.
Country profiles
Structured single-country intelligence products
Connect profile outputs to their selected country, indicator records, source publishers, methods,
missing-data states, interpretation notes, and release version.
Comparison records
Two-country evidence and compatibility findings
Preserve country pairs, selected indicators, units, years, source identity, compatibility state,
missing values, event context, and comparison limitations.
Thematic dashboards
Cross-domain public evidence collections
Register supported thematic views while preserving the individual records, publishers, methods,
periods, units, and domain-specific interpretation boundaries.
Briefing manifests
Claims, sources, gaps, and limitations
Connect a public briefing to the evidence it cites, the questions it addresses, its source ledger,
unresolved gaps, limitations, and export format.
Saved research paths
Portable interface state and investigation context
Preserve supported public state such as country selection, comparison pair, active workspace,
filters, selected records, and continuation links.
Source records
Publisher, dataset, coverage, and delivery state
Register source identity, public URL, license context, geographic coverage, temporal coverage,
connector state, transformations, feature usage, and limitations.
Methodology records
Rules that shape public outputs
Document latest-value selection, country matching, trend construction, event deduplication,
comparison compatibility, caching, brief generation, and export behavior.
Verification levels
Describe what has been checked without overstating certainty
Verification labels should communicate the scope of the check. A structural or integrity check does
not establish factual truth, publisher authority, authenticity, completeness, or legal validity.
Registered
Artifact identity recorded
The artifact has a stable identifier, schema reference, artifact type, release context, and links to
available source and method records.
Schema checked
Required structure validated
The artifact conforms to the expected public schema or reports explicit validation failures and
unsupported fields.
Lineage linked
Support relationships recorded
The artifact is connected to the source, methodology, workspace, and release records that support
its public use.
Digest verified
Canonical payload matched an expected digest
The computed digest matches the expected value under the stated canonicalization rules and digest
scope.
Source reviewed
Publisher and coverage metadata inspected
Available publisher identity, source URL, license context, geographic and temporal coverage, and
known limitations have been reviewed.
Not fact certified
Integrity is not factual authority
No verification label should imply that Site Intelligence independently proved the truth,
completeness, authenticity, or legal effect of the underlying evidence.
Public lineage model
Follow the path from publisher to public output
The observatory makes support relationships visible so that a public artifact can be traced back
through the records and methods that shaped it.
-
01 · Publisher
Identify the public institution, organization, registry, or platform that provides the source record. -
02 · Source
Record dataset identity, public URL, license context, coverage, update behavior, and limitations. -
03 · Connector
Document retrieval, normalization, caching, fallback, failure isolation, and delivery state. -
04 · Method
Apply documented rules for matching, selection, transformation, comparison, trends, events, and exports. -
05 · Evidence
Produce a normalized public record with value, unit, period, geography, source, state, and limitations. -
06 · Artifact
Assemble the evidence into a profile, comparison, dashboard, map, brief, saved view, or export. -
07 · Workspace
Present the artifact in the public interface with interpretation guidance and responsible-use boundaries. -
08 · Audit
Register schema, lineage, release context, verification state, canonical record, and digest information.
Integrity boundary
What a matching digest can and cannot show
Canonical digests are useful for change detection and reproducibility. They must not be presented as
proof that the underlying data, claim, publisher, or interpretation is correct.
Can show
The canonical payload matched
Under the stated canonicalization rules and digest scope, the recomputed record matches the expected
digest.
Can show
A substantive record changed
When volatile fields are excluded correctly, a digest mismatch can indicate that a substantive field
changed relative to a prior canonical record.
Cannot show
The evidence is factually accurate
A digest verifies consistency with an expected representation. It does not independently validate
the truth of the underlying value or claim.
Cannot show
The publisher is authentic or authoritative
Publisher identity, institutional authority, source authenticity, and legal status require separate
verification outside the digest calculation.
Cannot show
The record is complete
A stable canonical payload may still omit important evidence, contain outdated information, or
reflect incomplete geographic, temporal, or population coverage.
Cannot show
The interpretation is justified
Correctly preserved evidence can still be misread, compared inappropriately, or used outside its
methodological and responsible-use boundaries.
Release ledger
Track how the public observatory system changes over time
Release records provide context for public features, schemas, connectors, verification behavior,
exports, accessibility, mobile hardening, and known limitations.
Release identity
Version, date, channel, and status
Each public release should identify the version, release channel, status, release date, major
capabilities, and compatibility expectations.
Feature lineage
Capabilities added, changed, or retired
Record new workspaces, connector expansions, export formats, observatory functions, reliability
changes, accessibility improvements, and removed behavior.
Schema lineage
Public record structure across versions
Document schema versions, field changes, compatibility rules, migrations, deprecated fields, and
changes affecting canonicalization or verification.
Known limitations
What remains unsupported or uncertain
Publish connector gaps, optional-feed limitations, incomplete coverage, stale-data risks, unresolved
compatibility issues, and areas requiring further review.
Verification changes
Digest and canonicalization behavior
Record changes to canonical field ordering, normalization, excluded volatile fields, digest scope,
verification contracts, and audit-packet structure.
Public documentation
Release notes and reproducibility records
Connect releases to public documentation, source registries, method notes, test evidence,
repositories, exported schemas, and migration guidance.
Public observatory workflow
Move from public question to inspectable research record
The observatories support a repeatable process for selecting evidence, reviewing source and method
context, documenting outputs, and preserving audit information.
-
01 · Ask
Define the country, place, comparison, theme, event, source, artifact, or public question. -
02 · Select
Choose the observatory workspace that matches the evidence type and research task. -
03 · Inspect
Review values, events, layers, dates, geography, units, source identity, and data state. -
04 · Trace
Follow each record into its source publisher, connector, method, feature usage, and limitations. -
05 · Document
Create a briefing manifest, save the research path, or export a portable evidence record. -
06 · Register
Connect supported outputs to artifact identity, schema, lineage, release context, and verification state. -
07 · Verify
Recompute canonical digests where supported and interpret the result within the stated verification boundary. -
08 · Continue
Move into Research Librarian, Workbench, Decision Studio, or the wider Research Library.
Platform connections
Connect observatory records to research, analysis, and decisions
Public observatory records can continue into supporting publications, calculations, models,
source-aware briefs, and reviewable decision-support workflows.
Research Librarian
Find supporting research
Continue from a country, event, theme, source, or artifact into Sustainable Catalyst articles,
references, repositories, methodology pages, and guided research paths.
Research Library
Deepen the knowledge context
Use article maps, publications, references, code companions, and knowledge architecture to interpret
public evidence beyond the observatory layer.
Workbench
Calculate, model, and validate
Extend supported evidence into transparent calculations, scenarios, graphs, sensitivity analysis,
validation workflows, and domain-specific analytical tools.
Decision Studio
Build a source-aware decision packet
Carry evidence, assumptions, tradeoffs, scenarios, calculations, claims, limitations, and audit
context into a reviewable decision-support workflow.
Responsible-use boundaries
Public observatories support inspection and documentation; they do not certify truth
Public Observatories makes evidence, methods, lineage, and integrity records easier to inspect. It does
not replace authoritative source verification, field investigation, current local records, or
qualified professional judgment.
A matching digest can show that a canonical payload matches an expected record. It does not prove
accuracy, authenticity, completeness, authority, or legal validity.
A visible source–method–artifact path explains support relationships. It does not mean that every
record, publisher, method, or interpretation is independently endorsed.
A registered artifact may still contain missing records, stale evidence, limited geographic
coverage, uncertain transformations, or unresolved methodological gaps.
Indicators, maps, events, and generated briefs may depend on reporting delays, model assumptions,
remote sensing, aggregation, incomplete coverage, and source-specific limitations.
Related values, events, geographic features, trends, and artifacts may support investigation without
establishing a causal mechanism.
Public Observatories does not provide legal, financial, medical, engineering, environmental
consulting, compliance, tax, investment, assurance, certification, emergency-response, or
safety-critical advice.
methodology, data state, lineage, verification scope, uncertainty, and known limitations before using
observatory records in consequential work.