{"count":50,"documents":[{"doc_id":"AWS-RUNBOOK","title":"GemStone-Nexus — AWS Deploy Runbook","category":"reference","source_path":"DevResources/docs/aws-runbook.md","summary":"> **Status (Stage 2):** Ohio T4 host is live (`i-04333dae160ab0daa`, us-east-2). > Day-to-day Deploy is documented in `DOC-Deploy-Pipeline.md` and driven by > `scripts/run-remote-docker-deploy.ps1` / `scripts/aws/deploy.sh`. > The us-east-1 “Phase 1 baseline” section below is historical plan context; > do not re-run those skeletons against Ohio without review.","updated_at":"2026-07-22 18:33:18"},{"doc_id":"CAPACITOR-ANDROID-INSTALLATION-PLAYBOOK","title":"Capacitor Android — Practitioner Installation & Operation Playbook","category":"playbook","source_path":"DevResources/docs/CAPACITOR-ANDROID-INSTALLATION-PLAYBOOK.md","summary":"This playbook is the end-to-end install and operate guide. It does **not** replace mobility specs or device UAT scripts — those live in the referenced docs below.","updated_at":"2026-07-23 16:50:22"},{"doc_id":"CONTRACT-NOTES","title":"GemStone-Nexus — Contract Notes","category":"reference","source_path":"DevResources/docs/contract-notes.md","summary":"Behavioral contract for the ported stack. These notes capture what the API and voice loop promise, and what changed during the port from a prior StackOne extraction.","updated_at":"2026-11-18 16:51:43"},{"doc_id":"DIDYMUS-ARCH-01","title":"DIDYMUS-ARCH-01 — Didymus Hub Architecture","category":"didymus","source_path":"DevResources/docs/DIDYMUS-ARCH-01.md","summary":"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.","updated_at":"2026-07-22 18:33:18"},{"doc_id":"DIDYMUS-PLAYBOOK","title":"DIDYMUS-PLAYBOOK — Practitioner Provisioning and Queue Ops","category":"playbook","source_path":"DevResources/docs/DIDYMUS-PLAYBOOK.md","summary":"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.","updated_at":"2026-07-22 18:33:18"},{"doc_id":"DOC-ATLAS-DATA-MODEL","title":"Atlas Data Model — Index B Durable Schema","category":"reference","source_path":"DevResources/docs/DOC-Atlas-Data-Model.md","summary":"vault may still be stubbed. GemStone remains an MCP *client*; these Postgres tables are the durable local Index B mirror (org + practitioner segmented).","updated_at":"2026-07-23 14:28:28"},{"doc_id":"DOC-ATLAS-INDEX-B","title":"Atlas Vault — MCP Index B Integration (DOC02 Phase 2A)","category":"reference","source_path":"DevResources/docs/DOC-Atlas-Index-B.md","summary":"GemStone is an **MCP client** to a remote Atlas Vault. This document describes the Index B contract GemStone speaks, how to point at a real vault, and the local stub used when no remote endpoint is configured.","updated_at":"2026-11-18 16:51:43"},{"doc_id":"DOC-AUTH0-PROVISIONING","title":"DOC — Auth0 Provisioning (Phase 0 → production closeout)","category":"reference","source_path":"DevResources/docs/DOC-Auth0-Provisioning.md","summary":"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`.","updated_at":"2026-07-22 18:33:18"},{"doc_id":"DOC-AWS-SMS-RECOVERY","title":"DOC-AWS-SMS-Recovery","category":"reference","source_path":"DevResources/docs/DOC-AWS-SMS-Recovery.md","summary":"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.","updated_at":"2026-07-22 18:33:18"},{"doc_id":"DOC-BABA-WESTERN-ORIGIN-CHECKLIST","title":"BABA Western-Origin Checklist (Phase 5 engineering pass)","category":"reference","source_path":"DevResources/docs/DOC-BABA-Western-Origin-Checklist.md","summary":"| 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 | | Po…","updated_at":"2026-07-22 18:33:18"},{"doc_id":"DOC-CAPACITOR-LIVE-EC2","title":"Capacitor Android / iOS against live EC2","category":"reference","source_path":"DevResources/docs/DOC-Capacitor-Live-EC2.md","summary":"Auth0 deferred (not required). Device UAT still open (`DOC-Device-UAT-Checklist.md`).","updated_at":"2026-07-22 18:33:18"},{"doc_id":"DOC-DEPLOY-PIPELINE","title":"GemStone Deploy Procedure (Stage 2)","category":"reference","source_path":"DevResources/docs/DOC-Deploy-Pipeline.md","summary":"| 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 |","updated_at":"2026-07-22 18:33:18"},{"doc_id":"DOC-DEVICE-UAT-CHECKLIST","title":"Device UAT Checklist (DOC20 mobility + Phase 2B/2C gates)","category":"reference","source_path":"DevResources/docs/DOC-Device-UAT-Checklist.md","summary":"| Check | Notes | | --- | --- | | Capacitor Android project present | `frontend/android` after `npm run cap:sync` | | Capacitor iOS project present | `frontend/ios` — requires macOS + Xcode + CocoaPods | | Staging `/healthz` green | Auth0 may still be `configured:false` (deferred); not a device-UAT blocker for UI/mobility scripts | | Android debug → live EC2 | See `DOC-Capacitor-Live-EC2.md`: `server.url` → `/app`, debug TLS trust for `18.116.188.14` | | Physical devices | O…","updated_at":"2026-07-22 18:33:18"},{"doc_id":"DOC-DIDYMUS-BRIDGE-PUNCHLIST","title":"DOC — Didymus orchestration & desktop bridge (practitioner punchlist)","category":"punchlist","source_path":"DevResources/docs/DOC-Didymus-Bridge-Punchlist.md","summary":"GemStone is the **orchestrator**. Practitioners connect AI workers (Cursor, Claude, Gemini, Ollama). Didymus shows approval-gated tasks and buffered conversation events linked to **registered** desktop sessions. Changes in the GemStone Agent window are mirrored into the Didymus relay as far as APIs allow; **desktop IDE chat windows are not claimed as live** until vendor bridge keys exist.","updated_at":"2026-08-06 19:15:30"},{"doc_id":"DOC-GEMSTONE-GOLDEN-HOST-VERIFY","title":"DOC GemStone Golden Host Verify","category":"reference","source_path":"DevResources/docs/DOC-GemStone-Golden-Host-Verify.md","summary":"﻿# GemStone-Golden host contract verify","updated_at":"2026-07-22 18:33:18"},{"doc_id":"DOC-GEMSTONEGUARDRAILS","title":"DOC — GemStoneGuardRails","category":"reference","source_path":"DevResources/docs/DOC-GemStoneGuardRails.md","summary":"Before GemStone answers (sovereign chat, Gemini Live, or ledger RAG), it checks **GemStoneGuardRails**. If the user question matches a rule (exact or inferred similarity), GemStone returns the **fixed response** — no freelancing.","updated_at":"2026-08-06 18:37:27"},{"doc_id":"DOC-PENTEST-ENGAGEMENT-BRIEF","title":"Phase 5 — Penetration Test Engagement Brief","category":"reference","source_path":"DevResources/docs/DOC-PenTest-Engagement-Brief.md","summary":"- Independent third-party assessment covering OWASP Top 10 at minimum. - All Critical and High findings remediated and re-tested before production. - Medium findings: documented remediation plan with owner + date (DOC12 / punchlist).","updated_at":"2026-07-22 18:33:18"},{"doc_id":"DOC-PHASE4-GATE","title":"DOC-Phase4-Gate","category":"reference","source_path":"DevResources/docs/DOC-Phase4-Gate.md","summary":"| View | API | UI | | --- | --- | --- | | Approval Queue | `/api/dashboard/approval-queue` | `/app/dashboard` | | Worker Health | `/api/dashboard/worker-health` | same | | Tier Distribution | `/api/dashboard/tier-distribution` | same | | Open Mode Consent Audit | `/api/dashboard/open-mode-consent` | same | | Research Agent Volume | `/api/dashboard/research-volume` | same | | Audio Pipeline Health | `/api/dashboard/audio-pipeline` | same | | Wake-Word Tuning | `/api/dashboard…","updated_at":"2026-07-22 18:33:18"},{"doc_id":"DOC-PHASE5-HARDENING-SCAFFOLD","title":"Phase 5 Hardening — Status","category":"reference","source_path":"DevResources/docs/DOC-Phase5-Hardening-Scaffold.md","summary":"| Work item | Engineering (this pass) | Practitioner / vendor | | --- | --- | --- | | Playwright E2E ×2 clean | `frontend/e2e/` critical paths + `npm run test:e2e:twice` | Device UAT (DOC20) still practitioner | | Third-party pen test | Checklist + engagement brief | Engage vendor — agent cannot execute | | 10k-session load (p95 &lt; 3s) | Scaled proxy + JSON report (`scripts/load/phase5_load_stub.py`) | Full 10k voice soak after disk/RAM headroom | | Syft SBOM + BABA | Gene…","updated_at":"2026-07-22 18:33:18"},{"doc_id":"DOC-PRACTITIONER-RULES","title":"DOC — Practitioner personal Atlas rules","category":"reference","source_path":"DevResources/docs/DOC-Practitioner-Rules.md","summary":"Each signed-in practitioner can save **personal** fixed-response rules in their Atlas segment (`org_id` + `practitioner_id`). These are consulted **after** product-wide `GemStoneGuardRails` and **before/with** ledger context so freelanced answers do not violate personal preferences.","updated_at":"2026-07-23 13:57:31"},{"doc_id":"DOC-PUSH-NOTIFICATIONS-SNS","title":"DOC — GemStone Push Notifications (AWS SNS + FCM + Capacitor)","category":"reference","source_path":"DevResources/docs/DOC-Push-Notifications-SNS.md","summary":"Do these in order. Do **not** paste secret values into chat or git.","updated_at":"2026-07-23 15:20:09"},{"doc_id":"DOC-STORE-SUBMISSION-CHECKLIST","title":"Phase 5 — App Store / Play Store Submission Prep","category":"reference","source_path":"DevResources/docs/DOC-Store-Submission-Checklist.md","summary":"| Blocker | Status | | --- | --- | | Apple Developer Program enrollment | **On punchlist** — required for App Store Connect | | Google Play Console developer account | **On punchlist** — required for Play upload | | Auth0 production tenant + Universal Login | Deferred punchlist — `DOC-Auth0-Provisioning.md` | | Privacy policy + support URLs hosted | TBD by NEXTECH | | Signing keys (iOS distribution / Android upload keystore) | Must live in secrets vault — never in repo |","updated_at":"2026-07-22 18:33:18"},{"doc_id":"DOC-SUITE-GAP-SUMMARY","title":"DOC Suite Gap Summary","category":"reference","source_path":"DevResources/docs/DOC-Suite-Gap-Summary.md","summary":"| Capability | Doc source | Live code | Status | |---|---|---|---| | Gemini Live voice (`/ws/gemstone/live`) | contract-notes, punchlist | `api/app/ws/gemstone_live.py`, `web/gemstone-live.js` | **Done** | | Sovereign Whisper/Piper wake loop | DOC03 §2, contract-notes | `whisper_stt`, `piper_tts`, `gemstone-voice.js` | **Done** (primary path is Live in development mode) | | Recents ≥20 + notebooks + inferenced search | DOC03/04 US-07/08, punchlist | `/api/sessions`, `/api/no…","updated_at":"2026-07-23 15:02:12"},{"doc_id":"DOC-WORKER-KEY-ONBOARDING","title":"DOC — Practitioner Vendor-Key Onboarding & Secure Storage","category":"reference","source_path":"DevResources/docs/DOC-Worker-Key-Onboarding.md","summary":"Didymus live worker execution (Cursor, Claude, Gemini, optional Ollama) runs against **your** vendor accounts. This playbook explains how a practitioner connects each worker by providing an API key/token, how GemStone stores those keys securely, and how to rotate or remove them. It complements `DIDYMUS-PLAYBOOK.md` (operator/host provisioning) and `DIDYMUS-ARCH-01.md` (architecture). The permanent human-approval invariant is unchanged: connecting a key never lets a task run …","updated_at":"2026-07-22 18:33:18"},{"doc_id":"DOC01","title":"DOC01 — Abstract","category":"doc_suite","source_path":"DevResources/docs/DOC01-Abstract.md","summary":"GemStone is the voice-first, mobile-first agentic interface layer of the NEXTECH Triptych (GemStone, Horizon Atlas, Horizon IQ), functioning as an executive assistant that works alongside, ahead of, and behind the individual practitioner. It is a full-capability AI partner, not a chatbot: it takes complex requests, executes autonomously within a human-approved envelope, produces deliverables, asks one clarifying question at a time, and reports outcomes.","updated_at":"2026-07-22 18:33:18"},{"doc_id":"DOC02","title":"DOC02 — Statement of Work","category":"sow","source_path":"DevResources/docs/DOC02-SOW.md","summary":"| Term | Definition | | --- | --- | | Practitioner | The licensed end user of GemStone; owns one Atlas Vault; scoped by org_id and practitioner_id. | | Session | A single continuous voice or text interaction, WebSocket-backed, assigned exactly one Security Tier at creation. | | Security Tier | One of High Security, Standard, or Open Mode; immutable for the life of a session; enforced exclusively by TierGuard. | | Domain Pack | An installable bundle of system prompt extension…","updated_at":"2026-07-22 18:33:18"},{"doc_id":"DOC03","title":"DOC03 — Product Requirements Document","category":"prd","source_path":"DevResources/docs/DOC03-PRD.md","summary":"``` class SecurityTier(str, Enum): HIGH_SECURITY = \"high_security\"   # numeric value 0 (most restrictive) STANDARD = \"standard\"             # numeric value 1 OPEN_MODE = \"open_mode\"           # numeric value 2 (least restrictive)","updated_at":"2026-07-22 18:33:18"},{"doc_id":"DOC04","title":"DOC04 — Granular User Stories","category":"doc_suite","source_path":"DevResources/docs/DOC04-Granular-User-Stories.md","summary":"US-01: As a practitioner, I can speak a request to GemStone and receive a response without losing context if I step away mid-session.","updated_at":"2026-07-22 18:33:18"},{"doc_id":"DOC05","title":"DOC05 — Feature Requests Register","category":"doc_suite","source_path":"DevResources/docs/DOC05-Feature-Requests-Register.md","summary":"| ID | Feature | Acceptance Criteria Summary | Dependency | | --- | --- | --- | --- | | FR-GS-001 | Capacitor Field Mode voice interaction | Voice activates <1s on tap; standard WebView audio only | Phase 1A voice pipeline | | FR-GS-002 | Extended Session native background audio | Survives OS audio-focus interruption; Android priority | Phase 2B Field Mode complete | | FR-GS-004 | Didymus integration, universal approval gate | No task reaches RUNNING without approved_by/appr…","updated_at":"2026-07-22 18:33:18"},{"doc_id":"DOC06","title":"DOC06 — Master Prompt","category":"doc_suite","source_path":"DevResources/docs/DOC06-Master-Prompt.md","summary":"This is the last document in the GemStone set, built only after DOC01 through DOC05 and DOC07 through DOC21 (plus Amendments 1 and 2) are complete, because it aggregates and references them rather than standing alone. Cursor should treat this document as the entry point for any GemStone build task, and should follow its section references back to the source document for full detail rather than relying on this summary alone for anything schema-, endpoint-, or test-critical.","updated_at":"2026-07-22 18:33:18"},{"doc_id":"DOC07","title":"DOC07 — Punchlist","category":"punchlist","source_path":"DevResources/docs/DOC07-Punchlist.md","summary":"| Item | Owner | Verification Artifact | | --- | --- | --- | | Docker Compose stack, all services healthy | Engineering | docker compose ps output, 10-min idle stability log | | gemstone-db schema migrations applied | Engineering | Alembic migration history, schema diff | | Auth0 RBAC roles configured | Engineering | RBAC matrix (DOC03 Sec 7) mapped to live Auth0 config export | | make rollback verified | Engineering | Rollback dry-run log, timestamped |","updated_at":"2026-07-23 16:24:57"},{"doc_id":"DOC08","title":"DOC08 — Playbook","category":"playbook","source_path":"DevResources/docs/DOC08-Playbook.md","summary":"1. Query the sessions table for the session_id; confirm state and check interruption_snapshot is non-null. 2. If interruption_snapshot is null and state is PAUSED, this is a defect: the snapshot write failed silently. Escalate immediately; do not attempt manual state repair without engineering. 3. If state is PAUSED but the session-ready chime should already have fired, confirm cue scheduling; stuck-before-chime is distinct from stuck-after-chime (RESUMABLE). 4. If interrupt…","updated_at":"2026-07-22 18:33:18"},{"doc_id":"DOC09","title":"DOC09 — Glossary of Terms","category":"doc_suite","source_path":"DevResources/docs/DOC09-Glossary.md","summary":"GemStone: the voice-first, mobile-first agentic interface layer of the NEXTECH Triptych, and the single universal presentation/approval surface for all build task suggestions.","updated_at":"2026-07-22 18:33:18"},{"doc_id":"DOC10","title":"DOC10 — Training and Support","category":"doc_suite","source_path":"DevResources/docs/DOC10-Training-and-Support.md","summary":"1. Security tier selection: explain High Security, Standard, and Open Mode (canonical display names; wire values high_security / standard / open_mode per DOC03); confirm the practitioner understands tier is immutable for the session once chosen. Script cue: \"Once we start, this session stays at the level we pick, we can't loosen or tighten it partway through.\" 2. Notebooks, Recents, and inferenced search: introduce as three distinct capabilities, since practitioners coming f…","updated_at":"2026-07-22 18:33:18"},{"doc_id":"DOC11","title":"DOC11 — Promotion and Go-to-Market","category":"doc_suite","source_path":"DevResources/docs/DOC11-Promotion-and-GTM.md","summary":"GemStone is positioned as a full-capability AI partner, not a chatbot, and its mobility layer is explicitly positioned against the documented shortcomings of existing voice-assistant products, without naming competitors directly in public-facing materials.","updated_at":"2026-07-22 18:33:18"},{"doc_id":"DOC12","title":"DOC12 — Development History","category":"doc_suite","source_path":"DevResources/docs/DOC12-Development-History.md","summary":"1. Original 21-document GemStone suite built: React Native/Expo/PWA mobile stack, Whisper/Piper voice pipeline, Atlas Vault via MCP Index B, Domain Pack framework, three-tier security model. 2. Amendment 1 (v1.1): security tier infrastructure, voice provider abstraction, External Research API added to Phase 1 MVP. HUME AI placed in Pending Review status. 3. Circular dependency identified in applying the standard Triptych-governance DOC26 template to GemStone itself; resolved…","updated_at":"2026-07-22 18:33:18"},{"doc_id":"DOC13","title":"DOC13 — Diagrams","category":"doc_suite","source_path":"DevResources/docs/DOC13-Diagrams.md","summary":"``` Practitioner        gemstone-api        atlas-ollama (Whisper)      gemstone-tts (Piper) |-- audio chunk -->|                     |                          | |                  |-- stream ---------->|                          | |                  |<-- partial transcript|                          | |                  |-- final transcript ->|  (VAD end-of-turn)       | |                  |-- query MCP Index B (Atlas context) ----------->| |                  |-- response t…","updated_at":"2026-07-22 18:33:18"},{"doc_id":"DOC14","title":"DOC14 — Unit Test Results","category":"doc_suite","source_path":"DevResources/docs/DOC14-Unit-Test-Results.md","summary":"GemStone implements a three-tier testing architecture plus a UAT framework. All runs are logged to a dated narrative file and the Project Ledger database. make test executes all tiers in sequence.","updated_at":"2026-07-22 18:33:18"},{"doc_id":"DOC15","title":"DOC15 — Disaster Recovery and Business Continuity","category":"doc_suite","source_path":"DevResources/docs/DOC15-DR-BC.md","summary":"| System | RTO | RPO | Backup Frequency | | --- | --- | --- | --- | | gemstone-db (sessions, tiers, ledger) | 15 minutes | 5 minutes | Continuous WAL archiving + hourly snapshot | | Redis session state | 5 minutes | 0 (AOF persistence enabled) | AOF every write | | Atlas Vault (external dependency) | Governed by Atlas Vault's own DR plan | Governed by Atlas Vault's own DR plan | N/A, out of GemStone scope | | Didymus raw archive | 30 minutes | 15 minutes | Hourly snapshot |","updated_at":"2026-07-22 18:33:18"},{"doc_id":"DOC16","title":"DOC16 — Security and Penetration Testing","category":"doc_suite","source_path":"DevResources/docs/DOC16-Security-and-Pen-Testing.md","summary":"- Session transcripts are never transmitted externally, in any security tier, without exception. - Human approval is required for every build task execution, without exception, regardless of platform maturity. - No audio data is ever sent to external APIs. - AES-256 encryption at rest; TLS 1.3 in transit.","updated_at":"2026-07-22 18:33:18"},{"doc_id":"DOC17","title":"DOC17 — BABA Compliance","category":"doc_suite","source_path":"DevResources/docs/DOC17-BABA-Compliance.md","summary":"GemStone and its Mobility Layer adhere to the standing Western-origin technology stack constraint across AI/ML frameworks, messaging infrastructure, and MQTT brokering. Core voice components (Whisper/OpenAI/US, Piper/Rhasspy/US, Ollama/US) are confirmed Western-origin.","updated_at":"2026-07-22 18:33:18"},{"doc_id":"DOC18","title":"DOC18 — Software Bill of Materials","category":"doc_suite","source_path":"DevResources/docs/DOC18-SBOM.md","summary":"| Component | Origin | License | Container | | --- | --- | --- | --- | | FastAPI | OSS (International) | MIT | gemstone-api | | Whisper large-v3 (weights) | OpenAI (US) | MIT | atlas-ollama | | Ollama runtime | Ollama Inc. (US) | MIT | atlas-ollama | | Piper TTS runtime | Rhasspy (US/International, open-source) | MIT | gemstone-tts | | ONNX Runtime | Microsoft (US) | MIT | gemstone-tts | | webrtcvad | Google (US) | BSD-3-Clause | gemstone-api | | PostgreSQL | PostgreSQL Glob…","updated_at":"2026-07-22 18:33:18"},{"doc_id":"DOC19","title":"DOC19 — Project Ledger and Intelligence Layer","category":"doc_suite","source_path":"DevResources/docs/DOC19-Project-Ledger-Intelligence-Layer.md","summary":"The GemStone Project Ledger is a standalone ledger-api instance tracking session history, deploy events, UAT results, Domain Pack versions, and Didymus task/approval history, bidirectionally synced with Development History (DOC12).","updated_at":"2026-07-22 18:33:18"},{"doc_id":"DOC20","title":"DOC20 — UAT Framework","category":"doc_suite","source_path":"DevResources/docs/DOC20-UAT-Framework.md","summary":"1. Start a Standard-tier session and begin a voice conversation. 2. Background the app for 2 minutes (within Extended Session grace window). 3. Reopen the app. Expected: session restores to ACTIVE with the last exchange visible, no re-authentication required. 4. Repeat steps 1-3 substituting an incoming phone call for backgrounding. Expected: identical restoration behavior. 5. Repeat steps 1-3 substituting a forced network disconnect. Expected: identical restoration behavior.","updated_at":"2026-07-22 18:33:18"},{"doc_id":"DOC21","title":"DOC21 — Platform Dashboard","category":"doc_suite","source_path":"DevResources/docs/DOC21-Platform-Dashboard.md","summary":"| View | Metric | Source / Calculation | | --- | --- | --- | | Approval Queue | Pending task count by age bucket | COUNT from didymus_tasks WHERE status=PENDING, grouped by created_at age | | Worker Health | Lease success rate per worker | COMPLETED+VERIFIED / total leases, per target_worker, trailing 24h | | Tier Distribution | Active sessions by tier | COUNT from sessions WHERE ended_at IS NULL, grouped by tier | | Open Mode Consent Audit | Consent events vs. Open Mode ses…","updated_at":"2026-07-22 18:33:18"},{"doc_id":"DOC26","title":"DOC26 — Bootstrap and Self-Hosting","category":"doc_suite","source_path":"DevResources/docs/DOC26-Bootstrap-Self-Hosting.md","summary":"This document defines the maturity gates that move GemStone from Bootstrap (human-directed build with external AI workers proposing tasks) to Self-Hosting (GemStone may propose build tasks against itself) without ever relaxing the human-approval invariant. It is the executable reference named by DOCA1 and DOC06; phase product gates remain in DOC02.","updated_at":"2026-07-22 18:33:18"},{"doc_id":"DOCA1","title":"DOCA1 — Amendment 1","category":"amendment","source_path":"DevResources/docs/DOCA1-Amendment-1-Didymus-Self-Hosting.md","summary":"This amendment folds the Didymus orchestration architecture and the Bootstrap-to-Self-Hosting lifecycle into the core GemStone suite by reference. GemStone is the single, universal presentation and approval surface for every build task suggestion, regardless of originating AI tool. No task, from any source or category, ever executes without human approval; this is a permanent, platform-wide invariant, not a maturity-gated exception.","updated_at":"2026-07-22 18:33:18"},{"doc_id":"DOCA2","title":"DOCA2 — Amendment 2","category":"amendment","source_path":"DevResources/docs/DOCA2-Amendment-2-Mobility-Layer.md","summary":"This amendment folds the Capacitor-based GemStone Mobility Layer into the core GemStone suite by reference, replacing the original React Native/Expo/PWA mobile stack in full.","updated_at":"2026-07-22 18:33:18"},{"doc_id":"GS-MOB-01","title":"GS-MOB-01 — GemStone Mobility Layer","category":"mobility","source_path":"DevResources/docs/GS-MOB-01.md","summary":"This document is the executable Mobility Layer specification named by DOCA2, DOC02 Phases 2B/2C, DOC03 Section 13, and DOC06 Section 7. It replaces the superseded React Native/Expo/PWA mobile stack with Capacitor as the sole mobile client.","updated_at":"2026-07-22 18:33:18"},{"doc_id":"OHIO-TERRAFORM-PLAN","title":"GemStone-Nexus — Ohio (us-east-2) Terraform Bring-up Plan","category":"plan","source_path":"DevResources/plans/ohio-terraform-plan.md","summary":"Recreate the GemStone dev stack in **us-east-2 (Ohio)** — the home datacenter — as","updated_at":"2026-07-22 18:33:18"}]}