Continuous 3GPP ingestion
Automation status
Atlas watches official 3GPP source fingerprints, triggers durable refresh jobs, ingests canonical databases and then updates meeting, release and lineage evidence automatically.
Two health layers: canonical ingestion determines whether Atlas is operational. Live meeting TDocs are faster pre-database evidence and are monitored separately so a changing meeting-page layout cannot falsely make canonical ingestion look down.
Official source watcher
What Atlas is watching
Trigger → ingest
Refresh latency
Canonical datasets
Latest imports
Automation contract
How updates happen
The watcher reacts to changes in official source fingerprints. Meeting references and live TDocs accelerate interpretation and provide an audit trail, but the canonical CR/spec/Work Plan databases remain the source of post-meeting truth.
Pre-database SLO
Live meeting feeds
Recent standards activity