Micro World Agent Storyboard

Repairs3

Skipped36

Invalid Held36

Harness Repairs36

Issue Categories10

Clean Frames36

Issue Categories

identity 22 vehicle-transport 115 phone-task 121 harness-validation 122 skipped 36 harness-invalid 36 repair 3 continuity 11 social-identity 13 spatial 64

Identity

Frame 1 identity
John's clothing and tan baseball cap match the expected continuity.
Frame 10 identity
John's shoes are not clearly visible, so brown work shoe continuity cannot be confirmed.
Frame 11 identity
John's shoes are not visible, so footwear continuity cannot be confirmed.
Frame 13 identity
John's shoes are cropped out and cannot be verified in this frame.
Frame 15 identity
No continuity issue with John's outfit or garage position is visible.
Frame 16 identity
No visible evidence that John has taken or sent the requested backyard photo yet.
Frame 20 identity
No visible evidence that John has taken or sent the requested backyard photo yet.
Frame 21 identity
John's wardrobe and physical continuity match expected state: tan baseball cap, black hoodie, blue jeans, brown work shoes.
Frame 25 identity
No visible wardrobe change for John; outfit matches expected continuity.
Frame 25 identity
John's wardrobe and pose remain consistent with the expected state.
Frame 37 identity
John's brown work shoes are not visible in this crop, so shoe continuity cannot be confirmed.
Frame 39 identity
John's shoes are cropped out and cannot be verified in this frame.
Frame 43 identity
John's shoes are not visible in this framing, so brown work shoe continuity cannot be confirmed.
Frame 44 identity
John's brown work shoes are not visible in this frame due to the crop/angle.
Frame 56 identity
John's outfit and identity remain consistent with the expected tan baseball cap, black hoodie, blue jeans, and brown work shoes.
Frame 56 identity
No visible issue with John's wardrobe continuity; outfit matches expected cap, black hoodie, jeans, and brown work shoes.
Frame 56 identity
John's outfit and tan baseball cap match the expected continuity.
Frame 56 identity
John's outfit and identity are consistent with the expected state.
Frame 58 identity
John's outfit and identity appear consistent with prior frames.
Frame 67 identity
Expected pose said John's right hand was touching the black wall control, but in this frame the control is visible and neither hand is clearly touching it.
Frame 68 identity
Expected wardrobe and pose continuity are preserved.
Frame 72 identity
Tight framing shows only John’s hand and sleeve, so his face, tan baseball cap, jeans, and brown work shoes cannot be verified in this frame.

Vehicle Transport

