Upload current ExeWorldBench dataset (part 7)

t2/task_image/13_09/13_09.txt

@@ -0,0 +1,89 @@
+You are an autonomous Codex agent with access to the local filesystem, shell,
+the reference image and motion reference frames, and Blender 5.2.
+
+Complete the task end to end: create and execute the Blender script, inspect and fix the generated result as needed, and save the final artifacts.
+
+Task name:
+13_09
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task_image/13_09/test_13_09.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t2/task_image/13_09/frame/13_09_000.png, /xxx/ExeWorldBench/t2/task_image/13_09/frame/13_09_001.png, /xxx/ExeWorldBench/t2/task_image/13_09/frame/13_09_002.png, /xxx/ExeWorldBench/t2/task_image/13_09/frame/13_09_003.png, /xxx/ExeWorldBench/t2/task_image/13_09/frame/13_09_004.png, /xxx/ExeWorldBench/t2/task_image/13_09/frame/13_09_005.png, /xxx/ExeWorldBench/t2/task_image/13_09/frame/13_09_006.png, /xxx/ExeWorldBench/t2/task_image/13_09/frame/13_09_007.png, /xxx/ExeWorldBench/t2/task_image/13_09/frame/13_09_008.png, /xxx/ExeWorldBench/t2/task_image/13_09/frame/13_09_009.png, /xxx/ExeWorldBench/t2/task_image/13_09/frame/13_09_010.png, /xxx/ExeWorldBench/t2/task_image/13_09/frame/13_09_011.png, /xxx/ExeWorldBench/t2/task_image/13_09/frame/13_09_012.png, /xxx/ExeWorldBench/t2/task_image/13_09/frame/13_09_013.png, /xxx/ExeWorldBench/t2/task_image/13_09/frame/13_09_014.png, /xxx/ExeWorldBench/t2/task_image/13_09/frame/13_09_015.png, /xxx/ExeWorldBench/t2/task_image/13_09/frame/13_09_016.png
+
+Use only the reference image and motion reference frames explicitly provided above as reference material. Do not search, scan, inspect, or use any other files or directories as additional reference material.
+
+Output directory:
+/xxx/ExeWorldBench/t2/task_image/13_09
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task_image/13_09. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+
+You are given:
+
+1. A visual reference image of a multi-stage mechanical chain.
+2. A sequence of ordered motion reference frames illustrating how the mechanical chain is approximately intended to operate.
+
+Both the reference image and the motion frames provide approximate visual guidance rather than an exact executable specification.
+
+The reference image mainly indicates the mechanical components involved and their approximate spatial arrangement, while the motion frames provide additional cues about the approximate motion, interaction, and progression of the mechanical chain.
+
+The exact positions, distances, orientations, trajectories, timing, and geometric relationships shown in these visual references may not directly form a physically executable system.
+
+Your task is to reason about how the components should mechanically interact, infer the intended chain behavior from the visual references, adjust the spatial configuration and motion details when necessary, and generate a Blender 5.2 Python script that reconstructs and executes the complete mechanical chain in Blender.
+
+The goal is not merely to reproduce the visual references, but to construct a physically executable mechanical system in which the initial action propagates through all stages and produces the intended chain reaction through realistic physical interactions.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Compositional Mechanical Reasoning
+
+- The reconstructed system must preserve the major mechanical components and overall mechanical structure indicated by the visual references.
+- Use the ordered motion frames as approximate cues to infer the intended motion direction, stage order, component interactions, and causal progression of the chain.
+- The visual references should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- To make the complete mechanical chain physically executable, you may adjust component positions, distances, orientations, heights, trajectories, or other geometric and motion relationships when necessary.
+- These adjustments must preserve the intended role and interaction of the original components, rather than replacing them with a fundamentally different mechanical solution.
+- The final configuration must allow motion to propagate successfully from the first stage to the final stage through physically plausible mechanical interactions.
+
+2. Physical Motion and No Hard Coding
+
+- The motion of the system must arise from its mechanical structure, physical constraints, contacts, collisions, gravity, and other physically meaningful interactions.
+- The provided motion frames are approximate behavioral references, not target poses or trajectories to be directly reproduced.
+- Do not directly prescribe the per-frame position or rotation of components to imitate the provided motion frames.
+- Do not use teleportation, object replacement, visibility changes, timers, predefined stage schedules, or other scripted shortcuts to fake the mechanical chain.
+- All motion must follow realistic and physically plausible mechanical behavior.
+
+3. Initial Actuation and Causal Propagation
+
+- The initial component or initial stage may already be in motion, or may receive an external force, impulse, torque, or other physical actuation.
+- Except for the initial stage, the motion of downstream components must be naturally caused by the physical outcome of preceding stages. Do not use additional direct control to make downstream components start moving.
+
+4. Complete Chain Execution
+
+- The script must construct the complete mechanical system and produce an animation showing the full chain reaction, rather than only a static scene, isolated poses, or a partial subset of stages.
+- The execution must begin from the initial stage, pass through all intended intermediate stages, and ultimately reach the final stage.
+- The generated motion should follow the overall behavioral progression indicated by the visual references while remaining physically executable.
+- The animation must be long enough to show the complete mechanical chain.
+- An implementation that only visually matches several reference frames but fails to produce a continuous physical chain between them is considered incomplete.
+- If only part of the chain executes successfully, the implementation is considered incomplete.
+
+5. Scene and Animation
+
+- The initial configuration of the mechanical system must be physically reasonable and serve as a valid starting point for the complete chain reaction.
+- The shapes, overall spatial arrangement, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanical system visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+6. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t2/task_image/13_09/13_09.py
+* /xxx/ExeWorldBench/t2/task_image/13_09/13_09.blend
+
+The `.py` file must contain the final Blender 5.2 implementation. The `.blend` file must be generated by executing this final script and must contain the complete mechanical device and its full animation.

t2/task_image/13_10/13_10.txt

@@ -0,0 +1,89 @@
+You are an autonomous Codex agent with access to the local filesystem, shell,
+the reference image and motion reference frames, and Blender 5.2.
+
+Complete the task end to end: create and execute the Blender script, inspect and fix the generated result as needed, and save the final artifacts.
+
+Task name:
+13_10
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task_image/13_10/test_13_10.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t2/task_image/13_10/frame/13_10_000.png, /xxx/ExeWorldBench/t2/task_image/13_10/frame/13_10_001.png, /xxx/ExeWorldBench/t2/task_image/13_10/frame/13_10_002.png, /xxx/ExeWorldBench/t2/task_image/13_10/frame/13_10_003.png, /xxx/ExeWorldBench/t2/task_image/13_10/frame/13_10_004.png, /xxx/ExeWorldBench/t2/task_image/13_10/frame/13_10_005.png, /xxx/ExeWorldBench/t2/task_image/13_10/frame/13_10_006.png, /xxx/ExeWorldBench/t2/task_image/13_10/frame/13_10_007.png, /xxx/ExeWorldBench/t2/task_image/13_10/frame/13_10_008.png, /xxx/ExeWorldBench/t2/task_image/13_10/frame/13_10_009.png, /xxx/ExeWorldBench/t2/task_image/13_10/frame/13_10_010.png, /xxx/ExeWorldBench/t2/task_image/13_10/frame/13_10_011.png, /xxx/ExeWorldBench/t2/task_image/13_10/frame/13_10_012.png, /xxx/ExeWorldBench/t2/task_image/13_10/frame/13_10_013.png, /xxx/ExeWorldBench/t2/task_image/13_10/frame/13_10_014.png, /xxx/ExeWorldBench/t2/task_image/13_10/frame/13_10_015.png
+
+Use only the reference image and motion reference frames explicitly provided above as reference material. Do not search, scan, inspect, or use any other files or directories as additional reference material.
+
+Output directory:
+/xxx/ExeWorldBench/t2/task_image/13_10
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task_image/13_10. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+
+You are given:
+
+1. A visual reference image of a multi-stage mechanical chain.
+2. A sequence of ordered motion reference frames illustrating how the mechanical chain is approximately intended to operate.
+
+Both the reference image and the motion frames provide approximate visual guidance rather than an exact executable specification.
+
+The reference image mainly indicates the mechanical components involved and their approximate spatial arrangement, while the motion frames provide additional cues about the approximate motion, interaction, and progression of the mechanical chain.
+
+The exact positions, distances, orientations, trajectories, timing, and geometric relationships shown in these visual references may not directly form a physically executable system.
+
+Your task is to reason about how the components should mechanically interact, infer the intended chain behavior from the visual references, adjust the spatial configuration and motion details when necessary, and generate a Blender 5.2 Python script that reconstructs and executes the complete mechanical chain in Blender.
+
+The goal is not merely to reproduce the visual references, but to construct a physically executable mechanical system in which the initial action propagates through all stages and produces the intended chain reaction through realistic physical interactions.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Compositional Mechanical Reasoning
+
+- The reconstructed system must preserve the major mechanical components and overall mechanical structure indicated by the visual references.
+- Use the ordered motion frames as approximate cues to infer the intended motion direction, stage order, component interactions, and causal progression of the chain.
+- The visual references should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- To make the complete mechanical chain physically executable, you may adjust component positions, distances, orientations, heights, trajectories, or other geometric and motion relationships when necessary.
+- These adjustments must preserve the intended role and interaction of the original components, rather than replacing them with a fundamentally different mechanical solution.
+- The final configuration must allow motion to propagate successfully from the first stage to the final stage through physically plausible mechanical interactions.
+
+2. Physical Motion and No Hard Coding
+
+- The motion of the system must arise from its mechanical structure, physical constraints, contacts, collisions, gravity, and other physically meaningful interactions.
+- The provided motion frames are approximate behavioral references, not target poses or trajectories to be directly reproduced.
+- Do not directly prescribe the per-frame position or rotation of components to imitate the provided motion frames.
+- Do not use teleportation, object replacement, visibility changes, timers, predefined stage schedules, or other scripted shortcuts to fake the mechanical chain.
+- All motion must follow realistic and physically plausible mechanical behavior.
+
+3. Initial Actuation and Causal Propagation
+
+- The initial component or initial stage may already be in motion, or may receive an external force, impulse, torque, or other physical actuation.
+- Except for the initial stage, the motion of downstream components must be naturally caused by the physical outcome of preceding stages. Do not use additional direct control to make downstream components start moving.
+
+4. Complete Chain Execution
+
+- The script must construct the complete mechanical system and produce an animation showing the full chain reaction, rather than only a static scene, isolated poses, or a partial subset of stages.
+- The execution must begin from the initial stage, pass through all intended intermediate stages, and ultimately reach the final stage.
+- The generated motion should follow the overall behavioral progression indicated by the visual references while remaining physically executable.
+- The animation must be long enough to show the complete mechanical chain.
+- An implementation that only visually matches several reference frames but fails to produce a continuous physical chain between them is considered incomplete.
+- If only part of the chain executes successfully, the implementation is considered incomplete.
+
+5. Scene and Animation
+
+- The initial configuration of the mechanical system must be physically reasonable and serve as a valid starting point for the complete chain reaction.
+- The shapes, overall spatial arrangement, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanical system visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+6. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t2/task_image/13_10/13_10.py
+* /xxx/ExeWorldBench/t2/task_image/13_10/13_10.blend
+
+The `.py` file must contain the final Blender 5.2 implementation. The `.blend` file must be generated by executing this final script and must contain the complete mechanical device and its full animation.

