Repository navigation
docs: explain how vendor neutrality is achieved - #613
Merged
Merged
Conversation
The framework asserts vendor neutrality in PRINCIPLES.md §9/§3, MISSION.md, and RFC-AI-0004 §3, but the *mechanism* was scattered across labels-and-capabilities.md, setup/privacy-llm.md, tools/vcs/, and README.md. No single doc answered "how is vendor neutrality actually achieved?" — the recurring question raised on the website tracker (apache/magpie-site#17). Add docs/vendor-neutrality.md as the authoritative explanation: - Separates the two questions that get conflated — is the *architecture* vendor-neutral (yes, by construction) vs is *every* vendor already implemented (impossible for anyone, and not what neutrality means). - Names the five axes (LLM, agentic runtime, forge/tracker, VCS, project governance) and shows each is independent. - Reads the skills / tools / capabilities model as the neutrality mechanism: skills target the abstraction, tools are the only vendor-specific layer, capabilities are the contract; backed by the real adapter-contract tools (cve-tool, mail-archive, mail-source, forwarder-relay, scan-format, vcs). - Documents the per-axis status honestly (e.g. VCS = Git complete, Hg/SVN detected extension points, the rest tracked) with a status-at-a-glance table and an explicit does/does-not-claim section. - Covers what keeps it neutral over time (principle block, capability-floor minimisation, eval discipline) and the contribution model. Wire it in: a "Where to go next" row in docs/index.md and a pointer from PRINCIPLES.md §9 to the new how-to doc. Generated-by: Claude Code (Opus 4.8)
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.
What
Adds
docs/vendor-neutrality.md— the authoritative explanation of howMagpie achieves vendor neutrality — and wires it into
docs/index.mdandPRINCIPLES.md§9.Why
The framework already asserts vendor neutrality (
PRINCIPLES.md§9/§3,MISSION.md§ Affordability,RFC-AI-0004§3), but the mechanism wasscattered across
labels-and-capabilities.md,setup/privacy-llm.md,tools/vcs/, andREADME.md. No single doc answered the recurring question"is Magpie really vendor neutral, and how?" — raised most recently on the
website tracker (apache/magpie-site#17).
What the new doc says
vendor-neutral (yes, by construction) vs. is every vendor already
implemented and hardened (impossible for anyone, and not what neutrality
means).
governance — each independent.
target the abstraction, tools are the only vendor-specific layer,
capabilities are the contract — backed by the real adapter-contract tools
(
cve-tool,mail-archive,mail-source,forwarder-relay,scan-format,vcs).extension points, the rest tracked), a status-at-a-glance table, and an
explicit does / does-not claim section so website wording stays accurate.
minimisation, eval discipline) and the contribution model.
Notes
🤖 Generated with Claude Code