Upload folder using huggingface_hub

docs/placement_asset_notes.md

@@ -9,6 +9,12 @@ This repository is intended to support placement-oriented robotics tasks such as
 
 ## Currently available local assets
 
+For any imported source, the upstream-to-local directory mapping is recorded in:
+
+```text
+docs/structure_mapping.md
+```
+
 ### RoboCasa
 
 RoboCasa currently contributes dishwasher fixtures:

docs/source_notes/discoverse.md

@@ -9,7 +9,8 @@ Imported from local clone:
 - Imported asset root: `models/`
 
 ```text
-assets/discoverse/collections/models/discoverse_models/
+upstream: DISCOVERSE/models/
+current : assets/discoverse/collections/models/discoverse_models/
 ├── mjcf/
 ├── meshes/
 └── urdf/
@@ -17,6 +18,17 @@ assets/discoverse/collections/models/discoverse_models/
 
 This source is stored as a collection-level asset rather than splitting every XML into a separate asset. Reason: many MJCF files reference sibling meshes and support XML files through relative paths, so preserving the upstream tree is the safest default.
 
+## Structure mapping
+
+| Upstream | Current | Notes |
+| --- | --- | --- |
+| `models/mjcf/` | `assets/discoverse/collections/models/discoverse_models/mjcf/` | Preserved unchanged. MJCF include/file paths remain relative. |
+| `models/meshes/` | `assets/discoverse/collections/models/discoverse_models/meshes/` | Preserved unchanged. Mesh references stay valid. |
+| `models/urdf/` | `assets/discoverse/collections/models/discoverse_models/urdf/` | Preserved unchanged. |
+| `models/metadata.yaml` | `assets/discoverse/collections/models/discoverse_models/metadata.yaml` | Added locally for indexing. |
+
+Reference preservation: yes. The directory tree was wrapped in one collection asset, but no inner filenames were renamed.
+
 Current imported inventory:
 
 - Total files: 1427

docs/source_notes/robocasa.md

@@ -38,3 +38,13 @@ Included dishwasher-related files:
 - 25 dishwasher fixture model directories: `Dishwasher031`, `Dishwasher032`, `Dishwasher034`, `Dishwasher036`, `Dishwasher038`, `Dishwasher039`, `Dishwasher040`, `Dishwasher042`, `Dishwasher043`, `Dishwasher044`, `Dishwasher045`, `Dishwasher046`, `Dishwasher048`, `Dishwasher049`, `Dishwasher051`, `Dishwasher053`, `Dishwasher054`, `Dishwasher055`, `Dishwasher058`, `Dishwasher059`, `Dishwasher060`, `Dishwasher061`, `Dishwasher062`, `Dishwasher063`, `Dishwasher067`
 - Fixture registry: `assets/robocasa/fixtures/fixture_registry/dishwasher.yaml`
 - Fixture implementation reference: `docs/source_notes/robocasa/dishwasher_fixture.py`
+
+## Structure mapping
+
+| Upstream | Current | Notes |
+| --- | --- | --- |
+| `robocasa/models/assets/fixtures/dishwashers/Dishwasher031/` | `assets/robocasa/fixtures/dishwashers/Dishwasher031/` | One-to-one directory mapping for each dishwasher model. `model.xml` and `visuals/` kept intact. |
+| `robocasa/models/assets/fixtures/fixture_registry/dishwasher.yaml` | `assets/robocasa/fixtures/fixture_registry/dishwasher.yaml` | Registry copied without renaming. |
+| `robocasa/models/fixtures/dishwasher.py` | `docs/source_notes/robocasa/dishwasher_fixture.py` | Reference copy for implementation and naming conventions. |
+
+Reference preservation: yes. The assets were normalized into the unified library layout, but per-asset filenames and relative mesh references were preserved.

docs/storage_spec.md

@@ -29,6 +29,13 @@ assets/discoverse/collections/models/discoverse_models/
 - Source asset files, preserving upstream structure where practical.
 - `metadata.yaml`.
 
+If a source is reorganized during import, also record the upstream-to-local structure mapping in:
+
+```text
+docs/structure_mapping.md
+docs/source_notes/<source>.md
+```
+
 ## Global index
 
 All assets must be indexed in:

docs/structure_mapping.md

@@ -0,0 +1,35 @@
+# Structure Mapping Record
+
+Whenever an upstream asset source is reorganized during import, record the mapping between:
+
+- original upstream directory layout
+- current on-disk layout in this repository
+- reason for the transformation
+- whether internal relative references were preserved
+
+## Required fields
+
+For each source, record:
+
+- `upstream_root`
+- `original_layout`
+- `current_layout`
+- `mapping_notes`
+- `reference_preservation`
+
+## Why this matters
+
+Without explicit structure mapping, a repository can no longer answer:
+
+- which files came from which upstream directory
+- whether a path change was semantic or only organizational
+- whether relative XML/mesh references were preserved
+- how to re-import a source after upstream updates
+
+## Rule
+
+If you change a source’s on-disk structure, update:
+
+- `docs/source_notes/<source>.md`
+- the source’s `metadata.yaml`
+- any manifest row that stores `path`