Data contract and provenance sample

All delivery samples

Shows field definitions, source ownership, freshness and reconciliation rules.

Synthetic data-engineering sample. Version 1.0, published November 7, 2026. Authored by Newton & Carter for demonstration; no client, participant or measured outcome is implied.

Newton & CarterDefine what ready means.
01

Scope

02

Build

03

Review

Illustrative planning diagram. Scope and acceptance are agreed per engagement.

Inspect the artifact

The complete, machine-readable source is below. Use it to discuss the structure and acceptance of an engagement.

Download the versioned JSON source →

{
  "version": "1.0",
  "dataset": "Fictional shelter availability",
  "sourceOwner": "Example operations team",
  "fields": {
    "location_id": "Stable source identifier",
    "capacity": "Nonnegative integer; people",
    "updated_at": "ISO timestamp supplied by source owner"
  },
  "validation": [
    "Reject duplicate location IDs",
    "Flag missing timestamps",
    "Flag available spaces greater than capacity"
  ],
  "freshness": "Agree a freshness window with the owner; show stale data explicitly.",
  "reconciliation": "Retain source count, accepted count and rejected records for each import.",
  "limits": "Synthetic planning sample; no live emergency feed."
}

Explore the related engagement scopes →