- build_nexus_one_ai_datasheet.py (root, outside cgit): new Product Structure section, Server S/M/L/Max tier table (was Starter/Basic/Pro/ Max), Platform Roadmap section (7 capabilities). Regenerated docx + pdf. - architecture-overview.svg / technical-service-flow.svg: relabeled tier banner to Server S/M/L/Max, fixed stale terminology (Agent builder -> Agent Studio, Connector sync -> MCP & Enterprise Connector sync, Pro/Max -> Server L/Max), added a one-line Workstation callout in existing whitespace. Verified by rendering both to PNG before committing. - docs/README.md: notes docx/pdf/SVGs are current; the 3 jpg visuals still need a design refresh (raster images, tracked as follow-up).
2.2 KiB
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.
Nexus_One_AI_Datasheet.docx/.pdf, architecture-overview.svg, and
technical-service-flow.svg are updated to this structure — Server S/M/L/Max
labeling throughout, a Workstation callout, and a Platform Roadmap section in
the datasheet. The three .jpg visuals below (package overview, opportunity,
tier comparison) are raster images from an earlier design pass and still
predate this relabeling — they need a design refresh, not a text edit, and
are tracked as follow-up work.
Suggested Usage
- Start with the main repo
README.mdfor 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.