Quickstart

Once installation reports READY, start the platform:

livemore doctor          # readiness check; the last line should read READY
livemore start           # starts LIFE :8851, Aegle :8850 and Cendos :8852
livemore status          # what is up
livemore open            # opens the console in your browser
livemore programs list   # what can and cannot run, and why

You should see:

  LivemoreBio infrastructure
  ----------------------------------------------------
  ● up   LIFE    :8851   20 diseases · 172 risk loci
  ● up   Aegle   :8850   twin:
  ● up   Cendos  :8852   in-silico assays ready
  ----------------------------------------------------
  registry: /home/you/.livemore/registry.json  (3 registered)

Each service has one job:

• Aegle (:8850): the digital twins, and the console you look at.
• LIFE (:8851): the patch and continuous-measurement side.
• Cendos (:8852): the in-silico lab where experiments run.

Stop everything with livemore stop.

A new workspace

A fresh workspace starts with an unregistered healthy reference preview, not an admitted twin. That is deliberate: admitting a twin is a governed step with consent and a source class attached, and the installer does not do it for you.

Works immediately:

• all six reference programs, and their refusals;
• the genome-scale metabolic engine;
• in-silico assays (assay metformin dose=1.0);
• the console, the notebooks and every export.

Needs an admitted twin first:

• continuous execution and the LIFE Patch closed loop.

Asked for these without one, the product refuses with EXECUTION_SOURCE_REQUIRED and tells you to create and activate a twin. That is the intended answer, not a failure.

Create an admitted twin

In the console, open Twins, select Create admitted twin, then Activate numerical model.

From the terminal, attach a shell to the running platform and admit a bundle:

livemore attach

twin admit <bundle.json>
twin activate <twin-id> version=<n>

Exactly one twin is authoritative at a time, across Atlas, LIFE Patch, Cendos, the terminal and notebooks.

Next: learn the terminal commands or try the worked examples.