docs(notations): normalize spec_version to the quoted string form#13
Merged
Conversation
spec_version is typed as a string in CONTRACT.md, but the contract's own header example and the FGCA example file used the unquoted form `spec_version: 0.1` (a YAML float). Normalise both to `"0.1"` so the declared type and the literal agree across the family.
Match the string type declared in CONTRACT.md.
Match the string type declared in CONTRACT.md.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
spec_versionis typed as a string inCONTRACT.md, but the header block was written with the unquoted formspec_version: 0.1(a YAML float) in the contract's own example and in three notation specs / example files. This PR normalizes every occurrence to the quoted string form"0.1", so the declared type and the literal agree across the whole family.Files changed (one line each):
notations/CONTRACT.md— the canonical header example.notations/02-fgca.md— §"Top-level structure" inline example.notations/07-activities.md— §4 document-structure inline example.notations/examples/fgca/strategy-2026.fgca.transitrix.yaml— the one example file still on the unquoted form (all other example files already use"0.1").notations/13-process-blueprint.mdreceived the same fix on its own branch (PR #12).Scope
Pure normalization — exactly one line changed per file (
spec_version: 0.1→spec_version: "0.1"). No semantic, schema, or wording changes.Refs: vkgeorgia/strategy#25