The MagicEight system implements a form of tagged-token dynamic dataflow. Instead of a normal tagged-token dataflow -- where tokens refer to data using a ``tag'' which contains both function and iteration specifiers -- a MagicEight data reference contains a tag identifying a stream object, along with the dimensions, offset and extent of the data being stored or demanded. Additional explicit dependencies are addressed using the tag of the target task token.
An initial dependency graph of tasks and streams is presented to the resource manager for execution when a program is started. The dependencies are not explicitly indicated, instead it they are embodied in the dependencies present in each stream or task object. These initial tasks, when executed, may in turn create (or merely reference existing) graphs and post them for execution. The resource manager is resposible for evaluating the graphs posted to it to produce output data. The method of evaluation selected, eduction, heavily influences the inherent fault-tolerance of a MagicEight system.