diff --git a/README.md b/README.md index c240a79..62d6e48 100644 --- a/README.md +++ b/README.md @@ -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. ![Nexus One AI architecture overview](docs/architecture-overview.svg) +## Technical Service Flow + +![Nexus One AI technical service flow](docs/technical-service-flow.svg) + ## Visual Overview ### Package Positioning diff --git a/docs/README.md b/docs/README.md index ba898c0..79d9e7a 100644 --- a/docs/README.md +++ b/docs/README.md @@ -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. - diff --git a/docs/technical-service-flow.svg b/docs/technical-service-flow.svg new file mode 100644 index 0000000..b46084c --- /dev/null +++ b/docs/technical-service-flow.svg @@ -0,0 +1,140 @@ + + Nexus One AI Technical Service Flow + 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. + + + + + + + + + + + NEXUS ONE AI ยท TECHNICAL SERVICE FLOW + Runtime, Data, and Operations Paths Inside Customer-Controlled Infrastructure + Separates user access, orchestration, retrieval, inference, storage, and support services for buyer evaluation and technical review. + + + + ACCESS SURFACES + + + APPLICATION AND ORCHESTRATION + + + AI AND DATA SERVICES + + + OPERATIONS AND PLATFORM + + + Users + Admins and review teams + Department users + Security and procurement + + + Portal Access + Browser over internal network + Nexus One AI portal + Open WebUI surface + + + Integration Access + API consumers + Service accounts + Internal automation jobs + + + Portal and Session Layer + Nexus One AI Portal and Open WebUI + Authentication, session control, and admin UX + Prompt workflows, model selection, and review screens + + + FastAPI Control Plane + REST APIs and orchestration + License, settings, users, API keys, and system reports + Audit logs, backup and restore, readiness, and install state + Feature gating by commercial tier + + + Workflow and Agent Execution + Server-side task coordination + Prompt chains, scheduled jobs, document actions + Connector sync and save-to-knowledge-base flows + + + Inference Runtime + Ollama local model serving + Model catalog, runtime status, and local inference + CPU or NVIDIA GPU execution path + + + Knowledge Retrieval + ChromaDB and embedding pipeline + Document upload, chunking, indexing, and query retrieval + RAG context delivery back to application services + + + Content and Config Storage + Persistent local state + Uploads, backups, install config, and license artifacts + Model files and service configuration + + + Observability + Prometheus and Grafana + System, GPU, and service health metrics + Operational dashboards for support and handover + + + Deployment Substrate + Ubuntu 22.04 install target + Bootable ISO or scripted installer path + Internal-network and air-gapped deployment friendly + + + Operations Controls + Backup, restore, readiness, and audit + Pre-restore safety snapshots and support workflows + Commercial licensing and post-install administration + + + + + + + + + + + + + + + + + + Customer-controlled boundary: portal, APIs, inference, retrieval, and operational telemetry remain on infrastructure owned or managed by the customer. + Powered by Cezen +