docs: define scoped sequential resource IDs - #762
Open
behinddwalls wants to merge 3 commits into
Open
behinddwalls wants to merge 3 commits into
behinddwalls wants to merge 3 commits into
Conversation
behinddwalls
marked this pull request as ready for review
September 30, 2026 22:09
mnoah1
reviewed
Oct 1, 2026
behinddwalls
force-pushed
the
preetam/id-uri-rfc
branch
from
October 2, 2026 19:58
d08a8da to
343875c
Compare
behinddwalls
added this pull request to stack #771
October 2, 2026 20:48
behinddwalls
force-pushed
the
preetam/id-uri-rfc
branch
from
October 2, 2026 22:41
343875c to
d16ebc4
Compare
mnoah1
approved these changes
Oct 5, 2026
behinddwalls
force-pushed
the
preetam/id-uri-rfc
branch
from
October 5, 2026 19:05
d16ebc4 to
fcef650
Compare
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Oct 5, 2026
behinddwalls
force-pushed
the
preetam/id-uri-rfc
branch
2 times, most recently
from
October 5, 2026 23:21
d9fb34b to
c54b882
Compare
## Summary ### Why? Slash-delimited resource IDs repeat queue and resource-kind context that stores, APIs, and messages already carry separately, while making a single ID span multiple browser path segments. ### What? Define counter-generated resource IDs as positive numeric values scoped by owner domain, queue, and resource kind. Persist durable counter high-water marks, store numeric IDs directly under queue-leading keys, keep queue and kind out of the ID, and reserve prefixes such as `request.42` for presentation only. ## Test Plan ✅ `make fmt` ✅ `make lint-binary lint-license lint-message-id lint-queue-shard` ✅ `git diff --check`
## Summary ### Why? Resource identity should stay flexible at storage and API boundaries even when the current allocator produces sequential numbers. ### What? Define generated IDs as canonical decimal strings, keep resource and reference columns as VARCHAR, and limit integer storage to counter high-water marks.
## Summary ### Why? Resource identity should stay flexible at storage and API boundaries even when the current allocator produces sequential numbers. ### What? Define generated IDs as canonical decimal strings, keep resource and reference columns as VARCHAR, and limit integer storage to counter high-water marks. Replace the URLs and display examples with a before/after table showing base64url, percent-encoded, and readable queue-scoped routes; leave the rest of the proposal intact.
behinddwalls
force-pushed
the
preetam/id-uri-rfc
branch
from
October 5, 2026 23:40
c54b882 to
e6bfaa0
Compare
This branch has not been deployed
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
2 participants
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
Why?
Resource identity should stay flexible at storage and API boundaries even when the current allocator produces sequential numbers.
What?
Define generated IDs as canonical decimal strings, keep resource and reference columns as VARCHAR, and limit integer storage to counter high-water marks.
Replace the URLs and display examples with a before/after table showing base64url, percent-encoded, and readable queue-scoped routes; leave the rest of the proposal intact.
Stack