Skip to content

[Vulcan] Clarify randomized UUIDv2 uniqueness limits - #36

Merged
iliaal merged 1 commit into
masterfrom
vulcan/uuid2-randomness-docs
Nov 19, 2026
Merged

iliaal merged 1 commit into
masterfrom
vulcan/uuid2-randomness-docs

Conversation

@iliaal

@iliaal iliaal commented Nov 19, 2026 •

Copy link
Copy Markdown
Owner

From Vulcan.

Correct the UUIDv2 “never repeat” claim and both matching C comments. Defaulted fields use randomness, not the v2 high-water mark. With a fixed node, only six random sequence bits survive the domain overwrite.

Validation on PHP 8.4.26: 1,000 fixed-node/default-sequence calls produced 64 unique UUIDs in one visible timestamp interval. V1/v6 controls each produced 1,000 unique values. Strict native build had zero warnings; 102 PHPTs passed, 3 environment skips (opcache/php-cgi); 35 guard tests passed. Independent review and merge-tree passed.

Sibling sweep: both v2 comments corrected; README/docs v1/v6 guarantees remain valid because those generators always use the shared monotonic timestamp. No generator change: GCC preprocessed base/head C compares byte-identically. Documentation only, so no new prose assertions or changelog entry (same policy as #35); no multi-PHP or sanitizer claim. Existing GUID documentation work is untouched.

Head: 148ec66c26e57a7b12d0f4cd0dcfed10e3f784c4. CI passed: all 36 Tests jobs in run 44482145063 and Check CHANGELOG.md in run 44482144783 succeeded. Peer recheck skipped, not counted as passed.

@iliaal
iliaal merged commit ed16093 into master Nov 19, 2026
40 checks passed
@iliaal
iliaal deleted the vulcan/uuid2-randomness-docs branch November 19, 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.

1 participant