Frame 1 vehicle-transport
John is in the expected garage location and moving inward from the driveway as expected.
Frame 1 vehicle-transport
John's dark pickup truck is not visible; no visible vehicle damage, repair, identity, or status change can be assessed.
Frame 2 vehicle-transport
John's dark pickup truck is not in frame; no vehicle damage or identity continuity can be assessed.
Frame 3 vehicle-transport
John's dark pickup truck is not visible in this frame; vehicle identity, damage, and repair status cannot be assessed.
Frame 4 vehicle-transport
John's dark pickup truck is not in frame; no vehicle damage, repair change, or identity continuity can be assessed from this view.
Frame 5 vehicle-transport
John's dark pickup truck is not visible in this frame; no vehicle damage, repair change, or identity continuity can be assessed.
Frame 5 vehicle-transport
John's dark pickup truck is not visible, so its identity, damage, or repair state cannot be assessed.
Frame 6 vehicle-transport
John's dark pickup truck is not in frame; no visible vehicle damage, repair change, or identity continuity can be assessed.
Frame 7 vehicle-transport
John's dark pickup truck is not in frame, so persistent vehicle identity and damage status cannot be assessed.
Frame 8 vehicle-transport
John's dark pickup truck is not in frame, so persistent vehicle identity and damage status cannot be assessed.
Frame 9 vehicle-transport
John's dark pickup truck is not in frame, so persistent vehicle identity, damage, repair status, or any change cannot be assessed.
Frame 10 vehicle-transport
John's dark pickup truck is not in frame; persistent vehicle identity, damage, repair status, or change cannot be assessed.
Frame 11 vehicle-transport
John's dark pickup truck is not visible, so persistent vehicle identity, damage, repair status, or changes cannot be assessed.
Frame 12 vehicle-transport
John's dark pickup truck is not visible, so persistent vehicle identity, damage, repair status, or change cannot be assessed.
Frame 13 vehicle-transport
John's dark pickup truck is not visible, so persistent vehicle identity, damage, repair status, or any change cannot be assessed.
Frame 14 vehicle-transport
John's dark pickup truck is not visible; persistent vehicle identity, damage, repair status, or any change cannot be assessed from this frame.
Frame 15 vehicle-transport
John's dark pickup truck is not visible in this frame, so persistent vehicle identity, damage, or repair status cannot be assessed.
Frame 16 vehicle-transport
John's dark pickup truck is not visible in this tight garage-facing composition, so persistent vehicle identity, damage, or repair status cannot be assessed.
Frame 16 vehicle-transport
John's dark pickup truck is not visible in this frame; no vehicle identity, damage, repair status, or change can be assessed from this view.
Frame 16 vehicle-transport
John's dark pickup truck is not visible in this frame; vehicle identity, damage, repair status, or changes cannot be assessed.
Frame 17 vehicle-transport
John's dark pickup truck is not visible in this frame, so persistent vehicle identity, visible damage, repair status, or any change cannot be assessed.
Frame 18 vehicle-transport
John's dark pickup truck is not visible, so persistent vehicle identity, damage, repair status, or change cannot be assessed.
Frame 18 vehicle-transport
John's dark pickup truck is not visible in this frame, so vehicle identity, visible damage, repair status, or change cannot be assessed.
Frame 19 vehicle-transport
John's dark pickup truck is not in frame, so persistent vehicle identity, visible damage, repair status, or any change cannot be assessed.
Frame 20 vehicle-transport
John's dark pickup truck is not visible, so persistent vehicle identity, damage, repair status, or change cannot be assessed.
Frame 20 vehicle-transport
John's dark pickup truck is not visible in this frame; no vehicle damage, repair change, or identity continuity can be assessed.
Frame 20 vehicle-transport
John's dark pickup truck is not visible, so vehicle identity, damage, repair status, or continuity cannot be assessed.
Frame 20 vehicle-transport
John's dark pickup truck is not visible in this frame, so vehicle identity, damage, repair status, or any change cannot be assessed.
Frame 21 vehicle-transport
John's dark pickup truck is not in frame, so persistent vehicle identity, visible damage, repair status, or any change cannot be assessed.
Frame 21 vehicle-transport
John's dark pickup truck is not visible, so persistent vehicle identity, damage, repair status, or any change cannot be assessed from this frame.
Frame 21 vehicle-transport
John's dark pickup truck is not in frame, so persistent vehicle identity, visible damage, repair status, or any change cannot be assessed.
Frame 22 vehicle-transport
John's dark pickup truck is not in frame, so its persistent identity, visible damage, repair status, or any change cannot be assessed.
Frame 23 vehicle-transport
John's dark pickup truck is not visible in frame, so vehicle identity, visible damage, repair status, or any change cannot be assessed.
Frame 23 vehicle-transport
John's dark pickup truck is not visible in this tight garage-facing frame, so vehicle identity, damage, repair status, or any change cannot be assessed.
Frame 24 vehicle-transport
John's dark pickup truck is not visible, so persistent vehicle identity, damage, repair status, or any change cannot be assessed from this frame.
Frame 24 vehicle-transport
John's dark pickup truck is not in frame; its identity, damage, repair status, or any change cannot be assessed from this view.
Frame 25 vehicle-transport
John's dark pickup truck is not in frame, so persistent vehicle identity, visible damage, repair status, or changes cannot be assessed.
Frame 25 vehicle-transport
John's dark pickup truck is not in frame, so vehicle identity, visible damage, repair status, or any change cannot be assessed.
Frame 25 vehicle-transport
John's dark pickup truck is not in frame, so persistent vehicle identity, damage, repair status, or any change cannot be assessed.
Frame 26 vehicle-transport
John's dark pickup truck is not in frame, so persistent vehicle identity, visible damage, repair status, or any change cannot be assessed.
Frame 26 vehicle-transport
John's dark pickup truck is not visible in this frame, so vehicle identity, damage, repair status, or any change cannot be assessed.
Frame 26 vehicle-transport
The dark pickup truck is not in frame, so persistent vehicle identity, damage, repair status, or any change cannot be assessed.
Frame 27 vehicle-transport
John's dark pickup truck is not in frame, so its persistent identity, damage, repair status, or any change cannot be assessed.
Frame 27 vehicle-transport
John's dark pickup truck is not visible, so persistent vehicle identity and moderate damage status cannot be assessed from this frame.
Frame 28 vehicle-transport
John's dark pickup truck is not in frame, so persistent vehicle identity, damage, repair status, or any change cannot be assessed.
Frame 29 vehicle-transport
John's dark pickup truck is not visible in this frame, so persistent vehicle identity, damage, repair status, or any change cannot be assessed.
Frame 30 vehicle-transport
John's dark pickup truck is not visible, so persistent vehicle identity, damage, or repair continuity cannot be verified.
Frame 31 vehicle-transport
John's dark pickup truck is not visible in this tight garage-facing composition, so persistent vehicle identity, damage, repair status, or change cannot be assessed.
Frame 32 vehicle-transport
John's dark pickup truck is not in frame, so persistent vehicle identity, damage, repair status, or any change cannot be assessed.
Frame 33 vehicle-transport
John's dark pickup truck is not visible in this frame, so persistent vehicle identity, damage, repair status, or any change cannot be assessed.
Frame 33 vehicle-transport
John's dark pickup truck is not in frame, so persistent vehicle identity, damage, repair status, or any change cannot be assessed.
Frame 34 vehicle-transport
John's dark pickup truck is not in frame, so its persistent identity, visible damage, repair status, or any change cannot be assessed.
Frame 35 vehicle-transport
John's dark pickup truck is not visible in this frame, so persistent vehicle identity, damage, and repair status cannot be assessed.
Frame 36 vehicle-transport
John's dark pickup truck is not visible in this frame, so persistent vehicle identity, visible damage, repair status, or any change cannot be assessed.
Frame 37 vehicle-transport
John's dark pickup truck is not in frame, so vehicle identity, damage, repair status, or any change cannot be assessed.
Frame 38 vehicle-transport
John's dark pickup truck is not visible in this tight garage-facing frame; vehicle identity, damage, and repair status cannot be assessed.
Frame 39 vehicle-transport
John's dark pickup truck is not visible, so vehicle identity, visible damage, repair status, or any change cannot be assessed.
Frame 40 vehicle-transport
John's dark pickup truck is not in frame, so persistent vehicle identity, damage, repair status, or any change cannot be assessed.
Frame 40 vehicle-transport
John's dark pickup truck is not visible, so persistent vehicle identity, damage, repair status, or any change cannot be assessed.
Frame 41 vehicle-transport
John's dark pickup truck is not visible; vehicle identity, damage, repair status, or change cannot be assessed.
Frame 42 vehicle-transport
John's dark pickup truck is not in frame, so persistent vehicle identity, visible damage, repair status, or any change cannot be assessed.
Frame 43 vehicle-transport
John's dark pickup truck is not visible, so vehicle identity and damage continuity cannot be assessed.
Frame 44 vehicle-transport
John's dark pickup truck is not visible; persistent vehicle identity, damage, and repair status cannot be assessed from this frame.
Frame 45 vehicle-transport
John's dark pickup truck is not in frame, so persistent vehicle identity, visible damage, repair status, or any change cannot be assessed.
Frame 46 vehicle-transport
John's dark pickup truck is not visible; persistent vehicle identity, damage, repair status, or any change cannot be assessed from this frame.
Frame 46 vehicle-transport
John's dark pickup truck is not in frame, so persistent vehicle identity, damage, repair status, or change cannot be assessed.
Frame 47 vehicle-transport
John's dark pickup truck is not in frame, so persistent vehicle identity, visible damage, repair status, or change cannot be assessed.
Frame 48 vehicle-transport
John's dark pickup truck is not in frame; vehicle identity, damage, repair status, or any change cannot be assessed.
Frame 49 vehicle-transport
John's dark pickup truck is not visible; persistent vehicle identity, damage, or repair status cannot be assessed.
Frame 50 vehicle-transport
Persistent dark pickup truck is not in frame; vehicle identity, visible damage, repair status, or any change cannot be assessed.
Frame 51 vehicle-transport
John's dark pickup truck is not visible, so persistent vehicle identity, existing moderate damage, repair status, or any change cannot be assessed.
Frame 52 vehicle-transport
John's dark pickup truck is not visible in this composition, so persistent vehicle identity, damage, and repair status cannot be assessed.
Frame 53 vehicle-transport
John's dark pickup truck is not visible, so its persistent identity, damage, and repair state cannot be assessed from this frame.
Frame 53 vehicle-transport
No wallet or truck key fob is visible in John's hands.
Frame 53 vehicle-transport
John's dark pickup truck is not visible in this garage-facing frame, so persistent vehicle identity, visible damage, repair status, or any change cannot be assessed.
Frame 54 vehicle-transport
John's dark pickup truck is not visible, so persistent vehicle identity, moderate damage, repair status, or any change cannot be verified from this frame.
Frame 54 vehicle-transport
No wallet or truck key fob is visible in John's hands.
Frame 54 vehicle-transport
John's dark pickup truck is not visible, so its persistent identity, moderate damage, and repair status cannot be assessed from this frame.
Frame 54 vehicle-transport
No wallet or truck key fob is visible in John's hands.
Frame 55 vehicle-transport
John's dark pickup truck is not in frame, so persistent vehicle identity, visible damage, repair status, or any change cannot be assessed.
Frame 56 vehicle-transport
John's dark pickup truck is not in frame, so its identity, visible damage, repair status, or any change cannot be assessed.
Frame 56 vehicle-transport
Wallet and truck key fob are not visible in this frame.
Frame 56 vehicle-transport
John's dark pickup truck is not visible in this frame, so vehicle identity, damage, repair status, or changes cannot be assessed.
Frame 56 vehicle-transport
John's dark pickup truck is not visible in this frame; its persistent identity, moderate damage state, repair status, or any change cannot be assessed from this view.
Frame 56 vehicle-transport
John's dark pickup truck is out of frame, so persistent vehicle identity, visible damage, repair status, or change cannot be assessed.
Frame 56 vehicle-transport
John's dark pickup truck is not in frame, so persistent vehicle identity and existing damage continuity cannot be visually assessed.
Frame 56 vehicle-transport
John's dark pickup truck is not visible in this frame, so its persistent identity, moderate damage, repair status, or any change cannot be assessed.
Frame 56 vehicle-transport
Expected actor state placed John near the open interior door with his right hand on the brass doorknob and looking into the hallway; in this frame he has moved to the pickup and is touching the truck door handle.
Frame 56 vehicle-transport
Expected unresolved hook says to step through the already-open interior door into the hallway, but the visible action is toward the vehicle instead.
Frame 56 vehicle-transport
Persistent vehicle state says John's dark pickup is in the driveway or not visible in the tight garage-facing composition; here a dark pickup is prominently visible inside/at the garage opening.
Frame 56 vehicle-transport
Truck damage continuity cannot be fully assessed: the vehicle is dusty/muddy but no obvious moderate structural damage or repair change is visible from this view.
Frame 56 vehicle-transport
John's dark pickup truck is not in frame, so vehicle identity, visible damage, repair status, or any change cannot be assessed.
Frame 56 vehicle-transport
John's dark pickup truck is not in frame; vehicle identity, visible damage, repair status, or any change cannot be assessed.
Frame 56 vehicle-transport
John's dark pickup truck is not visible, so persistent vehicle identity, damage, repair status, or any change cannot be assessed from this view.
Frame 56 vehicle-transport
John's dark pickup truck is not in frame; persistent vehicle identity and existing damage status cannot be visually assessed from this composition.
Frame 56 vehicle-transport
John's dark pickup truck is not visible in this frame; vehicle identity, damage, and repair status cannot be assessed.
Frame 56 vehicle-transport
John's dark pickup truck is not visible; persistent vehicle identity, damage, repair status, or any change cannot be assessed.
Frame 56 vehicle-transport
John's dark pickup truck is not visible, so persistent vehicle identity, moderate damage, repair status, or any change cannot be assessed.
Frame 57 vehicle-transport
John's dark pickup truck is not visible in this frame, so persistent vehicle identity, damage, repair status, or any change cannot be assessed.
Frame 58 vehicle-transport
John's dark pickup truck is not in frame, so persistent vehicle identity, visible damage, repair status, or any change cannot be assessed.
Frame 59 vehicle-transport
John's dark pickup truck is not in frame; vehicle identity, visible damage, repair status, or any continuity change cannot be assessed.
Frame 60 vehicle-transport
John's dark pickup truck is not in frame; persistent vehicle identity, visible damage, repair status, or any change cannot be assessed.
Frame 61 vehicle-transport
John's dark pickup truck is not in frame; vehicle identity, visible damage, repair status, and continuity changes cannot be assessed.
Frame 62 vehicle-transport
John's dark pickup truck is not visible in this frame; vehicle identity, damage, and repair continuity cannot be assessed from this view.
Frame 63 vehicle-transport
John's dark pickup truck is not visible in this frame, so persistent vehicle identity, damage, repair status, or any change cannot be assessed.
Frame 64 vehicle-transport
John's dark pickup truck is not visible in this frame; no vehicle identity, visible damage, repair status, or continuity change can be assessed.
Frame 65 vehicle-transport
John's dark pickup truck is not in frame, so persistent vehicle identity, visible damage, repair status, or any change cannot be assessed.
Frame 66 vehicle-transport
John's dark pickup truck is not in frame, so persistent vehicle identity, visible damage, repair status, or any change cannot be assessed.
Frame 67 vehicle-transport
John's dark pickup truck is not visible in this tight garage-facing composition; vehicle identity, damage, repair status, or continuity changes cannot be assessed.
Frame 68 vehicle-transport
John's pickup truck is not in frame, so its persistent identity, visible damage, repair status, or any continuity change cannot be assessed.
Frame 69 vehicle-transport
John's dark pickup truck is not in frame, so persistent vehicle identity, visible damage, repair status, or any change cannot be assessed.
Frame 70 vehicle-transport
John's dark pickup truck is not visible in this tight garage-doorway framing, so vehicle identity, damage, repair status, or changes cannot be assessed.
Frame 71 vehicle-transport
John's dark pickup truck is not visible in this frame, so its persistent identity, damage, repair status, or any change cannot be assessed.
Frame 72 vehicle-transport
John’s dark pickup truck is not in frame; vehicle identity, damage, repair status, and continuity changes cannot be assessed.
Frame 72 vehicle-transport
John's dark pickup truck is not in frame; vehicle identity, visible damage, repair status, and continuity changes cannot be assessed.

