Spec: the snapshot artifact - #42
Merged
Merged
Conversation
- the top-level shape, plus listings, packs, index status and the game release list - the builder joins, filters and attaches, and copies every document verbatim, so this page never becomes a second copy of RFC 0031's field tables - no wall-clock field, so an unchanged index keeps its ETag and the backstop rebuild costs clients nothing - an unknown snapshot_version refuses the whole document, where an unknown spec_version renders one entry as unknown
MrJeranimo
approved these changes
Aug 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.
The client contract, written down.
spec/was reserved and empty, so this is its first document.RFC 0033 defines the snapshot as one merged JSON document and stops there, which leaves a client author inferring the fields from two RFCs.
Closes #39.