organize exampels according to products

README.md

@@ -8,7 +8,7 @@ and several runnable examples for camera and video-based workflows.
 
 - `src/orisys/`: installable SDK package
 - `config/`: default and lab/runtime JSON configurations
-- `examples/`: user-facing example scripts
+- `examples/`: product demos (`products/ory_box`, `ory_mini`, `ory_finger`) plus shared `gui/`, `pipeline/`, `viz/`
 - `scripts/`: maintenance, calibration, packaging, and demo scripts
 - `tools/`: non-package tooling such as patch-generation utilities
 - `tests/`: automated pytest suite
@@ -49,18 +49,36 @@ pytest
 
 ### 4. Run an example
 
+ORY-BOX:
+
 ```bash
-python examples/basic_pipeline.py -v 0 -c ./config/ddjx01.json
+python examples/products/ory_box/basic_pipeline.py -v 0 -c ddjx01
 ```
 
+ORY-MINI:
+
+```bash
+python examples/products/ory_mini/basic_pipeline.py -v 0 -c mini
+```
+
+ORY-FINGER:
+
+```bash
+python examples/products/ory_finger/finger_pipeline.py --camera_id 0 --config dd02
+```
+
+Compatibility wrappers remain at `examples/basic_pipeline.py` and
+`examples/finger_pipeline*.py`.
+
 ## Configuration
 
 The canonical configuration files now live in the repo-level `config/` folder.
 The package loader `orisys.configs` resolves configs from:
 
 1. an explicit JSON file path
-2. a config file stem under `config/`
-3. a backward-compatible JSON `"name"` match, such as `"prototype"`
+2. a config file stem under `config/` (for example `ddjx01`, `mini`, `dd02`)
+3. a product alias such as `dd02` -> `dd02-ov`
+4. a backward-compatible JSON `"name"` match, such as `"prototype"`
 
 Examples: