| # Next Steps |
|
|
| ## Product follow-ups |
|
|
| 1. Add a dedicated hardware diagnostic workflow that compares: |
| - `request_space_hardware()` after Space creation; |
| - `create_repo(..., space_hardware=...)` at creation time; |
| - OAuth token vs personal access token behavior. |
|
|
| 2. Add optional live Pi progress streaming: |
| - periodic heartbeat during the Pi run; |
| - partial `pi_output.txt` tailing; |
| - intermediate trace syncing. |
|
|
| 3. Add a repair workflow: |
| - read target Space build/runtime logs; |
| - ask Pi to patch generated files; |
| - upload patch; |
| - re-run validation. |
|
|
| 4. Improve validation presets per task: |
| - text-to-image prompt → image output; |
| - text-generation prompt → text output; |
| - ASR audio sample → text output; |
| - image-to-image test image → image output. |
|
|
| 5. Improve generated report UI: |
| - clearer final status badges; |
| - direct links to generated Space, Bucket files, and trace JSONL; |
| - explicit manual hardware checklist. |
|
|
| ## Current product workflow |
|
|
| ```text |
| Build from model card |
| → if hardware automatic assignment succeeds, validate directly |
| → if not, set hardware manually in target Space Settings |
| → Validate existing Space |
| → full_inference_success if output type and latency are validated |
| ``` |
|
|
