From 52b5df9a283552db03605f120d3a13defc4533cc Mon Sep 17 00:00:00 2001 From: Hongsheng Liu Date: Sat, 8 Aug 2026 22:22:18 +0800 Subject: [PATCH] docs: remove architecture source attribution Signed-off-by: Hongsheng Liu --- docs/design/architecture_overview.md | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/docs/design/architecture_overview.md b/docs/design/architecture_overview.md index 63892739f..3ae7678cb 100644 --- a/docs/design/architecture_overview.md +++ b/docs/design/architecture_overview.md @@ -256,13 +256,11 @@ resources. ## System architecture -The overview below adapts the [general vLLM-Omni architecture -slide](https://docs.google.com/presentation/d/111-L8zF7A1j_YI_cR8JsblofdScdRr2f/edit?slide=id.p17#slide=id.p17) -to the current stage-based runtime. It keeps only the main components: -entrypoints, the shared `AsyncOmniEngine`, request orchestration, stage -lifecycle management, AR and diffusion execution modules, model/layer -operations, connector transport, and multimodal outputs. `AsyncOmniEngine` is -the composition root between the entrypoints and the orchestrator. +The figure shows the main components of the stage-based runtime: entrypoints, +the shared `AsyncOmniEngine`, request orchestration, stage lifecycle +management, AR and diffusion execution modules, model/layer operations, +connector transport, and multimodal outputs. `AsyncOmniEngine` is the +composition root between the entrypoints and the orchestrator. ```mermaid flowchart TB