Phone Task

Frame 1 phone-task
object_disappearance: smartphone was targeted but is not visible in the resulting frame.
Frame 2 phone-task
Expected phone state was not_visible, but a dark phone-sized device appears visible near John's right hand/back pocket.
Frame 2 phone-task
Camera framing is wider than the expected tight hand-and-phone microgesture framing.
Frame 2 phone-task
object_disappearance: smartphone was targeted but is not visible in the resulting frame.
Frame 3 phone-task
Expected phone state said not_visible, but a dark phone-sized object is now visibly being held or adjusted at John's right back pocket.
Frame 3 phone-task
Framing is wider than the expected tight hand-and-phone microgesture, though the hand/phone action is visible.
Frame 3 phone-task
object_disappearance: smartphone was targeted but is not visible in the resulting frame.
Frame 4 phone-task
Expected phone state was not_visible/possibly behind John near the back pocket, but in this frame the phone is clearly visible in his raised right hand with the screen on.
Frame 5 phone-task
Expected phone state listed as not_visible, but the frame clearly shows John holding and looking at a smartphone.
Frame 5 phone-task
Expected hand-and-phone continuity framing is not present; the image shows a wider rear view of John in the garage.
Frame 5 phone-task
Expected right hand raised holding and viewing a smartphone, but no smartphone is visible and John's right hand appears low near his back or pocket.
Frame 5 phone-task
object_disappearance: smartphone was targeted but is not visible in the resulting frame.
Frame 6 phone-task
Phone remains not visible, so Emily Miller's unread message has not visibly been read or acted on.
Frame 6 phone-task
The camera shows a wider rear view of John and the garage rather than a tight hand-and-phone microgesture framing.
Frame 6 phone-task
object_disappearance: smartphone was targeted but is not visible in the resulting frame.
Frame 7 phone-task
Phone was expected as not visible, but it is visible in John's hand/rear pocket area; no screen text is visible.
Frame 8 phone-task
Expected phone state was not_visible, but the phone is clearly visible and active in John's right hand.
Frame 8 phone-task
Expected pose described him walking away with the right hand behind him near his back pocket; this frame shows him paused and looking down at the phone held in front of his body.
Frame 9 phone-task
Expected phone state says not_visible, but the phone is clearly visible and lit in John's right hand.
Frame 9 phone-task
fact_filter: dropped message_thread_opened, message_read because frame analysis did not visibly support them.
Frame 9 phone-task
message_evaluation: needs_repair; Complete the requested photo/camera evidence.
Frame 10 phone-task
Camera/framing is not close enough to read the phone UI despite the expected phone_screen close-up mode.
Frame 11 phone-task
The phone screen is visible but message content cannot be reliably transcribed; no visible evidence confirms that Emily's request has been read or answered yet.
Frame 12 phone-task
Expected phone state says locked with lock-screen text, but the visible phone appears unlocked and open to an Emily Miller message thread.
Frame 13 phone-task
Expected phone state says locked, but the visible screen appears to show an open Emily Miller message thread.
Frame 13 phone-task
message_evaluation: needs_repair; Complete the requested photo/camera evidence.
Frame 14 phone-task
Camera framing is a third-person medium view of John rather than a true phone-screen close-up, so the phone UI is not clearly readable.
Frame 16 phone-task
Phone content is visible only as an unreadable interface, so Emily Miller's thread or specific message text cannot be confirmed from the image alone.
Frame 18 phone-task
Phone screen is not readable, so the expected Emily Miller message/thread state cannot be confirmed visually.
Frame 20 phone-task
John was expected to be holding/looking at a smartphone in his right hand, but no phone is visible; his right hand appears near the doorknob.
Frame 20 phone-task
Phone thread/content is not readable in this frame, so Emily's message cannot be visually confirmed here.
Frame 20 phone-task
The phone is present, but Emily's message/thread text is not readable in the frame.
Frame 21 phone-task
Phone thread content is not readable in this frame, so Emily's message/request cannot be visually confirmed here.
Frame 23 phone-task
No visible confirmation that John has read Emily's text, taken a backyard photo, or sent a reply/photo.
Frame 25 phone-task
Phone screen is not readable, so Emily's message thread cannot be visually confirmed in this frame.
Frame 26 phone-task
Expected phone state says not_visible, but the smartphone is visibly in John's hand; screen text remains unreadable.
Frame 26 phone-task
Expected smartphone is not clearly visible despite John's hand being near waist level; phone state cannot be visually confirmed.
Frame 26 phone-task
Expected phone task remains unresolved because no readable phone screen or backyard photo action is visible.
Frame 26 phone-task
object_disappearance: smartphone was targeted but is not visible in the resulting frame.
Frame 27 phone-task
No phone screen or message text is visible, so Emily Miller's requested photo/message task cannot be visually confirmed in this frame.
Frame 27 phone-task
The expected phone-related microgesture is not visible in this frame; John's hand is near his hip but no smartphone can be clearly identified.
Frame 27 phone-task
object_disappearance: smartphone was targeted but is not visible in the resulting frame.
Frame 28 phone-task
John's phone remains not visible, so Emily Miller's message thread and any photo-sending task cannot be visually confirmed in this frame.
Frame 28 phone-task
object_disappearance: smartphone was targeted but is not visible in the resulting frame.
Frame 29 phone-task
The phone is not visible, so Emily Miller's pending message/photo task has not visibly progressed in this frame.
Frame 29 phone-task
object_disappearance: smartphone was targeted but is not visible in the resulting frame.
Frame 30 phone-task
Expected phone state was not_visible, but the phone is now visible and held up in John's right hand.
Frame 30 phone-task
Expected pose had one hand near the hip/back pocket area; current pose shows the right arm raised holding the phone.
Frame 30 phone-task
The phone screen content is not readable, so Emily's message status or any outbound photo cannot be confirmed from this frame.
Frame 31 phone-task
Phone state differs from the expected 'not_visible' state: the phone is clearly visible in John's hand in this frame.
Frame 31 phone-task
message_evaluation: needs_repair; complete
Frame 32 phone-task
Expected camera mode was phone_screen with readable phone UI, but the frame shows a third-person view of John in the garage instead.
Frame 32 phone-task
Expected John to be holding a visible phone, but no phone is clearly visible in his hand.
Frame 32 phone-task
object_disappearance: smartphone was targeted but is not visible in the resulting frame.
Frame 33 phone-task
No visible evidence that John has read Emily's text, taken a backyard photo, or sent a reply/photo yet.
Frame 33 phone-task
The phone is not clearly visible despite the active message-related thread, leaving hand/phone continuity ambiguous.
Frame 33 phone-task
No visible phone screen or Emily message text is present in this frame despite the unresolved phone task.
Frame 33 phone-task
object_disappearance: smartphone was targeted but is not visible in the resulting frame.
Frame 34 phone-task
Framing is wider than the expected tight hand-and-phone microgesture view, showing most of John's body and the garage wall area.
Frame 34 phone-task
object_disappearance: smartphone was targeted but is not visible in the resulting frame.
Frame 35 phone-task
Expected phone state says not_visible, but a dark phone-like object is partially visible at John's back pocket/hip; screen remains hidden and no text can be read.
Frame 35 phone-task
object_disappearance: smartphone was targeted but is not visible in the resulting frame.
Frame 36 phone-task
The phone is now visible in John's hand with the screen on, whereas the expected state listed it as not visible/partially at the back pocket; this appears to be a natural continuation of him retrieving or checking it, not an identity issue.
Frame 37 phone-task
The phone is now visible with its screen lit, but no Emily Miller message content or active thread is visible.
Frame 38 phone-task
No non-John people are visible despite the active Emily Miller message thread.
Frame 39 phone-task
No non-John people are visible despite the active message thread; no in-person conversation is occurring.
Frame 39 phone-task
message_evaluation: complete; complete
Frame 40 phone-task
Camera/framing does not match expected phone_screen close-up; this is a third-person garage view with no readable phone UI.
Frame 40 phone-task
Expected state says John is holding the phone upright in front of him near the door, but the visible frame shows him still pulling it from his back pocket.
Frame 40 phone-task
Expected Mark Chen message text is not visible; no phone thread can be confirmed in this frame.
Frame 40 phone-task
Camera/framing does not match expected phone_screen close-up; this is a third-person garage view with no readable phone UI.
Frame 40 phone-task
Expected state says John is holding a smartphone upright near the closed interior door, but the frame shows him reaching into or pulling from his back pocket instead.
Frame 40 phone-task
object_disappearance: smartphone was targeted but is not visible in the resulting frame.
Frame 41 phone-task
Phone screen is not visible, so Mark Chen's message thread state cannot be confirmed from the image.
Frame 41 phone-task
message_evaluation: complete; complete
Frame 42 phone-task
Camera/framing does not match the expected phone-screen macro perspective; this is an over-the-shoulder third-person view of John holding the phone.
Frame 42 phone-task
Expected action suggested John had lowered/slipped the phone back into his jeans pocket, but in this frame he is still holding and checking the phone.
Frame 42 phone-task
Phone message content such as Mark Chen's message is not legible; only the lock-screen time is readable.
Frame 42 phone-task
fact_filter: dropped message_thread_opened, message_read because frame analysis did not visibly support them.
Frame 43 phone-task
Expected phone state says locked with 10:42/thread_emily_miller, but the visible phone appears to show an unlocked app grid or active screen; no clear lock-screen time or message thread text is readable.
Frame 44 phone-task
Expected phone state listed as locked, but the visible phone is unlocked with a messaging thread and keyboard open.
Frame 45 phone-task
Expected phone state says locked, but the visible phone is unlocked and actively showing Emily's Messages thread with the Photos picker open.
Frame 45 phone-task
John's full body, cap, jeans, and shoes are not visible in this tight phone-screen framing, so those wardrobe details cannot be confirmed here.
Frame 45 phone-task
fact_filter: dropped message_thread_opened because frame analysis did not visibly support them.
Frame 46 phone-task
Expected phone state says locked, but the frame clearly shows the phone unlocked with the Messages app open.
Frame 46 phone-task
Phone display now shows 4:24, while the expected prior locked-screen text referenced 4:22; this may be normal time progression but is a visible difference.
Frame 46 phone-task
The phone is visibly unlocked in Emily's Messages thread despite the expected phone state listing locked; current frame evidence supports unlocked Messages app.
Frame 46 phone-task
fact_filter: dropped message_thread_opened because frame analysis did not visibly support them.
Frame 47 phone-task
Expected phone-screen close-up of Emily Miller's message thread/photo picker, but the frame shows a wider garage view with John putting the phone into his pocket and no readable phone UI.
Frame 47 phone-task
Expected actor pose described as hands/forearms holding the phone for typing or sending an attached photo; actual pose is full-body standing with phone at pocket level.
Frame 47 phone-task
Phone expected state/thread cannot be confirmed visually because the screen is not readable.
Frame 48 phone-task
Camera framing is wider full-body garage view rather than the expected tight hand-and-phone microgesture framing.
Frame 48 phone-task
The phone screen and Emily message thread are no longer visible, so the active thread state cannot be confirmed visually in this frame.
Frame 48 phone-task
fact_filter: dropped message_thread_opened, message_read, photo_captured because frame analysis did not visibly support them.
Frame 48 phone-task
message_evaluation: complete; complete
Frame 49 phone-task
Camera/framing is not a close phone-screen macro view; it shows a full-body garage view instead.
Frame 49 phone-task
No phone text is visible, so the Mark Chen message notification/thread state cannot be confirmed from this frame.
Frame 50 phone-task
Camera framing is wider full-body garage view rather than the expected tight hand-and-phone microgesture framing.
Frame 50 phone-task
message_evaluation: complete; complete
Frame 51 phone-task
Camera framing does not match the expected phone_screen close-up; this is a wider third-person view of John in the garage.
Frame 51 phone-task
John's pose has progressed from finishing pocketing the phone to reaching toward the interior door area, which is plausible but should be treated as a visible action change.
Frame 55 phone-task
fact_filter: dropped message_thread_opened, message_read, photo_captured because frame analysis did not visibly support them.
Frame 56 phone-task
Phone is not visible, so the locked state and any message thread cannot be confirmed visually.
Frame 56 phone-task
No visible phone use; this is consistent with the instruction not to reopen the phone unless a new notification appears.
Frame 56 phone-task
Phone is not visible, so the prior locked phone state cannot be confirmed from this frame.
Frame 56 phone-task
The phone is not visible, so its locked state and message thread cannot be confirmed visually.
Frame 56 phone-task
Phone is not visible, so the expected locked state and message thread cannot be visually confirmed.
Frame 62 phone-task
No phone is visible; no new message or phone interaction is evident.
Frame 63 phone-task
No visible phone despite prior phone thread context; this is consistent with the expected phone state of not visible.
Frame 67 phone-task
object_disappearance: smartphone was targeted but is not visible in the resulting frame.
Frame 68 phone-task
The unresolved Linda recycling-pickup message is not visible; John is not shown reading or replying to it in this frame.
Frame 69 phone-task
Expected phone state was not_visible, but a phone-like device is visible protruding from John's rear pocket; screen content remains unreadable.
Frame 69 phone-task
The requested camera/framing mentioned tight hand-and-phone microgesture, but this frame is a wider full-body garage doorway view with the phone stowed rather than in hand.
Frame 69 phone-task
Unresolved Linda recycling message thread is not addressed because the phone screen is not visible.
Frame 69 phone-task
object_disappearance: smartphone was targeted but is not visible in the resulting frame.
Frame 70 phone-task
Expected phone state listed as not_visible, but the phone is now clearly visible in John's right hand.
Frame 71 phone-task
The expected phone state said not_visible, but the phone is clearly visible in John's right hand in this frame.
Frame 71 phone-task
Framing is wider full-body garage doorway view rather than the expected tight hand-and-phone microgesture framing.
Frame 72 phone-task
The phone is now visible and opened to Linda Ortiz’s thread, updating the prior phone state from not_visible.
Frame 72 phone-task
Expected phone microgesture is not visible; John is not visibly holding or looking at a phone in this frame.
Frame 72 phone-task
Phone state remains not_visible, so Linda's unread recycling pickup message cannot be read or answered from visible evidence.

