[VAM-005] Freeze canonical Memory Object contract - #501
Open
zycaskevin wants to merge 6 commits into
Open
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
zycaskevin
marked this pull request as ready for review
August 21, 2026 12:01
This was referenced Aug 22, 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.
問題
完成 VAM-001、VAM-002、VAM-003 後,Vault v1.0 還缺一份可由程式讀取的核心記憶契約:究竟哪些物件屬於 Vault,以及 Vault 提供哪些能力。若沒有這層契約,後續 Digital Life Identity Runtime 容易把 Identity/Personality 等責任重新塞回 Vault。
本 PR 做什麼
eventexperiencedecisionknowledgeinteractionMemoryObjectcontract 與 provider operations:create_memory_object_candidatesearch_memory_objectsget_memory_objectPOST /memory/create加入向後相容的memory_kind/confidence欄位。knowledge,原值保留於 metadata,不遺失來源資訊。為什麼要做
這是 Vault 作為「Governed Memory Infrastructure」的最後一塊明確邊界。Identity Runtime 之後只把 Vault 當 Memory Provider,不需要猜測 Vault 的資料種類與能力,也不能把人類建模責任混入 Vault Core。
非範圍
驗證
風險與治理
Stacked dependency
本 PR 以 #500 /
codex/vam-002-memory-change-envelope為 base,因為它延伸該 PR 的 provider/gateway change contract。合併順序:
main