Z+ Programs

Three libraries. One language. Same signal chains everywhere.

38 curated programs across robotics, dev, the bridge between them, system stress-tests, and competition infrastructure. Plus more under construction — the corpus is 85+ .zp files and growing.

Zeros — Robotics

9 programs

Programs that start with hardware. Sensors, motors, physical things. Levels L0 → L5.

Blink

L0

LED on/off, first hardware signal

Light Chaser

L1

Photo-sensors, differential steering, moth vs cockroach

Line Follower

L1

Sensor → decision → motor loop, PID concept

Sensor Dashboard

L2

Read any sensor, display everything, recording

Sumo Bot

L2

State machines, priority, edge detection

Maze Solver

L3

Wall following, pathfinding, map building

Arm Controller

L3

Servo kinematics, record/playback, presets

Swarm

L4

Multi-robot coordination, emergent behavior, three rules

Autonomous Nav

L5

LIDAR SLAM, A* pathfinding, PID — the capstone

DereZ — Dev

11 programs

Programs that start on screen. Code, signals, creative tools, games. Levels L0 → L3.

Hello Chain

L0

First signal chain, data flow

Signal Playground

L1

Build chains live, experiment

Pixel Art Editor

L1

Input, grid, tools, export, Pico-8 palette

Music Tracker

L2

Step sequencer, audio, timing, beat

Chat Room

L2

Networking, state, presence, commands

Platform Run

L2

Physics, collision, coyote time, animation

Block Builder

L2

Voxel world, crafting, day/night, first-person

Tower Line

L3

Pathfinding, economy, targeting, splash/slow

Crew Suspect

L3

Networking, state machines, voting, vision

Bot Trainer

L3

Neural network from scratch, backprop, ML concepts

Dashboard Builder

L3

Data viz, gauges, graphs, alerts, heatmaps

Multimodal — The Bridge

8 programs

Same codebase, two targets. Game code IS robot code. Levels L2 → L4.

Shadow Bot

L2

One brain, screen or robot — switch with one line

Sound Reactive

L2

Audio FFT → screen visuals AND LED strips / servos

Weather World

L2

Real sensors drive a game world (snow, rain, night)

Mission Control

L3

Dashboard side of a signal contract

Rover

L3

Robot side — broadcast + commands

Digital Twin

L3

Physical robot + live virtual mirror

Gesture Controller

L3

Accelerometer glove → game OR robot

Battle Arena

L4

Robot combat + live broadcast + instant replay

System Programs

8 programs

Language stress tests. Prove Z+ works at scale. Each one replaces hundreds to thousands of lines of conventional code.

File Watcher

Replaces ~500 LOC of Python

Log Monitor

Replaces ~400 LOC of Python

HTTP Server

Replaces ~800 LOC of Python

Key-Value Store

Replaces ~600 LOC of Python (Redis-style)

Firewall

Replaces ~1,000 LOC of C

Chirp

A whole Twitter-class platform in ~120 lines

Goya Fleet

Self-healing accelerator fleet management

Goya Fleet T3

Tier-3 variant — bench / heal / re-route

Competition

2 programs

Tournament infrastructure for robotics events.

FIRST Challenge

Full match: autonomous + teleop + endgame

Zeros Tournament

Bracket, scheduling, scoring, leaderboard, replay

How every program is built

  1. 01Under 2 minutes to first modification — retention threshold
  2. 02Every template ships working — not a skeleton, a complete thing
  3. 03TRY THIS section in every file — 5-8 progressive experiments
  4. 04Comments explain WHY, not WHAT — respect the reader
  5. 05Same API for screen and hardware — sense() and act() everywhere
  6. 06Telemetry built in — every template has ~> dashboard lines
  7. 07Save/load via VAULT — temporal state, not manual file management
  8. 08Every game concept maps to a robot concept — documented in each file

Want to write your own?

Z+ is documented end-to-end. Paste a program into the playground and watch the signal graph resolve in real time.