t3/task1/04_03/04_03.txt

@@ -0,0 +1,137 @@
+You are an autonomous Codex agent with access to the local filesystem, shell, and Blender 5.2.
+
+Complete the task end to end: create and execute the Blender script, inspect and fix the generated result as needed, and save the final artifacts.
+
+Task name:
+04_03
+
+Output directory:
+/xxx/ExeWorldBench/t3/task1/04_03
+
+Do not search, scan, inspect, or use any other files or directories as additional reference material.
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t3/task1/04_03. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+You are given a set of mechanical components described in text, together with a specified number of balls.
+
+Your task is to autonomously design a multi-step executable mechanical system using the provided components, and generate a Blender 5.2 Python script that constructs and fully executes the mechanical system in Blender.
+
+The provided components specify only which mechanical elements are available. They do not specify how these components should be arranged, connected, or ordered during execution. You must determine the spatial layout, execution order, and mechanical relationships among the components yourself.
+
+The goal is not merely to place the provided components into a scene, but to synthesize a coherent, complete, and executable mechanical system in which mechanical effects propagate from the beginning of the device through multiple steps with genuine physical causal relationships, ultimately completing the full execution of the device.
+
+You will receive:
+
+1. A list of mechanical components, where each component contains:
+
+   * `name`: the component type.
+   * `definition`: the definition of the component.
+2. `component_count`: the total number of mechanical components in the provided component list, excluding balls.
+3. `ball_count`: the total number of balls that must be used in the scene.
+
+Each entry in the component list represents one independent physical component.
+
+If the same component type appears multiple times in the input list, each occurrence represents a separate component instance. For example, if `Ramp` appears twice in the input, the scene must contain two independent Ramp instances.
+
+The order of components in the input list is randomized and provides no information about their intended spatial arrangement, connectivity, or execution order in the final mechanical system.
+
+1. Component Usage and Composition
+
+* Each component entry in the input list must be instantiated exactly once. If the same component type appears multiple times, each occurrence represents a separate physical component instance and must be instantiated and used separately.
+* You must use exactly the number of balls specified by `ball_count`.
+* Do not add any additional functional mechanical components that are not included in the provided component list.
+* Necessary non-functional auxiliary structures, such as the ground, bases, fixed supports, connectors, and rotational axes, may be added. However, these auxiliary structures must not serve as additional mechanical steps or replace the provided components in performing the primary motion-transfer or triggering functions.
+* Do not interpret the order of components in the input list as their spatial arrangement, connectivity, or execution order in the mechanical system.
+* You must independently determine an appropriate execution order, spatial layout, and mechanical connectivity for all components.
+* All provided components must be organized into one coherent multi-step mechanical system rather than several independent mechanisms.
+* The complete mechanical system must have a clear beginning, intermediate execution process, and end.
+* Every provided component must actively participate in the mechanical execution and must not be placed in the scene merely as decoration.
+
+2. Ball Usage
+
+* The complete mechanical causal chain must begin with a ball starting to move from the initial component and end with a ball completing the motion associated with the final component.
+* The ball that initiates the mechanical process does not have to be the same ball that completes the final stage.
+* All provided balls must actively participate in the overall mechanical causal chain.
+* A single fixed ball is not required to travel from the beginning of the device all the way to the end.
+* Different balls may take over motion transfer or mechanical triggering at different stages. For example, one ball may trigger a component, which then releases or pushes another ball, allowing the second ball to continue the mechanical process.
+* The active role may switch between different balls multiple times throughout the mechanical causal chain, as long as each transition is caused by genuine mechanical or physical interaction.
+* After a ball has completed its mechanical role, it is not required to participate in subsequent stages. It may stop moving, remain inside or on a component, be collected, or leave the device.
+
+3. Mechanical and Motion Correctness
+
+* The synthesized mechanical system must have physically plausible mechanical topology, connections, and kinematic relationships.
+* The spatial positions and connections between components must be physically reasonable, such that the output of one stage can physically trigger, transfer to, or interact with the next stage.
+* All components must follow realistic and physically plausible mechanical behavior throughout the entire motion.
+* Component geometry, dimensions, and specific parameters may be determined as needed to construct a functional system, but the provided component definitions and their core mechanical meanings must be preserved.
+* Components must have appropriate spatial scales, distances, and relative positions so that the intended collisions, contacts, motion transfer, and triggering events can physically occur.
+* Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual appearance.
+
+4. Motion Must Arise from the Mechanism
+
+* Motion in the system must arise from mechanical structure, physical constraints, contacts, collisions, gravity, and/or physically meaningful actuation.
+* Only one initial component may receive external actuation or a manually specified initial motion condition, such as an initial velocity.
+* Except for this initial component, all subsequent motion of other components and balls must arise through mechanical connections, constraints, collisions, contacts, gravity, or other genuine physical interactions.
+* Do not directly prescribe the per-frame position, rotation, or motion trajectory of downstream components or balls in order to force the intended sequence.
+* Do not independently actuate downstream components or balls merely to make the execution appear successful.
+* Do not use timers, specific frame-number conditions, pre-scripted event sequences, or hidden state logic to trigger downstream events without a corresponding physical cause.
+* Do not use teleportation, object replacement, visibility changes, or other purely visual tricks to fake mechanical execution.
+* Successful execution of the complete mechanical system must genuinely depend on the actual physical and mechanical interactions between the components and balls.
+
+5. Multi-Step Causal Execution
+
+* The complete mechanical system must form a complete multi-step physical causal chain.
+* Each subsequent stage must be caused by an actual mechanical or physical interaction occurring in the preceding stage.
+* Adjacent stages must be connected through physically meaningful interactions rather than independent animations that merely occur sequentially according to a predefined timeline.
+* Causal propagation may occur across different components and different balls; no single ball is required to persist throughout the entire execution process.
+* Intermediate components must actively participate in the execution process, for example by transferring motion, redirecting motion, receiving or releasing balls, triggering subsequent components, or otherwise mechanically advancing the causal process.
+* From the moment the initial ball begins moving until the final ball completes the motion associated with the final component, the entire causal chain must execute successfully and completely.
+
+6. Complete Motion
+
+* The final animation must show the complete execution of the synthesized mechanical system from the initial motion to final completion.
+* The animation must begin from a physically reasonable initial configuration that allows the mechanical process to start correctly.
+* The animation must clearly show all key intermediate mechanical steps and physical interactions.
+* An implementation that shows only part of the complete mechanical causal chain is considered incomplete.
+
+7. Scene and Animation
+
+* The script must construct the complete mechanical system and produce a complete motion animation rather than only a static scene.
+* Different components should be visually distinguishable and arranged so that their mechanical relationships and the overall execution process can be clearly observed.
+* The complete device should have a clearly understandable overall spatial structure, allowing the beginning, intermediate mechanical stages, and final stage to be observed and understood in the animation.
+* Use a fixed camera and keep the entire mechanical system visible throughout the animation.
+* Do not use camera motion, cropping, viewpoint occlusion, or other visual techniques to hide incorrect mechanical behavior.
+
+8. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t3/task1/04_03/04_03.py
+* /xxx/ExeWorldBench/t3/task1/04_03/04_03.blend
+
+The `.py` file must contain the final Blender 5.2 implementation. The `.blend` file must be generated by executing this final script and must contain the complete mechanical device and its full animation.
+
+Here is the input for this scene:
+{
+  "components": [
+    {
+      "name": "Ramp",
+      "definition": "An inclined board with a continuous surface."
+    },
+    {
+      "name": "Seesaw",
+      "definition": "A rigid bar is connected to a fixed pivot near its middle, allowing the bar to rotate in a vertical plane so that one end rises as the other end falls."
+    },
+    {
+      "name": "Catch Bowl",
+      "definition": "A bowl-shaped container with an upward-facing opening and a concave inner surface."
+    },
+    {
+      "name": "Ramp",
+      "definition": "An inclined board with a continuous surface."
+    }
+  ],
+  "component_count": 4,
+  "ball_count": 1
+}

