Skip to content

Spec: point to the registry for ID ranges and close the §7 gap - #41

Merged
JBlaak merged 1 commit into
mainfrom
spec/registry-single-list
Oct 12, 2026
Merged

JBlaak merged 1 commit into
mainfrom
spec/registry-single-list

Conversation

@JBlaak

@JBlaak JBlaak commented Oct 9, 2026

Copy link
Copy Markdown
Member

What this changes

  • §9.1 range table removed. It disagreed with registry/field-ids.md: it listed 0–19 as one assigned block, even though 10 is session-level and 11–18 are oarlock fields, and it called the reserved curve ranges "Available" where the registry says "Reserved". Two hand-kept tables drift, so the spec now keeps the hard 0–254 limit and points to the registry as the single list of allocations.
  • Sections renumbered. §7 disappeared with the compliance levels (Spec: remove the compliance levels #26), which deliberately kept the numbers stable for open PRs. That batch is merged, so §8 Data Quality becomes §7 and §9 Field Registry becomes §8. The two §8 references in the Python sample's validation.py are updated with it.

Part of the follow-up review of the 1.0 batch.

Class of change

  • Editorial — no requirement changes
  • Substantive
  • Structural
  • Repository plumbing only

Links

  • Issue: —
  • Proposal: —

Compatibility

  • No
  • Yes

Checklist

  • One logical change: one table and the numbering around it
  • Paragraphs I did not change are not reflowed
  • registry/field-ids.md updated, if any field ID is touched (none touched; the registry is now the only range list)
  • Version number in spec/FIT_STANDARD.md not changed

Other open PRs that mention §8.x (#38, #40) refer to the old numbers in their descriptions. The text they change is the same.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Comment thread spec/FIT_STANDARD.md
| 93-199 | Extended standard fields | SlipThreshold (94), WashThreshold (95) and StrokeState (96) assigned; remainder available |
| 200-211 | Dual oarlock per-side | Assigned |
| 212-254 | Reserved for future extensions | Available |
Which IDs are assigned, reserved or available is listed in the [field ID registry](../registry/field-ids.md). It is the single list of allocations; no ID is used before it is recorded there.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These two registries were drifting, making it hard to maintain

@JBlaak
JBlaak merged commit 908a69a into main Oct 12, 2026
4 checks passed
@JBlaak
JBlaak deleted the spec/registry-single-list branch October 12, 2026 12:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants