docs: capability & runtime metadata long-term design#31
Merged
Conversation
Add sub-design doc covering the two-plane (hermetic vs host) dependency model, the mcpp.runtime capability schema (glfw/glx-runtime worked example + glfw->glx-runtime wiring), proposed abi capability and capability->provider resolution, and the immutable-version policy.
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
2 participants
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.
Adds
.agents/docs/2026-06-03-capability-runtime-metadata.md, the long-term industrial design for how this registry models dependency capabilities and runtime requirements.Covers:
compat.glx-runtime, never vendored; intent-level reproducibility).mcpp.runtime.{library_dirs, dlopen_libs, capabilities}) withcompat.glfw/compat.glx-runtimeas the worked example, plus the verifiedglfw -> glx-runtimeLinux dependency wiring.abicapability (glibc/musl/msvc) so the resolver auto-selects an ABI-compatible toolchain (avoids the musl-static default trap without consumer pinning — the field is absent today); and capability->provider resolution per platform. Declarative-first, keeping theinstall()imperative escape hatch.References the master plan and the sibling GL-runtime package-boundary doc.