Harness Validation

Frame 2 harness-validation
harness_retry: actor_missing_required_visibility, missing_required_beat, microstep_skipped; The frame does not depict the required micro-beat (grip_phone_in_pocket) with the phone visible; phone remains not visible and the user-visible micro-movement is not demonstrated. This prevents confirming the intended single beat and risks mis-advancement.
Frame 3 harness-validation
accept: off_phase_visual - Frame shows micro-beat progress consistent with 'pull_phone_from_pocket' (phone partly visible near back pocket). However, prior frame indicated phone_state 'not_visible', creating a minor continuity mismatch flagged as off_phase_visual. No macro action completed and frame is within movement constraints.
Frame 5 harness-validation
harness_retry: macro_overcompleted; Rendered frame conflicts with the required beat or current state: macro_overcompleted.
Frame 5 harness-validation
harness_rejected: phone_overcompleted; Frame shows phone visible in John's hand; the frame's prior data expected phone to be not_visible per phone state, indicating a mismatch that may disrupt continuity. Retry budget exhausted; holding prior accepted state.
Frame 5 harness-validation
hold_previous: phone_overcompleted - Frame shows phone visible in John's hand; the frame's prior data expected phone to be not_visible per phone state, indicating a mismatch that may disrupt continuity. Retry budget exhausted; holding prior accepted state.
Frame 13 harness-validation
harness_retry: frame_advance_overrun, phone_overcompleted; The current frame shows Emily's thread opened and a reply occurred within the same micro-beat, which exceeds the allowed progression for the 'open_active_thread' micro-beat. There is also a mismatch between the documented phone state (locked) and the visible phone being unlocked/open, indicating an inconsistency that needs repair before advancing.
Frame 14 harness-validation
harness_retry: missing_required_beat, microstep_skipped; Frame shows John standing in the garage looking at his phone; the current micro-movement beat is to turn toward the next path or doorway without changing location, which is not observed. The plan expects a turn, but the camera shows no such micro-rotation yet.
Frame 15 harness-validation
harness_retry: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 16 harness-validation
harness_retry: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 16 harness-validation
harness_rejected: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 16 harness-validation
hold_previous: micro_location_overrun - Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 16 harness-validation
harness_retry: missing_required_beat; Frame shows phone taken out and a reply was sent, but the required steps of taking a backyard photo and sending it to Emily have not been completed in this frame.
Frame 16 harness-validation
harness_rejected: missing_required_beat; Evidence shows the phone is out and a reply occurred, but the next required beat (turn_toward_path toward hallway) has not been rendered in this frame. The frame's orientation and phase plan indicate the actor should perform a micro-movement before advancing location or performing photo capture. The contract's completion requires going through subsequent steps (move to backyard view, take photo, send). Retry budget exhausted; holding prior accepted state.
Frame 16 harness-validation
hold_previous: missing_required_beat - Evidence shows the phone is out and a reply occurred, but the next required beat (turn_toward_path toward hallway) has not been rendered in this frame. The frame's orientation and phase plan indicate the actor should perform a micro-movement before advancing location or performing photo capture. The contract's completion requires going through subsequent steps (move to backyard view, take photo, send). Retry budget exhausted; holding prior accepted state.
Frame 18 harness-validation
harness_retry: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 18 harness-validation
harness_rejected: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 18 harness-validation
hold_previous: micro_location_overrun - Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 18 harness-validation
harness_retry: missing_required_beat, frame_advance_overrun; Current frame shows John in garage reading/replying to Emily but no backyard photo or outbound photo has been captured/sent. The required beat set (take photo of backyard and send) has not been satisfied; a micro-movement toward hallway is visible but the backyard photo step is not completed. frameAdvance constraints not clearly violated, but the contract progress is incomplete, requiring a repair/re-render to include taking the backyard photo and sending it.
Frame 20 harness-validation
harness_retry: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 20 harness-validation
harness_rejected: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 20 harness-validation
hold_previous: micro_location_overrun - Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 20 harness-validation
harness_retry: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 20 harness-validation
harness_rejected: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 20 harness-validation
hold_previous: micro_location_overrun - Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 20 harness-validation
harness_retry: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 20 harness-validation
harness_rejected: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 20 harness-validation
hold_previous: micro_location_overrun - Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 20 harness-validation
harness_retry: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 21 harness-validation
harness_retry: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 21 harness-validation
harness_rejected: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 21 harness-validation
hold_previous: micro_location_overrun - Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 21 harness-validation
harness_retry: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 21 harness-validation
harness_rejected: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 21 harness-validation
hold_previous: micro_location_overrun - Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 21 harness-validation
harness_retry: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 22 harness-validation
harness_retry: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 23 harness-validation
harness_retry: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 23 harness-validation
harness_rejected: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 23 harness-validation
hold_previous: micro_location_overrun - Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 24 harness-validation
harness_retry: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 24 harness-validation
harness_rejected: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 24 harness-validation
hold_previous: micro_location_overrun - Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 25 harness-validation
harness_retry: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 25 harness-validation
harness_rejected: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 25 harness-validation
hold_previous: micro_location_overrun - Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 25 harness-validation
harness_retry: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 25 harness-validation
harness_rejected: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 25 harness-validation
hold_previous: micro_location_overrun - Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 25 harness-validation
harness_retry: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 26 harness-validation
harness_retry: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 26 harness-validation
harness_rejected: missing_required_beat, frame_advance_overrun; Current frame shows John in the garage facing the interior door with minimal or no visible micro-movement, not yet performing the required beat 'take_first_steps'. The frameAnalysis describes the beat expected as a small step toward the hallway within the garage, but the observed frame shows no such movement and the phone is visible (contradicting the not_visible state). This indicates we should retry to render a frame that correctly renders the next micro-beat within the allowed space and time. Retry budget exhausted; holding prior accepted state.
Frame 26 harness-validation
hold_previous: missing_required_beat, frame_advance_overrun - Current frame shows John in the garage facing the interior door with minimal or no visible micro-movement, not yet performing the required beat 'take_first_steps'. The frameAnalysis describes the beat expected as a small step toward the hallway within the garage, but the observed frame shows no such movement and the phone is visible (contradicting the not_visible state). This indicates we should retry to render a frame that correctly renders the next micro-beat within the allowed space and time. Retry budget exhausted; holding prior accepted state.
Frame 26 harness-validation
harness_retry: missing_required_beat, frame_advance_overrun, microstep_skipped; The current frame shows the phone already partially visible in John's hand, which violates the expected micro-beat where the phone should remain unseen while reaching toward the pocket. This indicates sequencing drift from the planned beat (reach_to_phone_pocket). It also suggests a later beat occurred before finishing the required micro-step.
Frame 26 harness-validation
harness_rejected: macro_overcompleted; Frame shows phone_taken_out and message_replied contradicting the current micro-beat ('reach_to_phone_pocket'); macro action completed too early; frame should be repaired to align with the planned micro-beats. Retry budget exhausted; holding prior accepted state.
Frame 26 harness-validation
hold_previous: macro_overcompleted - Frame shows phone_taken_out and message_replied contradicting the current micro-beat ('reach_to_phone_pocket'); macro action completed too early; frame should be repaired to align with the planned micro-beats. Retry budget exhausted; holding prior accepted state.
Frame 27 harness-validation
harness_rejected: missing_required_beat; Current frame does not visually confirm completion of Emily's instruction: open/read the message and take a backyard photo and send it. The required visible evidence (read state, backyard view, outbound photo) is not present in this frame; therefore, do not advance the frame.
Frame 27 harness-validation
hold_previous: missing_required_beat - Current frame does not visually confirm completion of Emily's instruction: open/read the message and take a backyard photo and send it. The required visible evidence (read state, backyard view, outbound photo) is not present in this frame; therefore, do not advance the frame.
Frame 29 harness-validation
harness_retry: off_phase_visual, frame_advance_overrun; Continuity issue: phone state changed from not_visible to visible in the current frame, which does not align with the expected beat. The current micro-beat is pull_phone_from_pocket and the macro action has not completed; the image appears to progress beyond the allowed micro-movement.
Frame 33 harness-validation
harness_rejected: off_phase_visual; Current frame shows a micro-movement (pocketing the phone) but phone remains not clearly visible; no evidence yet that Emily's message was read or that backyard photo was taken. The frame fails to clearly advance the required steps; hold to avoid advancing state.
Frame 33 harness-validation
hold_previous: off_phase_visual - Current frame shows a micro-movement (pocketing the phone) but phone remains not clearly visible; no evidence yet that Emily's message was read or that backyard photo was taken. The frame fails to clearly advance the required steps; hold to avoid advancing state.
Frame 35 harness-validation
accept: off_phase_visual - Frame matches the intended micro-beat pull_phone_from_pocket; phone partially visible as expected. Minor continuity issue: the reported phone state conflicts with observed visibility.
Frame 37 harness-validation
harness_retry: macro_overcompleted; Rendered frame conflicts with the required beat or current state: macro_overcompleted.
Frame 40 harness-validation
harness_retry: microstep_skipped; Frame shows phone being pulled from back pocket, not the required micro-beat 'lower_phone_toward_pocket'. The phone screen visibility and beat alignment fail.
Frame 40 harness-validation
harness_rejected: microstep_skipped, frame_advance_overrun; Frame shows John pulling the phone from his back pocket rather than performing the expected micro-movement 'lower_phone_toward_pocket'; this misaligns with the current beat as described in the frame plan. The system requires a micro-beat consistent with the expected action; re-rendering or a new frame is needed to confirm the intended micro-movement. Retry budget exhausted; holding prior accepted state.
Frame 40 harness-validation
hold_previous: microstep_skipped, frame_advance_overrun - Frame shows John pulling the phone from his back pocket rather than performing the expected micro-movement 'lower_phone_toward_pocket'; this misaligns with the current beat as described in the frame plan. The system requires a micro-beat consistent with the expected action; re-rendering or a new frame is needed to confirm the intended micro-movement. Retry budget exhausted; holding prior accepted state.
Frame 46 harness-validation
harness_retry: missing_required_beat; The frame shows a photo attachment within a read/open/check phone context, which is disallowed by the current beat constraints (read/open beats should not attach/send photos). The evidence indicates the next action would advance to sending an attached photo, violating the beat rules.
Frame 46 harness-validation
harness_rejected: off_phase_visual, actor_missing_required_visibility; Frame shows phone unlocked with Emily thread and photo attachment, conflicting with the 'phone state' observed elsewhere and with a visible lack of John's full body; John is not visible (hands only) which fails the requirement that John be visible in this beat. Additionally, the current frame's visuals do not strictly reflect the designated beat (tap_recent_backyard_photo_thumbnail) as a single, clearly framed action in the garage; the frame contains mismatch in expected phone state and actor visibility. Retry budget exhausted; holding prior accepted state.
Frame 46 harness-validation
hold_previous: off_phase_visual, actor_missing_required_visibility - Frame shows phone unlocked with Emily thread and photo attachment, conflicting with the 'phone state' observed elsewhere and with a visible lack of John's full body; John is not visible (hands only) which fails the requirement that John be visible in this beat. Additionally, the current frame's visuals do not strictly reflect the designated beat (tap_recent_backyard_photo_thumbnail) as a single, clearly framed action in the garage; the frame contains mismatch in expected phone state and actor visibility. Retry budget exhausted; holding prior accepted state.
Frame 50 harness-validation
harness_retry: macro_overcompleted; Frame shows the macro action of pocketing the phone reaching completion in this beat, which conflicts with the safety note that macro completion should not be shown unless terminal. The plan indicates more beats should follow (i.e., not terminal).
Frame 52 harness-validation
harness_retry: macro_overcompleted; Macro action 'open_door' appears completed (door open) in a non-terminal beat; per rules, micro-movement beats should not show macro action completion until terminal. Provide a frame showing the door opening as an ongoing micro-beat or a frame where the door remains closed while the action is initiated.
Frame 53 harness-validation
harness_retry: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 53 harness-validation
harness_rejected: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 53 harness-validation
hold_previous: micro_location_overrun - Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 53 harness-validation
harness_retry: microstep_skipped; The frame shows the interior door opened, indicating the next micro-beat (open_vehicle_door_micro) occurred while the current beat (reach_vehicle_handle) was not yet completed. This breaks the beat sequencing and macro action gating.
Frame 54 harness-validation
harness_retry: transport_mismatch, frame_advance_overrun; The visible frame shows John at an open interior doorway with the hallway visible, not the vehicle door as the current microbeat expects. This indicates a mismatch between the intended micro-beat (open_vehicle_door_micro) and what is actually depicted (open interior door to hallway). The frame advances a different beat than planned and may prevent proper sequencing.
Frame 54 harness-validation
harness_rejected: macro_overcompleted; Rendered frame conflicts with the required beat or current state: macro_overcompleted.
Frame 54 harness-validation
hold_previous: macro_overcompleted - Rendered frame conflicts with the required beat or current state: macro_overcompleted.
Frame 56 harness-validation
harness_retry: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 56 harness-validation
harness_rejected: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 56 harness-validation
hold_previous: micro_location_overrun - Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 56 harness-validation
harness_retry: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 56 harness-validation
harness_rejected: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 56 harness-validation
hold_previous: micro_location_overrun - Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 56 harness-validation
harness_retry: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 56 harness-validation
harness_rejected: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 56 harness-validation
hold_previous: micro_location_overrun - Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 56 harness-validation
harness_retry: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 56 harness-validation
harness_rejected: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 56 harness-validation
hold_previous: micro_location_overrun - Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 56 harness-validation
harness_retry: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 56 harness-validation
harness_rejected: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 56 harness-validation
hold_previous: micro_location_overrun - Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 56 harness-validation
harness_retry: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 56 harness-validation
harness_rejected: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 56 harness-validation
hold_previous: micro_location_overrun - Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 56 harness-validation
harness_retry: macro_overcompleted; Rendered frame conflicts with the required beat or current state: macro_overcompleted.
Frame 56 harness-validation
harness_rejected: macro_overcompleted; Rendered frame conflicts with the required beat or current state: macro_overcompleted.
Frame 56 harness-validation
hold_previous: macro_overcompleted - Rendered frame conflicts with the required beat or current state: macro_overcompleted.
Frame 56 harness-validation
harness_retry: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 56 harness-validation
harness_rejected: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 56 harness-validation
hold_previous: micro_location_overrun - Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 56 harness-validation
harness_retry: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 56 harness-validation
harness_rejected: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 56 harness-validation
hold_previous: micro_location_overrun - Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 56 harness-validation
harness_retry: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 56 harness-validation
harness_rejected: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 56 harness-validation
hold_previous: micro_location_overrun - Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 56 harness-validation
harness_retry: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 56 harness-validation
harness_rejected: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 56 harness-validation
hold_previous: micro_location_overrun - Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 56 harness-validation
harness_retry: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 56 harness-validation
harness_rejected: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 56 harness-validation
hold_previous: micro_location_overrun - Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 56 harness-validation
harness_retry: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 56 harness-validation
harness_rejected: micro_location_overrun; Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 56 harness-validation
hold_previous: micro_location_overrun - Rendered frame conflicts with the required beat or current state: micro_location_overrun.
Frame 61 harness-validation
harness_retry: macro_overcompleted, microstep_skipped; The frame shows John twisting toward the interior doorway, aligning with the arrive_oriented beat (macro action completion), but the current frameAdvance plan expects the take_first_steps micro-beat (a small forward step) within the current space. This indicates macro action completed ahead of the terminal beat and/or a missing micro-movement step, violating the beat progression and distance constraints.
Frame 72 harness-validation
harness_retry: macro_overcompleted; Rendered frame conflicts with the required beat or current state: macro_overcompleted.
Frame 72 harness-validation
harness_rejected: macro_overcompleted; Rendered frame conflicts with the required beat or current state: macro_overcompleted.
Frame 72 harness-validation
hold_previous: macro_overcompleted - Rendered frame conflicts with the required beat or current state: macro_overcompleted.
Frame 72 harness-validation
harness_rejected: missing_required_beat; Current frame does not display the required 'reach_to_phone_pocket' micro-beat: no visible phone; phone state not_visible; cannot read or reply Linda.
Frame 72 harness-validation
hold_previous: missing_required_beat - Current frame does not display the required 'reach_to_phone_pocket' micro-beat: no visible phone; phone state not_visible; cannot read or reply Linda.

