Skip to main content

SFDS Validation Checklist

  • Standard directory has a README.md that explains the standard's City Hall role.
  • Standard has a primary specification.
  • Scope and non-goals are explicit.
  • [StandardName].manifest.toml exists and describes the standard suite, not an adopter project.
  • Required suite artifacts are listed in the manifest.
  • Domain schemas or adopter manifest templates are separate from [StandardName].manifest.toml.
  • Adoption guide exists.
  • Validation checklist exists and distinguishes suite validation from adopter/domain validation.
  • Changelog exists.
  • Templates exist or are explicitly deferred.
  • Examples exist for candidate/reference maturity or are explicitly deferred for draft maturity.
  • Validator notes, scripts, or manual validation procedures are documented when compliance can be checked.
  • Maturity level is assigned.
  • Known gaps are recorded.
  • Existing mature standards preserve their authoritative domain rules and are normalized without unnecessary rewrites.
  • Stable or reference standards have no unresolved stability blockers from the SFDS primary specification.