| # Task assets | |
| Task payloads are grouped by data-driven manifests in `../modules/tasks/`. | |
| Each module declares one task family, its station dependency, checkpoint-bound | |
| scene JSON, optional initial state, thin USDA layout layer, and task-owned | |
| metric protocol. | |
| Scene paths are portable: | |
| - `asset://...` resolves from the downloaded TOWER-Assets root. | |
| - `generator://...` resolves from the separately installed generator root. | |
| - `dataset://...` is provenance only and is never opened by the evaluator. | |
| The Task 2/4/5/6 USDA files added in release `0.0.3` are additive | |
| compositions over a shared station. They contain task layout prims and | |
| overrides, not duplicated station geometry or textures. The original Task | |
| 1/2/3 staging USDA files remain descriptors until replaced by a qualified | |
| module release. | |
| To add a task family, create its payloads and one | |
| `tower-asset-module-v1` document, then include that module in the next release | |
| descriptor. No publisher registry change is required. | |