Skipped

Frame 5 skipped
Harness rejected rendered frame: phone_overcompleted
Frame 16 skipped
Harness rejected rendered frame: micro_location_overrun
Frame 16 skipped
Harness rejected rendered frame: missing_required_beat
Frame 18 skipped
Harness rejected rendered frame: micro_location_overrun
Frame 20 skipped
Harness rejected rendered frame: micro_location_overrun
Frame 20 skipped
Harness rejected rendered frame: micro_location_overrun
Frame 20 skipped
Harness rejected rendered frame: micro_location_overrun
Frame 21 skipped
Harness rejected rendered frame: micro_location_overrun
Frame 21 skipped
Harness rejected rendered frame: micro_location_overrun
Frame 23 skipped
Harness rejected rendered frame: micro_location_overrun
Frame 24 skipped
Harness rejected rendered frame: micro_location_overrun
Frame 25 skipped
Harness rejected rendered frame: micro_location_overrun
Frame 25 skipped
Harness rejected rendered frame: micro_location_overrun
Frame 26 skipped
Harness rejected rendered frame: missing_required_beat, frame_advance_overrun
Frame 26 skipped
Harness rejected rendered frame: macro_overcompleted
Frame 27 skipped
Harness rejected rendered frame: missing_required_beat
Frame 33 skipped
Harness rejected rendered frame: off_phase_visual
Frame 40 skipped
Harness rejected rendered frame: microstep_skipped, frame_advance_overrun
Frame 46 skipped
Harness rejected rendered frame: off_phase_visual, actor_missing_required_visibility
Frame 53 skipped
Harness rejected rendered frame: micro_location_overrun
Frame 54 skipped
Harness rejected rendered frame: macro_overcompleted
Frame 56 skipped
Harness rejected rendered frame: micro_location_overrun
Frame 56 skipped
Harness rejected rendered frame: micro_location_overrun
Frame 56 skipped
Harness rejected rendered frame: micro_location_overrun
Frame 56 skipped
Harness rejected rendered frame: micro_location_overrun
Frame 56 skipped
Harness rejected rendered frame: micro_location_overrun
Frame 56 skipped
Harness rejected rendered frame: micro_location_overrun
Frame 56 skipped
Harness rejected rendered frame: macro_overcompleted
Frame 56 skipped
Harness rejected rendered frame: micro_location_overrun
Frame 56 skipped
Harness rejected rendered frame: micro_location_overrun
Frame 56 skipped
Harness rejected rendered frame: micro_location_overrun
Frame 56 skipped
Harness rejected rendered frame: micro_location_overrun
Frame 56 skipped
Harness rejected rendered frame: micro_location_overrun
Frame 56 skipped
Harness rejected rendered frame: micro_location_overrun
Frame 72 skipped
Harness rejected rendered frame: macro_overcompleted
Frame 72 skipped
Harness rejected rendered frame: missing_required_beat

