Skip to main content

SFDS Changelog

1.0.0 - 2026-06-11

  • Promoted SFDS to the stable governing standard for City Hall standard formulation.
  • Defined the standard directory contract: README as role/index, primary specification as authority, and entity-named manifests as suite metadata.
  • Clarified suite validation versus adopter/domain validation.
  • Formalized stability blockers, maturity expectations, and the process for normalizing mature existing standards.
  • Confirmed DRS as the first reference implementation for the mature SFDS suite pattern.

0.1.2 - 2026-06-10

  • Applied the DRS-derived two-layer suite pattern across the City Hall standard set.
  • Added suite map examples for WGS, PPS, CTS, WDS, DDS, ATS, AAS, AAMHS, AADR, SESM, and NeonInk.
  • Standardized README, adoption, checklist, and manifest language for suite governance versus adopter-domain readiness.

0.1.1 - 2026-06-10

  • Defined the two-layer manifest model for standard suites and adopter-facing schemas/templates.
  • Recognized DRS as the first reference implementation for mature SFDS-governed suites.
  • Expanded validation guidance to distinguish suite validation from domain/adopter validation.
  • Updated templates to preserve the distinction between STANDARD.manifest.toml and adopter artifacts.

0.1.0 - 2026-06-10

  • Created initial SFDS documentation suite.
  • Defined required standard artifacts, maturity levels, conformance levels, and validation expectations.