Skip to main content
Every row in the Axiom Locus data catalog carries a uniform set of metadata columns called the APRS envelope (AI-Ready Public Record Standard). The envelope makes it possible to deduplicate records, sync incrementally, cite sources, join across datasets, and feed data directly into ML pipelines.

Envelope columns

All catalog tables include these columns:

Schema profiles

Each data domain uses a versioned schema profile in schema_version:

Domain-specific envelope extensions

Some data domains extend the base envelope with additional indexed columns that are critical for their query patterns. These columns appear alongside the ten standard envelope columns and are tracked in the envelope coverage dashboard. Both columns are indexed and included in the codex_compliance_summary view as h3_index_pct and mmsi_pct.

Record ID format

Every record_id follows a deterministic URN pattern so the same real-world record always maps to the same identifier:
For example:
  • urn:aprs:record:civic:granicus:12345 — a civic record ingested from Granicus
  • urn:aprs:record:maritime:vessel_visit:9434210:USLAX:7891 — a vessel visit keyed by IMO, port, and visit ID
  • urn:aprs:record:commodity:conab:soy:2025/26:09:MT — a crop report keyed by commodity, crop year, report month, and state

Access tiers

The acl_tier column controls data visibility:

Querying with envelope fields

You can use envelope columns to filter, sort, and join across any Locus table. For example, to find recently ingested records from a specific source:
To join records across tables by time window:

Compliance enforcement

Every change to collectors, edge functions, and migrations is validated against the APRS standard before it can be merged. The compliance pipeline runs three checks:
  1. Shape check — verifies that every catalog table with data has envelope coverage tracked. If a table has rows but no record_id population metrics, the change is blocked.
  2. Runtime compliance — samples the last 500 rows per table and validates them against nine APRS rules (valid URN format, non-null source_uri, valid timestamps, correct acl_tier, temporal ordering, and schema version format). Tables below 95% compliance with critical issues block the change.
  3. Static analysis — flags collector files that write to catalog tables without importing the envelope function. This check is advisory and posts a warning rather than blocking.
These checks run automatically — you do not need to trigger them. If you query Locus data through the API, every record you receive has passed these validations.

Coverage

The APRS envelope is present on all tables registered in the Locus data catalog. Envelope columns are populated automatically for new records at ingestion time. Historical records are being backfilled progressively — check modified_at to confirm a row has been fully normalized.

Commodity tables

The following commodity and logistics tables carry the APRS envelope with the aprs.commodity/1.0.0 or aprs.maritime/1.0.0 profile:

Transit and vacancy tables

The following tables carry the APRS envelope with the aprs.urban/1.0.0 profile: Every new row written to these tables includes record_id, source_system, source_uri, schema_version, occurred_at, ingested_at, and modified_at. Nightly backfill jobs continue to populate envelope fields on historical rows.