Repository navigation
docs(rfc): propose Artifact plugin framework - #2175
Conversation
| text vectors can be re-encoded from original text. When changing models for plugin-owned vectors, the plugin must save | ||
| recomputed content revisions while search is stopped; the framework accepts only vectors compatible with the target space. |
There was a problem hiding this comment.
[P2] Define a migration path for plugin-owned vector model changes
In a Scope whose Source cursor is already caught up, this rewrite has no defined execution path: Section 5 skips generate without accepted Source input, Section 6 preserves cursors across reloads, historical replay is out of scope, and registration exposes no write API by default. Existing heads therefore retain vectors from the old model, preventing the new build from completing and keeping even text-only search at 503 under Section 8.3. Please define a bounded, recoverable migration path that runs without new Sources, or explicitly reject these changes before accepting the target and disabling search.
There was a problem hiding this comment.
For v1, index definitions and schema identity are fixed at registration. Changes are rejected before they affect existing search. Reloads can still update query policies, such as defaults and ranking weights, without rebuilding indexes. Vector migration is out of scope.
Which issue or RFC does this PR close?
This PR proposes a new RFC. Related: Source plugin RFC #2012. It does not close an issue.
Rationale for this change
Applications need to generate and retrieve domain-specific Artifacts without adding a built-in Artifact family for each use case. This RFC defines an Artifact plugin framework that reuses the existing Supervisor and Worker execution model.
What changes are included in this PR?
Add matching English and Chinese RFCs covering:
Are there any user-facing changes?
Documentation only. This PR proposes contracts and capability boundaries; it does not change runtime behavior, public APIs, or persisted data.
How was this change tested?
make docs-testuv run --locked prek run --files docs/en/rfcs/2175-artifact-plugin-system.md docs/zh/rfcs/2175-artifact-plugin-system.mdAI usage statement
OpenAI Codex assisted with drafting and revising the bilingual RFCs. A separate subagent reviewed bilingual consistency and implementation alignment, with a final LGTM verdict. The author reviewed the design and directed the revisions.