OUI_XFAB documentation
OUI Web UI Documentation
OUI is a feature-first Vue 3 modular monolith for real-time EAP equipment monitoring and control. This site is the navigable documentation layer; the repository handbook and authoritative documents remain the source of truth.
Explore
- Architecture guide: ownership, dependency direction, public module APIs, and runtime composition.
- Complete system architecture and Web Manager UI decision: OUI, EAPWebManager, EAP, workflows, ownership, deployment, and the linked-hybrid recommendation.
- Runtime flows: WebSocket synchronization, command lifecycle, reconnect behavior, and workstation identity binding.
- Security and deployment: IIS/nginx topology, access-service boundary, environment rules, and release verification.
- UI and dependency migration: PrimeVue to Vuetify migration, icon replacement, TypeScript 6, and visual evidence.
- Verification and operations: quality gates, browser review, release checks, and troubleshooting boundaries.
- Dependency handbook: direct package purpose, ownership, version lines, and audit policy.
- Release guide: versioning, artifacts, approvals, and deployment workflows.
- UI migration tracker: module-by-module before/after review inventory.
Interactive architecture
The OUI Runtime Architecture diagram is generated and validated with Archify. The complete system report adds interactive diagrams for the system landscape, operator command roundtrip, equipment synchronization lifecycle, and linked-hybrid UI decision.
The diagram is pinned to commit 699439d438a711b22997d11b1337ef776c058d89, passed all nine Archify showcase checks, and passed desktop containment checks at 1440x900, 1600x1000, 1920x1080, and 2048x1320 in light and dark themes.
UI review evidence
The UI migration review retains deterministic before/after screenshots for each migrated module. The full tracker records scope, dependency sequencing, and review state.
Source of truth
The application handbook remains authoritative for repository rules. These pages summarize and link to those contracts; they do not replace AGENTS.md, docs/architecture.md, docs/dependencies.md, or docs/releasing.md.