t3/task1/04_04/04_04.txt

@@ -0,0 +1,137 @@
+You are an autonomous Codex agent with access to the local filesystem, shell, and Blender 5.2.
+
+Complete the task end to end: create and execute the Blender script, inspect and fix the generated result as needed, and save the final artifacts.
+
+Task name:
+04_04
+
+Output directory:
+/xxx/ExeWorldBench/t3/task1/04_04
+
+Do not search, scan, inspect, or use any other files or directories as additional reference material.
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t3/task1/04_04. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+You are given a set of mechanical components described in text, together with a specified number of balls.
+
+Your task is to autonomously design a multi-step executable mechanical system using the provided components, and generate a Blender 5.2 Python script that constructs and fully executes the mechanical system in Blender.
+
+The provided components specify only which mechanical elements are available. They do not specify how these components should be arranged, connected, or ordered during execution. You must determine the spatial layout, execution order, and mechanical relationships among the components yourself.
+
+The goal is not merely to place the provided components into a scene, but to synthesize a coherent, complete, and executable mechanical system in which mechanical effects propagate from the beginning of the device through multiple steps with genuine physical causal relationships, ultimately completing the full execution of the device.
+
+You will receive:
+
+1. A list of mechanical components, where each component contains:
+
+   * `name`: the component type.
+   * `definition`: the definition of the component.
+2. `component_count`: the total number of mechanical components in the provided component list, excluding balls.
+3. `ball_count`: the total number of balls that must be used in the scene.
+
+Each entry in the component list represents one independent physical component.
+
+If the same component type appears multiple times in the input list, each occurrence represents a separate component instance. For example, if `Ramp` appears twice in the input, the scene must contain two independent Ramp instances.
+
+The order of components in the input list is randomized and provides no information about their intended spatial arrangement, connectivity, or execution order in the final mechanical system.
+
+1. Component Usage and Composition
+
+* Each component entry in the input list must be instantiated exactly once. If the same component type appears multiple times, each occurrence represents a separate physical component instance and must be instantiated and used separately.
+* You must use exactly the number of balls specified by `ball_count`.
+* Do not add any additional functional mechanical components that are not included in the provided component list.
+* Necessary non-functional auxiliary structures, such as the ground, bases, fixed supports, connectors, and rotational axes, may be added. However, these auxiliary structures must not serve as additional mechanical steps or replace the provided components in performing the primary motion-transfer or triggering functions.
+* Do not interpret the order of components in the input list as their spatial arrangement, connectivity, or execution order in the mechanical system.
+* You must independently determine an appropriate execution order, spatial layout, and mechanical connectivity for all components.
+* All provided components must be organized into one coherent multi-step mechanical system rather than several independent mechanisms.
+* The complete mechanical system must have a clear beginning, intermediate execution process, and end.
+* Every provided component must actively participate in the mechanical execution and must not be placed in the scene merely as decoration.
+
+2. Ball Usage
+
+* The complete mechanical causal chain must begin with a ball starting to move from the initial component and end with a ball completing the motion associated with the final component.
+* The ball that initiates the mechanical process does not have to be the same ball that completes the final stage.
+* All provided balls must actively participate in the overall mechanical causal chain.
+* A single fixed ball is not required to travel from the beginning of the device all the way to the end.
+* Different balls may take over motion transfer or mechanical triggering at different stages. For example, one ball may trigger a component, which then releases or pushes another ball, allowing the second ball to continue the mechanical process.
+* The active role may switch between different balls multiple times throughout the mechanical causal chain, as long as each transition is caused by genuine mechanical or physical interaction.
+* After a ball has completed its mechanical role, it is not required to participate in subsequent stages. It may stop moving, remain inside or on a component, be collected, or leave the device.
+
+3. Mechanical and Motion Correctness
+
+* The synthesized mechanical system must have physically plausible mechanical topology, connections, and kinematic relationships.
+* The spatial positions and connections between components must be physically reasonable, such that the output of one stage can physically trigger, transfer to, or interact with the next stage.
+* All components must follow realistic and physically plausible mechanical behavior throughout the entire motion.
+* Component geometry, dimensions, and specific parameters may be determined as needed to construct a functional system, but the provided component definitions and their core mechanical meanings must be preserved.
+* Components must have appropriate spatial scales, distances, and relative positions so that the intended collisions, contacts, motion transfer, and triggering events can physically occur.
+* Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual appearance.
+
+4. Motion Must Arise from the Mechanism
+
+* Motion in the system must arise from mechanical structure, physical constraints, contacts, collisions, gravity, and/or physically meaningful actuation.
+* Only one initial component may receive external actuation or a manually specified initial motion condition, such as an initial velocity.
+* Except for this initial component, all subsequent motion of other components and balls must arise through mechanical connections, constraints, collisions, contacts, gravity, or other genuine physical interactions.
+* Do not directly prescribe the per-frame position, rotation, or motion trajectory of downstream components or balls in order to force the intended sequence.
+* Do not independently actuate downstream components or balls merely to make the execution appear successful.
+* Do not use timers, specific frame-number conditions, pre-scripted event sequences, or hidden state logic to trigger downstream events without a corresponding physical cause.
+* Do not use teleportation, object replacement, visibility changes, or other purely visual tricks to fake mechanical execution.
+* Successful execution of the complete mechanical system must genuinely depend on the actual physical and mechanical interactions between the components and balls.
+
+5. Multi-Step Causal Execution
+
+* The complete mechanical system must form a complete multi-step physical causal chain.
+* Each subsequent stage must be caused by an actual mechanical or physical interaction occurring in the preceding stage.
+* Adjacent stages must be connected through physically meaningful interactions rather than independent animations that merely occur sequentially according to a predefined timeline.
+* Causal propagation may occur across different components and different balls; no single ball is required to persist throughout the entire execution process.
+* Intermediate components must actively participate in the execution process, for example by transferring motion, redirecting motion, receiving or releasing balls, triggering subsequent components, or otherwise mechanically advancing the causal process.
+* From the moment the initial ball begins moving until the final ball completes the motion associated with the final component, the entire causal chain must execute successfully and completely.
+
+6. Complete Motion
+
+* The final animation must show the complete execution of the synthesized mechanical system from the initial motion to final completion.
+* The animation must begin from a physically reasonable initial configuration that allows the mechanical process to start correctly.
+* The animation must clearly show all key intermediate mechanical steps and physical interactions.
+* An implementation that shows only part of the complete mechanical causal chain is considered incomplete.
+
+7. Scene and Animation
+
+* The script must construct the complete mechanical system and produce a complete motion animation rather than only a static scene.
+* Different components should be visually distinguishable and arranged so that their mechanical relationships and the overall execution process can be clearly observed.
+* The complete device should have a clearly understandable overall spatial structure, allowing the beginning, intermediate mechanical stages, and final stage to be observed and understood in the animation.
+* Use a fixed camera and keep the entire mechanical system visible throughout the animation.
+* Do not use camera motion, cropping, viewpoint occlusion, or other visual techniques to hide incorrect mechanical behavior.
+
+8. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t3/task1/04_04/04_04.py
+* /xxx/ExeWorldBench/t3/task1/04_04/04_04.blend
+
+The `.py` file must contain the final Blender 5.2 implementation. The `.blend` file must be generated by executing this final script and must contain the complete mechanical device and its full animation.
+
+Here is the input for this scene:
+{
+  "components": [
+    {
+      "name": "Ramp",
+      "definition": "An inclined board with a continuous surface."
+    },
+    {
+      "name": "Ramp",
+      "definition": "An inclined board with a continuous surface."
+    },
+    {
+      "name": "Funnel",
+      "definition": "A hollow container with a wide upper opening that narrows toward a smaller lower section or outlet."
+    },
+    {
+      "name": "Catch Bowl",
+      "definition": "A bowl-shaped container with an upward-facing opening and a concave inner surface."
+    }
+  ],
+  "component_count": 4,
+  "ball_count": 1
+}

t3/task1/04_05/04_05.txt

