BuildUpgrade machines and sites
NODE-01CORE
LIVE TERMINAL●
root@relay:~$ status
NODE-01 · IDLE queue ready · 1.0 compute
SITE 01 · HOME LAB
The Workbench
One old machine, one open queue. Nothing else is guaranteed.
1 node online
HOW COMMAND WORKSWork → build headroom → compoundShow loop
1Run workYour click starts a paid task→2Build headroomHardware prevents slowdowns→AUTOCompoundSoftware keeps Credits moving
OUTPUT MULTIPLIER×1.000 credits/s · starter machine
MEMORY HEADROOM82 free18 / 100 reserved · ready for automation
ARCHITECTURE MATURITYWorkbench1 node · 1 site · local only
ACTIVE INFRASTRUCTURE PROJECT
Project in progress
Other decisions remain available.
ROUTINE WORK
Contract board
Choose yield, queue pressure and manual response for your automated work.
ROUTINE ACTIVEPause contracts
Pause routine Credits and reserve capacity for Operations.
FICTIONAL SIGNAL OPERATIONS
Operations console
Grow the network, choose a fictional target, then trade a controlled Secure payout against a faster, riskier Deep payout.
Build a real network first
Install NODE-02 and reach 6 compute to unlock the scanner.
HOW OPERATIONS WORKMap automatically → choose target + risk → resolveShow loop
AUTOMapScanner reveals reachable signals→YOUTarget + riskSecure is safer; Deep pays more→AUTOResolveRewards, Heat and Trace update
The scanner maintains the map. Choose a reachable target and its risk profile.
SIGNAL SCANNER
Scanner offline
Build a scanner to discover signal sources.
AUTOMATICWatching reachable signalsNo scan click or project slot required
SETUP 01 · SELECT TARGET
Operations board
Choose the target you want to train. Its brief shows the exact Secure and Deep setup before anything runs.
NETWORK SUPPORTInfrastructure bonuses apply automaticallyShow routes
POST-REBOOT AUTOMATIONOperator layersOpen controls
Later runs automate mastered decisions without removing Heat, Trace or capacity consequences.
SITES, POWER & CONNECTIONS
Infrastructure
Upgrade machines, install software and extend the physical network from one dedicated build workspace.
HOW NETWORK FABRIC WORKSBuild site → provision link → support OperationsShow loop
YOUBuild a siteAdd power and capacity→YOUProvision linkAdd usable bandwidth→AUTOSupport OpsIntel, Heat, time or Trace
INTERNET UPLINKS
Connection portfolio
Provision links per site. More bandwidth unlocks heavier operations and shortens compatible transfers.
HOW SYSTEMS WORKUpgrade core → deploy systems → specializeShow loop
1Upgrade coreRaise speed and capacity→2Deploy systemsUnlock new mechanics→3SpecializeImprove a concrete role
NODE-01 HARDWARE
Core system
CPU, Memory, SSD and Cooling solve different limits. Every card previews its actual output and System Health result.
AVAILABLE DEPLOYMENT
Next capability
Only immediately compatible systems appear here. After installation, their controls move to the area where they are used.
CONNECTED HARDWARE
System console
Deploy specialized machines, then invest excess Credits into two concrete hardware tracks per system. Every track changes output, Operations or live System Health.
HOW SOFTWARE WORKSInstall → optimize → run automaticallyShow loop
1InstallUnlock automation→2OptimizeIncrease yield or speed→AUTORun queueConsumes Memory and power
CORE AUTOMATION
Runtime layer
Install the automation foundation before adding specialized optimizers.
OPERATIONS TOOLCHAIN
Signal software
Install analysis and defense tools here. Their live controls appear in Operations once online.
RUN SOFTWARE
Software stack
Credit-funded optimizers deepen systems you already own. Their gains also create Memory, CPU, storage or power pressure.
DATA LAB · CURRENT RUN
Research
Turn Operation Data into a deliberate specialization. New branches appear only when later runs can use them.
HOW RESEARCH WORKSEarn Data → choose a discipline → reshape this runShow loop
AUTOEarn DataComplete signal Access→YOUChoose researchFund one clear advantage→RUNExploit itEffects reset at Reboot
No research data yet
Complete your first Operation to fund the lab.
RUN HISTORY & META PROGRESSION
Archive
Keep the knowledge. Rebuild the infrastructure. Each Cold Reboot opens a more specialized route through the next run.
HOW ARCHIVE WORKSFinish Zero → choose Doctrine → keep a lessonShow loop
1Finish ZeroComplete the current run→YOUChoose DoctrineDefine the next run→KEEPArchive lessonPermanent progress remains
Cold Reboot
Complete the Zero Kernel, then choose one Doctrine for the next run.
RELAY DOCTRINE
One Reboot decision
Finish the Zero Kernel to combine a next-run identity with one permanent lesson.
PERSONAL BESTS
Network records
These records persist across Cold Reboots and give each completed run a measurable identity.
PERMANENT ARCHIVE
Earned network seals
Only earned seals reveal their identity; the next discovery remains unknown.
RUN JOURNAL
Recorded moments
The Archive shows what this run has achieved without previewing its future checklist.