Bindrs
A bindr is a named collection of node references. It doesn't copy data — it points at paths or whole folders elsewhere in the tree. Use them for:
- Assembling a training set out of scattered episodes
- Sharing a curated slice of a project with a teammate
- Defining "everything I need for experiment X" as a single name
Create a bindr from paths
Inside a Prefix context, members are paths relative to the current episode:
The SDK resolves each path string to a node ID via /nodes/lookup. Folders are kept as folder references, files as file references. The bindr stores only the IDs — moving or renaming the source files breaks the reference (intentional — bindrs aren't symlinks).
Cross-episode bindrs
Step out of the Prefix context and use absolute paths to mix multiple episodes:
Download a bindr as one tree
dl.download_bindr resolves every member, walks any folder members recursively, and writes each file under to= preserving its relative path:
Result on disk:
Folder members keep their internal structure under to=. File members land at to=/<filename>.
Add more members later
Calling dl.bindr with an existing name adds to it (rather than replacing). Useful for incrementally building up a set:
If you want to replace members, delete and recreate the bindr (preview UI has a delete button, or use the lower-level client).
Nested bindrs
A bindr can contain other bindrs. Useful for rolling up smaller, focused bindrs into a larger curated set without copying members around.
The new kwarg is bindrs= — distinct from members= (paths). You can pass both:
Cycles are rejected
The server runs a reachability check on every add. Trying to put a bindr inside one of its own descendants is rejected with 400 cycle detected:
download_bindr also tracks visited bindr IDs at download time — even if a cycle somehow slipped through, the recursion terminates.
Bindrs vs folders vs episodes
| Folder | Episode | Bindr | |
|---|---|---|---|
| Stores data? | No (tree node) | No (tree node) | No (just refs) |
| Has a fixed location? | Yes — under one parent | Yes — under one project | No — references anywhere |
| Members can be from different episodes? | No | N/A | Yes |
| Moves with the data? | Yes (rename folder = rename path) | Yes | No (paths frozen at creation) |
Use folders to organize. Use episodes to demarcate experiment runs. Use bindrs to assemble curated views that cut across the structural hierarchy.
What you can do next
- Download Files — direct download by path or node ID
- Upload an Episode — get data into the tree to bindr in the first place