Concepts in 5 minutes.
UseDesktop packages are evidence objects. A package is only useful when the task can be attempted, scored, audited, and exported with enough context for another team to trust the result.
Flow
source workflow
-> environment
-> task
-> grader
-> model run
-> audits
-> export packageVocabulary
The human completion path that supplies the real-world task shape and tacit decisions.
The resettable app, workflow twin, or runtime boundary where a model can act.
The prompt, start state, constraints, and expected outcome for one model attempt.
The scoring contract that checks final state, process evidence, and invalid shortcuts.
One model attempt with trace, score, reward, verdict, and failure evidence.
Evidence about verifier FP/FN risk, difficulty, contamination, and known loopholes.
Why it matters
A trajectory alone shows that a person did something. A workflow package shows whether a model can attempt the same class of work, whether the result can be scored, and whether the score is trustworthy.