Generator logic can indirectly cause dynamic work. It does not instantiate tasks through a Generator API.
Indirect flow
The relationship follows this sequence:
- Starting State declares a collection and a work definition.
- Generator logic creates or changes a world object.
- The object's state changes collection membership or appearance.
- The runtime evaluates the declared work definition.
- The runtime creates a task instance for a new matching member.
This separation keeps task templates declarative and Generator operations focused on world state.
Identity and correlation
The runtime correlates each instance with its work definition and collection member. The snapshot records the definition ID, correlation ID, collection ID, and instantiation time.
The runtime creates an instance pair once for each definition and member. A member that re-enters does not create a second instance in the run.
Collection boundaries
An open collection can accept new instances until its declared close time. After that cutoff, new matching members do not create instances.
A work definition can cancel pending instances when their members leave the collection. This behavior comes from the authored definition, not Generator source.
Ownership boundaries
- Work definitions own authored templates and triggers.
- Runtime task instances own execution-created instance records.
- This page owns only the causal relationship with Generator state.