Harness Invalid

Frame 5 harness-invalid
Frame was rejected by the nano harness and did not advance world state.
Frame 16 harness-invalid
Frame was rejected by the nano harness and did not advance world state.
Frame 16 harness-invalid
Frame was rejected by the nano harness and did not advance world state.
Frame 18 harness-invalid
Frame was rejected by the nano harness and did not advance world state.
Frame 20 harness-invalid
Frame was rejected by the nano harness and did not advance world state.
Frame 20 harness-invalid
Frame was rejected by the nano harness and did not advance world state.
Frame 20 harness-invalid
Frame was rejected by the nano harness and did not advance world state.
Frame 21 harness-invalid
Frame was rejected by the nano harness and did not advance world state.
Frame 21 harness-invalid
Frame was rejected by the nano harness and did not advance world state.
Frame 23 harness-invalid
Frame was rejected by the nano harness and did not advance world state.
Frame 24 harness-invalid
Frame was rejected by the nano harness and did not advance world state.
Frame 25 harness-invalid
Frame was rejected by the nano harness and did not advance world state.
Frame 25 harness-invalid
Frame was rejected by the nano harness and did not advance world state.
Frame 26 harness-invalid
Frame was rejected by the nano harness and did not advance world state.
Frame 26 harness-invalid
Frame was rejected by the nano harness and did not advance world state.
Frame 27 harness-invalid
Frame was rejected by the nano harness and did not advance world state.
Frame 33 harness-invalid
Frame was rejected by the nano harness and did not advance world state.
Frame 40 harness-invalid
Frame was rejected by the nano harness and did not advance world state.
Frame 46 harness-invalid
Frame was rejected by the nano harness and did not advance world state.
Frame 53 harness-invalid
Frame was rejected by the nano harness and did not advance world state.
Frame 54 harness-invalid
Frame was rejected by the nano harness and did not advance world state.
Frame 56 harness-invalid
Frame was rejected by the nano harness and did not advance world state.
Frame 56 harness-invalid
Frame was rejected by the nano harness and did not advance world state.
Frame 56 harness-invalid
Frame was rejected by the nano harness and did not advance world state.
Frame 56 harness-invalid
Frame was rejected by the nano harness and did not advance world state.
Frame 56 harness-invalid
Frame was rejected by the nano harness and did not advance world state.
Frame 56 harness-invalid
Frame was rejected by the nano harness and did not advance world state.
Frame 56 harness-invalid
Frame was rejected by the nano harness and did not advance world state.
Frame 56 harness-invalid
Frame was rejected by the nano harness and did not advance world state.
Frame 56 harness-invalid
Frame was rejected by the nano harness and did not advance world state.
Frame 56 harness-invalid
Frame was rejected by the nano harness and did not advance world state.
Frame 56 harness-invalid
Frame was rejected by the nano harness and did not advance world state.
Frame 56 harness-invalid
Frame was rejected by the nano harness and did not advance world state.
Frame 56 harness-invalid
Frame was rejected by the nano harness and did not advance world state.
Frame 72 harness-invalid
Frame was rejected by the nano harness and did not advance world state.
Frame 72 harness-invalid
Frame was rejected by the nano harness and did not advance world state.

