01
An endless abandoned computer network corridor lined with CRT monitors and cables
SYS://01/ROOT/LAUNCHPAD000→001→011→111
■ 01_LAUNCHPAD.EXE[_][□][x]
ROOT@01:~$ ./launchpad --from=0 --to=1 █

[BOOT:OK] [NETWORK:NULL] [MODE:DEMO]

From 0
to 1._

PROGRAMMABLE TOKEN LAUNCH SYSTEM
CONFIGURE EACH BIT. VERIFY EACH STATE.
NOTHING IS BROADCAST.

MEM: 00000001 // PROC: 0101000110 01010010 01001111 01001101 00100000 00110000 00100000 01010100 01001111 00100000 00110001 00101110
■ deploy.log — tty1[_][□][x]
$ ./01 --init --network=null
[ OK ] mounted /dev/launch0
> loading kernel.module ........ done
WARN: tx_signing = 0 (disabled)
0x0000: 4652 4f4d 2030 2054 4f20 312e
fn launch(cfg: &Config) -> Result<State, Err>
  assert!(cfg.reviewed == true);
  return State::from(0b000);
[ .. ] waiting for operator input_
deploy.log: 000 -> 001 -> 011 -> 111
chmod 0101 /var/codie/home
$ █

$ ls -la /launches --sort=new # SIMULATED FEED

New signals

$ man 01 // PROCESS

000

CONFIGURE

Define identity, metadata and public links. Every switch is a 0 or a 1.

011

REVIEW

Inspect every parameter before any future transaction exists.

111

LAUNCH

Disabled. Production behavior stays 0 until on-chain rules are verified.

Codie, the pale chibi 01 terminal alien

$ whoami

Codie

Something lives inside the terminal. It watches the logs, waits in empty states, and blinks when you configure a launch. It is friendly. Probably.

01000011 01001111 01000100 01001001 01000101