PUBLIC-RECORD DATA. Real organization name, phone & address from the NCES Common Core of Data (CCD). The contact-name, title, email & web-domain columns are empty disclosed seams — the source does not publish them and they are never fabricated. Scope is the Education (K-12) layer of SLED.
FForge Outcome Delivery
US SLED Contact Directory — Education layer

Outcome Contract

← Back to case study Browse the directory ↗

Outcome Contract — US SLED Contact Directory

Scope (in)

  • Segment: SLED → Education layer (public school districts / local education

agencies and state-operated education institutions).

  • Coverage: all 50 US states + the District of Columbia (51 jurisdictions).
  • Source: public-record only — NCES Common Core of Data (CCD) LEA Directory,

via the Urban Institute Education Data Portal (key-free JSON API).

  • Fields delivered (real): organization name, organization type, phone, street

address, city, ZIP, county, enrollment, school count, NCES leaid, and full provenance (source, source URL, dataset year, retrieval timestamp).

  • Deliverables: whole-file dataset/contacts.csv + contacts.json, per-state

files under dataset/by-state/, a self-contained browsable public/index.html, a verification suite, and a full proof package.

  • Grouping: by state (deterministic, canonical sort).

Scope (out — disclosed seams, never fabricated)

  • Named contact + title per organization (contactName, contactTitle) — empty.
  • Email address (email) — empty.
  • Web domain (domain) — empty.
  • State agencies, local/county/municipal governments, and higher-ed institutions

(the rest of SLED breadth) — deferred to v2.

Success criteria (MUST_PASS — see verify.mjs)

  1. All 51 jurisdictions present; ≥1 organization each.
  2. Every record has the real required fields; phone coverage ≥ 99%.
  3. The four seam fields are empty for every record (no fabrication).
  4. Dataset bytes match the sha256 recorded in the provenance manifest.
  5. One HTTP 200 source request logged per jurisdiction (51/51).
  6. Grouping partitions every record exactly once; CSV is consistent; ordering is

deterministic.

  1. Raw API responses retained for sample states and matching delivered counts.
  2. The standalone site builds and embeds the full directory.

Definition of done

Verification passes 17/17, the Frontier Layer permits delivery (gaps disclosed as approved capability seams), and the Proof Layer assigns the certification state, Evidence Grade, and Trust Score from the real evidence.