Add technical service flow diagram
This commit is contained in:
Jino Jose
parent
7d6223125e
commit
3a204ac2e7
@ -13,6 +13,7 @@ evaluation, partner enablement, and internal technical review.
|
||||
- `docs/Nexus_One_AI_Datasheet.docx`
|
||||
- `docs/Nexus_One_AI_Datasheet.pdf`
|
||||
- `docs/architecture-overview.svg`
|
||||
- `docs/technical-service-flow.svg`
|
||||
|
||||
## Why Nexus One AI
|
||||
|
||||
@ -26,6 +27,10 @@ evaluation, partner enablement, and internal technical review.
|
||||
|
||||
|
||||
|
||||
## Technical Service Flow
|
||||
|
||||
|
||||
|
||||
## Visual Overview
|
||||
|
||||
### Package Positioning
|
||||
|
||||
@ -11,6 +11,7 @@ technical handoff point.
|
||||
| `Nexus_One_AI_Datasheet.docx` | Editable technical buyer datasheet. |
|
||||
| `Nexus_One_AI_Datasheet.pdf` | Shareable PDF export of the technical buyer datasheet. |
|
||||
| `architecture-overview.svg` | Simple stack view for repo pages, partner notes, and internal explainers. |
|
||||
| `technical-service-flow.svg` | Deeper service and data-path view for buyer evaluation, architecture review, and implementation planning. |
|
||||
|
||||
## Visuals
|
||||
|
||||
@ -24,5 +25,6 @@ technical handoff point.
|
||||
|
||||
- Start with the main repo `README.md` for installation and deployment paths.
|
||||
- Use the datasheet for technical buyer review and partner follow-up.
|
||||
- Use the architecture snapshot when a fast orientation diagram is enough.
|
||||
- Use the technical service flow when reviewers need runtime, storage, retrieval, and operations detail.
|
||||
- Use the visuals in proposal notes, partner onboarding, and internal solutioning.
|
||||
|
||||
|
||||
140
docs/technical-service-flow.svg
Normal file
140
docs/technical-service-flow.svg
Normal file
@ -0,0 +1,140 @@
|
||||
<svg xmlns="http://www.w3.org/2000/svg" width="1600" height="1040" viewBox="0 0 1600 1040" role="img" aria-labelledby="title desc">
|
||||
<title id="title">Nexus One AI Technical Service Flow</title>
|
||||
<desc id="desc">Technical service flow diagram for Nexus One AI showing user access, portal services, backend orchestration, inference, retrieval, storage, and operations components inside customer-controlled infrastructure.</desc>
|
||||
<defs>
|
||||
<marker id="arrow" viewBox="0 0 14 14" refX="11" refY="7" markerWidth="8" markerHeight="8" orient="auto">
|
||||
<path d="M1 1 L13 7 L1 13 Z" fill="#315E8A"/>
|
||||
</marker>
|
||||
<style>
|
||||
.bg { fill: #F5F8FC; }
|
||||
.frame { fill: #FFFFFF; stroke: #C9D5E4; stroke-width: 2; }
|
||||
.zone { fill: #EDF3FA; stroke: #D3DEEB; stroke-width: 2; }
|
||||
.zoneTitle { fill: #5B7590; font: 700 14px Arial, sans-serif; letter-spacing: 0.16em; }
|
||||
.title { fill: #17304D; font: 700 34px Arial, sans-serif; }
|
||||
.kicker { fill: #0D7B72; font: 700 14px Arial, sans-serif; letter-spacing: 0.16em; }
|
||||
.subtitle { fill: #58708A; font: 400 18px Arial, sans-serif; }
|
||||
.card { fill: #FFFFFF; stroke: #C8D5E3; stroke-width: 2; }
|
||||
.cardAccent { fill: #F0F7F6; stroke: #9FD3C7; stroke-width: 2; }
|
||||
.cardTitle { fill: #1F3854; font: 700 18px Arial, sans-serif; }
|
||||
.lead { fill: #284868; font: 700 15px Arial, sans-serif; }
|
||||
.text { fill: #516A84; font: 400 15px Arial, sans-serif; }
|
||||
.small { fill: #6A8198; font: 400 13px Arial, sans-serif; }
|
||||
.flow { stroke: #315E8A; stroke-width: 4; fill: none; marker-end: url(#arrow); }
|
||||
.sync { stroke: #5F8FB9; stroke-width: 3; fill: none; marker-end: url(#arrow); }
|
||||
.ops { stroke: #7D95AE; stroke-width: 2.5; stroke-dasharray: 8 8; fill: none; marker-end: url(#arrow); }
|
||||
.rule { stroke: #D5DFEA; stroke-width: 2; }
|
||||
</style>
|
||||
</defs>
|
||||
|
||||
<rect width="1600" height="1040" class="bg"/>
|
||||
<rect x="40" y="36" width="1520" height="968" rx="20" class="frame"/>
|
||||
|
||||
<text x="86" y="104" class="kicker">NEXUS ONE AI · TECHNICAL SERVICE FLOW</text>
|
||||
<text x="86" y="150" class="title">Runtime, Data, and Operations Paths Inside Customer-Controlled Infrastructure</text>
|
||||
<text x="86" y="184" class="subtitle">Separates user access, orchestration, retrieval, inference, storage, and support services for buyer evaluation and technical review.</text>
|
||||
<line x1="86" y1="214" x2="1514" y2="214" class="rule"/>
|
||||
|
||||
<rect x="86" y="246" width="240" height="676" rx="18" class="zone"/>
|
||||
<text x="110" y="282" class="zoneTitle">ACCESS SURFACES</text>
|
||||
|
||||
<rect x="358" y="246" width="390" height="676" rx="18" class="zone"/>
|
||||
<text x="382" y="282" class="zoneTitle">APPLICATION AND ORCHESTRATION</text>
|
||||
|
||||
<rect x="780" y="246" width="350" height="676" rx="18" class="zone"/>
|
||||
<text x="804" y="282" class="zoneTitle">AI AND DATA SERVICES</text>
|
||||
|
||||
<rect x="1162" y="246" width="352" height="676" rx="18" class="zone"/>
|
||||
<text x="1186" y="282" class="zoneTitle">OPERATIONS AND PLATFORM</text>
|
||||
|
||||
<rect x="110" y="316" width="192" height="132" rx="14" class="card"/>
|
||||
<text x="132" y="352" class="cardTitle">Users</text>
|
||||
<text x="132" y="386" class="lead">Admins and review teams</text>
|
||||
<text x="132" y="414" class="text">Department users</text>
|
||||
<text x="132" y="442" class="text">Security and procurement</text>
|
||||
|
||||
<rect x="110" y="510" width="192" height="150" rx="14" class="card"/>
|
||||
<text x="132" y="546" class="cardTitle">Portal Access</text>
|
||||
<text x="132" y="580" class="lead">Browser over internal network</text>
|
||||
<text x="132" y="608" class="text">Nexus One AI portal</text>
|
||||
<text x="132" y="636" class="text">Open WebUI surface</text>
|
||||
|
||||
<rect x="110" y="722" width="192" height="146" rx="14" class="card"/>
|
||||
<text x="132" y="758" class="cardTitle">Integration Access</text>
|
||||
<text x="132" y="792" class="lead">API consumers</text>
|
||||
<text x="132" y="820" class="text">Service accounts</text>
|
||||
<text x="132" y="848" class="text">Internal automation jobs</text>
|
||||
|
||||
<rect x="386" y="316" width="334" height="144" rx="14" class="cardAccent"/>
|
||||
<text x="410" y="352" class="cardTitle">Portal and Session Layer</text>
|
||||
<text x="410" y="386" class="lead">Nexus One AI Portal and Open WebUI</text>
|
||||
<text x="410" y="414" class="text">Authentication, session control, and admin UX</text>
|
||||
<text x="410" y="442" class="text">Prompt workflows, model selection, and review screens</text>
|
||||
|
||||
<rect x="386" y="500" width="334" height="170" rx="14" class="card"/>
|
||||
<text x="410" y="536" class="cardTitle">FastAPI Control Plane</text>
|
||||
<text x="410" y="570" class="lead">REST APIs and orchestration</text>
|
||||
<text x="410" y="598" class="text">License, settings, users, API keys, and system reports</text>
|
||||
<text x="410" y="626" class="text">Audit logs, backup and restore, readiness, and install state</text>
|
||||
<text x="410" y="654" class="text">Feature gating by commercial tier</text>
|
||||
|
||||
<rect x="386" y="710" width="334" height="158" rx="14" class="card"/>
|
||||
<text x="410" y="746" class="cardTitle">Workflow and Agent Execution</text>
|
||||
<text x="410" y="780" class="lead">Server-side task coordination</text>
|
||||
<text x="410" y="808" class="text">Prompt chains, scheduled jobs, document actions</text>
|
||||
<text x="410" y="836" class="text">Connector sync and save-to-knowledge-base flows</text>
|
||||
|
||||
<rect x="808" y="316" width="294" height="150" rx="14" class="card"/>
|
||||
<text x="832" y="352" class="cardTitle">Inference Runtime</text>
|
||||
<text x="832" y="386" class="lead">Ollama local model serving</text>
|
||||
<text x="832" y="414" class="text">Model catalog, runtime status, and local inference</text>
|
||||
<text x="832" y="442" class="text">CPU or NVIDIA GPU execution path</text>
|
||||
|
||||
<rect x="808" y="508" width="294" height="164" rx="14" class="card"/>
|
||||
<text x="832" y="544" class="cardTitle">Knowledge Retrieval</text>
|
||||
<text x="832" y="578" class="lead">ChromaDB and embedding pipeline</text>
|
||||
<text x="832" y="606" class="text">Document upload, chunking, indexing, and query retrieval</text>
|
||||
<text x="832" y="634" class="text">RAG context delivery back to application services</text>
|
||||
|
||||
<rect x="808" y="714" width="294" height="154" rx="14" class="card"/>
|
||||
<text x="832" y="750" class="cardTitle">Content and Config Storage</text>
|
||||
<text x="832" y="784" class="lead">Persistent local state</text>
|
||||
<text x="832" y="812" class="text">Uploads, backups, install config, and license artifacts</text>
|
||||
<text x="832" y="840" class="text">Model files and service configuration</text>
|
||||
|
||||
<rect x="1190" y="316" width="296" height="150" rx="14" class="card"/>
|
||||
<text x="1214" y="352" class="cardTitle">Observability</text>
|
||||
<text x="1214" y="386" class="lead">Prometheus and Grafana</text>
|
||||
<text x="1214" y="414" class="text">System, GPU, and service health metrics</text>
|
||||
<text x="1214" y="442" class="text">Operational dashboards for support and handover</text>
|
||||
|
||||
<rect x="1190" y="508" width="296" height="164" rx="14" class="card"/>
|
||||
<text x="1214" y="544" class="cardTitle">Deployment Substrate</text>
|
||||
<text x="1214" y="578" class="lead">Ubuntu 22.04 install target</text>
|
||||
<text x="1214" y="606" class="text">Bootable ISO or scripted installer path</text>
|
||||
<text x="1214" y="634" class="text">Internal-network and air-gapped deployment friendly</text>
|
||||
|
||||
<rect x="1190" y="714" width="296" height="154" rx="14" class="card"/>
|
||||
<text x="1214" y="750" class="cardTitle">Operations Controls</text>
|
||||
<text x="1214" y="784" class="lead">Backup, restore, readiness, and audit</text>
|
||||
<text x="1214" y="812" class="text">Pre-restore safety snapshots and support workflows</text>
|
||||
<text x="1214" y="840" class="text">Commercial licensing and post-install administration</text>
|
||||
|
||||
<path d="M302 584 L386 584" class="flow"/>
|
||||
<path d="M302 796 L386 796" class="flow"/>
|
||||
<path d="M720 392 L808 392" class="flow"/>
|
||||
<path d="M720 574 L808 574" class="flow"/>
|
||||
<path d="M720 584 C770 584 770 392 808 392" class="sync"/>
|
||||
<path d="M720 584 C770 584 770 590 808 590" class="sync"/>
|
||||
<path d="M720 790 C770 790 770 606 808 606" class="sync"/>
|
||||
<path d="M1102 392 L1190 392" class="flow"/>
|
||||
<path d="M1102 590 L1190 590" class="flow"/>
|
||||
<path d="M553 670 L553 710" class="flow"/>
|
||||
<path d="M955 672 L955 714" class="flow"/>
|
||||
<path d="M1338 466 L1338 508" class="ops"/>
|
||||
<path d="M1338 672 L1338 714" class="ops"/>
|
||||
<path d="M1190 790 C1110 790 1110 812 1102 812" class="ops"/>
|
||||
<path d="M1190 392 C1120 392 1120 392 1102 392" class="ops"/>
|
||||
|
||||
<text x="108" y="956" class="small">Customer-controlled boundary: portal, APIs, inference, retrieval, and operational telemetry remain on infrastructure owned or managed by the customer.</text>
|
||||
<text x="1490" y="956" text-anchor="end" class="small">Powered by Cezen</text>
|
||||
</svg>
|
||||
|
After Width: | Height: | Size: 8.6 KiB |
Loading…
Reference in New Issue
Block a user