RFC: unify artifact family reads and registration - #1549
Draft
Zxf-xufeng wants to merge 2 commits into
Draft
Conversation
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.
Which issue or RFC does this PR close?\n\nDesign RFC for unified Topic Memory artifact reads and registry-driven Source/Artifact Family extensions.\n\n## Rationale for this change\n\nTopic Memory is already persisted as an artifact but is not accepted by the standard artifact list contract. Family definitions are also scattered across contract and runtime integration points. This RFC proposes one shared read contract and a registry-based extension model.\n\n## What changes are included in this PR?\n\n- Adds synchronized English and Chinese RFC documents.\n- Defines standard list/get/revision read support for
topic-memory.\n- Defines registry capabilities and OpenAPI/runtime consistency checks for future families.\n- Records alternatives, compatibility boundaries, and a test plan.\n\n## Are there any user-facing changes?\n\nNo implementation behavior changes. This is a design proposal.\n\n## How was this change tested?\n\n-git diff --check\n\n## AI usage statement\n\nCreated with OpenAI Codex assistance; the design and final scope are reviewed by the repository owner.