Keysat
c53fdcb4a0
Incorporates the signal-engine workstream's v2.0 thesis correction: the spine is bitcoin as the apex NON-DEBASABLE RESERVE ASSET (debasement = forcing function, AI = abundance engine), NOT "infrastructure settles on bitcoin" (the settlement/payments claim — Strike's payments thesis died in backtest). thesis_seed.ensure_thesis_v2_candidate stages the v2.0 root/forcing-function, throughline, the verifiable-vs-contrarian decomposition, and the 3 seams (Energy↔Compute, Debasement↔Bitcoin, AI↔Data-Ownership) as CANDIDATE nodes under the core line (idempotent sentinel; provenance + "unratified, exposure unconfirmed" on the section). Nothing canonical (guardrail #4). docs/thesis-handoff.md gets a SUPERSEDED-spine banner pointing to v2.0. NOT done (gated on partner ratification): the live THROUGHLINE/PILLAR_1 constants and architect_agent.py's system prompt ("scarcity as the connecting idea") still encode the old spine — until ratified+updated, Vary/Revise/outreach regenerate the old framing. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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:
- How the image-seed data-preservation mechanism works.
- How to refresh the seed with live production data from the 0.3.5 host
(via
./refresh_seed.shor manual scp). - How to install the build prerequisites (Node, Docker,
start-cli). - How to build the x86_64
.s9pk. - How to sideload onto the StartOS 0.4 beta node.
- 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 --noEmitclean against@start9labs/start-sdk0.4.0. - Dockerfile: self-contained under
start9/0.4/with no cross-folder references tostart9/0.3.5/. - Seed snapshot: present at
seed/data/(repo dev DB — replace with live prod data before building). - Not yet built into a
.s9pkhere; build on a machine with Docker +start-cliperDEPLOY_040.md.