
The Move
THE TOWER / THE MOVE
Two systems. One new home.
Follow the cover into the actual system. The art gives the work a world; the engineering below shows what runs, what has been tested, and what still needs evidence.
Read the engineering01 / THE QUESTION
What changes when both sisters run from the same Linux host?
J-Bot and Twilight are software systems, not the robots in the picture. The move places their runtimes on the Tower while keeping their jobs distinct: J-Bot's business-facing work in one lane and Twilight's local operator work in another.
02 / THE SYSTEM
What the build has to hold together.
- 01Service ownership
Each runtime has a separate job and lifecycle to inspect.
- 02Working space
The two systems use different work areas and state paths.
- 03Shared compute
They can use one host and local model capacity without becoming one application.
- 04Recovery
Both runtimes have been exercised through service restart, full host reboot, and state restore.
03 / THE CURRENT RECORD
What we can say today.
Both runtimes are active on Linux. Each has returned after service restart, full Tower reboot, and state restore in lab exercises. The public-facing test record has not been attached yet.
04 / THE LIMIT
What the cover cannot prove.
Those three successful recovery paths do not establish uninterrupted service, failover to another host, or behavior during a prolonged model outage. The cover also does not show what state was checked after each recovery.
05 / NEXT RECEIPT
What belongs beside this chapter.
Attach a dated service inventory and a redacted recovery receipt for each runtime and each of the three exercised scenarios.