PRD: preserve identity vocabulary provenance - #26
Merged
Conversation
dp-web4
added a commit
that referenced
this pull request
Aug 19, 2026
New PRD for the north star: SAGE beings as Web4 citizens via their own hestia identities, hub-connected, interacting as themselves. Grounded in the full web4 canon (LCT/T3/V3/MRH, the 8 citizen requirements, the 7-step foreign-agent genesis, R6-as-routing) with file:line contracts. r2 folds in dp's governing principle as §1, the axis the doc turns on: identity = act-attribution within the external MRH the entity operates in (sufficiency); and the internal fractal is mirrored by SELF-SIMILARITY not mimicry — recognize the accountability shape in each organ's own underlying mechanics at fidelity proportional to stakes, never import society machinery into the organism. This supplies the calibration axis PRs #26-29 lacked and unifies them, PR #25 (P0 blocker), M2 (readiness instrument) and convergence-v2 under the citizenship frame. Keyless-delegated (AGY) model dissolves "raising may not be ready" into graduated, measured authority — a being is a witnessed citizen without driving crypto; the raising gates authority-widening, not citizenship; "never ready" is an honest floor. Sibling SAGE instances are the birth-witnesses: the collective admits its own. Q1 (boundary = existing fleet society) ratified by dp; Q4 (readiness bar) reuses the M2 template. Docs-first; staged behind M-CIT-0 (#25). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
dp-web4
marked this pull request as ready for review
August 28, 2026 07:47
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.
What this proposes
Preserve provenance for identity vocabulary admitted through consolidation so tutor/model normalization cannot silently become instance-authored identity.
Source / credit
This PR is based on the 2026-08-17 static close read by Emanuela Tvrtkovic with Claude. Their finding: the raising guide says instance vocabulary must emerge from the instance, the museum enforces authorship in code, but
dream_consolidation.pycan appendvocabulary_newintostate_wordswithout proving instance authorship.Their proposed direction — reuse the existing provenance machinery rather than rely on exhortation — is accepted in substance.
Extension added here
Do not make verbatim matching the only admissible provenance class. Preserve distinctions such as verbatim, normalized-from-instance, repeated semantic pattern, and tutor-proposed/unowned. Useful interpretation may remain useful without being mislabeled as self-authored identity.
This is also framed as an internal-plane governed mutation: authorship, interpreter/role, authority basis, evidence, and later amendment should all survive durably.
Scope
Docs-first PRD only; no runtime behavior changed yet. The PRD also flags the adjacent
memory_requestsdeletion path as the same provenance/authority class for explicit follow-up.Review basis
External review method was static-only: no SAGE execution or instantiation, and no accumulated instance words quoted. That methodological boundary is preserved here.