Repair

Frame 5 repair
Decision repaired: John takes his phone out before reading or replying to the active message.
Frame 26 repair
Decision repaired: John takes his phone out before reading or replying to the active message.
Frame 27 repair
Decision repaired: John pulls his smartphone out from his pocket while standing in the garage facing the interior door.

Continuity

Frame 9 continuity
Shoes are not clearly visible due to framing, so brown work shoes cannot be confirmed in this frame.
Frame 12 continuity
Shoes are cropped out, so brown work shoes cannot be visually confirmed.
Frame 21 continuity
Emily's requested backyard photo has not been visibly completed in this frame.
Frame 24 continuity
No visible evidence that Emily's requested backyard photo has been taken or sent yet.
Frame 24 continuity
Emily Miller is not visible in the frame.
Frame 25 continuity
No visible evidence that Emily's requested backyard photo has been taken or sent in this frame.
Frame 36 continuity
Shoes are cropped/not visible, so brown work shoe continuity cannot be confirmed from this frame.
Frame 38 continuity
Shoes are cropped out/not visible, so expected brown work shoes cannot be confirmed in this frame.
Frame 41 continuity
Shoes are cropped out/not visible, so brown work shoes cannot be confirmed in this frame.
Frame 42 continuity
Shoes are cropped/not visible, so brown work shoes cannot be confirmed in this frame.
Frame 46 continuity
object_disappearance: Photos picker panel was targeted but is not visible in the resulting frame.

