ROTE · DEVELOPER DOCUMENTATION

Plays, from first run to reusable method.

Run a published play in five minutes. Then learn how a recorded execution trace becomes a typed, inspectable DAG that any permitted agent can run again.

Run your first play →

READING PATH

Start with a run. Go deeper when the work demands it.

START HERERun and use a play

01Run your first playRun a published play from one URI, inspect its contract, and pass real inputs.5 min →02Work with playsSearch, inspect, pin, and share proven work without inheriting a black box.8 min →

MAKE & SHAREKeep and distribute a method

03Create your first playDo the work once in a recorded workspace, then crystallize the trace.12 min →04How the play travelsPush, discover, inspect, and pull a Play without losing identity, dependencies, privacy, or lineage.10 min →05What Plays make possibleUse Plays as operational memory, transferable expertise, evaluation tasks, and governed trajectory evidence.16 min →

UNDERSTANDLearn the execution substrate

06Anatomy of a playUnderstand the executable contract, dependency DAG, presentation, and failure model.14 min →07Three kinds of reachReach APIs, local processes, and the browser through one persistent memory.9 min →08Workspace & CAUsSee why persistent references form the dataflow graph a play can run again.10 min →

LOOK UPCommands and rules

09ReferenceCommands, grammar, failure behavior, publishing rules, and troubleshooting.lookup →