gemstone-nexus · Phase 6
DOC01 — Abstract
Metadata
| id | doc_id | title | category | source_path | summary | content_hash | indexed_at |
|---|---|---|---|---|---|---|---|
| 19 | DOC01 | DOC01 — Abstract | doc_suite | DevResources/docs/DOC01-Abstract.md | GemStone is the voice-first, mobile-first agentic interface layer of the NEXTECH Triptych (GemStone, Horizon Atlas, Horizon IQ), functioning as an executive assistant that works alongside, ahead of, and behind the individual practitioner. It is a full-capability AI partner, not a chatbot: it takes complex requests, executes autonomously within a human-approved envelope, produces deliverables, asks one clarifying question at a time, and reports outcomes. | d127cefcad35f51cee7294d7f06baf12c38062ec | 2026-07-22 18:33:18 |
Content
# DOC01 — Abstract *Executive summary of the GemStone initiative* **Initiative:** GemStone · **Version:** v2.0 (Rewrite) · **Status:** Approved for Build · **Date:** July 17, 2026 ## 1. What GemStone Is GemStone is the voice-first, mobile-first agentic interface layer of the NEXTECH Triptych (GemStone, Horizon Atlas, Horizon IQ), functioning as an executive assistant that works alongside, ahead of, and behind the individual practitioner. It is a full-capability AI partner, not a chatbot: it takes complex requests, executes autonomously within a human-approved envelope, produces deliverables, asks one clarifying question at a time, and reports outcomes. GemStone is the primary interface through which a practitioner interacts with their own Atlas Vault and, where permitted, the aggregated Horizon IQ organizational corpus. ## 2. Core Design Commitments - Mobile-first: Capacitor-native for iOS and Android. - Always-on sessions: WebSocket-based persistent connections, no context loss. - Perfect cross-session recall via Atlas Vault (MCP Index B). - Fine-tuning flywheel: practitioner corrections and ratings improve GemStone continuously. - Domain Packs: curated, installable knowledge bundles. - Human-in-the-loop, always: no self-building feature executes without human approval, at any maturity level, permanently. ## 3. What Changed in This Revision This v2.0 rewrite supersedes the original 23-document suite in three respects: mobile stack migrated from React Native/Expo/PWA to Capacitor; GemStone orchestrates Cursor, Claude, and Gemini (with further workers planned) through Didymus, distinct from HorizonNEXUS; and GemStone is confirmed as the single universal presentation and approval surface for every build suggestion regardless of origin. A fourth addition, the GemStone Mobility Layer, was engineered specifically against documented Gemini Live production failures. ## 3A. Locked Build Decisions (Stage 0, July 2026) The following decisions are locked for the v2.0 build in `GemStone-Nexus-StackOne`. Do not re-litigate during implementation without a written SOW amendment. | Decision | Lock | | --- | --- | | Client | Capacitor (web + Android + iOS); React Native/Expo prohibited (DOCA2) | | Auth | Auth0 roles: SuperAdmin, Org Admin, Practitioner, GemStone Agent; social logins Google, Facebook, LinkedIn | | Inference | Sovereign-first: Ollama + Whisper + Piper on T4 GPU; Gemini development mode available | | Data tier | PostgreSQL (app) + Redis (session state, AOF) + SQLite (Project Ledger); GemStone is MCP client to remote Atlas Vault | | Primary env | T4 GoldenAMI EC2 Ohio `i-04333dae160ab0daa` | | Local secondary | NEW clean clone from `DataRightGoldenOVAFullBase` at `D:\Virtual Machines\DataRightGoldenOVAFullBase\` only; retire dirty GemStone VM `10.0.0.210` | | Repo | Build in `GemStone-Nexus-StackOne`; `DataRightAppBundle` is build machinery only | | Capacitor gate | First-class / atomic concurrency: a Capacitor build or test fail is a feature fail | | UI | Strict DataRightTailwind; login modeled on HorizonORBIT (HorizonCRM repo, clone at frontend stage) | | Naming | After first green GoldenAMI build, purge legacy product naming/imports/paths from the prior StackOne extraction | | Didymus ops | Practitioner provisioning of AI tool credentials per DIDYMUS-PLAYBOOK; architecture in DIDYMUS-ARCH-01 | ## 4. How This Document Set Is Organized This is DOC01 of 23 core docs, plus Amendments 1–2 and the executable references DOC26, DIDYMUS-ARCH-01, GS-MOB-01, and DIDYMUS-PLAYBOOK. DOC02 (SOW) and DOC03 (PRD) form the scope and technical backbone from which every other document derives. DOC06 (Master Prompt) is deliberately the last document in the build sequence, since it aggregates and references the full, completed set into Cursor-facing build instructions rather than standing alone. --- NEXTECH Business Technology Management LLC · nex-tech.biz · (941) 499-5505