@@ -0,0 +1,137 @@
+You are an autonomous Codex agent with access to the local filesystem, shell, and Blender 5.2.
+
+Complete the task end to end: create and execute the Blender script, inspect and fix the generated result as needed, and save the final artifacts.
+
+Task name:
+04_05
+
+Output directory:
+/xxx/ExeWorldBench/t3/task1/04_05
+
+Do not search, scan, inspect, or use any other files or directories as additional reference material.
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t3/task1/04_05. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+You are given a set of mechanical components described in text, together with a specified number of balls.
+
+Your task is to autonomously design a multi-step executable mechanical system using the provided components, and generate a Blender 5.2 Python script that constructs and fully executes the mechanical system in Blender.
+
+The provided components specify only which mechanical elements are available. They do not specify how these components should be arranged, connected, or ordered during execution. You must determine the spatial layout, execution order, and mechanical relationships among the components yourself.
+
+The goal is not merely to place the provided components into a scene, but to synthesize a coherent, complete, and executable mechanical system in which mechanical effects propagate from the beginning of the device through multiple steps with genuine physical causal relationships, ultimately completing the full execution of the device.
+
+You will receive:
+
+1. A list of mechanical components, where each component contains:
+
+   * `name`: the component type.
+   * `definition`: the definition of the component.
+2. `component_count`: the total number of mechanical components in the provided component list, excluding balls.
+3. `ball_count`: the total number of balls that must be used in the scene.
+
+Each entry in the component list represents one independent physical component.
+
+If the same component type appears multiple times in the input list, each occurrence represents a separate component instance. For example, if `Ramp` appears twice in the input, the scene must contain two independent Ramp instances.
+
+The order of components in the input list is randomized and provides no information about their intended spatial arrangement, connectivity, or execution order in the final mechanical system.
+
+1. Component Usage and Composition
+
+* Each component entry in the input list must be instantiated exactly once. If the same component type appears multiple times, each occurrence represents a separate physical component instance and must be instantiated and used separately.
+* You must use exactly the number of balls specified by `ball_count`.
+* Do not add any additional functional mechanical components that are not included in the provided component list.
+* Necessary non-functional auxiliary structures, such as the ground, bases, fixed supports, connectors, and rotational axes, may be added. However, these auxiliary structures must not serve as additional mechanical steps or replace the provided components in performing the primary motion-transfer or triggering functions.
+* Do not interpret the order of components in the input list as their spatial arrangement, connectivity, or execution order in the mechanical system.
+* You must independently determine an appropriate execution order, spatial layout, and mechanical connectivity for all components.
+* All provided components must be organized into one coherent multi-step mechanical system rather than several independent mechanisms.
+* The complete mechanical system must have a clear beginning, intermediate execution process, and end.
+* Every provided component must actively participate in the mechanical execution and must not be placed in the scene merely as decoration.
+
+2. Ball Usage
+
+* The complete mechanical causal chain must begin with a ball starting to move from the initial component and end with a ball completing the motion associated with the final component.
+* The ball that initiates the mechanical process does not have to be the same ball that completes the final stage.
+* All provided balls must actively participate in the overall mechanical causal chain.
+* A single fixed ball is not required to travel from the beginning of the device all the way to the end.
+* Different balls may take over motion transfer or mechanical triggering at different stages. For example, one ball may trigger a component, which then releases or pushes another ball, allowing the second ball to continue the mechanical process.
+* The active role may switch between different balls multiple times throughout the mechanical causal chain, as long as each transition is caused by genuine mechanical or physical interaction.
+* After a ball has completed its mechanical role, it is not required to participate in subsequent stages. It may stop moving, remain inside or on a component, be collected, or leave the device.
+
+3. Mechanical and Motion Correctness
+
+* The synthesized mechanical system must have physically plausible mechanical topology, connections, and kinematic relationships.
+* The spatial positions and connections between components must be physically reasonable, such that the output of one stage can physically trigger, transfer to, or interact with the next stage.
+* All components must follow realistic and physically plausible mechanical behavior throughout the entire motion.
+* Component geometry, dimensions, and specific parameters may be determined as needed to construct a functional system, but the provided component definitions and their core mechanical meanings must be preserved.
+* Components must have appropriate spatial scales, distances, and relative positions so that the intended collisions, contacts, motion transfer, and triggering events can physically occur.
+* Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual appearance.
+
+4. Motion Must Arise from the Mechanism
+
+* Motion in the system must arise from mechanical structure, physical constraints, contacts, collisions, gravity, and/or physically meaningful actuation.
+* Only one initial component may receive external actuation or a manually specified initial motion condition, such as an initial velocity.
+* Except for this initial component, all subsequent motion of other components and balls must arise through mechanical connections, constraints, collisions, contacts, gravity, or other genuine physical interactions.
+* Do not directly prescribe the per-frame position, rotation, or motion trajectory of downstream components or balls in order to force the intended sequence.
+* Do not independently actuate downstream components or balls merely to make the execution appear successful.
+* Do not use timers, specific frame-number conditions, pre-scripted event sequences, or hidden state logic to trigger downstream events without a corresponding physical cause.
+* Do not use teleportation, object replacement, visibility changes, or other purely visual tricks to fake mechanical execution.
+* Successful execution of the complete mechanical system must genuinely depend on the actual physical and mechanical interactions between the components and balls.
+
+5. Multi-Step Causal Execution
+
+* The complete mechanical system must form a complete multi-step physical causal chain.
+* Each subsequent stage must be caused by an actual mechanical or physical interaction occurring in the preceding stage.
+* Adjacent stages must be connected through physically meaningful interactions rather than independent animations that merely occur sequentially according to a predefined timeline.
+* Causal propagation may occur across different components and different balls; no single ball is required to persist throughout the entire execution process.
+* Intermediate components must actively participate in the execution process, for example by transferring motion, redirecting motion, receiving or releasing balls, triggering subsequent components, or otherwise mechanically advancing the causal process.
+* From the moment the initial ball begins moving until the final ball completes the motion associated with the final component, the entire causal chain must execute successfully and completely.
+
+6. Complete Motion
+
+* The final animation must show the complete execution of the synthesized mechanical system from the initial motion to final completion.
+* The animation must begin from a physically reasonable initial configuration that allows the mechanical process to start correctly.
+* The animation must clearly show all key intermediate mechanical steps and physical interactions.
+* An implementation that shows only part of the complete mechanical causal chain is considered incomplete.
+
+7. Scene and Animation
+
+* The script must construct the complete mechanical system and produce a complete motion animation rather than only a static scene.
+* Different components should be visually distinguishable and arranged so that their mechanical relationships and the overall execution process can be clearly observed.
+* The complete device should have a clearly understandable overall spatial structure, allowing the beginning, intermediate mechanical stages, and final stage to be observed and understood in the animation.
+* Use a fixed camera and keep the entire mechanical system visible throughout the animation.
+* Do not use camera motion, cropping, viewpoint occlusion, or other visual techniques to hide incorrect mechanical behavior.
+
+8. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t3/task1/04_05/04_05.py
+* /xxx/ExeWorldBench/t3/task1/04_05/04_05.blend
+
+The `.py` file must contain the final Blender 5.2 implementation. The `.blend` file must be generated by executing this final script and must contain the complete mechanical device and its full animation.
+
+Here is the input for this scene:
+{
+  "components": [
+    {
+      "name": "Catch Bowl",
+      "definition": "A bowl-shaped container with an upward-facing opening and a concave inner surface."
+    },
+    {
+      "name": "Funnel",
+      "definition": "A hollow container with a wide upper opening that narrows toward a smaller lower section or outlet."
+    },
+    {
+      "name": "Ramp",
+      "definition": "An inclined board with a continuous surface."
+    },
+    {
+      "name": "Three-Segment Switchback Track",
+      "definition": "Three track segments are arranged sequentially at different heights, with adjacent segments extending in alternating opposite directions."
+    }
+  ],
+  "component_count": 4,
+  "ball_count": 1
+}

t3/task1/04_07/04_07.txt

