Z+ Language Reference
Signal flow. Nothing else. Z+ describes connections between signals. The OS resolves them. You don't tell the machine what to do. You tell it what's connected to what.
sensor -> gate(> 20cm) -> motor
That's a program. The sensor emits. The gate evaluates. The motor responds. Continuously.
Sections
->Flow, structure, logic, temporal, and value operators. The entire language.
gate()The universal logic construct. Threshold, range, knee, sustained, on_block, composite.
delta()Rate of change. Baseline, deviation, sigma. Reason about what signals are doing, not what they are.
|Multiple signals converge. Policies: all, any, quorum. Resonance and confluence.
vaultSignal-aware data surface. Store, query, search, vector similarity, ledger, replay.
@Signal-oriented type system. Unit enforcement. Structured signals. No generics, no classes.
mde()AI models as signal graph nodes. Hardware pinning, hot-swap, cascading experts.
reflexTwo speeds of resolution. Reflex is spinal. Deliberate is cortical.
on_silenceGraceful degradation. Silence detection. Graded failure. Retry with escalation.
channelNamed merge points with storage and taps. Chat, queues, timelines, feeds.
<->Bidirectional signal flow. Request/response. The wire remembers where the signal came from.
File format
Z+ programs use the .zp extension. No imports, no main function, no boilerplate. The file is wiring. The wiring is the program.
$ ls my-project/ main.zp # primary wiring sensors.zp # sensor definitions behaviors.zp # behavior logic