Source Registry

The provenance layer for claims that hold up.

Sources explains which datasets, standards, papers, public records, and provider documents support ALCUB3 Research. The goal is not to overwhelm readers with citations; it is to make the evidence chain inspectable.

Different claims need different sources.

Platform

Provider docs + standards

Model provider documentation, MCP references, OpenTelemetry, OCI, NIST AI RMF, benchmark papers, and deployment standards.

Impact

Public records + satellite observation

EPA, USGS, NOAA, Drought.gov, NASA SWOT, Landsat, Sentinel-2, public water records, and partner-validated field sources.

Labs

Experiments + artifacts

Lab notes, benchmark runs, simulation artifacts, code repos, and controlled experiment outputs that may graduate into public claims.

Primary source groups currently used.

Source groupSupportsLimitTrack
ManyIH / PAC-Bench / c-CRABControl-plane, privacy-constrained coordination, and reliability claims under review.Synthesis is required before product claims.Platform
Provider documentationModel capability, tool interfaces, context handling, API and deployment behavior.Vendor docs change quickly.Platform
EPA / SDWIS / ECHOPublic drinking-water systems, violations, compliance records.Private wells and small systems are not fully covered.Impact
USGS / NOAA / WRIStreamflow, drought, flood, regional water stress, and environmental signals.Resolution and refresh cadence vary by geography.Impact
NASA SWOT / Landsat / Sentinel-2 / SAM 2Surface-water context, historical water-body change, optical observation, and segmentation baselines.Cloud cover, refresh cadence, resolution, and model uncertainty must be disclosed.Impact + Labs
ALCUB3 Labs artifactsRuntime experiments, simulation outputs, data pipelines, and graduation evidence.Requires review before public publication.Labs + Research

Sources do not automatically become claims.

  • Scope: every source gets a clear description of what it can and cannot support.
  • Freshness: sources are tagged as static, periodically refreshed, or actively monitored.
  • Transformation: if ALCUB3 estimates, scores, models, or normalizes source material, the method must be named.
  • Retirement: if a source becomes stale or unsupported, dependent claims must be downgraded or removed.