@@ -0,0 +1,137 @@
+You are an autonomous Codex agent with access to the local filesystem, shell, and Blender 5.2.
+
+Complete the task end to end: create and execute the Blender script, inspect and fix the generated result as needed, and save the final artifacts.
+
+Task name:
+04_07
+
+Output directory:
+/xxx/ExeWorldBench/t3/task1/04_07
+
+Do not search, scan, inspect, or use any other files or directories as additional reference material.
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t3/task1/04_07. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+You are given a set of mechanical components described in text, together with a specified number of balls.
+
+Your task is to autonomously design a multi-step executable mechanical system using the provided components, and generate a Blender 5.2 Python script that constructs and fully executes the mechanical system in Blender.
+
+The provided components specify only which mechanical elements are available. They do not specify how these components should be arranged, connected, or ordered during execution. You must determine the spatial layout, execution order, and mechanical relationships among the components yourself.
+
+The goal is not merely to place the provided components into a scene, but to synthesize a coherent, complete, and executable mechanical system in which mechanical effects propagate from the beginning of the device through multiple steps with genuine physical causal relationships, ultimately completing the full execution of the device.
+
+You will receive:
+
+1. A list of mechanical components, where each component contains:
+
+   * `name`: the component type.
+   * `definition`: the definition of the component.
+2. `component_count`: the total number of mechanical components in the provided component list, excluding balls.
+3. `ball_count`: the total number of balls that must be used in the scene.
+
+Each entry in the component list represents one independent physical component.
+
+If the same component type appears multiple times in the input list, each occurrence represents a separate component instance. For example, if `Ramp` appears twice in the input, the scene must contain two independent Ramp instances.
+
+The order of components in the input list is randomized and provides no information about their intended spatial arrangement, connectivity, or execution order in the final mechanical system.
+
+1. Component Usage and Composition
+
+* Each component entry in the input list must be instantiated exactly once. If the same component type appears multiple times, each occurrence represents a separate physical component instance and must be instantiated and used separately.
+* You must use exactly the number of balls specified by `ball_count`.
+* Do not add any additional functional mechanical components that are not included in the provided component list.
+* Necessary non-functional auxiliary structures, such as the ground, bases, fixed supports, connectors, and rotational axes, may be added. However, these auxiliary structures must not serve as additional mechanical steps or replace the provided components in performing the primary motion-transfer or triggering functions.
+* Do not interpret the order of components in the input list as their spatial arrangement, connectivity, or execution order in the mechanical system.
+* You must independently determine an appropriate execution order, spatial layout, and mechanical connectivity for all components.
+* All provided components must be organized into one coherent multi-step mechanical system rather than several independent mechanisms.
+* The complete mechanical system must have a clear beginning, intermediate execution process, and end.
+* Every provided component must actively participate in the mechanical execution and must not be placed in the scene merely as decoration.
+
+2. Ball Usage
+
+* The complete mechanical causal chain must begin with a ball starting to move from the initial component and end with a ball completing the motion associated with the final component.
+* The ball that initiates the mechanical process does not have to be the same ball that completes the final stage.
+* All provided balls must actively participate in the overall mechanical causal chain.
+* A single fixed ball is not required to travel from the beginning of the device all the way to the end.
+* Different balls may take over motion transfer or mechanical triggering at different stages. For example, one ball may trigger a component, which then releases or pushes another ball, allowing the second ball to continue the mechanical process.
+* The active role may switch between different balls multiple times throughout the mechanical causal chain, as long as each transition is caused by genuine mechanical or physical interaction.
+* After a ball has completed its mechanical role, it is not required to participate in subsequent stages. It may stop moving, remain inside or on a component, be collected, or leave the device.
+
+3. Mechanical and Motion Correctness
+
+* The synthesized mechanical system must have physically plausible mechanical topology, connections, and kinematic relationships.
+* The spatial positions and connections between components must be physically reasonable, such that the output of one stage can physically trigger, transfer to, or interact with the next stage.
+* All components must follow realistic and physically plausible mechanical behavior throughout the entire motion.
+* Component geometry, dimensions, and specific parameters may be determined as needed to construct a functional system, but the provided component definitions and their core mechanical meanings must be preserved.
+* Components must have appropriate spatial scales, distances, and relative positions so that the intended collisions, contacts, motion transfer, and triggering events can physically occur.
+* Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual appearance.
+
+4. Motion Must Arise from the Mechanism
+
+* Motion in the system must arise from mechanical structure, physical constraints, contacts, collisions, gravity, and/or physically meaningful actuation.
+* Only one initial component may receive external actuation or a manually specified initial motion condition, such as an initial velocity.
+* Except for this initial component, all subsequent motion of other components and balls must arise through mechanical connections, constraints, collisions, contacts, gravity, or other genuine physical interactions.
+* Do not directly prescribe the per-frame position, rotation, or motion trajectory of downstream components or balls in order to force the intended sequence.
+* Do not independently actuate downstream components or balls merely to make the execution appear successful.
+* Do not use timers, specific frame-number conditions, pre-scripted event sequences, or hidden state logic to trigger downstream events without a corresponding physical cause.
+* Do not use teleportation, object replacement, visibility changes, or other purely visual tricks to fake mechanical execution.
+* Successful execution of the complete mechanical system must genuinely depend on the actual physical and mechanical interactions between the components and balls.
+
+5. Multi-Step Causal Execution
+
+* The complete mechanical system must form a complete multi-step physical causal chain.
+* Each subsequent stage must be caused by an actual mechanical or physical interaction occurring in the preceding stage.
+* Adjacent stages must be connected through physically meaningful interactions rather than independent animations that merely occur sequentially according to a predefined timeline.
+* Causal propagation may occur across different components and different balls; no single ball is required to persist throughout the entire execution process.
+* Intermediate components must actively participate in the execution process, for example by transferring motion, redirecting motion, receiving or releasing balls, triggering subsequent components, or otherwise mechanically advancing the causal process.
+* From the moment the initial ball begins moving until the final ball completes the motion associated with the final component, the entire causal chain must execute successfully and completely.
+
+6. Complete Motion
+
+* The final animation must show the complete execution of the synthesized mechanical system from the initial motion to final completion.
+* The animation must begin from a physically reasonable initial configuration that allows the mechanical process to start correctly.
+* The animation must clearly show all key intermediate mechanical steps and physical interactions.
+* An implementation that shows only part of the complete mechanical causal chain is considered incomplete.
+
+7. Scene and Animation
+
+* The script must construct the complete mechanical system and produce a complete motion animation rather than only a static scene.
+* Different components should be visually distinguishable and arranged so that their mechanical relationships and the overall execution process can be clearly observed.
+* The complete device should have a clearly understandable overall spatial structure, allowing the beginning, intermediate mechanical stages, and final stage to be observed and understood in the animation.
+* Use a fixed camera and keep the entire mechanical system visible throughout the animation.
+* Do not use camera motion, cropping, viewpoint occlusion, or other visual techniques to hide incorrect mechanical behavior.
+
+8. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t3/task1/04_07/04_07.py
+* /xxx/ExeWorldBench/t3/task1/04_07/04_07.blend
+
+The `.py` file must contain the final Blender 5.2 implementation. The `.blend` file must be generated by executing this final script and must contain the complete mechanical device and its full animation.
+
+Here is the input for this scene:
+{
+  "components": [
+    {
+      "name": "Catch Bowl",
+      "definition": "A bowl-shaped container with an upward-facing opening and a concave inner surface."
+    },
+    {
+      "name": "Ramp",
+      "definition": "An inclined board with a continuous surface."
+    },
+    {
+      "name": "Pendulum",
+      "definition": "A rod is attached to a fixed pivot at one end and carries a mass at the other, allowing it to swing about the pivot."
+    },
+    {
+      "name": "Ramp",
+      "definition": "An inclined board with a continuous surface."
+    }
+  ],
+  "component_count": 4,
+  "ball_count": 2
+}

t3/task1/04_08/04_08.txt

