docs(specs): resolve 004-16 spec number collision and edge-strengthening ambiguity - #6663
Merged
Merged
Conversation
github-actions
Bot
added
documentation
…ing ambiguity specs/004-memory/004-16-memory-type-aware-retrieval.md and 004-16-shadow-memory-safety.md both claimed the 004-16 slot. Renamed shadow-memory-safety to 004-19 and synced every rustdoc citation across the workspace (MAGE/TrajectoryRiskAccumulator/shadow-memory sites moved to spec 004-19; MemGuard/type-aware-retrieval sites stay at 004-16), including Obsidian wikilinks in 004-memory/spec.md and the cross-directory reference in 083-memory-write-consent-gate/spec.md. Also adds an authoritative statement in specs/004-memory/spec.md resolving which of three coexisting edge-strengthening mechanisms (A-MEM retrieval_count, Benna-Fusi dual-rate confidence, HeLa-Mem Hebbian weight) governs real graph traversal today, grounded in file:line citations against crates/zeph-memory/src/graph/. Closes #6636 Closes #6635
bug-ops
force-pushed
the
feat/issue-6636/004-16-spec-number-fix
branch
from
July 27, 2026 22:05
6e78ff5 to
9a7e513
Compare
bug-ops
enabled auto-merge (squash)
July 27, 2026 22:05
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.
Summary
specs/004-memory/004-16-memory-type-aware-retrieval.mdand004-16-shadow-memory-safety.mdboth claimed the004-16slot. Renamed shadow-memory-safety to004-19and synced every rustdoc citation across the workspace (26 sites incrates/: MAGE/TrajectoryRiskAccumulator/shadow-memory citations moved to spec004-19, MemGuard/type-aware-retrieval citations stay at004-16), plus the Obsidian wikilinks in004-memory/spec.mdand the cross-directory reference in083-memory-write-consent-gate/spec.md.specs/004-memory/spec.mdresolving which of three coexisting edge-strengthening mechanisms (A-MEMretrieval_countboost, Benna-Fusi dual-rateconfidence_fast/confidence_slow, HeLa-Mem Hebbianweight) actually governs graph traversal today, grounded in file:line citations againstcrates/zeph-memory/src/graph/.Closes #6636
Closes #6635
Test plan
cargo +nightly fmt --checkcargo clippy --profile ci --workspace --all-targets --features "desktop,ide,server,chat,pdf,scheduler,testing" -- -D warningsRUSTDOCFLAGS="--deny rustdoc::broken_intra_doc_links" cargo doc --no-deps --workspace --features "desktop,ide,server,chat,pdf,scheduler"(clean, no broken intra-doc links)gitleaks protect --staged --no-banner --redact(no leaks)004-16-shadow-memory-safetyreferences remaincrates/zeph-memory/src/graph/{types,retrieval,activation}.rs