Files
aipackage/docs
..

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.
Nexus_One_AI_Live_Features_and_Architecture_155.pdf Verified technical feature and architecture reference for the current .155 Enterprise Pilot environment.
Nexus_One_AI_Enterprise_Platform_Datasheet.pdf Customer-facing enterprise datasheet covering value, architecture, capabilities, security, operations, deployment and evaluation.
NEXUS_ONE_AI_ENTERPRISE_DATASHEET_SOURCE.md Editable customer-facing content source for the enterprise platform datasheet.
NEXUS_ONE_AI_LIVE_TECHNICAL_REFERENCE_155.md Editable source reference covering live topology, capabilities, evidence, limitations and next actions.
CURRENT_CAPABILITIES.md Concise live capability/status matrix, updated against .155.
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.

All core collateral and visuals are current: Nexus_One_AI_Datasheet.docx/ .pdf, architecture-overview.svg, technical-service-flow.svg, and the three .jpg visuals below all use Server S/M/L/Max labeling and a standalone Workstation callout. No collateral currently predates the relabeling.

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.