CR-039: Add AMD submission materials#31
Merged
Merged
Conversation
f19ef41 to
03fc012
Compare
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.
Summary
Adds AMD hackathon submission materials for the TriageCore AMD cloud routing demo path.
This PR keeps the AMD submission story separate from the Qwen MemoryAgent path and points judges toward the executable routing-policy evidence added in CR-040.
What changed
Relationship to CR-040 / PR #30
This PR is intentionally separate from PR #30.
PR #30 adds the executable routing-policy evidence. This PR explains the AMD submission story and points judges to that evidence.
Merge order should be:
Validation
git diff --checkScope boundary
This PR does not add:
Residual risk
The AMD routing path is still a governed demo and policy-evidence path, not a live AMD cloud execution backend. That is intentional for this submission slice.