gunnchOSArchitecture / UML
Research portal
Researchers need one front door that does not upgrade a repository into field validation.
Accepted source 3f3d07b9996f · ACCEPTED_MAIN · portal-software
Portal UML is the portal's own software structure. It does not grant peer review, field validation, or carrier acceptance.
Current is shown first. Future and legacy stay labeled. A rendered SVG is used when accepted main already committed one. Otherwise the Mermaid or Markdown source is shown and is not executed in the browser.
- current: Use case — current
- current: Component — current
- future: Future — hosted control plane
- legacy: Legacy — product-portal-only entry
Current
Use case — current
current mermaid
What this diagram shows
Actors: prospective supervisor, researcher, developer, curious reader, Edmund (owner). This portal does not execute RAN control.
What this diagram does NOT prove
This diagram does not prove the portal validated any experiment.
Source path docs/uml/current/use_case.md @ 3f3d07b9996f
Component — current
current mermaid
What this diagram shows
VAL[scripts/validate_supervisor_ready.py]
What this diagram does NOT prove
This diagram does not prove the portal validated any experiment.
Source path docs/uml/current/component.md @ 3f3d07b9996f
Future
Future — hosted control plane
future mermaid
What this diagram shows
GH[GitHub source of truth] --> SITE[Optional static site]
What this diagram does NOT prove
This diagram does not prove the portal validated any experiment.
Source path docs/uml/future/hosted_control_plane.md @ 3f3d07b9996f
Legacy
Legacy — product-portal-only entry
legacy markdown
What this diagram shows
Cycle 3A WP-012 treated this repository as the **equitable compute product** information architecture (`START_HERE.md` → `PRODUCT_FAMILY.md`). That path remains for non-research readers.
What this diagram does NOT prove
This diagram does not prove the portal validated any experiment.
Source path docs/uml/legacy/product_portal_only.md @ 3f3d07b9996f