gemstone-nexus · Phase 6

Ledger · ContextIndex

Table ContextIndex · all tables

idtopicsummarydetailsource_phasesource_tablesource_idembedding_id
16DIDYMUS-ARCH-01 DIDYMUS-ARCH-01 — Didymus Hub ArchitectureDIDYMUS-ARCH-01: DIDYMUS-ARCH-01 — Didymus Hub Architecture. Didymus is the AI-orchestration hub that registers build suggestions from AI tools and desktop workers, stores them under a schema-enforced approval gate, and presents every task through GemStone as the single universal approval surface. This document is the architecture reference named by DOCA1, DOC02 Phase 3C, and DOC06. Operator steps live in DIDYMUS-PLAYBOOK.md.# DIDYMUS-ARCH-01 — Didymus Hub Architecture *Worker contract, task storage, and MCP tool surface for GemStone integration* **Initiative:** GemStone · **Version:** v2.0 (Rewrite) · **Status:** Approved for Build · **Date:** July 21, 2026 ## 1. Purpose Didymus is the AI-orchestration hub that registers build suggestions from AI tools and desktop workers, stores them under a schema-enforced approval gate, and presents every task through GemStone as the single universal approval surface. This document is the architecture reference named by DOCA1, DOC02 Phase 3C, and DOC06. Operator steps live in DIDYMUS-PLAYBOOK.md. ## 2. Hybrid Topology ``` Workers (Cursor, Claude, Gemini, future Ollama/desktop) | submit_task / lease / report_status / verify_output v Didymus Hub (task store + lease coordinator + MCP tools) | | PENDING tasks projected identically v GemStone UI (universal approval surface; Auth0-gated) | | human sets approved_by + approved_at v Worker lease -> RUNNING -> COMPLETED/FAILED -> VERIFIED ``` GemStone never executes worker code itself at MVP. GemStone Agent may submit tasks (`requested_by="GemStone"`) but cannot approve them (DOC03 Section 7). ## 3. DidymusWorker Contract Every registered worker implements: | Method | Responsibility | | --- | --- | | `get_capabilities()` | Returns worker_id, tool family, supported task_types, max concurrency, tier affinity | | `execute_command(task)` | Runs only when task status is APPROVED and lease acquired; returns structured result | | `report_status(task_id)` | Heartbeat and progress; lease renewal | | `verify_output(task_id, result)` | Optional worker-side verification; GemStone may also verify | Workers that cannot implement the full contract are not registered. Capability claims are advisory; the hub enforces lease and status transitions. ## 4. Task Storage Model Logical table `didymus_tasks` (Postgres; mirrored summary rows may land in the SQLite Project Ledger for audit/UI): | Field | Rules | | --- | --- | | `id` | UUID PK | | `requested_by` | Human user_id or `"GemStone"` | | `target_worker` | Registered worker_id | | `task_type` | Allow-listed string | | `payload` | JSON; no secrets | | `status` | PENDING \| APPROVED \| RUNNING \| COMPLETED \| FAILED \| VERIFIED | | `approved_by` | NULL until human approval | | `approved_at` | NULL until human approval | | `org_id` | Required; RLS / query scoping | | `created_at` / `updated_at` | Timestamps | Schema constraints (mandatory): - CHECK: `status = 'RUNNING'` implies `approved_by IS NOT NULL AND approved_at IS NOT NULL` - No direct transition PENDING -> RUNNING - Lease claim is an atomic UPDATE that only succeeds when `status = 'APPROVED'` ## 5. State Machine Identical to DOC03 Section 6: ``` PENDING --(human approved_by + approved_at)--> APPROVED APPROVED --(worker lease)--> RUNNING RUNNING --(report)--> COMPLETED | FAILED COMPLETED --(verify)--> VERIFIED ``` Source never changes the path. Blind-source review: GemStone UI must not badge or color tasks by origin in the default queue view. ## 6. MCP Tool Surface Didymus Hub exposes MCP tools consumed by GemStone and registered workers: | Tool | Caller | Behavior | | --- | --- | --- | | `didymus.submit_task` | Workers, GemStone Agent | Creates PENDING task | | `didymus.list_pending` | GemStone UI | Org-scoped PENDING/APPROVED queue | | `didymus.approve_task` | Human roles only | Sets approved_by/approved_at; status APPROVED | | `didymus.lease_task` | Workers | Atomic lease into RUNNING | | `didymus.report_result` | Workers | COMPLETED/FAILED + payload | | `didymus.verify_task` | GemStone or worker | VERIFIED | Secrets and API keys never travel in MCP payloads; workers read credentials from the secrets tier (AWS Secrets Manager / host env) provisioned per DIDYMUS-PLAYBOOK. ## 7. GemStone Integration Points - Phase 3C API: `POST /api/didymus/tasks`, `POST /api/didymus/tasks/{id}/approve` (DOC03 Section 4). - Platform Dashboard Approval Queue view (DOC21). - Incident runbook if RUNNING without approval (DOC08 Section 3). - UAT: Universal Approval Queue script (DOC20). ## 8. MVP Worker Set | Worker | Family | Notes | | --- | --- | --- | | Cursor | IDE agent | PAT / API credential in secrets tier | | Claude | Cloud LLM agent | API key in secrets tier | | Gemini | Cloud LLM agent | API key in secrets tier | Deferred workers (DOC02 Section 3): Claude Code, AntiGravity, GemStone-as-worker runtime, SolidWorks, KiCad. Sovereign Ollama worker may be added under the same contract without changing the approval gate. ## 9. Security - Cross-org isolation on every list/approve/lease path. - Transcripts and session audio never appear in Didymus task payloads. - Western-origin stack constraints (DOC17) apply to any hub dependencies. --- NEXTECH Business Technology Management LLC · nex-tech.biz · (941) 499-5505 ProjectDocuments2
17DIDYMUS-ARCH-01 — OverviewDIDYMUS-ARCH-01 / Overview: # DIDYMUS-ARCH-01 — Didymus Hub Architecture *Worker contract, task storage, and MCP tool surface for GemStone integration* **Initiative:** GemStone · **Version:** v2.0 (Rewrite) · **Status:** Approved for Build · **Date:** July 21, 2026# DIDYMUS-ARCH-01 — Didymus Hub Architecture *Worker contract, task storage, and MCP tool surface for GemStone integration* **Initiative:** GemStone · **Version:** v2.0 (Rewrite) · **Status:** Approved for Build · **Date:** July 21, 2026ProjectDocuments2
18DIDYMUS-ARCH-01 — 1. PurposeDIDYMUS-ARCH-01 / 1. Purpose: Didymus is the AI-orchestration hub that registers build suggestions from AI tools and desktop workers, stores them under a schema-enforced approval gate, and presents every task through GemStone as the single universal approval surface. This document is the architecture reference named by DOCA1, DOC02 Phase 3C, and DOC06. Operator steps live in DIDYMUS-PLAYBOOK.md.Didymus is the AI-orchestration hub that registers build suggestions from AI tools and desktop workers, stores them under a schema-enforced approval gate, and presents every task through GemStone as the single universal approval surface. This document is the architecture reference named by DOCA1, DOC02 Phase 3C, and DOC06. Operator steps live in DIDYMUS-PLAYBOOK.md.ProjectDocuments2
19DIDYMUS-ARCH-01 — 2. Hybrid TopologyDIDYMUS-ARCH-01 / 2. Hybrid Topology: ``` Workers (Cursor, Claude, Gemini, future Ollama/desktop) | submit_task / lease / report_status / verify_output v Didymus Hub (task store + lease coordinator + MCP tools) | | PENDING tasks projected identically v GemStone UI (universal approval surface; Auth0-gated) | | human sets approved_by + approved_at v Worker lease -> RUNNI``` Workers (Cursor, Claude, Gemini, future Ollama/desktop) | submit_task / lease / report_status / verify_output v Didymus Hub (task store + lease coordinator + MCP tools) | | PENDING tasks projected identically v GemStone UI (universal approval surface; Auth0-gated) | | human sets approved_by + approved_at v Worker lease -> RUNNING -> COMPLETED/FAILED -> VERIFIED ``` GemStone never executes worker code itself at MVP. GemStone Agent may submit tasks (`requested_by="GemStone"`) but cannot approve them (DOC03 Section 7).ProjectDocuments2
20DIDYMUS-ARCH-01 — 3. DidymusWorker ContractDIDYMUS-ARCH-01 / 3. DidymusWorker Contract: Every registered worker implements: | Method | Responsibility | | --- | --- | | `get_capabilities()` | Returns worker_id, tool family, supported task_types, max concurrency, tier affinity | | `execute_command(task)` | Runs only when task status is APPROVED and lease acquired; returns structured result | | `report_status(task_id)` | Heartbeat and progress; lease renewal | | `verify_output(task_id,Every registered worker implements: | Method | Responsibility | | --- | --- | | `get_capabilities()` | Returns worker_id, tool family, supported task_types, max concurrency, tier affinity | | `execute_command(task)` | Runs only when task status is APPROVED and lease acquired; returns structured result | | `report_status(task_id)` | Heartbeat and progress; lease renewal | | `verify_output(task_id, result)` | Optional worker-side verification; GemStone may also verify | Workers that cannot implement the full contract are not registered. Capability claims are advisory; the hub enforces lease and status transitions.ProjectDocuments2
21DIDYMUS-ARCH-01 — 4. Task Storage ModelDIDYMUS-ARCH-01 / 4. Task Storage Model: Logical table `didymus_tasks` (Postgres; mirrored summary rows may land in the SQLite Project Ledger for audit/UI): | Field | Rules | | --- | --- | | `id` | UUID PK | | `requested_by` | Human user_id or `"GemStone"` | | `target_worker` | Registered worker_id | | `task_type` | Allow-listed string | | `payload` | JSON; no secrets | | `status` | PENDING \| APPROVED \| RUNNING \| COMPLETED \| FAILED Logical table `didymus_tasks` (Postgres; mirrored summary rows may land in the SQLite Project Ledger for audit/UI): | Field | Rules | | --- | --- | | `id` | UUID PK | | `requested_by` | Human user_id or `"GemStone"` | | `target_worker` | Registered worker_id | | `task_type` | Allow-listed string | | `payload` | JSON; no secrets | | `status` | PENDING \| APPROVED \| RUNNING \| COMPLETED \| FAILED \| VERIFIED | | `approved_by` | NULL until human approval | | `approved_at` | NULL until human approval | | `org_id` | Required; RLS / query scoping | | `created_at` / `updated_at` | Timestamps | Schema constraints (mandatory): - CHECK: `status = 'RUNNING'` implies `approved_by IS NOT NULL AND approved_at IS NOT NULL` - No direct transition PENDING -> RUNNING - Lease claim is an atomic UPDATE that only succeeds when `status = 'APPROVED'`ProjectDocuments2
22DIDYMUS-ARCH-01 — 5. State MachineDIDYMUS-ARCH-01 / 5. State Machine: Identical to DOC03 Section 6: ``` PENDING --(human approved_by + approved_at)--> APPROVED APPROVED --(worker lease)--> RUNNING RUNNING --(report)--> COMPLETED | FAILED COMPLETED --(verify)--> VERIFIED ``` Source never changes the path. Blind-source review: GemStone UI must not badge or color tasks by origin in the default queue view.Identical to DOC03 Section 6: ``` PENDING --(human approved_by + approved_at)--> APPROVED APPROVED --(worker lease)--> RUNNING RUNNING --(report)--> COMPLETED | FAILED COMPLETED --(verify)--> VERIFIED ``` Source never changes the path. Blind-source review: GemStone UI must not badge or color tasks by origin in the default queue view.ProjectDocuments2
23DIDYMUS-ARCH-01 — 6. MCP Tool SurfaceDIDYMUS-ARCH-01 / 6. MCP Tool Surface: Didymus Hub exposes MCP tools consumed by GemStone and registered workers: | Tool | Caller | Behavior | | --- | --- | --- | | `didymus.submit_task` | Workers, GemStone Agent | Creates PENDING task | | `didymus.list_pending` | GemStone UI | Org-scoped PENDING/APPROVED queue | | `didymus.approve_task` | Human roles only | Sets approved_by/approved_at; status APPROVED | | `didymus.lease_task` | WorkDidymus Hub exposes MCP tools consumed by GemStone and registered workers: | Tool | Caller | Behavior | | --- | --- | --- | | `didymus.submit_task` | Workers, GemStone Agent | Creates PENDING task | | `didymus.list_pending` | GemStone UI | Org-scoped PENDING/APPROVED queue | | `didymus.approve_task` | Human roles only | Sets approved_by/approved_at; status APPROVED | | `didymus.lease_task` | Workers | Atomic lease into RUNNING | | `didymus.report_result` | Workers | COMPLETED/FAILED + payload | | `didymus.verify_task` | GemStone or worker | VERIFIED | Secrets and API keys never travel in MCP payloads; workers read credentials from the secrets tier (AWS Secrets Manager / host env) provisioned per DIDYMUS-PLAYBOOK.ProjectDocuments2
24DIDYMUS-ARCH-01 — 7. GemStone Integration PointsDIDYMUS-ARCH-01 / 7. GemStone Integration Points: - Phase 3C API: `POST /api/didymus/tasks`, `POST /api/didymus/tasks/{id}/approve` (DOC03 Section 4). - Platform Dashboard Approval Queue view (DOC21). - Incident runbook if RUNNING without approval (DOC08 Section 3). - UAT: Universal Approval Queue script (DOC20).- Phase 3C API: `POST /api/didymus/tasks`, `POST /api/didymus/tasks/{id}/approve` (DOC03 Section 4). - Platform Dashboard Approval Queue view (DOC21). - Incident runbook if RUNNING without approval (DOC08 Section 3). - UAT: Universal Approval Queue script (DOC20).ProjectDocuments2
25DIDYMUS-ARCH-01 — 8. MVP Worker SetDIDYMUS-ARCH-01 / 8. MVP Worker Set: | Worker | Family | Notes | | --- | --- | --- | | Cursor | IDE agent | PAT / API credential in secrets tier | | Claude | Cloud LLM agent | API key in secrets tier | | Gemini | Cloud LLM agent | API key in secrets tier | Deferred workers (DOC02 Section 3): Claude Code, AntiGravity, GemStone-as-worker runtime, SolidWorks, KiCad. Sovereign Ollama worker may be added under the same contract without c| Worker | Family | Notes | | --- | --- | --- | | Cursor | IDE agent | PAT / API credential in secrets tier | | Claude | Cloud LLM agent | API key in secrets tier | | Gemini | Cloud LLM agent | API key in secrets tier | Deferred workers (DOC02 Section 3): Claude Code, AntiGravity, GemStone-as-worker runtime, SolidWorks, KiCad. Sovereign Ollama worker may be added under the same contract without changing the approval gate.ProjectDocuments2
26DIDYMUS-ARCH-01 — 9. SecurityDIDYMUS-ARCH-01 / 9. Security: - Cross-org isolation on every list/approve/lease path. - Transcripts and session audio never appear in Didymus task payloads. - Western-origin stack constraints (DOC17) apply to any hub dependencies. --- NEXTECH Business Technology Management LLC · nex-tech.biz · (941) 499-5505- Cross-org isolation on every list/approve/lease path. - Transcripts and session audio never appear in Didymus task payloads. - Western-origin stack constraints (DOC17) apply to any hub dependencies. --- NEXTECH Business Technology Management LLC · nex-tech.biz · (941) 499-5505ProjectDocuments2
27DIDYMUS-PLAYBOOK DIDYMUS-PLAYBOOK — Practitioner Provisioning and Queue OpsDIDYMUS-PLAYBOOK: DIDYMUS-PLAYBOOK — Practitioner Provisioning and Queue Ops. Operator and practitioner guide for provisioning AI development-tool workers, storing credentials in the secrets tier, registering workers with Didymus, and running the human approval queue. Architecture detail is in DIDYMUS-ARCH-01; this playbook is the how-to companion.# DIDYMUS-PLAYBOOK — Practitioner Provisioning and Queue Ops *Install, authorize, and operate Didymus AI workers through GemStone* **Initiative:** GemStone · **Version:** v2.0 (Rewrite) · **Status:** Phase 3C Implemented · **Date:** July 21, 2026 ## 1. Purpose Operator and practitioner guide for provisioning AI development-tool workers, storing credentials in the secrets tier, registering workers with Didymus, and running the human approval queue. Architecture detail is in DIDYMUS-ARCH-01; this playbook is the how-to companion. ## 2. Preconditions - Auth0 roles available: SuperAdmin, Org Admin, Practitioner (approvers); GemStone Agent may submit only (never approve). - Secrets tier ready: AWS Secrets Manager secret `DATARIGHT_DEV_SECRETS` (us-east-1) on GoldenAMI / EC2, **or** host `.env` injected into `gemstone-api` on the clean local FullBase clone. **Never commit secrets to the repo.** - Didymus runs in-process with GemStone API at Phase 3C (`DIDYMUS_HUB_URL` optional for a future external split; leave unset on the T4 host). - GemStone approval queue UI: `/app/didymus` (Capacitor + web). ## 3. Provision Workers (MVP) For each of **Cursor**, **Claude**, and **Gemini** (optional sovereign **Ollama**): 1. Create or identify the vendor account under the practitioner or org billing owner. 2. Generate the API key, PAT, or OAuth client secret required by that worker. 3. Store the secret in AWS Secrets Manager / host env under these exact keys (no repo files): | Worker | Env key(s) | Where to place | | --- | --- | --- | | Cursor | `DIDYMUS_WORKER_CURSOR_TOKEN` | `DATARIGHT_DEV_SECRETS` JSON field or compose `environment:` on `gemstone-api` | | Claude | `DIDYMUS_WORKER_CLAUDE_API_KEY` | same | | Gemini | `DIDYMUS_WORKER_GEMINI_API_KEY` (fallback: existing `GEMINI_API_KEY`) | same | | Ollama (optional) | `DIDYMUS_WORKER_OLLAMA_ENDPOINT` | e.g. `http://gemstone-ollama:11434` — omit to use simulated/local default | 4. Confirm the API container can read the key at process start (`docker exec gemstone-api printenv DIDYMUS_WORKER_CLAUDE_API_KEY` should print a non-empty value when provisioned). Values must never appear in task payloads, logs, or MCP arguments. 5. Install/authorize the worker runtime on the intended machine (Cursor IDE agent, Claude tooling, Gemini tooling, or Ollama service). Phase 3C hub workers implement `get_capabilities` / `execute_command` / `report_status` / `verify_output`; live vendor calls run when a matching **vault** key or host env key is present — otherwise execute is **simulated** so gates pass on sovereign hosts. ### 3.0 Practitioner vault (preferred for live execute) 1. Ensure host `.env` (never git) has `WORKER_SECRETS_KEY` (32-byte value, base64). Without it `GET /api/didymus/workers/credentials` reports `vault_available: false` and Connect in the UI will fail closed. 2. Sign in (local login when enabled) or use SuperAdmin/dev principal, open **`/app/onboarding/workers`**, Connect Cursor / Claude / Gemini keys. Values are AES-GCM sealed in `worker_credentials` (last-4 only returned). 3. Host env fallbacks (`DIDYMUS_WORKER_*` / `GEMINI_API_KEY`) still work for operators; Gemini Live voice key satisfies Gemini worker `credential_configured` when vault empty. 4. Confirm `GET /api/didymus/workers` / credentials show `configured: true`. Live path: approve → lease → `POST .../execute` with `worker_id` → `result.mode` is `live` or `simulated`. ### 3.1 Secrets placement (EC2 T4 / OD) ```text # Preferred: merge keys into DATARIGHT_DEV_SECRETS (us-east-1), then restart api # so app.core.secrets.load_aws_application_secrets picks them up. # Alternate: host override file (not git-tracked), e.g. /home/dr/AppDev/gemstone-nexus/.env.didymus DIDYMUS_WORKER_CURSOR_TOKEN=... DIDYMUS_WORKER_CLAUDE_API_KEY=... DIDYMUS_WORKER_GEMINI_API_KEY=... ``` Wire overrides into compose via an untracked env file or `environment:` block — do not add them to committed `docker-compose.yml` with real values. ### 3.2 Practitioner checklist (accounts) 1. **Cursor** — Settings → API / Account → create PAT with agent scopes; store as `DIDYMUS_WORKER_CURSOR_TOKEN`. 2. **Claude** — Anthropic Console → API Keys → create key; store as `DIDYMUS_WORKER_CLAUDE_API_KEY`. 3. **Gemini** — Google AI Studio / Cloud → API key; store as `DIDYMUS_WORKER_GEMINI_API_KEY` (or reuse stack `GEMINI_API_KEY` if already present for voice). 4. Confirm `GET /api/didymus/workers` shows `credential_configured: true` for each provisioned worker. ## 4. Register a Worker MVP workers (`cursor`, `claude`, `gemini`) auto-seed into `didymus_workers` for the default org on API startup. Manual / additional registration: ```bash curl -sS -X POST "http://127.0.0.1:8000/api/didymus/workers/register" \ -H "Content-Type: application/json" \ -H "X-Org-Id: 00000000-0000-4000-8000-000000000001" \ -d '{ "worker_id": "cursor", "family": "cursor", "display_name": "Cursor", "task_types": ["code_edit", "refactor", "generic"], "max_concurrency": 1, "tier_affinity": "any" }' ``` Or MCP: workers call `get_capabilities()` locally; hub stores the row via register. Map High Security workers so they do not call cloud-only paths (`tier_affinity` advisory at Phase 3C). Verify: ```bash curl -sS "http://127.0.0.1:8000/api/didymus/workers" -H "X-Org-Id: <org>" ``` Record registration in the Project Ledger (deploy note) without secret values. ## 5. Submit and Approve Tasks 1. Worker or GemStone Agent submits: - REST: `POST /api/didymus/tasks` `{requested_by, target_worker, task_type, payload}` → `PENDING` - MCP: `POST /mcp/didymus/submit_task` 2. Approver opens **`/app/didymus`**. Default cards are identical (blind-source). Audit metadata is behind an explicit expand — never used for color/badge styling. 3. Approver confirms intent → Approve → `approved_by` + `approved_at` set, status `APPROVED`. 4. Worker leases: `POST /api/didymus/tasks/{id}/lease` → `RUNNING`. `PENDING → RUNNING` returns **409**. Direct SQL/API force without approval fields hits **`didymus_tasks_approval_gate`** (schema CHECK). 5. Worker reports: `POST .../report` → `COMPLETED` | `FAILED`; verify → `VERIFIED`. 6. If a task ever reaches RUNNING without approval fields, execute DOC08 Section 3 immediately. ### 5.1 Example submit (three MVP sources) ```bash ORG=00000000-0000-4000-8000-000000000001 for pair in "cursor-agent|cursor" "claude-agent|claude" "gemini-agent|gemini"; do IFS='|' read -r BY W <<< "$pair" curl -sS -X POST "http://127.0.0.1:8000/api/didymus/tasks" \ -H "Content-Type: application/json" -H "X-Org-Id: $ORG" \ -d "{\"requested_by\":\"$BY\",\"target_worker\":\"$W\",\"task_type\":\"generic\",\"title\":\"Example from $W\",\"payload\":{\"summary\":\"Example from $W\"},\"org_id\":\"$ORG\"}" done ``` ## 6. Approval Queue Ops Checklist | Check | Pass criteria | | --- | --- | | Queue freshness | PENDING items visible within seconds of submit (`GET /api/didymus/tasks`) | | Org isolation | Approver never sees another org's tasks (RLS + `X-Org-Id`) | | Blind source | No origin badge/color in default view; `presentation.kind` always `didymus_task` | | Audit | Expand shows `requested_by` / `target_worker` without styling | | Schema gate | `POST .../force-running` returns `rejected: true, by: schema_constraint` | | Reject / leave PENDING | Leaving PENDING is safe; no auto-escalate to RUNNING | Gate script on host: `bash scripts/phase3c-gates.sh` (requires `gemstone-api` container). ## 7. Credential Rotation 1. Generate new secret at vendor. 2. Update secrets tier first; restart `gemstone-api` (and any external worker process) to pick up the new value. 3. Revoke the old secret at vendor. 4. Confirm `credential_configured: true` and a no-op lease/heartbeat still succeeds. 5. Log rotation in the Project Ledger without recording secret values. ## 8. Local vs Primary Env Notes - Primary: T4 GoldenAMI EC2 `i-04333dae160ab0daa` / `18.116.188.14` (production-like secrets via AWS Secrets Manager). - Local secondary: clean clone from `DataRightGoldenOVAFullBase` only; use host env / local secrets file, never the retired `10.0.0.210` GemStone VM. - Disk on T4 is tight (~3.5G free typical after Whisper CUDA) — prune carefully; keep Whisper CUDA images/models. - Social login testing (Google, Facebook, LinkedIn) uses the Auth0 tenant shared with the app; do not embed social app secrets in the mobile binary beyond Auth0 client config. ## 9. Auth0 Tenant Provisioning (practitioner checklist) **Do not invent or commit tenant credentials.** Placeholders (`AUTH0_*` / `VITE_AUTH0_*`) keep the stack bootable with `configured:false` on `/healthz` until a real tenant exists. ### 9.1 Create the Auth0 application 1. In the Auth0 dashboard, create (or select) a tenant for GemStone / NEXTECH. 2. Create a **Regular Web Application** for the Vite/Capacitor SPA (and optionally a Native app for store builds later). 3. Note **Domain**, **Client ID**, and (server-only) **Client Secret**. Never commit the secret; store it in AWS Secrets Manager / host `.env`. 4. Set **Allowed Callback URLs** to include: - `https://<host>/app/login` - Capacitor deep links when native builds are ready (`com.nextech.gemstone://...`) 5. Set **Allowed Logout URLs** and **Allowed Web Origins** to the same host origins (`https://<host>`, `https://<host>/app`). 6. Enable **Universal Login**. Connect social IdPs: Google, Facebook, LinkedIn (each requires its own vendor OAuth app; store those secrets in Auth0, not in this repo). ### 9.2 API / audience 1. Create an Auth0 **API** with identifier/audience matching `AUTH0_AUDIENCE` (e.g. `https://gemstone.dataright.net/api`). 2. Map roles per DOC03 Section 7: **SuperAdmin**, **Org Admin**, **Practitioner**, **GemStone Agent** (Auth0 Actions or Role claim). 3. Prefer org tenancy via Auth0 Organizations (`auth0_org_id` on `orgs`) when enabling multi-tenant login. ### 9.3 Wire into GemStone (after values exist) 1. Set host secrets (never git): - `AUTH0_DOMAIN`, `AUTH0_AUDIENCE`, `AUTH0_CLIENT_ID`, `AUTH0_CLIENT_SECRET`, `AUTH0_ISSUER`, `AUTH0_ENABLED=true` - `VITE_AUTH0_DOMAIN`, `VITE_AUTH0_CLIENT_ID` (rebuild `web` image after changing Vite args) 2. Redeploy: `.\scripts\run-remote-docker-deploy.ps1` 3. Confirm `/healthz` → `checks.auth0.configured: true` and login at `/app/login` reaches Universal Login. 4. Record completion in the Project Ledger (decision/deploy note) without secret values. ### 9.4 UX reference Login layout target remains **HorizonORBIT** from the **HorizonCRM** repo. Keep the Auth0 stub shell until HorizonCRM is cloned and the layout is ported under DataRightTailwind. ## 10. Out of Scope - Desktop SolidWorks / KiCad workers (DOC02 Section 3). - Autonomous execution of any task category. - Storing credentials in git, Capacitor bundled assets, or Didymus task JSON. - Claude Code / AntiGravity / GemStone-as-worker runtime (deferred until three-worker MVP stable 30+ days). --- NEXTECH Business Technology Management LLC · nex-tech.biz · (941) 499-5505 ProjectDocuments3
28DIDYMUS-PLAYBOOK — OverviewDIDYMUS-PLAYBOOK / Overview: # DIDYMUS-PLAYBOOK — Practitioner Provisioning and Queue Ops *Install, authorize, and operate Didymus AI workers through GemStone* **Initiative:** GemStone · **Version:** v2.0 (Rewrite) · **Status:** Phase 3C Implemented · **Date:** July 21, 2026# DIDYMUS-PLAYBOOK — Practitioner Provisioning and Queue Ops *Install, authorize, and operate Didymus AI workers through GemStone* **Initiative:** GemStone · **Version:** v2.0 (Rewrite) · **Status:** Phase 3C Implemented · **Date:** July 21, 2026ProjectDocuments3
29DIDYMUS-PLAYBOOK — 1. PurposeDIDYMUS-PLAYBOOK / 1. Purpose: Operator and practitioner guide for provisioning AI development-tool workers, storing credentials in the secrets tier, registering workers with Didymus, and running the human approval queue. Architecture detail is in DIDYMUS-ARCH-01; this playbook is the how-to companion.Operator and practitioner guide for provisioning AI development-tool workers, storing credentials in the secrets tier, registering workers with Didymus, and running the human approval queue. Architecture detail is in DIDYMUS-ARCH-01; this playbook is the how-to companion.ProjectDocuments3
30DIDYMUS-PLAYBOOK — 2. PreconditionsDIDYMUS-PLAYBOOK / 2. Preconditions: - Auth0 roles available: SuperAdmin, Org Admin, Practitioner (approvers); GemStone Agent may submit only (never approve). - Secrets tier ready: AWS Secrets Manager secret `DATARIGHT_DEV_SECRETS` (us-east-1) on GoldenAMI / EC2, **or** host `.env` injected into `gemstone-api` on the clean local FullBase clone. **Never commit secrets to the repo.** - Didymus runs in-process with GemStone API at Phase- Auth0 roles available: SuperAdmin, Org Admin, Practitioner (approvers); GemStone Agent may submit only (never approve). - Secrets tier ready: AWS Secrets Manager secret `DATARIGHT_DEV_SECRETS` (us-east-1) on GoldenAMI / EC2, **or** host `.env` injected into `gemstone-api` on the clean local FullBase clone. **Never commit secrets to the repo.** - Didymus runs in-process with GemStone API at Phase 3C (`DIDYMUS_HUB_URL` optional for a future external split; leave unset on the T4 host). - GemStone approval queue UI: `/app/didymus` (Capacitor + web).ProjectDocuments3
31DIDYMUS-PLAYBOOK — 3. Provision Workers (MVP)DIDYMUS-PLAYBOOK / 3. Provision Workers (MVP): For each of **Cursor**, **Claude**, and **Gemini** (optional sovereign **Ollama**): 1. Create or identify the vendor account under the practitioner or org billing owner. 2. Generate the API key, PAT, or OAuth client secret required by that worker. 3. Store the secret in AWS Secrets Manager / host env under these exact keys (no repo files): | Worker | Env key(s) | Where to place | | --- | --- | -For each of **Cursor**, **Claude**, and **Gemini** (optional sovereign **Ollama**): 1. Create or identify the vendor account under the practitioner or org billing owner. 2. Generate the API key, PAT, or OAuth client secret required by that worker. 3. Store the secret in AWS Secrets Manager / host env under these exact keys (no repo files): | Worker | Env key(s) | Where to place | | --- | --- | --- | | Cursor | `DIDYMUS_WORKER_CURSOR_TOKEN` | `DATARIGHT_DEV_SECRETS` JSON field or compose `environment:` on `gemstone-api` | | Claude | `DIDYMUS_WORKER_CLAUDE_API_KEY` | same | | Gemini | `DIDYMUS_WORKER_GEMINI_API_KEY` (fallback: existing `GEMINI_API_KEY`) | same | | Ollama (optional) | `DIDYMUS_WORKER_OLLAMA_ENDPOINT` | e.g. `http://gemstone-ollama:11434` — omit to use simulated/local default | 4. Confirm the API container can read the key at process start (`docker exec gemstone-api printenv DIDYMUS_WORKER_CLAUDE_API_KEY` should print a non-empty value when provisioned). Values must never appear in task payloads, logs, or MCP arguments. 5. Install/authorize the worker runtime on the intended machine (Cursor IDE agent, Claude tooling, Gemini tooling, or Ollama service). Phase 3C hub workers implement `get_capabilities` / `execute_command` / `report_status` / `verify_output`; live vendor calls run when a matching **vault** key or host env key is present — otherwise execute is **simulated** so gates pass on sovereign hosts. ### 3.0 Practitioner vault (preferred for live execute) 1. Ensure host `.env` (never git) has `WORKER_SECRETS_KEY` (32-byte value, base64). Without it `GET /api/didymus/workers/credentials` reports `vault_available: false` and Connect in the UI will fail closed. 2. Sign in (local login when enabled) or use SuperAdmin/dev principal, open **`/app/onboarding/workers`**, Connect Cursor / Claude / Gemini keys. Values are AES-GCM sealed in `worker_credentials` (last-4 only returned). 3. Host env fallbacks (`DIDYMUS_WORKER_*` / `GEMINI_API_KEY`) still work for operators; Gemini Live voice key satisfies Gemini worker `credential_configured` when vault empty. 4. Confirm `GET /api/didymus/workers` / credentials show `configured: true`. Live path: approve → lease → `POST .../execute` with `worker_id` → `result.mode` is `live` or `simulated`. ### 3.1 Secrets placement (EC2 T4 / OD) ```text # Preferred: merge keys into DATARIGHT_DEV_SECRETS (us-east-1), then restart api # so app.core.secrets.load_aws_application_secrets picks them up. # Alternate: host override file (not git-tracked), e.g. /home/dr/AppDev/gemstone-nexus/.env.didymus DIDYMUS_WORKER_CURSOR_TOKEN=... DIDYMUS_WORKER_CLAUDE_API_KEY=... DIDYMUS_WORKER_GEMINI_API_KEY=... ``` Wire overrides into compose via an untracked env file or `environment:` block — do not add them to committed `docker-compose.yml` with real values. ### 3.2 Practitioner checklist (accounts) 1. **Cursor** — Settings → API / Account → create PAT with agent scopes; store as `DIDYMUS_WORKER_CURSOR_TOKEN`. 2. **Claude** — Anthropic Console → API Keys → create key; store as `DIDYMUS_WORKER_CLAUDE_API_KEY`. 3. **Gemini** — Google AI Studio / Cloud → API key; store as `DIDYMUS_WORKER_GEMINI_API_KEY` (or reuse stack `GEMINI_API_KEY` if already present for voice). 4. Confirm `GET /api/didymus/workers` shows `credential_configured: true` for each provisioned worker.ProjectDocuments3
32DIDYMUS-PLAYBOOK — 4. Register a WorkerDIDYMUS-PLAYBOOK / 4. Register a Worker: MVP workers (`cursor`, `claude`, `gemini`) auto-seed into `didymus_workers` for the default org on API startup. Manual / additional registration: ```bash curl -sS -X POST "http://127.0.0.1:8000/api/didymus/workers/register" \ -H "Content-Type: application/json" \ -H "X-Org-Id: 00000000-0000-4000-8000-000000000001" \ -d '{ "worker_id": "cursor", "family": "cursor", "display_nameMVP workers (`cursor`, `claude`, `gemini`) auto-seed into `didymus_workers` for the default org on API startup. Manual / additional registration: ```bash curl -sS -X POST "http://127.0.0.1:8000/api/didymus/workers/register" \ -H "Content-Type: application/json" \ -H "X-Org-Id: 00000000-0000-4000-8000-000000000001" \ -d '{ "worker_id": "cursor", "family": "cursor", "display_name": "Cursor", "task_types": ["code_edit", "refactor", "generic"], "max_concurrency": 1, "tier_affinity": "any" }' ``` Or MCP: workers call `get_capabilities()` locally; hub stores the row via register. Map High Security workers so they do not call cloud-only paths (`tier_affinity` advisory at Phase 3C). Verify: ```bash curl -sS "http://127.0.0.1:8000/api/didymus/workers" -H "X-Org-Id: <org>" ``` Record registration in the Project Ledger (deploy note) without secret values.ProjectDocuments3
33DIDYMUS-PLAYBOOK — 5. Submit and Approve TasksDIDYMUS-PLAYBOOK / 5. Submit and Approve Tasks: 1. Worker or GemStone Agent submits: - REST: `POST /api/didymus/tasks` `{requested_by, target_worker, task_type, payload}` → `PENDING` - MCP: `POST /mcp/didymus/submit_task` 2. Approver opens **`/app/didymus`**. Default cards are identical (blind-source). Audit metadata is behind an explicit expand — never used for color/badge styling. 3. Approver confirms intent → Approve → `approved_by` + 1. Worker or GemStone Agent submits: - REST: `POST /api/didymus/tasks` `{requested_by, target_worker, task_type, payload}` → `PENDING` - MCP: `POST /mcp/didymus/submit_task` 2. Approver opens **`/app/didymus`**. Default cards are identical (blind-source). Audit metadata is behind an explicit expand — never used for color/badge styling. 3. Approver confirms intent → Approve → `approved_by` + `approved_at` set, status `APPROVED`. 4. Worker leases: `POST /api/didymus/tasks/{id}/lease` → `RUNNING`. `PENDING → RUNNING` returns **409**. Direct SQL/API force without approval fields hits **`didymus_tasks_approval_gate`** (schema CHECK). 5. Worker reports: `POST .../report` → `COMPLETED` | `FAILED`; verify → `VERIFIED`. 6. If a task ever reaches RUNNING without approval fields, execute DOC08 Section 3 immediately. ### 5.1 Example submit (three MVP sources) ```bash ORG=00000000-0000-4000-8000-000000000001 for pair in "cursor-agent|cursor" "claude-agent|claude" "gemini-agent|gemini"; do IFS='|' read -r BY W <<< "$pair" curl -sS -X POST "http://127.0.0.1:8000/api/didymus/tasks" \ -H "Content-Type: application/json" -H "X-Org-Id: $ORG" \ -d "{\"requested_by\":\"$BY\",\"target_worker\":\"$W\",\"task_type\":\"generic\",\"title\":\"Example from $W\",\"payload\":{\"summary\":\"Example from $W\"},\"org_id\":\"$ORG\"}" done ```ProjectDocuments3
34DIDYMUS-PLAYBOOK — 6. Approval Queue Ops ChecklistDIDYMUS-PLAYBOOK / 6. Approval Queue Ops Checklist: | Check | Pass criteria | | --- | --- | | Queue freshness | PENDING items visible within seconds of submit (`GET /api/didymus/tasks`) | | Org isolation | Approver never sees another org's tasks (RLS + `X-Org-Id`) | | Blind source | No origin badge/color in default view; `presentation.kind` always `didymus_task` | | Audit | Expand shows `requested_by` / `target_worker` without styling | | Schema ga| Check | Pass criteria | | --- | --- | | Queue freshness | PENDING items visible within seconds of submit (`GET /api/didymus/tasks`) | | Org isolation | Approver never sees another org's tasks (RLS + `X-Org-Id`) | | Blind source | No origin badge/color in default view; `presentation.kind` always `didymus_task` | | Audit | Expand shows `requested_by` / `target_worker` without styling | | Schema gate | `POST .../force-running` returns `rejected: true, by: schema_constraint` | | Reject / leave PENDING | Leaving PENDING is safe; no auto-escalate to RUNNING | Gate script on host: `bash scripts/phase3c-gates.sh` (requires `gemstone-api` container).ProjectDocuments3
35DIDYMUS-PLAYBOOK — 7. Credential RotationDIDYMUS-PLAYBOOK / 7. Credential Rotation: 1. Generate new secret at vendor. 2. Update secrets tier first; restart `gemstone-api` (and any external worker process) to pick up the new value. 3. Revoke the old secret at vendor. 4. Confirm `credential_configured: true` and a no-op lease/heartbeat still succeeds. 5. Log rotation in the Project Ledger without recording secret values.1. Generate new secret at vendor. 2. Update secrets tier first; restart `gemstone-api` (and any external worker process) to pick up the new value. 3. Revoke the old secret at vendor. 4. Confirm `credential_configured: true` and a no-op lease/heartbeat still succeeds. 5. Log rotation in the Project Ledger without recording secret values.ProjectDocuments3
36DIDYMUS-PLAYBOOK — 8. Local vs Primary Env NotesDIDYMUS-PLAYBOOK / 8. Local vs Primary Env Notes: - Primary: T4 GoldenAMI EC2 `i-04333dae160ab0daa` / `18.116.188.14` (production-like secrets via AWS Secrets Manager). - Local secondary: clean clone from `DataRightGoldenOVAFullBase` only; use host env / local secrets file, never the retired `10.0.0.210` GemStone VM. - Disk on T4 is tight (~3.5G free typical after Whisper CUDA) — prune carefully; keep Whisper CUDA images/models. - Social login te- Primary: T4 GoldenAMI EC2 `i-04333dae160ab0daa` / `18.116.188.14` (production-like secrets via AWS Secrets Manager). - Local secondary: clean clone from `DataRightGoldenOVAFullBase` only; use host env / local secrets file, never the retired `10.0.0.210` GemStone VM. - Disk on T4 is tight (~3.5G free typical after Whisper CUDA) — prune carefully; keep Whisper CUDA images/models. - Social login testing (Google, Facebook, LinkedIn) uses the Auth0 tenant shared with the app; do not embed social app secrets in the mobile binary beyond Auth0 client config.ProjectDocuments3
37DIDYMUS-PLAYBOOK — 9. Auth0 Tenant Provisioning (practitioner checklist)DIDYMUS-PLAYBOOK / 9. Auth0 Tenant Provisioning (practitioner checklist): **Do not invent or commit tenant credentials.** Placeholders (`AUTH0_*` / `VITE_AUTH0_*`) keep the stack bootable with `configured:false` on `/healthz` until a real tenant exists. ### 9.1 Create the Auth0 application 1. In the Auth0 dashboard, create (or select) a tenant for GemStone / NEXTECH. 2. Create a **Regular Web Application** for the Vite/Capacitor SPA (and optionally a Native app for st**Do not invent or commit tenant credentials.** Placeholders (`AUTH0_*` / `VITE_AUTH0_*`) keep the stack bootable with `configured:false` on `/healthz` until a real tenant exists. ### 9.1 Create the Auth0 application 1. In the Auth0 dashboard, create (or select) a tenant for GemStone / NEXTECH. 2. Create a **Regular Web Application** for the Vite/Capacitor SPA (and optionally a Native app for store builds later). 3. Note **Domain**, **Client ID**, and (server-only) **Client Secret**. Never commit the secret; store it in AWS Secrets Manager / host `.env`. 4. Set **Allowed Callback URLs** to include: - `https://<host>/app/login` - Capacitor deep links when native builds are ready (`com.nextech.gemstone://...`) 5. Set **Allowed Logout URLs** and **Allowed Web Origins** to the same host origins (`https://<host>`, `https://<host>/app`). 6. Enable **Universal Login**. Connect social IdPs: Google, Facebook, LinkedIn (each requires its own vendor OAuth app; store those secrets in Auth0, not in this repo). ### 9.2 API / audience 1. Create an Auth0 **API** with identifier/audience matching `AUTH0_AUDIENCE` (e.g. `https://gemstone.dataright.net/api`). 2. Map roles per DOC03 Section 7: **SuperAdmin**, **Org Admin**, **Practitioner**, **GemStone Agent** (Auth0 Actions or Role claim). 3. Prefer org tenancy via Auth0 Organizations (`auth0_org_id` on `orgs`) when enabling multi-tenant login. ### 9.3 Wire into GemStone (after values exist) 1. Set host secrets (never git): - `AUTH0_DOMAIN`, `AUTH0_AUDIENCE`, `AUTH0_CLIENT_ID`, `AUTH0_CLIENT_SECRET`, `AUTH0_ISSUER`, `AUTH0_ENABLED=true` - `VITE_AUTH0_DOMAIN`, `VITE_AUTH0_CLIENT_ID` (rebuild `web` image after changing Vite args) 2. Redeploy: `.\scripts\run-remote-docker-deploy.ps1` 3. Confirm `/healthz` → `checks.auth0.configured: true` and login at `/app/login` reaches Universal Login. 4. Record completion in the Project Ledger (decision/deploy note) without secret values. ### 9.4 UX reference Login layout target remains **HorizonORBIT** from the **HorizonCRM** repo. Keep the Auth0 stub shell until HorizonCRM is cloned and the layout is ported under DataRightTailwind.ProjectDocuments3
38DIDYMUS-PLAYBOOK — 10. Out of ScopeDIDYMUS-PLAYBOOK / 10. Out of Scope: - Desktop SolidWorks / KiCad workers (DOC02 Section 3). - Autonomous execution of any task category. - Storing credentials in git, Capacitor bundled assets, or Didymus task JSON. - Claude Code / AntiGravity / GemStone-as-worker runtime (deferred until three-worker MVP stable 30+ days). --- NEXTECH Business Technology Management LLC · nex-tech.biz · (941) 499-5505- Desktop SolidWorks / KiCad workers (DOC02 Section 3). - Autonomous execution of any task category. - Storing credentials in git, Capacitor bundled assets, or Didymus task JSON. - Claude Code / AntiGravity / GemStone-as-worker runtime (deferred until three-worker MVP stable 30+ days). --- NEXTECH Business Technology Management LLC · nex-tech.biz · (941) 499-5505ProjectDocuments3
39DOC-AWS-SMS-RECOVERY DOC-AWS-SMS-RecoveryDOC-AWS-SMS-RECOVERY: DOC-AWS-SMS-Recovery. Agent “text me” uses **Amazon SNS SMS**. The account is still in the **SNS SMS sandbox**. Destination `+14193063078` is stuck **Pending** (OTP never completed). US carriers often filter SNS sandbox short-code OTPs. **Delete/recreate of that sandbox number is blocked for 24h after create** — do not keep resending doomed OTPs to the same number.# DOC-AWS-SMS-Recovery **Account:** `209457336992` · **Region:** `us-east-1` · **Updated:** 2026-07-22 **Policy:** Never Twilio. Prefer SES email notify until SMS production path works. Do not take down `gemstone.dataright.net`. ## Root cause (why SMS lingered) Agent “text me” uses **Amazon SNS SMS**. The account is still in the **SNS SMS sandbox**. Destination `+14193063078` is stuck **Pending** (OTP never completed). US carriers often filter SNS sandbox short-code OTPs. **Delete/recreate of that sandbox number is blocked for 24h after create** — do not keep resending doomed OTPs to the same number. Parallel path **AWS End User Messaging (EUM) toll-free** `+18447531062` is **PENDING** because registration `registration-19835bd2d54e4914893a45181f098dd3` (`US_TOLL_FREE_REGISTRATION`) is **REQUIRES_UPDATES** after denied **v3**. **SES email notify works** (verified recipients include `mfuriate@nex-tech.biz`, `mfuriate@gmail.com`). Use email until SMS is fixed. ## EUM denial (exact) | Version | Status | Reason | |---------|--------|--------| | v1 | DENIED | Missing conditional field | | v2 | DENIED | Missing required field | | v3 | DENIED | **Business Registration Document Required** | | v4 | **DRAFT** (opened 2026-07-22) | Not submitted — waiting on Mark | ### v3 denial (carrier) > Your company identification number could not be independently verified by the carrier. To resolve this, upload an official business registration document (such as Articles of Incorporation, Certificate of Formation, or equivalent government-issued document) in the **Business Registration Document** field of the Company Info section, or update your company identification number if it was entered incorrectly. After making your changes, resubmit your registration. Docs: [Registering your toll-free number](https://docs.aws.amazon.com/sms-voice/latest/userguide/registrations-tfn-register.html) ### Field gaps vs what AWS wants | Field path | Status on denied v3 / draft v4 | Action | |------------|--------------------------------|--------| | `companyInfo.businessRegistrationDoc` | **Missing** (required by denial) | Mark uploads PDF/PNG/JPEG Articles / Certificate of Formation | | `companyInfo.taxId` | **Missing** (never successfully set; v1 had empty/denied) | Mark sets correct EIN | | `companyInfo.taxIdAuthority` | **Missing** | Set `EIN` | | `companyInfo.taxIdCountry` | **Missing** | Set `US` | | `companyInfo.businessType` | Was `SOLE_PROPRIETOR` on v3 (wrong for LLC) | **Fixed on draft v4 → `PRIVATE_PROFIT`** | | Company / contact / use-case / samples / opt-in image | Present on draft v4 (restored from v3) | Review; tweak only if inaccurate | **CLI cannot finish resubmit** without Mark’s EIN and business registration document file. Do not invent tax IDs or upload placeholder docs. ### Draft v4 (agent prep done) - Registration ID: `registration-19835bd2d54e4914893a45181f098dd3` - Toll-free phone ID: `phone-c8c26941520647f8ad840e9a54c1c589` (`+18447531062`, PENDING) - Opt-in attachment already uploaded: `attachment-9c98f8e16ee748e4ab8c47bbc76518ea` After Mark supplies EIN + registration PDF: ```powershell # Upload doc (example paths — Mark provides file) aws pinpoint-sms-voice-v2 create-registration-attachment --region us-east-1 --attachment-body fileb://C:\path\to\CertificateOfFormation.pdf # Then put fields (use returned attachment id; never echo taxId in chat logs) aws pinpoint-sms-voice-v2 put-registration-field-value --registration-id registration-19835bd2d54e4914893a45181f098dd3 --field-path companyInfo.taxIdAuthority --select-choices EIN --region us-east-1 aws pinpoint-sms-voice-v2 put-registration-field-value --registration-id registration-19835bd2d54e4914893a45181f098dd3 --field-path companyInfo.taxIdCountry --text-value US --region us-east-1 aws pinpoint-sms-voice-v2 put-registration-field-value --registration-id registration-19835bd2d54e4914893a45181f098dd3 --field-path companyInfo.taxId --text-value "<EIN>" --region us-east-1 aws pinpoint-sms-voice-v2 put-registration-field-value --registration-id registration-19835bd2d54e4914893a45181f098dd3 --field-path companyInfo.businessRegistrationDoc --registration-attachment-id attachment-XXXXXXXX --region us-east-1 aws pinpoint-sms-voice-v2 submit-registration-version --registration-id registration-19835bd2d54e4914893a45181f098dd3 --region us-east-1 ``` Or complete the same fields in console: **AWS End User Messaging → Configurations → Registrations** → open the REQUIRES_UPDATES registration → edit draft → submit. ## SNS sandbox → production - `get-sms-sandbox-account-status` → `IsInSandbox: true` - Sandbox destination `+14193063078` → **Pending**; opt-out **false** - There is **no CLI** to exit the SMS sandbox. Support API requires Premium Support (not enabled). Console creates the case. ### Console path (Mark) 1. https://console.aws.amazon.com/sns/v3/home?region=us-east-1#/mobile/text-messaging 2. Under **Account information** → **Exit SMS sandbox** (opens Support / Service quota increase). 3. Form answers for **DataRight agent alerts** (transactional, low volume): | Field | Recommended answer | |-------|-------------------| | Service | SNS Text Messaging | | Website / app | https://dataright.net (OmniFlowCRM / DataRight agent status alerts) | | Message type | **Transactional** (not promotional) | | Region | **us-east-1** | | Countries | United States | | Opt-in | Internal operator (Mark) explicitly requests SMS notify for agent/job completion; not marketing blast; STOP/HELP supported where applicable | | Message templates | `DataRight: Ready — <short status one-liner>` / `DataRight agent: <blocker one-liner>` | | Use case detail | Low-volume transactional alerts from Cursor/DataRight ops agents to an authenticated operator phone; expected volume tens–low hundreds SMS/month | | New limit | Request production access / raise monthly SMS spend as needed | **Note:** AWS docs also expect at least one **Verified** sandbox destination and a successful test SMS before approval. With `+141******3078` stuck Pending, either wait out delete cooldown and re-verify, or add a **second** sandbox number Mark provides (agent must not invent a number). ### Related quota (submitted 2026-07-22) - Service Quotas request **SMS Message Spending in USD** `L-BCD4AAF3`: **$1 → $10**, status **CASE_OPENED**, case `178473400100660`. - This raises spend ceiling; it is **not** the same as exiting the SMS sandbox. Mark still must run **Exit SMS sandbox** in console. ## Delivery logging (done 2026-07-22) Enabled SNS SMS delivery status → CloudWatch Logs: - IAM role: `arn:aws:iam::209457336992:role/SNSSuccessFeedback` - Attributes: `DeliveryStatusIAMRole` set; `DeliveryStatusSuccessSamplingRate=100`; `MonthlySpendLimit=1` (until quota increase approved) Inspect after next SMS attempt: CloudWatch log groups `sns/us-east-1/.../DirectPublishToPhoneNumber` (success/failure). Carriers can delay log appearance up to ~72h. ## Secrets (names only) `DATARIGHT_DEV_SECRETS`: `AWS_EUM`, `AWS_EUM_SMS_NUMBER`, `AWS_EUM_SMS_PHONE_ID`, `AWS_SNS_REGION` (+ `SES_FROM_EMAIL` for email path). Never print values. ## Mark actions (ordered) 1. **Use SES email** for agent notify until SMS works (`mfuriate@nex-tech.biz` / `mfuriate@gmail.com`). 2. **EUM v4:** Provide EIN + official business registration PDF → put `taxId` / `taxIdAuthority=EIN` / `taxIdCountry=US` / `businessRegistrationDoc` → **submit** draft v4. 3. **SNS Exit SMS sandbox** via console form (answers above); optionally reply on spend case `178473400100660`. 4. **Sandbox number:** Do **not** keep OTP-spamming `+141******3078` while delete cooldown blocks reset. After cooldown, delete + recreate **or** give agent a **second** E.164 to verify. 5. After production / verified destination: send one short test SMS; confirm CloudWatch delivery logs. 6. Only then point agent notify / secrets at a working origination path (SNS production and/or registered EUM toll-free). ## Never - Twilio - Print secret values or full tax IDs in chat/logs - Spam SMS / marketing - Treat EUM PENDING toll-free as working agent SMS path - Take down production GemStone hosts for SMS work ProjectDocuments4
40DOC-AWS-SMS-RECOVERY — OverviewDOC-AWS-SMS-RECOVERY / Overview: # DOC-AWS-SMS-Recovery **Account:** `209457336992` · **Region:** `us-east-1` · **Updated:** 2026-07-22 **Policy:** Never Twilio. Prefer SES email notify until SMS production path works. Do not take down `gemstone.dataright.net`.# DOC-AWS-SMS-Recovery **Account:** `209457336992` · **Region:** `us-east-1` · **Updated:** 2026-07-22 **Policy:** Never Twilio. Prefer SES email notify until SMS production path works. Do not take down `gemstone.dataright.net`.ProjectDocuments4
41DOC-AWS-SMS-RECOVERY — Root cause (why SMS lingered)DOC-AWS-SMS-RECOVERY / Root cause (why SMS lingered): Agent “text me” uses **Amazon SNS SMS**. The account is still in the **SNS SMS sandbox**. Destination `+14193063078` is stuck **Pending** (OTP never completed). US carriers often filter SNS sandbox short-code OTPs. **Delete/recreate of that sandbox number is blocked for 24h after create** — do not keep resending doomed OTPs to the same number. Parallel path **AWS End User Messaging (EUM) toll-freAgent “text me” uses **Amazon SNS SMS**. The account is still in the **SNS SMS sandbox**. Destination `+14193063078` is stuck **Pending** (OTP never completed). US carriers often filter SNS sandbox short-code OTPs. **Delete/recreate of that sandbox number is blocked for 24h after create** — do not keep resending doomed OTPs to the same number. Parallel path **AWS End User Messaging (EUM) toll-free** `+18447531062` is **PENDING** because registration `registration-19835bd2d54e4914893a45181f098dd3` (`US_TOLL_FREE_REGISTRATION`) is **REQUIRES_UPDATES** after denied **v3**. **SES email notify works** (verified recipients include `mfuriate@nex-tech.biz`, `mfuriate@gmail.com`). Use email until SMS is fixed.ProjectDocuments4
42DOC-AWS-SMS-RECOVERY — EUM denial (exact)DOC-AWS-SMS-RECOVERY / EUM denial (exact): | Version | Status | Reason | |---------|--------|--------| | v1 | DENIED | Missing conditional field | | v2 | DENIED | Missing required field | | v3 | DENIED | **Business Registration Document Required** | | v4 | **DRAFT** (opened 2026-07-22) | Not submitted — waiting on Mark | ### v3 denial (carrier) > Your company identification number could not be independently verified by the carrier. To re| Version | Status | Reason | |---------|--------|--------| | v1 | DENIED | Missing conditional field | | v2 | DENIED | Missing required field | | v3 | DENIED | **Business Registration Document Required** | | v4 | **DRAFT** (opened 2026-07-22) | Not submitted — waiting on Mark | ### v3 denial (carrier) > Your company identification number could not be independently verified by the carrier. To resolve this, upload an official business registration document (such as Articles of Incorporation, Certificate of Formation, or equivalent government-issued document) in the **Business Registration Document** field of the Company Info section, or update your company identification number if it was entered incorrectly. After making your changes, resubmit your registration. Docs: [Registering your toll-free number](https://docs.aws.amazon.com/sms-voice/latest/userguide/registrations-tfn-register.html) ### Field gaps vs what AWS wants | Field path | Status on denied v3 / draft v4 | Action | |------------|--------------------------------|--------| | `companyInfo.businessRegistrationDoc` | **Missing** (required by denial) | Mark uploads PDF/PNG/JPEG Articles / Certificate of Formation | | `companyInfo.taxId` | **Missing** (never successfully set; v1 had empty/denied) | Mark sets correct EIN | | `companyInfo.taxIdAuthority` | **Missing** | Set `EIN` | | `companyInfo.taxIdCountry` | **Missing** | Set `US` | | `companyInfo.businessType` | Was `SOLE_PROPRIETOR` on v3 (wrong for LLC) | **Fixed on draft v4 → `PRIVATE_PROFIT`** | | Company / contact / use-case / samples / opt-in image | Present on draft v4 (restored from v3) | Review; tweak only if inaccurate | **CLI cannot finish resubmit** without Mark’s EIN and business registration document file. Do not invent tax IDs or upload placeholder docs. ### Draft v4 (agent prep done) - Registration ID: `registration-19835bd2d54e4914893a45181f098dd3` - Toll-free phone ID: `phone-c8c26941520647f8ad840e9a54c1c589` (`+18447531062`, PENDING) - Opt-in attachment already uploaded: `attachment-9c98f8e16ee748e4ab8c47bbc76518ea` After Mark supplies EIN + registration PDF: ```powershell # Upload doc (example paths — Mark provides file) aws pinpoint-sms-voice-v2 create-registration-attachment --region us-east-1 --attachment-body fileb://C:\path\to\CertificateOfFormation.pdf # Then put fields (use returned attachment id; never echo taxId in chat logs) aws pinpoint-sms-voice-v2 put-registration-field-value --registration-id registration-19835bd2d54e4914893a45181f098dd3 --field-path companyInfo.taxIdAuthority --select-choices EIN --region us-east-1 aws pinpoint-sms-voice-v2 put-registration-field-value --registration-id registration-19835bd2d54e4914893a45181f098dd3 --field-path companyInfo.taxIdCountry --text-value US --region us-east-1 aws pinpoint-sms-voice-v2 put-registration-field-value --registration-id registration-19835bd2d54e4914893a45181f098dd3 --field-path companyInfo.taxId --text-value "<EIN>" --region us-east-1 aws pinpoint-sms-voice-v2 put-registration-field-value --registration-id registration-19835bd2d54e4914893a45181f098dd3 --field-path companyInfo.businessRegistrationDoc --registration-attachment-id attachment-XXXXXXXX --region us-east-1 aws pinpoint-sms-voice-v2 submit-registration-version --registration-id registration-19835bd2d54e4914893a45181f098dd3 --region us-east-1 ``` Or complete the same fields in console: **AWS End User Messaging → Configurations → Registrations** → open the REQUIRES_UPDATES registration → edit draft → submit.ProjectDocuments4
43DOC-AWS-SMS-RECOVERY — SNS sandbox → productionDOC-AWS-SMS-RECOVERY / SNS sandbox → production: - `get-sms-sandbox-account-status` → `IsInSandbox: true` - Sandbox destination `+14193063078` → **Pending**; opt-out **false** - There is **no CLI** to exit the SMS sandbox. Support API requires Premium Support (not enabled). Console creates the case. ### Console path (Mark) 1. https://console.aws.amazon.com/sns/v3/home?region=us-east-1#/mobile/text-messaging 2. Under **Account information** →- `get-sms-sandbox-account-status` → `IsInSandbox: true` - Sandbox destination `+14193063078` → **Pending**; opt-out **false** - There is **no CLI** to exit the SMS sandbox. Support API requires Premium Support (not enabled). Console creates the case. ### Console path (Mark) 1. https://console.aws.amazon.com/sns/v3/home?region=us-east-1#/mobile/text-messaging 2. Under **Account information** → **Exit SMS sandbox** (opens Support / Service quota increase). 3. Form answers for **DataRight agent alerts** (transactional, low volume): | Field | Recommended answer | |-------|-------------------| | Service | SNS Text Messaging | | Website / app | https://dataright.net (OmniFlowCRM / DataRight agent status alerts) | | Message type | **Transactional** (not promotional) | | Region | **us-east-1** | | Countries | United States | | Opt-in | Internal operator (Mark) explicitly requests SMS notify for agent/job completion; not marketing blast; STOP/HELP supported where applicable | | Message templates | `DataRight: Ready — <short status one-liner>` / `DataRight agent: <blocker one-liner>` | | Use case detail | Low-volume transactional alerts from Cursor/DataRight ops agents to an authenticated operator phone; expected volume tens–low hundreds SMS/month | | New limit | Request production access / raise monthly SMS spend as needed | **Note:** AWS docs also expect at least one **Verified** sandbox destination and a successful test SMS before approval. With `+141******3078` stuck Pending, either wait out delete cooldown and re-verify, or add a **second** sandbox number Mark provides (agent must not invent a number). ### Related quota (submitted 2026-07-22) - Service Quotas request **SMS Message Spending in USD** `L-BCD4AAF3`: **$1 → $10**, status **CASE_OPENED**, case `178473400100660`. - This raises spend ceiling; it is **not** the same as exiting the SMS sandbox. Mark still must run **Exit SMS sandbox** in console.ProjectDocuments4
44DOC-AWS-SMS-RECOVERY — Delivery logging (done 2026-07-22)DOC-AWS-SMS-RECOVERY / Delivery logging (done 2026-07-22): Enabled SNS SMS delivery status → CloudWatch Logs: - IAM role: `arn:aws:iam::209457336992:role/SNSSuccessFeedback` - Attributes: `DeliveryStatusIAMRole` set; `DeliveryStatusSuccessSamplingRate=100`; `MonthlySpendLimit=1` (until quota increase approved) Inspect after next SMS attempt: CloudWatch log groups `sns/us-east-1/.../DirectPublishToPhoneNumber` (success/failure). Carriers can delay log apEnabled SNS SMS delivery status → CloudWatch Logs: - IAM role: `arn:aws:iam::209457336992:role/SNSSuccessFeedback` - Attributes: `DeliveryStatusIAMRole` set; `DeliveryStatusSuccessSamplingRate=100`; `MonthlySpendLimit=1` (until quota increase approved) Inspect after next SMS attempt: CloudWatch log groups `sns/us-east-1/.../DirectPublishToPhoneNumber` (success/failure). Carriers can delay log appearance up to ~72h.ProjectDocuments4
45DOC-AWS-SMS-RECOVERY — Secrets (names only)DOC-AWS-SMS-RECOVERY / Secrets (names only): `DATARIGHT_DEV_SECRETS`: `AWS_EUM`, `AWS_EUM_SMS_NUMBER`, `AWS_EUM_SMS_PHONE_ID`, `AWS_SNS_REGION` (+ `SES_FROM_EMAIL` for email path). Never print values.`DATARIGHT_DEV_SECRETS`: `AWS_EUM`, `AWS_EUM_SMS_NUMBER`, `AWS_EUM_SMS_PHONE_ID`, `AWS_SNS_REGION` (+ `SES_FROM_EMAIL` for email path). Never print values.ProjectDocuments4
46DOC-AWS-SMS-RECOVERY — Mark actions (ordered)DOC-AWS-SMS-RECOVERY / Mark actions (ordered): 1. **Use SES email** for agent notify until SMS works (`mfuriate@nex-tech.biz` / `mfuriate@gmail.com`). 2. **EUM v4:** Provide EIN + official business registration PDF → put `taxId` / `taxIdAuthority=EIN` / `taxIdCountry=US` / `businessRegistrationDoc` → **submit** draft v4. 3. **SNS Exit SMS sandbox** via console form (answers above); optionally reply on spend case `178473400100660`. 4. **S1. **Use SES email** for agent notify until SMS works (`mfuriate@nex-tech.biz` / `mfuriate@gmail.com`). 2. **EUM v4:** Provide EIN + official business registration PDF → put `taxId` / `taxIdAuthority=EIN` / `taxIdCountry=US` / `businessRegistrationDoc` → **submit** draft v4. 3. **SNS Exit SMS sandbox** via console form (answers above); optionally reply on spend case `178473400100660`. 4. **Sandbox number:** Do **not** keep OTP-spamming `+141******3078` while delete cooldown blocks reset. After cooldown, delete + recreate **or** give agent a **second** E.164 to verify. 5. After production / verified destination: send one short test SMS; confirm CloudWatch delivery logs. 6. Only then point agent notify / secrets at a working origination path (SNS production and/or registered EUM toll-free).ProjectDocuments4
47DOC-AWS-SMS-RECOVERY — NeverDOC-AWS-SMS-RECOVERY / Never: - Twilio - Print secret values or full tax IDs in chat/logs - Spam SMS / marketing - Treat EUM PENDING toll-free as working agent SMS path - Take down production GemStone hosts for SMS work- Twilio - Print secret values or full tax IDs in chat/logs - Spam SMS / marketing - Treat EUM PENDING toll-free as working agent SMS path - Take down production GemStone hosts for SMS workProjectDocuments4
65DOC-AUTH0-PROVISIONING DOC — Auth0 Provisioning (Phase 0 → production closeout)DOC-AUTH0-PROVISIONING: DOC — Auth0 Provisioning (Phase 0 → production closeout). On punchlist (`DOC07-Punchlist.md` § Deferred). No live Auth0 credentials exist in AWS Secrets Manager or on the T4 host. Stack remains bootable with placeholders. **Phases 0–5 and production prep continue without a live tenant**; `/healthz` already allows `auth0.configured: false`.# DOC — Auth0 Provisioning (Phase 0 → production closeout) **Status (2026-07-21):** **DEFERRED — non-blocking for engineering.** On punchlist (`DOC07-Punchlist.md` § Deferred). No live Auth0 credentials exist in AWS Secrets Manager or on the T4 host. Stack remains bootable with placeholders. **Phases 0–5 and production prep continue without a live tenant**; `/healthz` already allows `auth0.configured: false`. **Audience:** Practitioner standing up Auth0 for GemStone on the T4 EC2 / local Golden clone. **Companion:** `DIDYMUS-PLAYBOOK.md` §9 (same steps), `DOC-Deploy-Pipeline.md`, `.env.example`, punchlist Auth0 row. ## Verification snapshot (automatable — done) | Check | Result | |-------|--------| | `DATARIGHT_DEV_SECRETS` (us-east-1 / us-east-2) | **No** `AUTH0_*` / `VITE_AUTH0_*` keys (21 keys total; `AUTH_TOKEN_SECRET` is unrelated) | | Sibling secrets (`Labs4You*`, `RusticRavinesSecrets`, `SagePeak_Dev_Secrets`) | **No** Auth0 keys | | EC2 `/home/dr/AppDev/gemstone-nexus/.env` | Keys declared; **all credential values empty**; `AUTH0_ENABLED=false` | | `GET https://18.116.188.14/healthz` → `checks.auth0` | `configured: false`, detail `AUTH0_DOMAIN/AUDIENCE placeholders — tenant TBD` | Wiring and Management API automation are **not possible** until Mark creates a tenant and stores secrets. ## Exact human actions (Mark) ### 1. Create Auth0 tenant + app + API 1. Sign up / log in at [https://auth0.com](https://auth0.com) (free or paid tenant is fine for closeout). 2. Create a **Regular Web Application** (name e.g. `GemStone Nexus`). 3. Create an **API** with Identifier/Audience, e.g. `https://gemstone.dataright.net/api` (this string becomes `AUTH0_AUDIENCE`). 4. Note from the Application settings: - Domain → `AUTH0_DOMAIN` / `VITE_AUTH0_DOMAIN` (e.g. `your-tenant.us.auth0.com`) - Client ID → `AUTH0_CLIENT_ID` / `VITE_AUTH0_CLIENT_ID` - Client Secret → `AUTH0_CLIENT_SECRET` 5. Set Application URIs (adjust if public URL differs): - Allowed Callback URLs: `https://18.116.188.14/app/callback`, `https://gemstone.dataright.net/app/callback`, `http://localhost:5173/app/callback` - Allowed Logout URLs: `https://18.116.188.14/`, `https://gemstone.dataright.net/`, `http://localhost:5173/` - Allowed Web Origins: same origins as above (no path) ### 2. Social connections + roles 1. Enable **Universal Login**. 2. Enable social connections: **Google**, **Facebook**, **LinkedIn** (developer consoles + Auth0 connection setup). 3. Define Auth0 roles (DOC03 §7): `SuperAdmin`, `Org Admin`, `Practitioner`, `GemStone Agent`. 4. (Optional) Auth0 Organizations → map to `orgs.auth0_org_id` + Postgres RLS GUC `app.current_org_id`. ### 3. Store secrets (required before agent can wire EC2) Update AWS Secrets Manager secret **`DATARIGHT_DEV_SECRETS`** (region **us-east-1**; mirror to us-east-2 if that copy is kept in sync) with these **exact key names** (string values, no placeholders): ```text AUTH0_DOMAIN AUTH0_AUDIENCE AUTH0_CLIENT_ID AUTH0_CLIENT_SECRET AUTH0_ISSUER # usually https://<AUTH0_DOMAIN>/ AUTH0_ENABLED # true VITE_AUTH0_DOMAIN VITE_AUTH0_CLIENT_ID ``` **Do not** commit these to git. Host `.env` is filled from Secrets Manager / deploy scripts. ### 4. Reply in chat when ready Tell the agent: **“Auth0 secrets are in DATARIGHT_DEV_SECRETS”** (no need to paste values). Next agent turn will: pull keys → write EC2 `.env` → recreate `api` (+ rebuild `web` for Vite args) → verify `/healthz` `auth0.configured: true` → optional token smoke. ## Why placeholders are intentional until then `/healthz` reports `auth0.configured: false` when `AUTH0_DOMAIN` / `AUTH0_AUDIENCE` are empty. That is **not** a Phase 0 failure and **does not block** Atlas, pen-test prep, BABA checklist, store assembly, device-UAT docs, or load-test prep: compose and required deps (Postgres, Redis, ledger) stay green while the tenant is provisioned out-of-band. User decision 2026-07-21: place Auth0 on the punchlist and move on. ## Login UI note HorizonORBIT login layout lives in **HorizonCRM** (not cloned here). Until that repo is available, `/app/login` remains a DataRightTailwind-compatible stub pointing at Auth0 once configured. ## Related env keys See `.env.example` / `DevResources/project.env.example` for `AUTH0_*` and `VITE_AUTH0_*`. Leave blank until the tenant exists. ProjectDocuments7
66DOC-AUTH0-PROVISIONING — OverviewDOC-AUTH0-PROVISIONING / Overview: # DOC — Auth0 Provisioning (Phase 0 → production closeout) **Status (2026-07-21):** **DEFERRED — non-blocking for engineering.** On punchlist (`DOC07-Punchlist.md` § Deferred). No live Auth0 credentials exist in AWS Secrets Manager or on the T4 host. Stack remains bootable with placeholders. **Phases 0–5 and production prep continue without a live tenant**; `/healthz` already allows `auth0.conf# DOC — Auth0 Provisioning (Phase 0 → production closeout) **Status (2026-07-21):** **DEFERRED — non-blocking for engineering.** On punchlist (`DOC07-Punchlist.md` § Deferred). No live Auth0 credentials exist in AWS Secrets Manager or on the T4 host. Stack remains bootable with placeholders. **Phases 0–5 and production prep continue without a live tenant**; `/healthz` already allows `auth0.configured: false`. **Audience:** Practitioner standing up Auth0 for GemStone on the T4 EC2 / local Golden clone. **Companion:** `DIDYMUS-PLAYBOOK.md` §9 (same steps), `DOC-Deploy-Pipeline.md`, `.env.example`, punchlist Auth0 row.ProjectDocuments7
67DOC-AUTH0-PROVISIONING — Verification snapshot (automatable — done)DOC-AUTH0-PROVISIONING / Verification snapshot (automatable — done): | Check | Result | |-------|--------| | `DATARIGHT_DEV_SECRETS` (us-east-1 / us-east-2) | **No** `AUTH0_*` / `VITE_AUTH0_*` keys (21 keys total; `AUTH_TOKEN_SECRET` is unrelated) | | Sibling secrets (`Labs4You*`, `RusticRavinesSecrets`, `SagePeak_Dev_Secrets`) | **No** Auth0 keys | | EC2 `/home/dr/AppDev/gemstone-nexus/.env` | Keys declared; **all credential values empty**; `AUTH0_ENABLED=false` || Check | Result | |-------|--------| | `DATARIGHT_DEV_SECRETS` (us-east-1 / us-east-2) | **No** `AUTH0_*` / `VITE_AUTH0_*` keys (21 keys total; `AUTH_TOKEN_SECRET` is unrelated) | | Sibling secrets (`Labs4You*`, `RusticRavinesSecrets`, `SagePeak_Dev_Secrets`) | **No** Auth0 keys | | EC2 `/home/dr/AppDev/gemstone-nexus/.env` | Keys declared; **all credential values empty**; `AUTH0_ENABLED=false` | | `GET https://18.116.188.14/healthz` → `checks.auth0` | `configured: false`, detail `AUTH0_DOMAIN/AUDIENCE placeholders — tenant TBD` | Wiring and Management API automation are **not possible** until Mark creates a tenant and stores secrets.ProjectDocuments7
68DOC-AUTH0-PROVISIONING — Exact human actions (Mark)DOC-AUTH0-PROVISIONING / Exact human actions (Mark): ### 1. Create Auth0 tenant + app + API 1. Sign up / log in at [https://auth0.com](https://auth0.com) (free or paid tenant is fine for closeout). 2. Create a **Regular Web Application** (name e.g. `GemStone Nexus`). 3. Create an **API** with Identifier/Audience, e.g. `https://gemstone.dataright.net/api` (this string becomes `AUTH0_AUDIENCE`). 4. Note from the Application settings: - Domain → `A### 1. Create Auth0 tenant + app + API 1. Sign up / log in at [https://auth0.com](https://auth0.com) (free or paid tenant is fine for closeout). 2. Create a **Regular Web Application** (name e.g. `GemStone Nexus`). 3. Create an **API** with Identifier/Audience, e.g. `https://gemstone.dataright.net/api` (this string becomes `AUTH0_AUDIENCE`). 4. Note from the Application settings: - Domain → `AUTH0_DOMAIN` / `VITE_AUTH0_DOMAIN` (e.g. `your-tenant.us.auth0.com`) - Client ID → `AUTH0_CLIENT_ID` / `VITE_AUTH0_CLIENT_ID` - Client Secret → `AUTH0_CLIENT_SECRET` 5. Set Application URIs (adjust if public URL differs): - Allowed Callback URLs: `https://18.116.188.14/app/callback`, `https://gemstone.dataright.net/app/callback`, `http://localhost:5173/app/callback` - Allowed Logout URLs: `https://18.116.188.14/`, `https://gemstone.dataright.net/`, `http://localhost:5173/` - Allowed Web Origins: same origins as above (no path) ### 2. Social connections + roles 1. Enable **Universal Login**. 2. Enable social connections: **Google**, **Facebook**, **LinkedIn** (developer consoles + Auth0 connection setup). 3. Define Auth0 roles (DOC03 §7): `SuperAdmin`, `Org Admin`, `Practitioner`, `GemStone Agent`. 4. (Optional) Auth0 Organizations → map to `orgs.auth0_org_id` + Postgres RLS GUC `app.current_org_id`. ### 3. Store secrets (required before agent can wire EC2) Update AWS Secrets Manager secret **`DATARIGHT_DEV_SECRETS`** (region **us-east-1**; mirror to us-east-2 if that copy is kept in sync) with these **exact key names** (string values, no placeholders): ```text AUTH0_DOMAIN AUTH0_AUDIENCE AUTH0_CLIENT_ID AUTH0_CLIENT_SECRET AUTH0_ISSUER # usually https://<AUTH0_DOMAIN>/ AUTH0_ENABLED # true VITE_AUTH0_DOMAIN VITE_AUTH0_CLIENT_ID ``` **Do not** commit these to git. Host `.env` is filled from Secrets Manager / deploy scripts. ### 4. Reply in chat when ready Tell the agent: **“Auth0 secrets are in DATARIGHT_DEV_SECRETS”** (no need to paste values). Next agent turn will: pull keys → write EC2 `.env` → recreate `api` (+ rebuild `web` for Vite args) → verify `/healthz` `auth0.configured: true` → optional token smoke.ProjectDocuments7
69DOC-AUTH0-PROVISIONING — Why placeholders are intentional until thenDOC-AUTH0-PROVISIONING / Why placeholders are intentional until then: `/healthz` reports `auth0.configured: false` when `AUTH0_DOMAIN` / `AUTH0_AUDIENCE` are empty. That is **not** a Phase 0 failure and **does not block** Atlas, pen-test prep, BABA checklist, store assembly, device-UAT docs, or load-test prep: compose and required deps (Postgres, Redis, ledger) stay green while the tenant is provisioned out-of-band. User decision 2026-07-21: place Auth0 on the punch`/healthz` reports `auth0.configured: false` when `AUTH0_DOMAIN` / `AUTH0_AUDIENCE` are empty. That is **not** a Phase 0 failure and **does not block** Atlas, pen-test prep, BABA checklist, store assembly, device-UAT docs, or load-test prep: compose and required deps (Postgres, Redis, ledger) stay green while the tenant is provisioned out-of-band. User decision 2026-07-21: place Auth0 on the punchlist and move on.ProjectDocuments7
70DOC-AUTH0-PROVISIONING — Login UI noteDOC-AUTH0-PROVISIONING / Login UI note: HorizonORBIT login layout lives in **HorizonCRM** (not cloned here). Until that repo is available, `/app/login` remains a DataRightTailwind-compatible stub pointing at Auth0 once configured.HorizonORBIT login layout lives in **HorizonCRM** (not cloned here). Until that repo is available, `/app/login` remains a DataRightTailwind-compatible stub pointing at Auth0 once configured.ProjectDocuments7
71DOC-AUTH0-PROVISIONING — Related env keysDOC-AUTH0-PROVISIONING / Related env keys: See `.env.example` / `DevResources/project.env.example` for `AUTH0_*` and `VITE_AUTH0_*`. Leave blank until the tenant exists.See `.env.example` / `DevResources/project.env.example` for `AUTH0_*` and `VITE_AUTH0_*`. Leave blank until the tenant exists.ProjectDocuments7
72DOC-BABA-WESTERN-ORIGIN-CHECKLIST BABA Western-Origin Checklist (Phase 5 engineering pass)DOC-BABA-WESTERN-ORIGIN-CHECKLIST: BABA Western-Origin Checklist (Phase 5 engineering pass). | Component | Origin claim | Evidence in repo | Engineering status | | --- | --- | --- | --- | | Whisper large-v3 | OpenAI (US) | DOC18 §1; whisper service | Confirmed in DOC18 baseline | | Piper TTS | Rhasspy (US/Intl OSS) | DOC18 §1; `voice/` | Confirmed in DOC18 baseline | | Ollama | Ollama Inc. (US) | DOC18 §1; compose | Confirmed in DOC18 baseline | | webrtcvad | Google (US) | DOC18 §1 | Confirmed i# BABA Western-Origin Checklist (Phase 5 engineering pass) *Companion to DOC17. Principal sign-off remains required — this checklist is the engineering evidence package, not a substitute for NEXTECH principal audit.* **Date:** 2026-07-21 · **Host evidence:** T4 GoldenAMI `i-04333dae160ab0daa` ## Engineering confirmation (automatable / repo-verified) | Component | Origin claim | Evidence in repo | Engineering status | | --- | --- | --- | --- | | Whisper large-v3 | OpenAI (US) | DOC18 §1; whisper service | Confirmed in DOC18 baseline | | Piper TTS | Rhasspy (US/Intl OSS) | DOC18 §1; `voice/` | Confirmed in DOC18 baseline | | Ollama | Ollama Inc. (US) | DOC18 §1; compose | Confirmed in DOC18 baseline | | webrtcvad | Google (US) | DOC18 §1 | Confirmed in DOC18 baseline | | FastAPI / SQLModel | OSS | DOC18 | Confirmed | | PostgreSQL | PGDG | compose / Alembic | Confirmed | | Redis | Redis Ltd. | compose (AOF) | Confirmed | | Capacitor / Ionic | Ionic (US) | `frontend/package.json` | Confirmed | | MQTT | Eclipse Mosquitto only (if/when introduced) | Not in MVP compose | N/A for current MVP | | AWS messaging | AWS-native only (SNS/SQS/EventBridge) | EventBridge start/stop in ops | Confirmed for schedule; no China-region messaging | | HUME AI | Must remain out of scope | DOC03 / DOC17 | Confirmed not integrated | ## Principal sign-off (practitioner — cannot complete in-agent) | Item | Status | | --- | --- | | Cross-check Syft SBOM (`DevResources/security/sbom-latest.json`) against this table | Pending — on punchlist | | Sign DOC17 checklist rows | Pending — on punchlist | | Record sign-off date + name in Project Ledger | Pending — on punchlist | **Ask:** NEXTECH principal reviews this table + SBOM and signs DOC17; reply in chat when signed so ledger/DOC07 can be updated. ## SBOM generation ```bash bash scripts/security/sbom-stub.sh # Install Syft if skipped: https://github.com/anchore/syft (Western-origin tooling) ``` --- NEXTECH Business Technology Management LLC · nex-tech.biz · (941) 499-5505 ProjectDocuments8
73DOC-BABA-WESTERN-ORIGIN-CHECKLIST — OverviewDOC-BABA-WESTERN-ORIGIN-CHECKLIST / Overview: # BABA Western-Origin Checklist (Phase 5 engineering pass) *Companion to DOC17. Principal sign-off remains required — this checklist is the engineering evidence package, not a substitute for NEXTECH principal audit.* **Date:** 2026-07-21 · **Host evidence:** T4 GoldenAMI `i-04333dae160ab0daa`# BABA Western-Origin Checklist (Phase 5 engineering pass) *Companion to DOC17. Principal sign-off remains required — this checklist is the engineering evidence package, not a substitute for NEXTECH principal audit.* **Date:** 2026-07-21 · **Host evidence:** T4 GoldenAMI `i-04333dae160ab0daa`ProjectDocuments8
74DOC-BABA-WESTERN-ORIGIN-CHECKLIST — Engineering confirmation (automatable / repo-verified)DOC-BABA-WESTERN-ORIGIN-CHECKLIST / Engineering confirmation (automatable / repo-verified): | Component | Origin claim | Evidence in repo | Engineering status | | --- | --- | --- | --- | | Whisper large-v3 | OpenAI (US) | DOC18 §1; whisper service | Confirmed in DOC18 baseline | | Piper TTS | Rhasspy (US/Intl OSS) | DOC18 §1; `voice/` | Confirmed in DOC18 baseline | | Ollama | Ollama Inc. (US) | DOC18 §1; compose | Confirmed in DOC18 baseline | | webrtcvad | Google (US) | DOC18 §1 | Conf| Component | Origin claim | Evidence in repo | Engineering status | | --- | --- | --- | --- | | Whisper large-v3 | OpenAI (US) | DOC18 §1; whisper service | Confirmed in DOC18 baseline | | Piper TTS | Rhasspy (US/Intl OSS) | DOC18 §1; `voice/` | Confirmed in DOC18 baseline | | Ollama | Ollama Inc. (US) | DOC18 §1; compose | Confirmed in DOC18 baseline | | webrtcvad | Google (US) | DOC18 §1 | Confirmed in DOC18 baseline | | FastAPI / SQLModel | OSS | DOC18 | Confirmed | | PostgreSQL | PGDG | compose / Alembic | Confirmed | | Redis | Redis Ltd. | compose (AOF) | Confirmed | | Capacitor / Ionic | Ionic (US) | `frontend/package.json` | Confirmed | | MQTT | Eclipse Mosquitto only (if/when introduced) | Not in MVP compose | N/A for current MVP | | AWS messaging | AWS-native only (SNS/SQS/EventBridge) | EventBridge start/stop in ops | Confirmed for schedule; no China-region messaging | | HUME AI | Must remain out of scope | DOC03 / DOC17 | Confirmed not integrated |ProjectDocuments8
75DOC-BABA-WESTERN-ORIGIN-CHECKLIST — Principal sign-off (practitioner — cannot complete in-agent)DOC-BABA-WESTERN-ORIGIN-CHECKLIST / Principal sign-off (practitioner — cannot complete in-agent): | Item | Status | | --- | --- | | Cross-check Syft SBOM (`DevResources/security/sbom-latest.json`) against this table | Pending — on punchlist | | Sign DOC17 checklist rows | Pending — on punchlist | | Record sign-off date + name in Project Ledger | Pending — on punchlist | **Ask:** NEXTECH principal reviews this table + SBOM and signs DOC17; reply in chat when signed so ledger/DOC07 can be updat| Item | Status | | --- | --- | | Cross-check Syft SBOM (`DevResources/security/sbom-latest.json`) against this table | Pending — on punchlist | | Sign DOC17 checklist rows | Pending — on punchlist | | Record sign-off date + name in Project Ledger | Pending — on punchlist | **Ask:** NEXTECH principal reviews this table + SBOM and signs DOC17; reply in chat when signed so ledger/DOC07 can be updated.ProjectDocuments8
76DOC-BABA-WESTERN-ORIGIN-CHECKLIST — SBOM generationDOC-BABA-WESTERN-ORIGIN-CHECKLIST / SBOM generation: ```bash bash scripts/security/sbom-stub.sh # Install Syft if skipped: https://github.com/anchore/syft (Western-origin tooling) ``` --- NEXTECH Business Technology Management LLC · nex-tech.biz · (941) 499-5505```bash bash scripts/security/sbom-stub.sh # Install Syft if skipped: https://github.com/anchore/syft (Western-origin tooling) ``` --- NEXTECH Business Technology Management LLC · nex-tech.biz · (941) 499-5505ProjectDocuments8
77DOC-CAPACITOR-LIVE-EC2 Capacitor Android / iOS against live EC2DOC-CAPACITOR-LIVE-EC2: Capacitor Android / iOS against live EC2. Auth0 deferred (not required). Device UAT still open (`DOC-Device-UAT-Checklist.md`).# Capacitor Android / iOS against live EC2 **Status 2026-07-21:** Engineering wiring COMPLETE for parallel-with-live-stack debug. Auth0 deferred (not required). Device UAT still open (`DOC-Device-UAT-Checklist.md`). **TLS (2026-07-21):** Live host serves a **Let's Encrypt** cert for `gemstone.dataright.net` (HTTP-01 via `scripts/aws/provision-letsencrypt.sh`). Prefer that hostname over the raw Elastic IP for Capacitor and browsers. **Full workstation install playbook:** [`CAPACITOR-ANDROID-INSTALLATION-PLAYBOOK.md`](CAPACITOR-ANDROID-INSTALLATION-PLAYBOOK.md). ## How Android runs against live EC2 Default debug path loads the **remote** SPA so asset `base` stays `/app/` for nginx web: 1. `frontend/capacitor.config.json` sets `server.url` → `https://gemstone.dataright.net/app` (override: `$env:CAPACITOR_SERVER_URL=...; npm run cap:sync` / `$env:CAPACITOR_USE_BUNDLED=1; npm run cap:sync` via `scripts/apply-capacitor-server.cjs`). 2. With the public LE cert, **debug `network_security_config` / `ec2_debug.crt` are obsolete for `gemstone.dataright.net`** (system CAs trust the chain). Those debug assets remain only as a fallback if you still hit the raw IP (`https://18.116.188.14`) with a self-signed leaf. Release builds never included the debug trust set. 3. API clients use `src/services/apiOrigin.js` — same-origin when on the live WebView; `VITE_API_BASE` or live default when bundled on `https://localhost`. ### Open in Android Studio ```powershell cd frontend npm install npm run build npx cap sync android npm run cap:open:android ``` Then Run ▶ **app** (debug) on an emulator or USB device. First load hits the live `/app/` SPA at `https://gemstone.dataright.net/app/`. ### assembleDebug without Studio ```powershell cd frontend\android .\gradlew.bat assembleDebug # APK: app\build\outputs\apk\debug\app-debug.apk ``` ### iOS (macOS) ```bash cd frontend && npm run build && npx cap sync ios && npm run cap:open:ios ``` Public CA hostname needs no custom trust store. Raw-IP / self-signed remains an ATS / trust-store problem (see `Info.plist` exception for the EIP only). ### Overrides | Knob | Effect | | --- | --- | | `CAPACITOR_SERVER_URL` | Alternate live SPA URL (no trailing slash required) | | `CAPACITOR_USE_BUNDLED=1` | Drop `server.url`; load `dist/` from the binary | | `VITE_API_BASE` | Force REST/WS origin (no trailing slash), e.g. `https://gemstone.dataright.net` | | Vite `base` | Keep `/app/` for web/nginx; bundled-native path later may use `./` | ### Web `/app/` unchanged Vite `base: "/app/"` and `BrowserRouter basename="/app"` stay for EC2 nginx. Capacitor does **not** rely on a second Vite base while `server.url` points at live. ProjectDocuments9
78DOC-CAPACITOR-LIVE-EC2 — OverviewDOC-CAPACITOR-LIVE-EC2 / Overview: # Capacitor Android / iOS against live EC2 **Status 2026-07-21:** Engineering wiring COMPLETE for parallel-with-live-stack debug. Auth0 deferred (not required). Device UAT still open (`DOC-Device-UAT-Checklist.md`). **TLS (2026-07-21):** Live host serves a **Let's Encrypt** cert for `gemstone.dataright.net` (HTTP-01 via `scripts/aws/provision-letsencrypt.sh`). Prefer that hostname over the raw E# Capacitor Android / iOS against live EC2 **Status 2026-07-21:** Engineering wiring COMPLETE for parallel-with-live-stack debug. Auth0 deferred (not required). Device UAT still open (`DOC-Device-UAT-Checklist.md`). **TLS (2026-07-21):** Live host serves a **Let's Encrypt** cert for `gemstone.dataright.net` (HTTP-01 via `scripts/aws/provision-letsencrypt.sh`). Prefer that hostname over the raw Elastic IP for Capacitor and browsers. **Full workstation install playbook:** [`CAPACITOR-ANDROID-INSTALLATION-PLAYBOOK.md`](CAPACITOR-ANDROID-INSTALLATION-PLAYBOOK.md).ProjectDocuments9
79DOC-CAPACITOR-LIVE-EC2 — How Android runs against live EC2DOC-CAPACITOR-LIVE-EC2 / How Android runs against live EC2: Default debug path loads the **remote** SPA so asset `base` stays `/app/` for nginx web: 1. `frontend/capacitor.config.json` sets `server.url` → `https://gemstone.dataright.net/app` (override: `$env:CAPACITOR_SERVER_URL=...; npm run cap:sync` / `$env:CAPACITOR_USE_BUNDLED=1; npm run cap:sync` via `scripts/apply-capacitor-server.cjs`). 2. With the public LE cert, **debug `network_security_coDefault debug path loads the **remote** SPA so asset `base` stays `/app/` for nginx web: 1. `frontend/capacitor.config.json` sets `server.url` → `https://gemstone.dataright.net/app` (override: `$env:CAPACITOR_SERVER_URL=...; npm run cap:sync` / `$env:CAPACITOR_USE_BUNDLED=1; npm run cap:sync` via `scripts/apply-capacitor-server.cjs`). 2. With the public LE cert, **debug `network_security_config` / `ec2_debug.crt` are obsolete for `gemstone.dataright.net`** (system CAs trust the chain). Those debug assets remain only as a fallback if you still hit the raw IP (`https://18.116.188.14`) with a self-signed leaf. Release builds never included the debug trust set. 3. API clients use `src/services/apiOrigin.js` — same-origin when on the live WebView; `VITE_API_BASE` or live default when bundled on `https://localhost`. ### Open in Android Studio ```powershell cd frontend npm install npm run build npx cap sync android npm run cap:open:android ``` Then Run ▶ **app** (debug) on an emulator or USB device. First load hits the live `/app/` SPA at `https://gemstone.dataright.net/app/`. ### assembleDebug without Studio ```powershell cd frontend\android .\gradlew.bat assembleDebug # APK: app\build\outputs\apk\debug\app-debug.apk ``` ### iOS (macOS) ```bash cd frontend && npm run build && npx cap sync ios && npm run cap:open:ios ``` Public CA hostname needs no custom trust store. Raw-IP / self-signed remains an ATS / trust-store problem (see `Info.plist` exception for the EIP only). ### Overrides | Knob | Effect | | --- | --- | | `CAPACITOR_SERVER_URL` | Alternate live SPA URL (no trailing slash required) | | `CAPACITOR_USE_BUNDLED=1` | Drop `server.url`; load `dist/` from the binary | | `VITE_API_BASE` | Force REST/WS origin (no trailing slash), e.g. `https://gemstone.dataright.net` | | Vite `base` | Keep `/app/` for web/nginx; bundled-native path later may use `./` | ### Web `/app/` unchanged Vite `base: "/app/"` and `BrowserRouter basename="/app"` stay for EC2 nginx. Capacitor does **not** rely on a second Vite base while `server.url` points at live.ProjectDocuments9
80DOC-DEPLOY-PIPELINE GemStone Deploy Procedure (Stage 2)DOC-DEPLOY-PIPELINE: GemStone Deploy Procedure (Stage 2). | Role | Where | |------|--------| | Author / edit | Windows workstation (this repo) | | Git | Local commit → `git push` with PAT (from `DATARIGHT_DEV_SECRETS`, never stored in repo) | | Build / run / test | T4 GoldenAMI EC2 Ohio (`i-04333dae160ab0daa`) over plink/SSH | | Local Docker | **Not used** on the co-dev PC |# GemStone Deploy Procedure (Stage 2) **Status:** Operating model wired; host half verified against T4 EC2. **No commit required for Stage 2** — first full Deploy of product code waits until Stage 3 bootstrap content is committed and pushed. ## Operating model | Role | Where | |------|--------| | Author / edit | Windows workstation (this repo) | | Git | Local commit → `git push` with PAT (from `DATARIGHT_DEV_SECRETS`, never stored in repo) | | Build / run / test | T4 GoldenAMI EC2 Ohio (`i-04333dae160ab0daa`) over plink/SSH | | Local Docker | **Not used** on the co-dev PC | **Deploy** = commit → push → pull-on-host → `docker compose up` → restart/health. ## Fixed paths / hosts (Stage 2 verify) | Item | Value | |------|--------| | Instance | `i-04333dae160ab0daa` (us-east-2) | | Public IP (verified) | `18.116.188.14` (re-check after stop/start if no EIP sticky) | | SSH (primary) | `dr` + `DR_SSH_PASSWORD` via plink; host key pinned | | SSH (break-glass) | `ubuntu` + `C:\Users\Mark\.ssh\gemstone-nexus-key.pem` | | Host key (ED25519) | `SHA256:TSExVVo9lcc48zJsQSrpXxEIHe8Wv7+qDTBl1MHCilw` | | `DEVELOPMENT_DIRECTORY` | `/home/dr/AppDev/gemstone-nexus` | | Git remote on host | `https://github.com/mfuriate/GemStone-Nexus-StackOne.git` (clean URL; PAT only at pull time via Basic auth) | | Compose nginx | Container `gemstone-nginx` publishes host `80`/`443` | | Supervisor | Stage 3 — inside API image / `supervisor/` scaffold; not host-level in Stage 2 | ## Scripts | Script | Purpose | |--------|---------| | `scripts/remote-exec.ps1` | Ad-hoc plink/OpenSSH command; `-RefreshHostKey` after instance replace | | `scripts/ensure-ec2-dev-dir.ps1` | Clone/pull `DEVELOPMENT_DIRECTORY`; PAT from Secrets Manager | | `scripts/run-remote-docker-deploy.ps1` | Host half of Deploy (pull → compose up → health) | | `scripts/aws/deploy.sh` | Same contract when already SSH'd onto the host as `dr` | Config template: `DevResources/project.env.example` → copy to `DevResources/project.env` (gitignored). ## Practitioner Deploy steps 1. **Commit** locally (when you intend to ship a change set). Do not commit secrets. 2. **Push** to `origin` (`git push`). PAT stays in credential helper / Secrets Manager — not in `.git/config` on the EC2. 3. **Pull + compose on host** from Windows: ```powershell .\scripts\run-remote-docker-deploy.ps1 ``` Or on the host: ```bash export GITHUB_PAT=... # from Secrets Manager session ./scripts/aws/deploy.sh ``` 4. Confirm `docker compose ps` and `/healthz` (full green expected after Stage 3). Optional host gates: ```bash make phase0-gates # healthz + WS echo <200ms make rollback # restore prior SHA + compose; budget <5 min make soak-start # 10-min healthy soak in background ``` Optional: `-PushLocal` pushes current `HEAD` before the host pull. ## Host key hygiene After EIP reuse or AMI relaunch, fingerprints change: ```powershell .\scripts\remote-exec.ps1 -RefreshHostKey # then update DR_SSH_HOSTKEY in DevResources/project.env ``` OpenSSH: `StrictHostKeyChecking=accept-new` only after removing the stale `known_hosts` line for that IP (`ssh-keygen -R <ip>`). ## Cost schedule (do not disable casually) EventBridge Scheduler (us-east-2), both **ENABLED**: - `gemstone-nexus-stop` — `cron(0 1 * * ? *)` America/New_York - `gemstone-nexus-start` — `cron(0 9 * * ? *)` America/New_York Terraform: `launch_instance = true` is intentional while this host is live — see `infra/terraform/ohio/README.md`. **Spot capacity note (2026-07-21):** After Stage 2 connectivity verify, the instance entered `stopped` with spot request status `marked-for-stop` ("no Spot capacity available"). `StartInstances` returns `IncorrectSpotRequestState` until capacity returns. Worktree `/home/dr/AppDev/gemstone-nexus` was cloned before the stop; re-run `ensure-ec2-dev-dir.ps1` after the next successful start. Do **not** destroy/recreate via Terraform without approval. ## Local secondary `GemStone-Golden` at `D:\Virtual Machines\GemStone-Golden\` — last IP `10.0.0.224`, `dr` contract PASSED (see `DOC-GemStone-Golden-Host-Verify.md`). Offline secondary; not the Deploy target. ProjectDocuments10
81DOC-DEPLOY-PIPELINE — OverviewDOC-DEPLOY-PIPELINE / Overview: # GemStone Deploy Procedure (Stage 2) **Status:** Operating model wired; host half verified against T4 EC2. **No commit required for Stage 2** — first full Deploy of product code waits until Stage 3 bootstrap content is committed and pushed.# GemStone Deploy Procedure (Stage 2) **Status:** Operating model wired; host half verified against T4 EC2. **No commit required for Stage 2** — first full Deploy of product code waits until Stage 3 bootstrap content is committed and pushed.ProjectDocuments10
82DOC-DEPLOY-PIPELINE — Operating modelDOC-DEPLOY-PIPELINE / Operating model: | Role | Where | |------|--------| | Author / edit | Windows workstation (this repo) | | Git | Local commit → `git push` with PAT (from `DATARIGHT_DEV_SECRETS`, never stored in repo) | | Build / run / test | T4 GoldenAMI EC2 Ohio (`i-04333dae160ab0daa`) over plink/SSH | | Local Docker | **Not used** on the co-dev PC | **Deploy** = commit → push → pull-on-host → `docker compose up` → restart/healt| Role | Where | |------|--------| | Author / edit | Windows workstation (this repo) | | Git | Local commit → `git push` with PAT (from `DATARIGHT_DEV_SECRETS`, never stored in repo) | | Build / run / test | T4 GoldenAMI EC2 Ohio (`i-04333dae160ab0daa`) over plink/SSH | | Local Docker | **Not used** on the co-dev PC | **Deploy** = commit → push → pull-on-host → `docker compose up` → restart/health.ProjectDocuments10