UPDATES

Updates

A running record of what's shipped — to the specification, the registry, and this site — in the order it happened. This is a changelog, not a roadmap: every entry below is something you can already read, use, or check against today.

Subscribe via RSSRead the specification

  1. Registry browser, machine catalog, and a reference page for every schema

    The registry is now a searchable, faceted index — filter by jurisdiction, category, and status, with the full filter state in the URL. Every published schema id resolves to a generated reference page at registry/{id} (field reference, verification record, version history, related schemas), and agents get a machine-readable catalog at registry/index.json.

  2. DS-82 worked example independently re-verified, advances to v2.0.0

    The DS-82 worked example — the schema behind this site's interview demo — has been independently re-verified against the live travel.state.gov source and the current fillable Form DS-82, under the adopted manual-source-review-v1 practice. The review found real drift (an eligibility-gate condition and the sex-marker enum), so the document advances with a MAJOR version bump to 2.0.0, targets spec v0.3, and its lifecycle status moves to verified. See the schema's own verification record for the method, date, and reviewer.

  3. Registry mirror advances to spec v0.1–v0.3

    This site's vendored registry mirror now tracks the canonical repository's current state (45 schemas across 8 jurisdictions, up from 24) instead of a fixed v0.1-only snapshot, and mirrors all three shipped meta-schemas (v0.1, v0.2, v0.3) so every entry's $schema URL actually resolves. All three lines are additive per VERSIONING.md, so nothing in the existing worked example changed at the time — the DS-82 worked example and the interview demo still targeted spec v0.1, until the independent re-verification above.

  4. About, Community, and Updates published

    This site's foundation pages are live: About explains who publishes the standard and how the specification changes; Community explains how to propose or improve a schema; and this page is the project's changelog, with an RSS feed so you don't have to check back manually.

  5. Site rebuilt around the specification

    Navigation now leads with the specification itself: a dedicated specification hub links its three chapters, alongside the registry, verification, and docs. The homepage is shorter, and the schema-driven interview moved to its own demo page.

  6. Live interview demo

    An agent can now walk a real registry schema end to end on this site: the interview demo drives a conversation against the DS-82 passport-renewal schema exactly as published in the registry, so you can watch a schema being consumed, not just read about it.

  7. Verification stated up front

    Every schema-reference page now opens with its verification status, last-verified date, and the source it was checked against, before any other detail. See how verification works.

  8. Specification reaches v0.3

    The open specification folded in seven accepted proposals covering field sensitivity classification, file constraints, schema maturity levels, richer conditional logic, documents as a first-class part of a schema, and a safety boundary for how a conforming agent may act on one — all additive; every v0.2 document is still a valid v0.3 document. At the time of this entry, this site's own worked example (DS-82) still targeted spec v0.1 — it has since advanced to v0.3 (see above); see spec/v0.3 in the open repository for the current specification text.

  9. Registry listing becomes self-updating

    The registry page is now generated directly from the published schema files instead of a hand-maintained list, so it can't drift out of sync with what the registry actually contains.

  10. Specification reaches v0.2

    An optional edition axis was added for forms that reissue every tax or award year — like an annual tax return — so a new year is modeled as a sibling edition, not a breaking version bump. See GSP-0005.

  11. Specification v0.1 accepted; first schemas published

    The founding document envelope — how a schema states its identity, source, verification, fields, and flow — was accepted as GSP-0001, and the first reference schemas were published against it.