Amend rappid format to the Eternity standard (canonical)#47
Open
kody-w wants to merge 1 commit into
Open
Conversation
Propagate the 2026-06-01 Eternity lock back into the constitution: the canonical rappid identity is rappid:<slug>:<64hex> (full 256-bit SHA-256; the hash is the join key; the string is never re-versioned; structure lives in the rappid.json record). The 2026-04-30 v2-structured form (rappid:v2:kind:@pub/slug:hash@host) becomes a legacy + addressing form: read forever, extract the 64-hex hash, emit Eternity. Sites: Rappid.md (the canonical spec), CONSTITUTION Art. XXXIV.1, ESTATE_SPEC, door_address.py docstring. Reference impl: kody-w/rapp-egg-hub SPEC §2. No code/regex change (door_address still reads the v2 addressing form per the compatibility contract). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Propagates your 2026-06-01 Eternity lock back into the constitution — it had never been applied to
Rappid.md/CONSTITUTION/door_address.py, which were stuck on the superseded 2026-04-30 v2 form.Canonical now:
rappid:<slug>:<64hex>— birth-slug + full 256-bit SHA-256 (the hash is the identity + join key; the string is never re-versioned; all structure lives in therappid.jsonrecord). Reference impl:kody-w/rapp-egg-hubSPEC §2.v2-structured becomes legacy + addressing: read forever → extract the 64-hex hash → emit Eternity (per the compatibility contract).
door_address.pykeeps reading the v2 addressing form (docstring-only change, no regex/code touched).Sites:
Rappid.md(the canonical spec),CONSTITUTION Art. XXXIV.1,ESTATE_SPEC,door_address.py.🤖 Generated with Claude Code