docs(research): publish verbatim-vs-derivative axis essay (#47) - #139
Closed
jphein wants to merge 2 commits into
Closed
docs(research): publish verbatim-vs-derivative axis essay (#47)#139jphein wants to merge 2 commits into
jphein wants to merge 2 commits into
Conversation
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
jphein
force-pushed
the
docs/verbatim-derivative-essay-47
branch
from
May 23, 2026 01:03
3743b3a to
e0892a1
Compare
Develops MemPalace's foundational architectural call — store verbatim, derive lazily, treat every derivative as replaceable — into a standalone reference piece, distinct from the README's compressed thesis section. Seven sections covering the architectural choice, why derive-on-write accumulates failure modes (lost nuance, classifier ceiling, irreversibility, locked-in derivation assumptions), the empirical 2026-04-25 → 2026-05-05 recovery-collection episode (210× token gap closed via structural change at the write layer), Anthropic's Managed Agents Dreams API (beta header dreaming-2026-04-21) as vendor-API ratification, operational implications, five named exceptions where the axis does NOT apply (explicit shelving, per-domain redaction, regulated-data classes, adversarial inputs, high-cardinality machine output), and a three-piece conclusion. Closes #47.
jphein
force-pushed
the
docs/verbatim-derivative-essay-47
branch
from
May 23, 2026 01:10
e0892a1 to
84a6fec
Compare
Collaborator
Author
|
Superseded by clean rebased PR. |
This was referenced May 23, 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.
Summary
Publishes
docs/research/verbatim-vs-derivative-axis.md— a standalone essay developing the foundational architectural call behind MemPalace's storage layer: store verbatim, derive lazily, treat every derivative as replaceable. Distinct surface from the README's compressed thesis section; the README's "What's next" already promised this writeup.Seven sections:
kind=content) closed by a single structural change at the write layer.dreaming-2026-04-21) as independent ratification of the axis. Input read-only, output a separate store, idempotent on inputs.~3300 words. Fork-changes.yaml entry + FORK_CHANGELOG.md + README's fork-change-queue table all regenerated.
Closes #47.
Test plan
scripts/render-docs.pyregenerates FORK_CHANGELOG.md + README.md cleanlyscripts/check-docs.sh— all four checks green (commit hashes resolve, FORK_CHANGELOG matches YAML, upstream PR states match, fork hash references resolve). Pre-existing 2538 vs 2641 test-count drift in README body text is out of scope for this PR.three-patterns-for-agent-memory.md,three-mempalace-consumers.md,adaptmem-orthogonal-layers.md,convergent-findings-kostadis-comparison.md,2026-05-05-verbatim-only-design.md, RFC 001, Dreams API canonical URL)