ALE Tasks β Operation Research: Task assets
The Hugging Face side of AgentsLastExam/ale-tasks-or.
That repository keeps its Tasks' code and configuration in Git; this dataset holds all of their
material (inputs, reference deliverables, rubric and source documents) under the same paths. The
rules are the shared
Task repository conventions.
For now it holds one example Task's material, tasks/demo/external_assets, copied from
ale-tasks-base
(agents-last-exam/ale-tasks-base at revision e8d8dac) to show the layout. Operation research Tasks
add their own tasks/<path>/ folders here when their material is pushed; the example can be
removed once the first real Task is in.
Layout
tasks/demo/external_assets/
βββ environment/assets/public.txt the image build copies it to /home/user/input/public.txt
βββ environment/assets/service-response.txt the image build copies it to a root-only service directory
βββ tests/assets/expected.json the verifier reads assets/expected.json
βββ solution/assets/result.json solve.sh copies it to /home/user/output/result.json
The three asset roots are the only places material lives. In the Task repository they are ignored
by Git (tasks/**/{environment,tests,solution}/assets/); here they are stored with Git LFS
(**/assets/** filter=lfs in .gitattributes), as ale assets push writes them.
Repository and access commands
This dataset belongs to AgentsLastExam/ale-tasks-or.
ALE finds it as <namespace>/<repository name> with the namespace ale-or, so asset commands
for that repository set ALE_ASSETS_NAMESPACE=ale-or (in the engine checkout's .env, or per
command); how namespaces work in general is in the
conventions.
cd /absolute/path/to/ale # engine checkout; ALE_HF_TOKEN in its .env
ALE_ASSETS_NAMESPACE=ale-or uv run ale assets push /absolute/path/to/ale-tasks-or/tasks/<path>
ALE_ASSETS_NAMESPACE=ale-or uv run ale assets pull /absolute/path/to/ale-tasks-or
Versions
Each push makes one dataset commit per Task (Update tasks/<path> assets). A Task's material is
identified by the git tree id of tasks/<path> on the dataset; together with the tree id of the
same folder in the Task repository it gives the Task's version, independent of every other Task.
The dataset revision moves with any Task's push and is recorded beside a version, not in it.
Access
Public and gated with manual approval: anyone can see the file list; downloading needs an administrator's approval, so tests, solutions and licensed material are never open to everyone.
- Downloads last month
- 35