docs(rfc): RFC-AI-0007 — selective (family-scoped) snapshot fetch#908
Open
potiuk wants to merge 1 commit into
Open
docs(rfc): RFC-AI-0007 — selective (family-scoped) snapshot fetch#908potiuk wants to merge 1 commit into
potiuk wants to merge 1 commit into
Conversation
Propose fetching only the chosen skill families (plus the always-on setup/ utilities families and their runtime closure) into the .apache-magpie/ snapshot via git sparse-checkout + partial clone, instead of the whole repo. Documentation cross-links resolve to canonical apache/magpie URLs; runtime deps (tools, projects/_template, AGENTS.md, PRINCIPLES.md) are fetched and declared per-skill via runtime_deps frontmatter enforced by the validator. The lock records chosen families so upgrade/verify reproduce the sparse set. Phase A (this RFC) is the review checkpoint; Phase B wires setup + install-recipes on approval. No change to the symlink/override model or PRINCIPLES §13.
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.
RFC-AI-0007 — proposes making the non-marketplace (
/magpie-setup) adoption fetch only the chosen skill families instead of the whole framework.The problem
The
.apache-magpie/snapshot today pulls the whole repo — all 10 families, every tool, all ofdocs/, theprojects/templates — even when an adopter opts into one or two families. Investigation showed skills reference outsideskills/heavily (docs ×319, AGENTS.md ×202, tools ×186, projects ×116), so a naive "chosen skills only" fetch would dangle real runtime dependencies.The proposal (Phase A — design review)
setup,utilities) + the runtime closure they execute against (AGENTS.md,PRINCIPLES.md,projects/_template/, invokedtools/).docs/…prose links are rewritten to canonicalgithub.com/apache/magpie/blob/<ref>/…URLs (deterministic at fetch time). A newruntime_deps:frontmatter, enforced byskill-and-tool-validator, keeps the closure from drifting.families:list soupgrade/verifyreproduce the sparse set.svn-zipstays a whole-release fetch (a signed zip can't be sparse); sparse applies to the git methods.Process
This is Phase A — the RFC is the review checkpoint. Phase B (wiring
setup+install-recipes.md+ the lock field + validator) follows on approval, per how RFC-AI-0006 (skill-sources) was staged.Decisions baked in per request: runtime-only closure, per-family granularity, RFC-first.