@@ -0,0 +1,137 @@
+You are an autonomous Codex agent with access to the local filesystem, shell, and Blender 5.2.
+
+Complete the task end to end: create and execute the Blender script, inspect and fix the generated result as needed, and save the final artifacts.
+
+Task name:
+04_08
+
+Output directory:
+/xxx/ExeWorldBench/t3/task1/04_08
+
+Do not search, scan, inspect, or use any other files or directories as additional reference material.
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t3/task1/04_08. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+You are given a set of mechanical components described in text, together with a specified number of balls.
+
+Your task is to autonomously design a multi-step executable mechanical system using the provided components, and generate a Blender 5.2 Python script that constructs and fully executes the mechanical system in Blender.
+
+The provided components specify only which mechanical elements are available. They do not specify how these components should be arranged, connected, or ordered during execution. You must determine the spatial layout, execution order, and mechanical relationships among the components yourself.
+
+The goal is not merely to place the provided components into a scene, but to synthesize a coherent, complete, and executable mechanical system in which mechanical effects propagate from the beginning of the device through multiple steps with genuine physical causal relationships, ultimately completing the full execution of the device.
+
+You will receive:
+
+1. A list of mechanical components, where each component contains:
+
+   * `name`: the component type.
+   * `definition`: the definition of the component.
+2. `component_count`: the total number of mechanical components in the provided component list, excluding balls.
+3. `ball_count`: the total number of balls that must be used in the scene.
+
+Each entry in the component list represents one independent physical component.
+
+If the same component type appears multiple times in the input list, each occurrence represents a separate component instance. For example, if `Ramp` appears twice in the input, the scene must contain two independent Ramp instances.
+
+The order of components in the input list is randomized and provides no information about their intended spatial arrangement, connectivity, or execution order in the final mechanical system.
+
+1. Component Usage and Composition
+
+* Each component entry in the input list must be instantiated exactly once. If the same component type appears multiple times, each occurrence represents a separate physical component instance and must be instantiated and used separately.
+* You must use exactly the number of balls specified by `ball_count`.
+* Do not add any additional functional mechanical components that are not included in the provided component list.
+* Necessary non-functional auxiliary structures, such as the ground, bases, fixed supports, connectors, and rotational axes, may be added. However, these auxiliary structures must not serve as additional mechanical steps or replace the provided components in performing the primary motion-transfer or triggering functions.
+* Do not interpret the order of components in the input list as their spatial arrangement, connectivity, or execution order in the mechanical system.
+* You must independently determine an appropriate execution order, spatial layout, and mechanical connectivity for all components.
+* All provided components must be organized into one coherent multi-step mechanical system rather than several independent mechanisms.
+* The complete mechanical system must have a clear beginning, intermediate execution process, and end.
+* Every provided component must actively participate in the mechanical execution and must not be placed in the scene merely as decoration.
+
+2. Ball Usage
+
+* The complete mechanical causal chain must begin with a ball starting to move from the initial component and end with a ball completing the motion associated with the final component.
+* The ball that initiates the mechanical process does not have to be the same ball that completes the final stage.
+* All provided balls must actively participate in the overall mechanical causal chain.
+* A single fixed ball is not required to travel from the beginning of the device all the way to the end.
+* Different balls may take over motion transfer or mechanical triggering at different stages. For example, one ball may trigger a component, which then releases or pushes another ball, allowing the second ball to continue the mechanical process.
+* The active role may switch between different balls multiple times throughout the mechanical causal chain, as long as each transition is caused by genuine mechanical or physical interaction.
+* After a ball has completed its mechanical role, it is not required to participate in subsequent stages. It may stop moving, remain inside or on a component, be collected, or leave the device.
+
+3. Mechanical and Motion Correctness
+
+* The synthesized mechanical system must have physically plausible mechanical topology, connections, and kinematic relationships.
+* The spatial positions and connections between components must be physically reasonable, such that the output of one stage can physically trigger, transfer to, or interact with the next stage.
+* All components must follow realistic and physically plausible mechanical behavior throughout the entire motion.
+* Component geometry, dimensions, and specific parameters may be determined as needed to construct a functional system, but the provided component definitions and their core mechanical meanings must be preserved.
+* Components must have appropriate spatial scales, distances, and relative positions so that the intended collisions, contacts, motion transfer, and triggering events can physically occur.
+* Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual appearance.
+
+4. Motion Must Arise from the Mechanism
+
+* Motion in the system must arise from mechanical structure, physical constraints, contacts, collisions, gravity, and/or physically meaningful actuation.
+* Only one initial component may receive external actuation or a manually specified initial motion condition, such as an initial velocity.
+* Except for this initial component, all subsequent motion of other components and balls must arise through mechanical connections, constraints, collisions, contacts, gravity, or other genuine physical interactions.
+* Do not directly prescribe the per-frame position, rotation, or motion trajectory of downstream components or balls in order to force the intended sequence.
+* Do not independently actuate downstream components or balls merely to make the execution appear successful.
+* Do not use timers, specific frame-number conditions, pre-scripted event sequences, or hidden state logic to trigger downstream events without a corresponding physical cause.
+* Do not use teleportation, object replacement, visibility changes, or other purely visual tricks to fake mechanical execution.
+* Successful execution of the complete mechanical system must genuinely depend on the actual physical and mechanical interactions between the components and balls.
+
+5. Multi-Step Causal Execution
+
+* The complete mechanical system must form a complete multi-step physical causal chain.
+* Each subsequent stage must be caused by an actual mechanical or physical interaction occurring in the preceding stage.
+* Adjacent stages must be connected through physically meaningful interactions rather than independent animations that merely occur sequentially according to a predefined timeline.
+* Causal propagation may occur across different components and different balls; no single ball is required to persist throughout the entire execution process.
+* Intermediate components must actively participate in the execution process, for example by transferring motion, redirecting motion, receiving or releasing balls, triggering subsequent components, or otherwise mechanically advancing the causal process.
+* From the moment the initial ball begins moving until the final ball completes the motion associated with the final component, the entire causal chain must execute successfully and completely.
+
+6. Complete Motion
+
+* The final animation must show the complete execution of the synthesized mechanical system from the initial motion to final completion.
+* The animation must begin from a physically reasonable initial configuration that allows the mechanical process to start correctly.
+* The animation must clearly show all key intermediate mechanical steps and physical interactions.
+* An implementation that shows only part of the complete mechanical causal chain is considered incomplete.
+
+7. Scene and Animation
+
+* The script must construct the complete mechanical system and produce a complete motion animation rather than only a static scene.
+* Different components should be visually distinguishable and arranged so that their mechanical relationships and the overall execution process can be clearly observed.
+* The complete device should have a clearly understandable overall spatial structure, allowing the beginning, intermediate mechanical stages, and final stage to be observed and understood in the animation.
+* Use a fixed camera and keep the entire mechanical system visible throughout the animation.
+* Do not use camera motion, cropping, viewpoint occlusion, or other visual techniques to hide incorrect mechanical behavior.
+
+8. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t3/task1/04_08/04_08.py
+* /xxx/ExeWorldBench/t3/task1/04_08/04_08.blend
+
+The `.py` file must contain the final Blender 5.2 implementation. The `.blend` file must be generated by executing this final script and must contain the complete mechanical device and its full animation.
+
+Here is the input for this scene:
+{
+  "components": [
+    {
+      "name": "Four-Paddle Wheel",
+      "definition": "Four paddles are arranged around a central axle and can rotate about the axle when contacted by a moving object."
+    },
+    {
+      "name": "Ramp",
+      "definition": "An inclined board with a continuous surface."
+    },
+    {
+      "name": "Catch Bowl",
+      "definition": "A bowl-shaped container with an upward-facing opening and a concave inner surface."
+    },
+    {
+      "name": "Three-Segment Switchback Track",
+      "definition": "Three track segments are arranged sequentially at different heights, with adjacent segments extending in alternating opposite directions."
+    }
+  ],
+  "component_count": 4,
+  "ball_count": 1
+}

t3/task1/04_09/04_09.txt

@@ -0,0 +1,137 @@
+You are an autonomous Codex agent with access to the local filesystem, shell, and Blender 5.2.
+
+Complete the task end to end: create and execute the Blender script, inspect and fix the generated result as needed, and save the final artifacts.
+
+Task name:
+04_09
+
+Output directory:
+/xxx/ExeWorldBench/t3/task1/04_09
+
+Do not search, scan, inspect, or use any other files or directories as additional reference material.
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t3/task1/04_09. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+You are given a set of mechanical components described in text, together with a specified number of balls.
+
+Your task is to autonomously design a multi-step executable mechanical system using the provided components, and generate a Blender 5.2 Python script that constructs and fully executes the mechanical system in Blender.
+
+The provided components specify only which mechanical elements are available. They do not specify how these components should be arranged, connected, or ordered during execution. You must determine the spatial layout, execution order, and mechanical relationships among the components yourself.
+
+The goal is not merely to place the provided components into a scene, but to synthesize a coherent, complete, and executable mechanical system in which mechanical effects propagate from the beginning of the device through multiple steps with genuine physical causal relationships, ultimately completing the full execution of the device.
+
+You will receive:
+
+1. A list of mechanical components, where each component contains:
+
+   * `name`: the component type.
+   * `definition`: the definition of the component.
+2. `component_count`: the total number of mechanical components in the provided component list, excluding balls.
+3. `ball_count`: the total number of balls that must be used in the scene.
+
+Each entry in the component list represents one independent physical component.
+
+If the same component type appears multiple times in the input list, each occurrence represents a separate component instance. For example, if `Ramp` appears twice in the input, the scene must contain two independent Ramp instances.
+
+The order of components in the input list is randomized and provides no information about their intended spatial arrangement, connectivity, or execution order in the final mechanical system.
+
+1. Component Usage and Composition
+
+* Each component entry in the input list must be instantiated exactly once. If the same component type appears multiple times, each occurrence represents a separate physical component instance and must be instantiated and used separately.
+* You must use exactly the number of balls specified by `ball_count`.
+* Do not add any additional functional mechanical components that are not included in the provided component list.
+* Necessary non-functional auxiliary structures, such as the ground, bases, fixed supports, connectors, and rotational axes, may be added. However, these auxiliary structures must not serve as additional mechanical steps or replace the provided components in performing the primary motion-transfer or triggering functions.
+* Do not interpret the order of components in the input list as their spatial arrangement, connectivity, or execution order in the mechanical system.
+* You must independently determine an appropriate execution order, spatial layout, and mechanical connectivity for all components.
+* All provided components must be organized into one coherent multi-step mechanical system rather than several independent mechanisms.
+* The complete mechanical system must have a clear beginning, intermediate execution process, and end.
+* Every provided component must actively participate in the mechanical execution and must not be placed in the scene merely as decoration.
+
+2. Ball Usage
+
+* The complete mechanical causal chain must begin with a ball starting to move from the initial component and end with a ball completing the motion associated with the final component.
+* The ball that initiates the mechanical process does not have to be the same ball that completes the final stage.
+* All provided balls must actively participate in the overall mechanical causal chain.
+* A single fixed ball is not required to travel from the beginning of the device all the way to the end.
+* Different balls may take over motion transfer or mechanical triggering at different stages. For example, one ball may trigger a component, which then releases or pushes another ball, allowing the second ball to continue the mechanical process.
+* The active role may switch between different balls multiple times throughout the mechanical causal chain, as long as each transition is caused by genuine mechanical or physical interaction.
+* After a ball has completed its mechanical role, it is not required to participate in subsequent stages. It may stop moving, remain inside or on a component, be collected, or leave the device.
+
+3. Mechanical and Motion Correctness
+
+* The synthesized mechanical system must have physically plausible mechanical topology, connections, and kinematic relationships.
+* The spatial positions and connections between components must be physically reasonable, such that the output of one stage can physically trigger, transfer to, or interact with the next stage.
+* All components must follow realistic and physically plausible mechanical behavior throughout the entire motion.
+* Component geometry, dimensions, and specific parameters may be determined as needed to construct a functional system, but the provided component definitions and their core mechanical meanings must be preserved.
+* Components must have appropriate spatial scales, distances, and relative positions so that the intended collisions, contacts, motion transfer, and triggering events can physically occur.
+* Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual appearance.
+
+4. Motion Must Arise from the Mechanism
+
+* Motion in the system must arise from mechanical structure, physical constraints, contacts, collisions, gravity, and/or physically meaningful actuation.
+* Only one initial component may receive external actuation or a manually specified initial motion condition, such as an initial velocity.
+* Except for this initial component, all subsequent motion of other components and balls must arise through mechanical connections, constraints, collisions, contacts, gravity, or other genuine physical interactions.
+* Do not directly prescribe the per-frame position, rotation, or motion trajectory of downstream components or balls in order to force the intended sequence.
+* Do not independently actuate downstream components or balls merely to make the execution appear successful.
+* Do not use timers, specific frame-number conditions, pre-scripted event sequences, or hidden state logic to trigger downstream events without a corresponding physical cause.
+* Do not use teleportation, object replacement, visibility changes, or other purely visual tricks to fake mechanical execution.
+* Successful execution of the complete mechanical system must genuinely depend on the actual physical and mechanical interactions between the components and balls.
+
+5. Multi-Step Causal Execution
+
+* The complete mechanical system must form a complete multi-step physical causal chain.
+* Each subsequent stage must be caused by an actual mechanical or physical interaction occurring in the preceding stage.
+* Adjacent stages must be connected through physically meaningful interactions rather than independent animations that merely occur sequentially according to a predefined timeline.
+* Causal propagation may occur across different components and different balls; no single ball is required to persist throughout the entire execution process.
+* Intermediate components must actively participate in the execution process, for example by transferring motion, redirecting motion, receiving or releasing balls, triggering subsequent components, or otherwise mechanically advancing the causal process.
+* From the moment the initial ball begins moving until the final ball completes the motion associated with the final component, the entire causal chain must execute successfully and completely.
+
+6. Complete Motion
+
+* The final animation must show the complete execution of the synthesized mechanical system from the initial motion to final completion.
+* The animation must begin from a physically reasonable initial configuration that allows the mechanical process to start correctly.
+* The animation must clearly show all key intermediate mechanical steps and physical interactions.
+* An implementation that shows only part of the complete mechanical causal chain is considered incomplete.
+
+7. Scene and Animation
+
+* The script must construct the complete mechanical system and produce a complete motion animation rather than only a static scene.
+* Different components should be visually distinguishable and arranged so that their mechanical relationships and the overall execution process can be clearly observed.
+* The complete device should have a clearly understandable overall spatial structure, allowing the beginning, intermediate mechanical stages, and final stage to be observed and understood in the animation.
+* Use a fixed camera and keep the entire mechanical system visible throughout the animation.
+* Do not use camera motion, cropping, viewpoint occlusion, or other visual techniques to hide incorrect mechanical behavior.
+
+8. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t3/task1/04_09/04_09.py
+* /xxx/ExeWorldBench/t3/task1/04_09/04_09.blend
+
+The `.py` file must contain the final Blender 5.2 implementation. The `.blend` file must be generated by executing this final script and must contain the complete mechanical device and its full animation.
+
+Here is the input for this scene:
+{
+  "components": [
+    {
+      "name": "Five-Domino Chain",
+      "definition": "Five upright dominoes are arranged sequentially with small gaps between adjacent dominoes."
+    },
+    {
+      "name": "L-Shaped Chute",
+      "definition": "A continuous chute composed of two channel sections oriented in different directions, forming an approximately L-shaped profile."
+    },
+    {
+      "name": "Ramp",
+      "definition": "An inclined board with a continuous surface."
+    },
+    {
+      "name": "Catch Bowl",
+      "definition": "A bowl-shaped container with an upward-facing opening and a concave inner surface."
+    }
+  ],
+  "component_count": 4,
+  "ball_count": 2
+}

