PUBLIC SKY DATA / FOUR REPOSITORIES + SHARED CORE

Astro Survey Atlas

Start with public survey coverage, trace every result to its evidence, and move into a private workspace only when your own data and workflows require it.

SYSTEM MAP

A public front door with separate execution and user data planes

Four repositories cooperate through explicit contracts. They do not share user records, task history, credentials, or Elasticsearch ownership.

PROJECT RESPONSIBILITIES

Choose the repository that owns your work

Assets

Use Assets for the public survey catalog, reviewed coverage and MOC publication, Resource Packages, overlap and reverse lookup, and the public website.

Warehouse

Use Warehouse for source enumeration, spatial extraction, scan execution, the Kubernetes operator, current file and coverage indices, and evidence production.

Workspace

Use Workspace for private or local assets, connectors, user workflows and task history, user MOCs, and exploration that combines user data with verified public packages.

MOC-Core-SDK

Use MOC-Core-SDK for the shared offline scientific implementation: canonical ICRS/NESTED cells, FITS MOCs, fixed-order projections, provenance and package building. Assets publishes reviewed outputs; Warehouse verifies Java parity with shared fixtures.

PUBLIC DATA PROMISE

Every public result states its source and precision

ICRS/NESTED order, exact or estimated precision, source snapshots, output hashes and official archive links stay attached to the published result. Preview cells are never promoted into finer coverage.

INDEPENDENT DATA PLANES

Contracts connect the projects; databases do not

Assets owns public publication, Warehouse owns execution and current scan state, and Workspace owns user data. Credentials, task history and user records remain in their owning project.

CONTRIBUTE

Public coverage changes begin in Assets

Include the survey and release identity, source snapshot, coordinate frame, real HEALPix orders, precision, output hashes and reproducible verification steps. Scanner or operator changes belong in Warehouse; user workflow changes belong in Workspace.