SFDS / template

Standard-Specification.md

Turn a repeatable practice into an explicit standard specification.

DownloadView source file Read related standard

Useful when

I want to formalize a repeatable practice.

Choose your situation

What you should change

Replace purpose, scope, requirements and conformance boundaries.

Use only the parts that help. These are starting points, not rigid requirements.

View resource

# [Standard Name]

## Status

[Maturity] v[Version].

## Scope

Describe what this standard governs.

## Does Not Govern

Describe what this standard intentionally leaves to other standards or projects.

## City Hall Role

Describe how this standard fits the City Hall system and which adjacent standards it depends on or complements.

## Required Behaviors or Artifacts

- `README.md` as the role statement and document map.
- This primary specification as the authoritative ruleset.
- `[StandardName].manifest.toml` for the standard suite.
- Domain schemas or adopter manifest templates, when applicable.
- Templates.
- Examples.
- Adoption guide.
- Validation checklist.
- Changelog.

## Manifest Model

Describe the difference between the standard-suite manifest and any adopter-facing manifests or schemas.

## Adoption

Describe who adopts this standard and which files they copy, create, fill in, or validate.

## Validation

Describe how suite conformance is checked.
Describe how adopter or domain conformance is checked, if different.

## Compatibility Policy

Describe which changes are allowed in minor versions and which require a major version.

## Adoption Blockers

List conditions that block stable adoption of this standard or release of governed artifacts.

Related resources

SFDS / template / Quick win

StandardName.manifest.toml

Describe a standard suite, version, maturity and supporting files.

View & adapt Download

SFDS / checklist / Quick win

Validation-Checklist.md

Review a standard suite for structure and adoption guidance.

View & adapt Download