Record decision 32: resolve #54 (independent versioning, computed-at-cutover target)#56
Merged
Conversation
…cutover target) /brainstorm resolution of the traverse-registry 0.8.1 collision (entry 31): independent versioning going forward, real-publish version computed at #9's cutover execution time rather than hardcoded, traverse#627's atomic-removal staging (decision 29e) reaffirmed unchanged, 0.0.1 placeholder left un-yanked, no new spec drafted for stale FR-006. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
enricopiovesan
enabled auto-merge (squash)
July 18, 2026 15:46
3 tasks
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
/brainstormresolution of #54 (the traverse-registry 0.8.1 collisionrecorded in decision-log entry 31). Key outcomes:
traverse-registrygoes independently versioned post-extraction(not lockstep with
traverse's workspace version).execution time (next minor above whatever's actually published then),
not hardcoded as
0.8.0— a hardcoded number today would risk the samestaleness that just invalidated
0.8.0, sincetraversekeepspublishing
traverse-registryreleases until cutover.traverse#627's existing "removetraverse-registryfrompublish_crates.shatomically with the cutover PR" plan (decision 29e)is reaffirmed, not reopened — no standalone early fix was requested.
0.0.1placeholder stays un-yanked (harmless, no benefit totouching it).
FR-006— the decision logplus DoD text in Extract traverse-registry crate + governing specs from traverse into this repo #9/
traverse#627carry the correction; the substantiverequirement (unchanged pipeline) still holds, only the illustrative
number was wrong.
Full six-question brainstorm transcript (including a mid-session
self-correction after reading
traverse#627's already-independentdiscovery of the same collision) is in the entry itself.
Governing Spec
no-spec-needed (decision-log entry, not a governing spec change)
Project Item
Definition of Done
docs/decision-log.mdin the file's existing numbered styleValidation