Refactor Nexus One AI product structure and roadmap

- Add Workstation as an additive standalone category, kept out of
  TIER_ORDER so it never enters the Server S/M/L/Max upgrade ladder
- Add Server S/M/L/Max commercial labels for existing starter/basic/pro/max
  tiers (slugs, license format, and APIs unchanged)
- Rename portal UI terminology: Connectors -> MCP & Enterprise Connectors,
  Audit Log -> Governance & Audit, Model Manager -> Model Catalog,
  Agent Builder -> Agent Studio, Workflow Automation -> Workflow Designer,
  Multimodal Chat -> AI Workspace
- Fix branding.js workflow.html tier-gating bug and entry.yml missing tier var
- Document 7-capability platform roadmap and Workstation/Server structure
  in README.md and docs/README.md
- Ignore __pycache__/*.pyc build artifacts
This commit is contained in:
Jino Jose committed 2026-07-08 15:00:02 +05:30
1 parent e5b2496b97
commit 12d9ea84f6
58 files changed
+587 -366

No files matched your search

+104 -32
View File
@@ -12,6 +12,37 @@ The ISO is only one delivery surface. It stays small by pulling this package
from cgit during setup, then the installer deploys the selected tier and
feature set on the target server.
## Product Structure
Nexus One AI, Powered by Cezen, has two product categories. This is a
packaging/labeling structure, not a rewrite — the existing installer,
license engine, and Server tiers below are unchanged.
```text
Nexus One AI
Powered by Cezen
├── Nexus One AI Workstation (personal AI appliance, 1-3 users, 5 max)
│
└── Nexus One AI Server (shared multi-user platform)
├── Server S (was: Starter)
├── Server M (was: Entry / Basic)
├── Server L (was: Pro)
└── Server Max (was: Max)
```
- **Nexus One AI Workstation** is a personal AI appliance for AI developers,
data scientists, researchers, universities, innovation labs, CXOs, and
individual knowledge workers — typically NVIDIA DGX Spark, RTX 5090
Workstation, or RTX PRO 6000 Workstation hardware. It is not a shared
server: no HA, no server-redundancy expectations. Internally it is an
additive `workstation` category in the license engine (`category:
"workstation"`), kept structurally separate from the Server tier ladder.
- **Nexus One AI Server** is the existing four-tier shared platform
(Server S/M/L/Max — internal license slugs `starter/basic/pro/max` are
unchanged; Server S/M/L/Max are the new commercial labels for the same
four tiers). See [Section 6](#6-tier-and-packaging-guide) and
[Section 8](#8-features-by-tier).
## Product Collateral
Technical buyer-facing collateral lives in `docs/` for reuse in customer
@@ -101,7 +132,8 @@ http://<server-ip>
6. Complete the setup wizard:
- Network: DHCP or static IP.
- License & customer details: customer name, project/customer ID, contact email, license key, support date.
- Tier: Starter, Entry, Pro, or Max.
- Tier: Server S, Server M, Server L, or Server Max (internal slugs
unchanged: `starter`/`basic`/`pro`/`max`).
- Tools: keep defaults unless a component should be skipped.
7. Click **Start Installation**.
8. Wait for Phase 1 NVIDIA driver setup. The server may reboot once.
@@ -215,12 +247,27 @@ The selected tier still wins, because the sale/license decision is commercial.
## 6. Tier And Packaging Guide
| Tier | Target Hardware | Typical Use | Default Models |
**Nexus One AI Server** (shared, multi-user; internal license slug in parentheses):
| Server Tier | Target Hardware | Typical Use | Default Models |
|---|---|---|---|
| Starter | 1 GPU around 24-32 GB VRAM, or constrained CPU system | Small team, RAG/admin portal, light chat | `phi3:mini`, `nomic-embed-text` |
| Entry / Basic | 1 RTX Pro 6000 class GPU, around 48-96 GB VRAM | Department deployment | `llama3.1:8b`, `mistral:7b`, `codellama:13b`, `nomic-embed-text` |
| Pro | 2+ high VRAM GPUs | Multi-team deployment, heavier coding/RAG/fine-tuning workflows | Entry models plus `llama3.1:70b`, `mixtral:8x7b`, `deepseek-coder-v2:16b` |
| Max | 4-8 enterprise GPUs such as H100/H200/A100 class | Enterprise deployment, large models, high concurrency | Pro models plus `llama3.1:405b`, `mixtral:8x22b` |
| Server S (`starter`) | 1 GPU around 24-32 GB VRAM, or constrained CPU system | Small team, RAG/admin portal, light chat | `phi3:mini`, `nomic-embed-text` |
| Server M (`basic`) | 1 RTX Pro 6000 class GPU, around 48-96 GB VRAM | Department deployment | `llama3.1:8b`, `mistral:7b`, `codellama:13b`, `nomic-embed-text` |
| Server L (`pro`) | 2+ high VRAM GPUs | Multi-team deployment, heavier coding/RAG/fine-tuning workflows | Server M models plus `llama3.1:70b`, `mixtral:8x7b`, `deepseek-coder-v2:16b` |
| Server Max (`max`) | 4-8 enterprise GPUs such as H100/H200/A100 class | Enterprise deployment, large models, high concurrency | Server L models plus `llama3.1:405b`, `mixtral:8x22b` |
**Nexus One AI Workstation** (personal appliance; internal category `workstation`,
kept outside the Server ladder — see [Product Structure](#product-structure)):
| Category | Target Hardware | Typical Use | Users |
|---|---|---|---|
| Workstation (`workstation`) | NVIDIA DGX Spark, RTX 5090 Workstation, or RTX PRO 6000 Workstation | Local chat, personal RAG, prompt studio, document intelligence | 1-3 active, 5 max |
The compact single-GPU ISO build path (`build-iso-starter.sh` /
`user-data-starter`) is the closest existing hardware profile to Workstation
today. It still writes the `starter` (Server S) tier marker — repointing it to
build a dedicated Workstation ISO is tracked as follow-up work, not done in
this pass (see [Migration Notes](../MIGRATION_NOTES.md)).
Large models can be pulled later. The ISO does not need to contain them.
@@ -238,20 +285,20 @@ Nexus One AI includes these application features through the portal and backend:
| Feature | What It Does |
|---|---|
| Secure admin portal | Browser UI for setup, chat, tools, users, models, reports, and system status. |
| Authentication and sessions | JWT login, role-aware admin access, brute-force lockout, active session tracking. |
| Authentication and sessions | JWT login, role-aware admin access, brute-force lockout, active session tracking. Portal nav label unchanged (no current single nav item maps to "Enterprise Authentication" — see [Section 15](#15-platform-roadmap)). |
| User and team management | Admin-managed users, teams, roles, and account status. |
| Private chat | On-prem chat over local or routed models. |
| AI Workspace *(was: Private Chat)* | On-prem chat over local or routed models. |
| RAG knowledge base | Upload documents, index them into ChromaDB, and query private knowledge. |
| Prompt library | Government/enterprise prompt templates grouped by use case. |
| Model management | View local models, pull Ollama models, upload GGUF models, and track model status. |
| Prompt library | Government/enterprise prompt templates grouped by use case. Kept as "Prompt Library" — the portal already has a distinct "Prompt Studio" authoring tool, so this label was not renamed to avoid duplicate nav entries. |
| Model Catalog *(was: Model Management)* | View local models, pull Ollama models, upload GGUF models, and track model status. |
| Model router | Route requests by rule to local, GPU, or external model endpoints on supported tiers. |
| Document intelligence | Parse, summarize, and extract structured information from documents. |
| Meeting assistant | Transcript/audio processing, summaries, decisions, action items, and follow-ups. |
| Agent builder | Create and run configured agents, including scheduled agent jobs. |
| Workflow automation | Run portal workflows with HTTP, email, RAG, save-to-knowledge-base, and filter steps. |
| Connectors | Store and sync supported data connectors. |
| Agent Studio *(was: Agent Builder)* | Create and run configured agents, including scheduled agent jobs. |
| Workflow Designer *(was: Workflow Automation)* | Run portal workflows with HTTP, email, RAG, save-to-knowledge-base, and filter steps. |
| MCP & Enterprise Connectors *(was: Connectors)* | Store and sync supported data connectors (DB/folder sync today; MCP-based connectors are on the roadmap — see [Section 15](#15-platform-roadmap)). |
| Guardrails | Keyword, regex, and PII checks for safer prompts and responses. |
| Analytics and audit | Query logs, usage summaries, audit reports, and admin visibility. |
| Governance & Audit *(was: Analytics and Audit)* | Query logs, usage summaries, audit reports, and admin visibility. |
| Evaluation suite | Manage datasets, eval jobs, and model/prompt quality checks. |
| Fine-tuning jobs | QLoRA and advanced training paths for higher tiers. |
| API key manager | Create, list, and revoke API keys for integrations. |
@@ -260,24 +307,31 @@ Nexus One AI includes these application features through the portal and backend:
## 8. Features By Tier
The backend exposes this same matrix from `GET /api/license`.
The backend exposes this same matrix from `GET /api/license` (now also
carrying `commercial_label` and `category` fields per tier — additive,
existing fields unchanged).
| Feature | Starter | Entry / Basic | Pro | Max |
|---|---|---|---|---|
| Max users | 10 | 25 | 100 | Custom |
| Portal | Yes | Yes | Yes | Yes |
| Private chat | Yes | Yes | Yes | Yes |
| RAG knowledge base | Yes | Yes | Advanced | Advanced |
| Meeting assistant | No | Yes | Yes | Yes |
| Workflows | Basic | Basic | Advanced | Advanced |
| Connectors | No | Limited | Yes | Yes |
| Model router | No | No | Yes | Yes |
| Audit reports | Yes | Yes | Yes | Yes |
| Backup and restore | Yes | Yes | Yes | Yes |
| Guardrails | Basic | Basic | Advanced | Advanced |
| GPU inference | No | Optional | Yes | Yes |
| Fine-tuning | No | No | QLoRA | Advanced |
| DeepSpeed / distributed training | No | No | No | Custom |
| Feature | Server S (`starter`) | Server M (`basic`) | Server L (`pro`) | Server Max (`max`) | Workstation (`workstation`) |
|---|---|---|---|---|---|
| Max users | 10 | 25 | 100 | Custom | 5 (1-3 active) |
| Portal | Yes | Yes | Yes | Yes | Yes |
| Chat / AI Workspace | Yes | Yes | Yes | Yes | Yes (local) |
| RAG knowledge base | Yes | Yes | Advanced | Advanced | Personal |
| Meeting assistant | No | Yes | Yes | Yes | No |
| Workflows | Basic | Basic | Advanced | Advanced | No |
| MCP & Enterprise Connectors | No | Limited | Yes | Yes | No |
| Model router | No | No | Yes | Yes | No |
| Governance & Audit reports | Yes | Yes | Yes | Yes | No |
| Backup and restore | Yes | Yes | Yes | Yes | Yes (local) |
| Guardrails | Basic | Basic | Advanced | Advanced | Basic |
| GPU inference | No | Optional | Yes | Yes | Yes (local) |
| Fine-tuning | No | No | QLoRA | Advanced | No |
| DeepSpeed / distributed training | No | No | No | Custom | No |
| Document intelligence / Model Catalog / Prompt Studio / API access | Per feature above | Per feature above | Per feature above | Per feature above | Yes |
Workstation is an additive, standalone category — it is not part of the
Server S/M/L/Max ladder and cannot be reached by a Server license upgrade.
See [Product Structure](#product-structure).
## 9. What Gets Installed
@@ -371,7 +425,25 @@ Before shipping to a customer, rotate these:
- Any temporary portal/backend admin credentials.
- Any staging license key if the final license is issued later.
## 14. Useful Files
## 15. Platform Roadmap
Seven enterprise capabilities planned for Nexus One AI. None of these are
implemented yet — this section documents scope and current-state dependencies
so future work builds on the right foundation. Grounded in what the current
codebase does and does not already provide (confirmed by direct inspection of
`cezen-backend/main.py`, `cezen-portal/`, and this repo).
| # | Capability | Scope | Current-state dependency |
|---|---|---|---|
| 1 | Enterprise Authentication | LDAP, Active Directory, SAML, OAuth, OIDC | Greenfield. Today's auth is username/password + JWT (`cezen-backend/main.py`), no SSO code anywhere in the stack. |
| 2 | MCP & Enterprise Connectors | SharePoint, OneDrive, SAP, Oracle, SQL, REST, GitHub, Jira, ServiceNow via MCP | Builds on today's DB/folder-sync connectors (`connectors.html`, `/api/connectors*`), which are not MCP-based. MCP is the planned future transport. |
| 3 | AI Monitoring | GPU/CPU/RAM/VRAM, latency, tokens/sec, queue depth, model usage, active sessions, health | Builds on existing `system-status.json` and `/api/metrics*` (CPU/GPU/RAM/uptime today). |
| 4 | Governance & Audit | Prompt history, model usage, compliance, PII detection, policy violations, usage reports | Builds on existing `audit.html` / `/api/audit*` (66 references in the backend today). |
| 5 | Model Catalog | Browse, install, update, rollback, versioning, recommended models | Builds on existing `models.html` / `models-admin.html` (browse/pull/upload today; no rollback/versioning yet). |
| 6 | Deployment Management | Node management, cluster health, storage, model synchronization, upgrade status, licensing overview | Greenfield for multi-node. Today's install/license flow (`install.sh`, `cezen_license.py`) is single-node. |
| 7 | Secrets Management | Secure storage for API keys, passwords, certificates, tokens, external credentials | Builds on existing API key manager (`apikeys.html` / `/api/apikeys*`); no general credential vault exists yet. |
## 16. Useful Files
```text
cgit/