In rSpace there is no copy-paste between apps. Every message, task, event, payment and vote is a single living object — re-viewed by many rApps, re-projected into any coordinate system, wired into flows, and governed peer-to-peer even when you're offline. Step through it.
Here are 25 data objects — messages, tasks, events, payments and docs, each drawn as its own shape and colour (its home rApp). There are no separate "views" to build. Step the projection and watch the same objects re-arrange — each one keeps its shape, colour and identity no matter how you look at it. Drag any object; it stays itself.
A single object — "Pay the catering invoice" — lives once. Each rApp lends it a different body (Morpheus calls these forms). Step through its lives. The identity never changes and nothing is ever copied: watch copies: 0 hold while only the changed cell re-derives.
Every rApp is a node with ports. Drag nodes to arrange. Click an output port then an input port to wire them — data streams as particles, transformed by Morpheus forges along the way. Add nodes from the palette, or load the value-flow preset to watch money split, get taxed by demurrage, and settle.
Five peers each run rSpace on their own device. Click a peer to cycle its vote · drag from one peer to another to delegate (liquid democracy — power flows transitively) · toggle a peer offline and keep editing locally. Reconnect and the CRDTs converge. Cycles circulate harmlessly — a signal, not fraud.
This is rFlows. A shared pool is split across work areas in proportion to the governance delegated to each area (the per-axis delegation from §4 — finance to your treasurer, infra to your builder). Within an area, a task only draws funds once its support crosses the threshold; funded tasks then share that area's budget proportionally to their backing. Drag a bar's support up and down; slide an area's mandate; watch the euros re-allocate live.
A linear time axis has to list every occurrence. But fold that axis into a cycle and recurring events converge onto a single spoke — every Friday lands on Friday. The recurrence stops being hundreds of stored events and becomes one rule. A calendar is just a folded line — and that fold is a massive compute win: store the generator, not the instances. Step it, and change the fold modulus to make different rhythms appear.