Jino Jose 12d9ea84f6 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

2026-07-08 15:00:02 +05:30

1.9 KiB

Raw Blame History

Nexus One AI Docs

This folder holds buyer-facing and partner-facing collateral for Nexus One AI. Use it when the repository needs to function as both installer source and technical handoff point.

Core Collateral

File	Purpose
`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

File	Use
`nexus-one-ai-package-overview.jpg`	High-level package positioning visual.
`nexus-one-ai-opportunity.jpg`	Business/problem framing visual.
`nexus-one-ai-tier-comparison.jpg`	Tier and hardware comparison visual.

Product Structure Note

Nexus One AI, Powered by Cezen, now has two product categories: Nexus One AI Workstation (personal AI appliance) and Nexus One AI Server (Server S/M/L/Max — the same four tiers as before, relabeled). See the main repo README.md → "Product Structure" and "Platform Roadmap" sections for the full structure and the seven planned enterprise capabilities. The datasheet and tier-comparison visual below predate this relabeling and should be refreshed in a follow-up design pass — this is a text/terminology update, not a visual/collateral redesign.

Suggested Usage

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.

1.9 KiB Raw Blame History