Proposal: Remove Versioning at the Bottom of the Constitution File

[brooke-hamilton]

Currently, the constitution file contains a version number at the bottom. However, these version numbers are not always applied correctly, likely due to the non-deterministic nature of LLMs.

Given that all Spec Kit outputs are stored in git (or another source control system), including version numbers and change logs inside the file itself is an anti-pattern. Git serves as the source of truth for version history and change logs, ensuring accurate and reliable tracking.

Proposal:

• Remove the versioning line(s) at the bottom of the constitution file.
• Rely solely on git or your SCM for versioning and change history.

Removing in-file versioning will eliminate redundant and potentially unreliable information and streamline file maintenance.

Example:
See the discussion in @radius-project/design-notes/pull/141 for context on improving constitution management and versioning practices.

[brooke-hamilton]

Also, I'm irritated that one of my PRs was delayed by having to fix a version number that doesn't matter. 😄

[mnriem]

While I am generally for less is more in this particular case the versioning at the bottom of the constitution file is there for human consumption. See it as reference that one would use to understand which (potentially shared) constitution an organization might be using for the project.

Note if you want option to disable this behavior please file an issue and if you can a PR that does just that