UX-ML-004 — Use an AI/ML umbrella
| Field | Value |
|---|---|
| Status | Open information-architecture finding; source-verified |
| Severity | Low |
| Components | sparqd/oqullus, sparqd/platform-docs |
| Associated issues | Not opened pending finding review |
Concrete observed case
Oqullus groups Experiments, Models, Auto ML, and AI Gateway under Machine Learning. Experiments, Models, and AutoML form an ML lifecycle. AI Gateway is a separate GenAI control plane for external provider requests and is only used by AutoML for reasoning. The narrower section label makes that distinction harder to understand and can imply that AI Gateway serves AutoML-trained models.
Expected condition
Use AI/ML for the shared navigation and documentation umbrella. Retain precise child names and boundaries:
- AutoML, Experiments, Models, and Synthetic Data describe ML lifecycle capabilities.
- AI Gateway describes external GenAI provider routing and remains distinct from trained-model registration and serving.
Stable documentation URLs may retain machine-learning; the user-visible label
does not need to mirror the route slug.
Why it matters
The umbrella should help users locate related capabilities without erasing the architectural boundary between predictive ML artifacts and externally hosted generative models. An overly narrow label makes the navigation incomplete; an overly broad child label would make the capabilities ambiguous.
Existing controls and workarounds
The individual page names are already specific, and the assessment explains that AI Gateway is not the model-serving destination. Users must currently read that explanation because the navigation label does not communicate it.
Alternatives considered
- Recommended: one AI/ML umbrella with precise child capabilities and explicit lifecycle boundaries.
- Split AI Gateway into a separate top-level AI section. This is clearer at scale but adds navigation weight for one visible AI capability today.
- Keep Machine Learning. Rejected because the section already includes a GenAI gateway whose purpose is not an MLflow lifecycle action.
Component involvement
- Oqullus owns the user-visible navigation section label.
- Platform documentation owns the umbrella terminology and boundary guidance.
- AutoML and AI Gateway retain separate runtime identities and responsibilities; this finding does not merge their architectures.
Reproduction and verification
Follow ML-S016.
Resolution conditions
Close when navigation and documentation use the AI/ML umbrella consistently, child capabilities remain precise, and no copy suggests that AI Gateway serves AutoML or MLflow artifacts.
Validation and blockers
The current Oqullus navigation definition is source-verified at
f76e57dbb88dbbfdeb2b9c4d076ad382fb326ca7. Product validation of the final
navigation terminology remains pending.