Repository navigation
Define evidence-based Skillspace graduation and an Argus pilot - #6
Merged
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
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.
Skillspace upload counts currently do not establish training readiness or robot performance. This adds a source-reviewed Argus assessment, a staged path from accepted episodes to versioned robot-tested releases, and a bounded annotation pilot with explicit success, failure and unknown outcomes.
The report distinguishes existing DVIDIA foundations from proposed integration, separates skill class from training maturity, and explains why robot compatibility requires an action/control profile beyond a DOF count. The pilot compares grounded annotations against a fixed visual baseline, measures missed and false successes, and keeps a later robot-policy experiment separate.
Tracks #5; no experiments have been run and the question stays open. No user recordings, account records, credentials or private source code are included. The catalog links the actual research issue and the inspected upstream revision.
Validation:
npm run check, all 13 catalog tests,git diff --check, public-file sensitive-pattern scan, and an independent source/design review. Review findings about baseline comparability and missed successes were incorporated.