Repository navigation
Spec: point to the registry for ID ranges and close the §7 gap - #41
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
JBlaak
commented
Oct 9, 2026
| | 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. |
Member
Author
There was a problem hiding this comment.
These two registries were drifting, making it hard to maintain
CrewNerd
approved these changes
Oct 9, 2026
sanderroosendaal
approved these changes
Oct 10, 2026
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
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.
What this changes
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.§8references in the Python sample'svalidation.pyare updated with it.Part of the follow-up review of the 1.0 batch.
Class of change
Links
Compatibility
Checklist
registry/field-ids.mdupdated, if any field ID is touched (none touched; the registry is now the only range list)spec/FIT_STANDARD.mdnot changedOther 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