Replay Portable AI carry pack contract on current main#11
Merged
Conversation
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.
Summary
Replays the Portable AI Carry Packs contract layer from draft #7 onto current
main.This preserves the valid contract work while avoiding the stale/diverged draft branch state.
Changes
docs/portable-ai-carry-packs.mddesign spec.contracts/model-carry-pack.schema.json.contracts/portable-ai-root.schema.json.tiny-routerlaptop-safeoffice-localcode-localfield-kitbyom-ggufexamples/portable-ai-root.laptop-safe.json.tools/validate_portable_ai_packs.py.make validate-portable-aiand wire it into top-levelmake validate.Boundary
This repository owns the portable model-carry manifest and validation layer only.
This PR does not download model weights, launch runtimes, run inference, train models, authorize personalization, enable prompt egress, enable tool use, or make BYOM files route-eligible before hash/provenance/license posture are recorded.
Validation target
Capture posture
Supersedes draft #7 if current-base validation passes.