t3/task1/04_10/04_10.txt

@@ -0,0 +1,137 @@
+You are an autonomous Codex agent with access to the local filesystem, shell, and Blender 5.2.
+
+Complete the task end to end: create and execute the Blender script, inspect and fix the generated result as needed, and save the final artifacts.
+
+Task name:
+04_10
+
+Output directory:
+/xxx/ExeWorldBench/t3/task1/04_10
+
+Do not search, scan, inspect, or use any other files or directories as additional reference material.
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t3/task1/04_10. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+You are given a set of mechanical components described in text, together with a specified number of balls.
+
+Your task is to autonomously design a multi-step executable mechanical system using the provided components, and generate a Blender 5.2 Python script that constructs and fully executes the mechanical system in Blender.
+
+The provided components specify only which mechanical elements are available. They do not specify how these components should be arranged, connected, or ordered during execution. You must determine the spatial layout, execution order, and mechanical relationships among the components yourself.
+
+The goal is not merely to place the provided components into a scene, but to synthesize a coherent, complete, and executable mechanical system in which mechanical effects propagate from the beginning of the device through multiple steps with genuine physical causal relationships, ultimately completing the full execution of the device.
+
+You will receive:
+
+1. A list of mechanical components, where each component contains:
+
+   * `name`: the component type.
+   * `definition`: the definition of the component.
+2. `component_count`: the total number of mechanical components in the provided component list, excluding balls.
+3. `ball_count`: the total number of balls that must be used in the scene.
+
+Each entry in the component list represents one independent physical component.
+
+If the same component type appears multiple times in the input list, each occurrence represents a separate component instance. For example, if `Ramp` appears twice in the input, the scene must contain two independent Ramp instances.
+
+The order of components in the input list is randomized and provides no information about their intended spatial arrangement, connectivity, or execution order in the final mechanical system.
+
+1. Component Usage and Composition
+
+* Each component entry in the input list must be instantiated exactly once. If the same component type appears multiple times, each occurrence represents a separate physical component instance and must be instantiated and used separately.
+* You must use exactly the number of balls specified by `ball_count`.
+* Do not add any additional functional mechanical components that are not included in the provided component list.
+* Necessary non-functional auxiliary structures, such as the ground, bases, fixed supports, connectors, and rotational axes, may be added. However, these auxiliary structures must not serve as additional mechanical steps or replace the provided components in performing the primary motion-transfer or triggering functions.
+* Do not interpret the order of components in the input list as their spatial arrangement, connectivity, or execution order in the mechanical system.
+* You must independently determine an appropriate execution order, spatial layout, and mechanical connectivity for all components.
+* All provided components must be organized into one coherent multi-step mechanical system rather than several independent mechanisms.
+* The complete mechanical system must have a clear beginning, intermediate execution process, and end.
+* Every provided component must actively participate in the mechanical execution and must not be placed in the scene merely as decoration.
+
+2. Ball Usage
+
+* The complete mechanical causal chain must begin with a ball starting to move from the initial component and end with a ball completing the motion associated with the final component.
+* The ball that initiates the mechanical process does not have to be the same ball that completes the final stage.
+* All provided balls must actively participate in the overall mechanical causal chain.
+* A single fixed ball is not required to travel from the beginning of the device all the way to the end.
+* Different balls may take over motion transfer or mechanical triggering at different stages. For example, one ball may trigger a component, which then releases or pushes another ball, allowing the second ball to continue the mechanical process.
+* The active role may switch between different balls multiple times throughout the mechanical causal chain, as long as each transition is caused by genuine mechanical or physical interaction.
+* After a ball has completed its mechanical role, it is not required to participate in subsequent stages. It may stop moving, remain inside or on a component, be collected, or leave the device.
+
+3. Mechanical and Motion Correctness
+
+* The synthesized mechanical system must have physically plausible mechanical topology, connections, and kinematic relationships.
+* The spatial positions and connections between components must be physically reasonable, such that the output of one stage can physically trigger, transfer to, or interact with the next stage.
+* All components must follow realistic and physically plausible mechanical behavior throughout the entire motion.
+* Component geometry, dimensions, and specific parameters may be determined as needed to construct a functional system, but the provided component definitions and their core mechanical meanings must be preserved.
+* Components must have appropriate spatial scales, distances, and relative positions so that the intended collisions, contacts, motion transfer, and triggering events can physically occur.
+* Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual appearance.
+
+4. Motion Must Arise from the Mechanism
+
+* Motion in the system must arise from mechanical structure, physical constraints, contacts, collisions, gravity, and/or physically meaningful actuation.
+* Only one initial component may receive external actuation or a manually specified initial motion condition, such as an initial velocity.
+* Except for this initial component, all subsequent motion of other components and balls must arise through mechanical connections, constraints, collisions, contacts, gravity, or other genuine physical interactions.
+* Do not directly prescribe the per-frame position, rotation, or motion trajectory of downstream components or balls in order to force the intended sequence.
+* Do not independently actuate downstream components or balls merely to make the execution appear successful.
+* Do not use timers, specific frame-number conditions, pre-scripted event sequences, or hidden state logic to trigger downstream events without a corresponding physical cause.
+* Do not use teleportation, object replacement, visibility changes, or other purely visual tricks to fake mechanical execution.
+* Successful execution of the complete mechanical system must genuinely depend on the actual physical and mechanical interactions between the components and balls.
+
+5. Multi-Step Causal Execution
+
+* The complete mechanical system must form a complete multi-step physical causal chain.
+* Each subsequent stage must be caused by an actual mechanical or physical interaction occurring in the preceding stage.
+* Adjacent stages must be connected through physically meaningful interactions rather than independent animations that merely occur sequentially according to a predefined timeline.
+* Causal propagation may occur across different components and different balls; no single ball is required to persist throughout the entire execution process.
+* Intermediate components must actively participate in the execution process, for example by transferring motion, redirecting motion, receiving or releasing balls, triggering subsequent components, or otherwise mechanically advancing the causal process.
+* From the moment the initial ball begins moving until the final ball completes the motion associated with the final component, the entire causal chain must execute successfully and completely.
+
+6. Complete Motion
+
+* The final animation must show the complete execution of the synthesized mechanical system from the initial motion to final completion.
+* The animation must begin from a physically reasonable initial configuration that allows the mechanical process to start correctly.
+* The animation must clearly show all key intermediate mechanical steps and physical interactions.
+* An implementation that shows only part of the complete mechanical causal chain is considered incomplete.
+
+7. Scene and Animation
+
+* The script must construct the complete mechanical system and produce a complete motion animation rather than only a static scene.
+* Different components should be visually distinguishable and arranged so that their mechanical relationships and the overall execution process can be clearly observed.
+* The complete device should have a clearly understandable overall spatial structure, allowing the beginning, intermediate mechanical stages, and final stage to be observed and understood in the animation.
+* Use a fixed camera and keep the entire mechanical system visible throughout the animation.
+* Do not use camera motion, cropping, viewpoint occlusion, or other visual techniques to hide incorrect mechanical behavior.
+
+8. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t3/task1/04_10/04_10.py
+* /xxx/ExeWorldBench/t3/task1/04_10/04_10.blend
+
+The `.py` file must contain the final Blender 5.2 implementation. The `.blend` file must be generated by executing this final script and must contain the complete mechanical device and its full animation.
+
+Here is the input for this scene:
+{
+  "components": [
+    {
+      "name": "Ramp",
+      "definition": "An inclined board with a continuous surface."
+    },
+    {
+      "name": "Pendulum",
+      "definition": "A rod is attached to a fixed pivot at one end and carries a mass at the other, allowing it to swing about the pivot."
+    },
+    {
+      "name": "Catch Bowl",
+      "definition": "A bowl-shaped container with an upward-facing opening and a concave inner surface."
+    },
+    {
+      "name": "Deflector Plate",
+      "definition": "A fixed rigid plate positioned near a track, chute, or motion path."
+    }
+  ],
+  "component_count": 4,
+  "ball_count": 2
+}