Spatial

Frame 12 spatial
The raised overhead garage door is not visible in this framing, so its open/closed state cannot be confirmed from the image.
Frame 16 spatial
Expected state listed the interior door as closed, but in this frame it is open and John is stepping through/onto the threshold.
Frame 16 spatial
John's outfit and location match the expected garage continuity.
Frame 17 spatial
The raised garage door is not visible from this tight interior-door-facing composition; its open/closed state cannot be confirmed visually.
Frame 18 spatial
Interior door was expected to be closed, but it is visibly open in this frame; this may indicate John has opened it and is transitioning toward the hallway.
Frame 18 spatial
No continuity issue with John's outfit or location is visible.
Frame 18 spatial
The raised overhead garage door is not visible from this tight interior-facing composition, so its open/closed state cannot be confirmed from this frame.
Frame 19 spatial
John's outfit, build, cap, and location remain consistent with the expected garage continuity.
Frame 19 spatial
The closed interior door remains visible and closed.
Frame 20 spatial
Interior door was expected to be closed, but it is visibly open in this frame.
Frame 20 spatial
John's outfit and location match the expected garage continuity.
Frame 20 spatial
No visible wardrobe or identity drift for John; outfit and garage location match expected continuity.
Frame 20 spatial
The closed white interior door remains closed, matching the expected state.
Frame 21 spatial
Expected garage context is consistent; interior door remains closed and John is still in the garage.
Frame 21 spatial
The interior door remains closed; John has not visibly moved into the hallway or backyard yet.
Frame 21 spatial
John remains in the garage near the closed interior door, consistent with expected location continuity.
Frame 22 spatial
John's outfit, cap, posture, and garage location match expected continuity.
Frame 22 spatial
The raised overhead garage door is not visible in this tight interior-door-facing composition.
Frame 23 spatial
Interior door was expected/previously described as closed, but it is now visibly open; track this as a door-state change rather than assuming hidden action details.
Frame 23 spatial
John's wardrobe and location match the expected garage continuity.
Frame 23 spatial
The interior door remains closed, consistent with the prior frame.
Frame 24 spatial
John's outfit, cap, pose direction, and garage location are consistent with the expected state.
Frame 24 spatial
Interior door remains closed.
Frame 24 spatial
John's outfit and garage location remain consistent with the expected state.
Frame 25 spatial
Interior door remains closed; no visible transition into the hallway yet.
Frame 25 spatial
The interior door is still closed, matching the expected garage-to-hallway transition point.
Frame 26 spatial
John's outfit and garage location match expected continuity.
Frame 26 spatial
Interior door remains closed.
Frame 26 spatial
John's outfit and location remain consistent with the expected garage continuity.
Frame 27 spatial
John's expected identity, location, and outfit are consistent with the current world state.
Frame 28 spatial
No visible continuity break in John's identity, outfit, or garage location.
Frame 29 spatial
John's outfit, location, and posture remain consistent with the expected garage continuity.
Frame 29 spatial
The interior door remains closed.
Frame 52 spatial
Interior door was expected to be closed with John preparing to open it; in this frame it is visibly open, so the world state should update to interior_door=open if this action is accepted.
Frame 53 spatial
The expected action was reaching for or opening the interior door; in this frame the door is already open with the hallway visible.
Frame 53 spatial
The visible interior door is closed; this matches the immediate action of reaching for the knob, though it conflicts with any prior object listing that described the interior door as already open.
Frame 54 spatial
The interior door is visibly open now, whereas the immediate expected pose described John near a closed door with his hand on or near the knob; this appears to be the next action completed rather than a major identity issue.
Frame 54 spatial
The visible interior door is closed; any prior object state listing it as open is inconsistent with this frame.
Frame 55 spatial
The interior door appears open now, updating the prior closed-door state; this matches John's ongoing action of opening it.
Frame 56 spatial
John's outfit and garage location remain consistent.
Frame 56 spatial
The interior door is now open, matching the prior action of opening it.
Frame 56 spatial
The interior door is now open, consistent with the prior action of turning the knob and opening it toward the hallway.
Frame 56 spatial
Expected pose included John's right hand on the brass knob, but in this frame his hand appears lowered after the door has been opened.
Frame 56 spatial
No visible continuity problem with John’s clothing or location; the interior door is open, consistent with the expected transition toward the hallway.
Frame 56 spatial
The interior door is now open, consistent with the prior action of turning the brass knob and opening it.
Frame 56 spatial
Door state has progressed from opening to open; John appears ready to move through the doorway, consistent with the prior action.
Frame 56 spatial
The interior door is open, consistent with the prior action of turning the knob and beginning to open it.
Frame 56 spatial
Expected pose mentioned right hand on the brass doorknob, but in this frame his right hand appears released and relaxed at his side, suggesting the action has progressed.
Frame 56 spatial
The interior door is open as expected, but John's right hand is no longer visibly on the knob; his arm appears relaxed at his side.
Frame 56 spatial
Garage overhead door is not visible in this tight composition, so its open/secured state cannot be confirmed.
Frame 57 spatial
The garage overhead door is not visible in this tight interior-door framing, so its open/secured state cannot be verified from the image.
Frame 58 spatial
The interior door is open and John is at the threshold as expected.
Frame 58 spatial
The raised overhead garage door is not visible in this tight garage-facing composition, so its open/secured status cannot be confirmed from this frame.
Frame 59 spatial
Garage overhead door is not visible from this framing, so its open/secured state cannot be visually confirmed in this frame.
Frame 59 spatial
John is transitioning farther into the hallway, while the scene remains anchored at the garage doorway.
Frame 59 spatial
teleportation: Movement from garage to front_entry is not connected.
Frame 60 spatial
John's outfit, cap, location, and calm purposeful posture remain consistent with prior frames.
Frame 61 spatial
Expected pose suggested John reaching for the wall switch/control, but in this frame his right hand appears lowered near the doorway rather than clearly pressing the control.
Frame 62 spatial
John's outfit, cap, body orientation, and garage doorway position match the expected continuity.
Frame 62 spatial
Interior door is open and John remains at the threshold, consistent with the prior movement toward/at the hallway.
Frame 64 spatial
John's outfit, location, and pose match the expected continuity.
Frame 65 spatial
The frame matches the expected doorway/control pose and garage location continuity.
Frame 66 spatial
Interior door remains open and John remains at the wall control, consistent with the prior doorway-control action.
Frame 72 spatial
Interior doorway appears open, consistent with recent garage-threshold continuity.

Issue Categories

Identity

Vehicle Transport

Phone Task

Harness Validation

Skipped

Harness Invalid

Repair

Continuity

Social Identity

Spatial