Level 2 of 3 This component, complete on its own. Its files, sources and tests are the detail below. Open the detail
Repository
sv-field-twin
A persistent, vendor-neutral digital twin of every farm field, for precision application. Demo build for Hollingsfield Agtech (white-label; every tenant brings its own brand).
The seed documents are in docs/: the venture brief and Journey J1, at the gate. This repository is built by a StellarView Slingshot Rapid Cloud Engagement; its run record lives in .stellarview/ as the engagement proceeds.
Phase 1: State Data Platform
The source registry, the state pack loader and the admin shell. Florida pack v0 loads 52 catalog rows; none is active or approved until an operator probes, licenses and approves it.
Prerequisites
Docker with Compose, and GNU Make. Nothing else is installed on the host: every build, test and tool runs in a container. Node 22 (.nvmrc) is the version those containers use; a local Node is only needed if you choose to run npm yourself.
Run it
make setup # creates .env from .env.example if missing
make up # database, migrations, API and admin shell
make seed # runs the pack loader for Florida (there are no SQL seeds)
make migrate # applies forward-only SQL migrations on their own
make down # stops the stack; the database volume is kept
The admin shell is at http://localhost:8080 (WEB_HOST_PORT) and the API at http://localhost:3000 (API_HOST_PORT). If a port is taken, change it in .env. The Dashboard shows API health, registry counts, probe coverage and the loaded packs, and can load an available pack; the Registry route lists, filters and opens sources.
Configuration
Every variable is required and has no in-code default; .env.example lists them all with comments. The ones the API reads: APP_ENV, DEV_AUTH_BYPASS, API_PORT, DATABASE_URL (role ft_app), MIGRATION_DATABASE_URL (role ft_owner), PACKS_DIR, MIGRATIONS_DIR. Change every password outside local development. See docs/dev-auth.md for what the auth bypass allows.