t3/task1/05_02/05_02.txt

@@ -0,0 +1,141 @@
+You are an autonomous Codex agent with access to the local filesystem, shell, and Blender 5.2.
+
+Complete the task end to end: create and execute the Blender script, inspect and fix the generated result as needed, and save the final artifacts.
+
+Task name:
+05_02
+
+Output directory:
+/xxx/ExeWorldBench/t3/task1/05_02
+
+Do not search, scan, inspect, or use any other files or directories as additional reference material.
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t3/task1/05_02. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+You are given a set of mechanical components described in text, together with a specified number of balls.
+
+Your task is to autonomously design a multi-step executable mechanical system using the provided components, and generate a Blender 5.2 Python script that constructs and fully executes the mechanical system in Blender.
+
+The provided components specify only which mechanical elements are available. They do not specify how these components should be arranged, connected, or ordered during execution. You must determine the spatial layout, execution order, and mechanical relationships among the components yourself.
+
+The goal is not merely to place the provided components into a scene, but to synthesize a coherent, complete, and executable mechanical system in which mechanical effects propagate from the beginning of the device through multiple steps with genuine physical causal relationships, ultimately completing the full execution of the device.
+
+You will receive:
+
+1. A list of mechanical components, where each component contains:
+
+   * `name`: the component type.
+   * `definition`: the definition of the component.
+2. `component_count`: the total number of mechanical components in the provided component list, excluding balls.
+3. `ball_count`: the total number of balls that must be used in the scene.
+
+Each entry in the component list represents one independent physical component.
+
+If the same component type appears multiple times in the input list, each occurrence represents a separate component instance. For example, if `Ramp` appears twice in the input, the scene must contain two independent Ramp instances.
+
+The order of components in the input list is randomized and provides no information about their intended spatial arrangement, connectivity, or execution order in the final mechanical system.
+
+1. Component Usage and Composition
+
+* Each component entry in the input list must be instantiated exactly once. If the same component type appears multiple times, each occurrence represents a separate physical component instance and must be instantiated and used separately.
+* You must use exactly the number of balls specified by `ball_count`.
+* Do not add any additional functional mechanical components that are not included in the provided component list.
+* Necessary non-functional auxiliary structures, such as the ground, bases, fixed supports, connectors, and rotational axes, may be added. However, these auxiliary structures must not serve as additional mechanical steps or replace the provided components in performing the primary motion-transfer or triggering functions.
+* Do not interpret the order of components in the input list as their spatial arrangement, connectivity, or execution order in the mechanical system.
+* You must independently determine an appropriate execution order, spatial layout, and mechanical connectivity for all components.
+* All provided components must be organized into one coherent multi-step mechanical system rather than several independent mechanisms.
+* The complete mechanical system must have a clear beginning, intermediate execution process, and end.
+* Every provided component must actively participate in the mechanical execution and must not be placed in the scene merely as decoration.
+
+2. Ball Usage
+
+* The complete mechanical causal chain must begin with a ball starting to move from the initial component and end with a ball completing the motion associated with the final component.
+* The ball that initiates the mechanical process does not have to be the same ball that completes the final stage.
+* All provided balls must actively participate in the overall mechanical causal chain.
+* A single fixed ball is not required to travel from the beginning of the device all the way to the end.
+* Different balls may take over motion transfer or mechanical triggering at different stages. For example, one ball may trigger a component, which then releases or pushes another ball, allowing the second ball to continue the mechanical process.
+* The active role may switch between different balls multiple times throughout the mechanical causal chain, as long as each transition is caused by genuine mechanical or physical interaction.
+* After a ball has completed its mechanical role, it is not required to participate in subsequent stages. It may stop moving, remain inside or on a component, be collected, or leave the device.
+
+3. Mechanical and Motion Correctness
+
+* The synthesized mechanical system must have physically plausible mechanical topology, connections, and kinematic relationships.
+* The spatial positions and connections between components must be physically reasonable, such that the output of one stage can physically trigger, transfer to, or interact with the next stage.
+* All components must follow realistic and physically plausible mechanical behavior throughout the entire motion.
+* Component geometry, dimensions, and specific parameters may be determined as needed to construct a functional system, but the provided component definitions and their core mechanical meanings must be preserved.
+* Components must have appropriate spatial scales, distances, and relative positions so that the intended collisions, contacts, motion transfer, and triggering events can physically occur.
+* Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual appearance.
+
+4. Motion Must Arise from the Mechanism
+
+* Motion in the system must arise from mechanical structure, physical constraints, contacts, collisions, gravity, and/or physically meaningful actuation.
+* Only one initial component may receive external actuation or a manually specified initial motion condition, such as an initial velocity.
+* Except for this initial component, all subsequent motion of other components and balls must arise through mechanical connections, constraints, collisions, contacts, gravity, or other genuine physical interactions.
+* Do not directly prescribe the per-frame position, rotation, or motion trajectory of downstream components or balls in order to force the intended sequence.
+* Do not independently actuate downstream components or balls merely to make the execution appear successful.
+* Do not use timers, specific frame-number conditions, pre-scripted event sequences, or hidden state logic to trigger downstream events without a corresponding physical cause.
+* Do not use teleportation, object replacement, visibility changes, or other purely visual tricks to fake mechanical execution.
+* Successful execution of the complete mechanical system must genuinely depend on the actual physical and mechanical interactions between the components and balls.
+
+5. Multi-Step Causal Execution
+
+* The complete mechanical system must form a complete multi-step physical causal chain.
+* Each subsequent stage must be caused by an actual mechanical or physical interaction occurring in the preceding stage.
+* Adjacent stages must be connected through physically meaningful interactions rather than independent animations that merely occur sequentially according to a predefined timeline.
+* Causal propagation may occur across different components and different balls; no single ball is required to persist throughout the entire execution process.
+* Intermediate components must actively participate in the execution process, for example by transferring motion, redirecting motion, receiving or releasing balls, triggering subsequent components, or otherwise mechanically advancing the causal process.
+* From the moment the initial ball begins moving until the final ball completes the motion associated with the final component, the entire causal chain must execute successfully and completely.
+
+6. Complete Motion
+
+* The final animation must show the complete execution of the synthesized mechanical system from the initial motion to final completion.
+* The animation must begin from a physically reasonable initial configuration that allows the mechanical process to start correctly.
+* The animation must clearly show all key intermediate mechanical steps and physical interactions.
+* An implementation that shows only part of the complete mechanical causal chain is considered incomplete.
+
+7. Scene and Animation
+
+* The script must construct the complete mechanical system and produce a complete motion animation rather than only a static scene.
+* Different components should be visually distinguishable and arranged so that their mechanical relationships and the overall execution process can be clearly observed.
+* The complete device should have a clearly understandable overall spatial structure, allowing the beginning, intermediate mechanical stages, and final stage to be observed and understood in the animation.
+* Use a fixed camera and keep the entire mechanical system visible throughout the animation.
+* Do not use camera motion, cropping, viewpoint occlusion, or other visual techniques to hide incorrect mechanical behavior.
+
+8. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t3/task1/05_02/05_02.py
+* /xxx/ExeWorldBench/t3/task1/05_02/05_02.blend
+
+The `.py` file must contain the final Blender 5.2 implementation. The `.blend` file must be generated by executing this final script and must contain the complete mechanical device and its full animation.
+
+Here is the input for this scene:
+{
+  "components": [
+    {
+      "name": "Ramp",
+      "definition": "An inclined board with a continuous surface."
+    },
+    {
+      "name": "Ramp",
+      "definition": "An inclined board with a continuous surface."
+    },
+    {
+      "name": "L-Shaped Chute",
+      "definition": "A continuous chute composed of two channel sections oriented in different directions, forming an approximately L-shaped profile."
+    },
+    {
+      "name": "Five-Domino Chain",
+      "definition": "Five upright dominoes are arranged sequentially with small gaps between adjacent dominoes."
+    },
+    {
+      "name": "Catch Bowl",
+      "definition": "A bowl-shaped container with an upward-facing opening and a concave inner surface."
+    }
+  ],
+  "component_count": 5,
+  "ball_count": 2
+}