Operating an organism

Files

FileWhat it is
.envMODE, COIN, TERRARIUM_KEY, optional ANTHROPIC_API_KEY, ORG_ID, NAME, TICKER, BEAT_SEC
organism.jsonthe organism's settings: persona, dev share and address, battery share, caps, hooks
data/<id>/everything it has done: its memory. Keep it

.env holds a private key. Never commit it, never paste it into a chat, never put it on a shared drive. .gitignore already excludes it.

Starting and stopping

launch.bat starts the site and, when a .env exists, the runner. To stop, close its window. The organism keeps no state in memory: on the next start it reads data/<id>/state.json and goes on. Fees arrive in the Pons escrow whether or not it runs, and are claimed on the next beat.

Changing the settings

Edit organism.json, then restart. The settings are read at start. They are validated before anything runs; a refused value is printed and the runner exits.

A ledger is bound to its mode: a ledger started in paper mode refuses to run in live mode. Use a new ORG_ID.

What it needs

Publishing the journal

With PUBLISH_GIT=1 in .env the runner pushes its public files to the data branch of the repository (PUBLISH_REPO to name another, PUBLISH_EVERY_SEC to change the 10-minute pace). The machine needs push access to that repository (a signed-in git is enough). A failed push is only a line in the console: the organism keeps running. See Publishing the site.

Reading what happened

Open the site: /coin?id=<ticker>. The journal, the battery, the caps and the Verify tab are there. The same data is in data/<id>/status.json and feed.json, see Files and data.

When something is wrong