docs(plugins): plugin composability design - #615
Open
ilackarms wants to merge 3 commits into
Open
Conversation
…sed inline pins, refresh path, scoping clarifications
ilackarms
marked this pull request as ready for review
August 11, 2026 15:26
…eclared-name skill keying, agent-plugins.org adapter plan
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.
Description
Design docs for plugin composability — making
Plugina composable bundle the wayAgentalready is.Motivation: today a Plugin is a pinned pointer at a single git repo, materialized 1:1. Product wants plugins to be declaratively composed from registry artifacts (Skills, MCP servers, Prompts) overlaid on an optional base git source, compiled deterministically into one flattened harness filesystem bundle at consumption time — while the API keeps representing the plugin as a collection of reusable objects.
What's here:
design-docs/PLUGIN_COMPOSABILITY_OVERVIEW.md— one-page summary for reviewers (start here).design-docs/PLUGIN_COMPOSABILITY_SPIKE.md— the full design: API shape (kindlessComponentRef, optionalsource,Status.ResolvedComponentspin set), controller resolution + freeze-at-spec-change pin semantics, deterministic compose rules (overlay-wins with provenance report), consumption paths (AgentCore runner,arctl pull, kagent-via-derived-OCI), and how it relates to the prior "no live refs" / "registry hosts nothing" decisions. Verified againstmain@98ce4b08.Key scope cuts (decided, rationale in the docs): no nested plugin-in-plugin; hooks/sub-agents stay base-source-only; composed plugins are skipped by the marketplace.json compat catalog in v1 (serving them is gated on the git-backed marketplace, tracked in enterprise #1195).
P1 implementation (spec refs + controller + compose package, OSS) is starting in parallel on a separate branch; this PR is the design of record for that work.
Change Type
/kind design
Changelog
Additional Notes
Reviewer focus areas are listed at the bottom of the overview doc: the compose/merge rules (spike §6), pin/freeze semantics + cross-kind reconcile race (§5), and the kagent derived-OCI consumption lean (§7).