Files
ten31-database/start9/0.4
Keysat c7b74a2704 Email search/query + windowed digest preview (v0.1.0:83)
Communications tab (search/query roadmap items 1 & 2):
- Fix the investor dropdown: the facet only listed grid investors, so it
  came back empty whenever email matched a classic contact or org domain
  (no grid id — the common case). It now mirrors the email list, resolving
  each link to a typed identity (fund:/org:/contact:/addr:) with precedence
  grid -> org -> contact -> address; investor_id accepts the typed key
  (bare id = fund: for back-compat) and an unknown prefix matches nothing.
- Add a date-range filter and a click-to-expand full-body view
  (GET /api/email/detail, admin, soft-delete-gated; body_text only, never
  raw remote HTML).
- Add a "Search content" mode: GET /api/email/search wraps the ingest
  hybrid_search over the Qdrant email index (doc_type=email), hydrated and
  soft-delete-filtered against SQLite (canonical), 503 if Spark/Qdrant down.

Daily digest:
- Settings -> Admin builds a digest over a chosen window (last 24h or since
  a date) as an in-app preview before sending (POST /api/admin/digest/preview),
  so the local-Spark summarizer can be verified on demand even on a quiet day.
  Manual send uses the same window; neither advances the daily cursor, so a
  preview never suppresses the scheduled digest.

Code-only, migrations no-op. 22/22 backend tests, render-smoke pass.
2026-06-16 20:46:15 -05:00
..

Ten31 Database — StartOS 0.4 wrapper (x86_64)

This directory is the self-contained StartOS 0.4 service package for Ten31 Database. It is the x86_64 successor to the 0.3.5 (aarch64) wrapper in ../0.3.5/. Both packages share the same package id (ten-database) and the same /data volume layout so data can be preserved across the migration.

Start here

Read DEPLOY_040.md first. It covers:

  1. How the image-seed data-preservation mechanism works.
  2. How to refresh the seed with live production data from the 0.3.5 host (via ./refresh_seed.sh or manual scp).
  3. How to install the build prerequisites (Node, Docker, start-cli).
  4. How to build the x86_64 .s9pk.
  5. How to sideload onto the StartOS 0.4 beta node.
  6. A rollback plan and a post-install verification checklist.

Quick cheat sheet

# From this directory:
./refresh_seed.sh embassy@embassy.local   # pull live prod data into seed/
make clean
make x86
make install                              # uses ~/.startos/config.yaml

Data layout (unchanged from 0.3.5)

Inside the container:

  • /data/crm.db — SQLite database
  • /data/backups/ — app-level JSON exports
  • /data/.crm-secret — JWT signing key (created on first boot if absent)

The entrypoint seeds an empty volume from the image's baked-in snapshot on first boot, and is a no-op for every later boot. Existing volumes are never overwritten.

Status

  • Source scaffold: complete and tsc --noEmit clean against @start9labs/start-sdk 0.4.0.
  • Dockerfile: self-contained under start9/0.4/ with no cross-folder references to start9/0.3.5/.
  • Seed snapshot: present at seed/data/ (repo dev DB — replace with live prod data before building).
  • Not yet built into a .s9pk here; build on a machine with Docker + start-cli per DEPLOY_040.md.