Micro World Agent Storyboard

Issue Categories

Continuity

1. Frame 0 continuity

   Initial seed frame recorded.

2. Frame 29 continuity

   The dark pickup is visible on the right and remains consistent, but only a partial side view is shown, so minor damage status cannot be fully assessed.

3. Frame 38 continuity

   Most expected garage interior objects such as shelves, red tool chest, recycling bin, and tools are not visible in this frame.

4. Frame 62 continuity

   Actor pose differs from expected rear-view walking-away pose; he appears paused or standing at a threshold.

5. Frame 65 continuity

   fact_filter: dropped photo_captured because frame analysis did not visibly support them.

6. Frame 77 continuity

   Expected shoe color is gray casual shoes; visible shoe appears brown/tan from this angle.

7. Frame 78 continuity

   Shoe color is ambiguous and may not clearly match the expected gray casual shoes.

Identity

1. Frame 1 identity

   John's clothing is consistent with expected black hoodie, blue jeans, brown work shoes, and tan baseball cap.

2. Frame 1 identity

   John is still in the garage and has not moved to a backyard view or taken/sent a backyard photo.

3. Frame 2 identity

   No backyard view is visible, so John has not visibly taken or sent the requested backyard photo.

4. Frame 8 identity

   John has not yet visibly taken or sent a backyard photo.

5. Frame 11 identity

   Expected actor pose says only John's hand and black hoodie sleeve should be visible; here John's upper body, jeans, shoes, and tan cap are visible.

6. Frame 12 identity

   Only John's hand/sleeve is visible, so full actor wardrobe, cap, jeans, and shoes cannot be confirmed in this frame.

7. Frame 17 identity

   John's tan baseball cap, jeans, and brown work shoes are not visible, so full wardrobe continuity cannot be confirmed.

8. Frame 18 identity

   Camera has shifted from close documentary follow framing of John's body and garage context to an extreme close-up of a wall switch.

9. Frame 18 identity

   John's face, cap, hoodie, jeans, and shoes are not visible, so wardrobe continuity cannot be confirmed in this frame.

10. Frame 19 identity

    John's tan baseball cap, jeans, and brown work shoes are not visible, so full wardrobe continuity cannot be verified.

11. Frame 20 identity

    Shoes cannot be confirmed because John's feet are cropped out/not visible.

12. Frame 25 identity

    John is transitioning from the garage into the hallway; current frame remains anchored at the garage threshold rather than fully inside the hallway.

13. Frame 39 identity

    Pickup damage status remains unresolved because only a partial side/rear view is visible; no obvious new damage, repair progress, or identity change is visible.

14. Frame 43 identity

    John remains in the garage and has not visibly taken or sent the requested backyard photo.

15. Frame 50 identity

    John's wardrobe, cap, build, and rear/three-quarter pose are consistent with the expected continuity.

16. Frame 54 identity

    John's dark pickup is only partially visible on the right; no obvious new damage or repair progress can be assessed from this angle.

17. Frame 54 identity

    No visible evidence that John has taken or sent the requested backyard photo yet.

18. Frame 59 identity

    John appears to be walking rather than standing casually with weight on both feet as expected.

19. Frame 63 identity

    Expected John's tan baseball cap and dark hoodie are not visible, so upper-body wardrobe continuity cannot be confirmed.

20. Frame 67 identity

    Expected wardrobe items beyond bare hands are not visible, so clothing continuity cannot be verified here.

21. Frame 74 identity

    Only John's hands and sleeves are visible, so jeans, shoes, cap, and full body posture cannot be confirmed in-frame.

22. Frame 76 identity

    John's wardrobe is not visible except hands; hoodie, jeans, shoes, and tan cap cannot be confirmed in this frame.

23. Frame 78 identity

    Expected wardrobe lists gray casual shoes, but visible footwear appears brown shoes/boots.

Phone Task

1. Frame 1 phone-task

   Phone remains not visible, so Emily Carter's unread message has not visibly been read or addressed.

2. Frame 1 phone-task

   object_disappearance: smartphone was targeted but is not visible in the resulting frame.

3. Frame 2 phone-task

   Camera is not a phone-screen close-up; it appears to be a wide third-person view from behind John inside the garage.

4. Frame 2 phone-task

   Phone UI/text is not visible, so Emily Carter's unread message cannot be read or confirmed.

5. Frame 2 phone-task

   object_disappearance: smartphone was targeted but is not visible in the resulting frame.

6. Frame 3 phone-task

   Camera/framing does not match the expected phone-screen macro view; this is a third-person garage view with John's phone screen not visible.

7. Frame 3 phone-task

   Emily Carter's unread message remains unresolved because the phone screen is not visible and John has not visibly read or replied.

8. Frame 3 phone-task

   object_disappearance: smartphone was targeted but is not visible in the resulting frame.

9. Frame 4 phone-task

   Phone state differs from expected not_visible: the phone is now clearly visible in John's hand, though unreadable.

10. Frame 4 phone-task

    No visible evidence that John has read Emily Carter's message, photographed the backyard, or sent a reply/photo yet.

11. Frame 5 phone-task

    Expected wardrobe includes tan baseball cap, blue jeans, and brown work shoes, but these are not visible due to phone-screen framing.

12. Frame 5 phone-task

    Phone UI text is mostly too small/blurry to read; Emily Carter's unread message is not visibly confirmed in this frame.

13. Frame 6 phone-task

    John's body, cap, hoodie, jeans, and shoes are not visible due the tight phone-screen framing, so wardrobe continuity cannot be fully verified.

14. Frame 6 phone-task

    Phone thread now clearly shows Emily Carter's message, resolving the prior need to read the message.

15. Frame 7 phone-task

    Expected phone text/state previously referenced “CRAFTSMAN,” but the visible phone is now in Emily Carter’s message thread.

16. Frame 7 phone-task

    John’s full body, tan baseball cap, jeans, and shoes are not visible due to first-person phone-screen framing.

17. Frame 8 phone-task

    Camera/framing does not match the expected phone-screen macro perspective; this is a third-person view from behind John, though the phone screen is partially readable.

18. Frame 8 phone-task

    Emily Carter's unread message is not visible; no message content is shown or read in this frame.

19. Frame 8 phone-task

    Camera/framing does not match the expected phone_screen close-up: the scene is a third-person view of John holding the phone, and the phone UI is too small to read Emily's message.

20. Frame 8 phone-task

    Emily Carter's unread message is not visible, so the task to read it has not visibly progressed.

21. Frame 8 phone-task

    Phone lock screen time reads 9:41, which may not align with the expected late-afternoon simulation context if interpreted as actual in-world time.

22. Frame 8 phone-task

    object_disappearance: smartphone was targeted but is not visible in the resulting frame.

23. Frame 9 phone-task

    Phone state differs from expected locked state: it is now unlocked and open to Emily Carter's message thread.

24. Frame 10 phone-task

    Expected phone state says locked, but the visible phone is unlocked/open to the Emily Carter message thread.

25. Frame 10 phone-task

    John’s full body, tan baseball cap, jeans, and brown work shoes are not visible in this close phone-screen framing, so full wardrobe and pose cannot be verified.

26. Frame 10 phone-task

    fact_filter: dropped message_read, message_thread_opened because frame analysis did not visibly support them.

27. Frame 10 phone-task

    episode_overcompleted: beat_03:phone_photo_taken | beat_03:backyard_view_in_photo | beat_04:phone_screen_send

28. Frame 10 phone-task

    message_evaluation: needs_repair; Complete the requested photo/camera evidence.

29. Frame 11 phone-task

    Expected camera mode is close first-person phone-screen perspective with readable phone UI, but this frame shows a third-person view of John standing in the garage and the phone screen is not readable.

30. Frame 11 phone-task

    Emily Carter's message cannot be visually confirmed in this frame because no phone text is readable.

31. Frame 12 phone-task

    Expected Emily message/thread is not visible; the phone screen appears dark/locked, so no message text can be confirmed.

32. Frame 13 phone-task

    Expected pose described John turned toward the closed interior door with phone at waist level, but the frame is a tight phone close-up from his hand perspective.

33. Frame 13 phone-task

    Phone expected state listed as locked, but the visible phone is unlocked/open to the Emily Carter Messages thread.

34. Frame 14 phone-task

    Expected John in third-person full-body view with tan baseball cap, jeans, and brown work shoes, but this frame shows only his hand/forearm and phone; cap, pants, and shoes cannot be verified.

35. Frame 14 phone-task

    Phone time appears to read 9:47, while expected state referenced 9:41.

36. Frame 15 phone-task

    Phone message from Emily cannot be confirmed visually because the phone screen text is not readable in this frame.

37. Frame 17 phone-task

    Phone is not visible, so Emily Carter's pending backyard-photo message remains unresolved from visible evidence.

38. Frame 19 phone-task

    The phone is not visible, so Emily Carter's message/photo task remains unresolved in this frame.

39. Frame 20 phone-task

    Phone is not visible, so Emily Carter's requested backyard photo has not visibly been taken or sent in this frame.

40. Frame 20 phone-task

    Phone was previously visible with Emily Carter's message, but no phone or screen is visible in this frame, so the message/photo task remains unresolved.

41. Frame 20 phone-task

    Expected pose/state says John is walking mid-step through an open interior doorway toward the hallway, but this frame shows him standing in the garage looking at his phone.

42. Frame 20 phone-task

    Phone was previously expected as not_visible in the current world state, but it is clearly visible and active in John's hand.

43. Frame 20 phone-task

    Phone/message thread is not visible in this frame, so Emily Carter's backyard-photo request remains unresolved.

44. Frame 20 phone-task

    Phone was expected to be relevant for Emily's message/photo task, but no phone or phone screen is visible in this frame.

45. Frame 21 phone-task

    Phone is not visible, so Emily Carter's backyard photo request remains unresolved in this frame.

46. Frame 23 phone-task

    Phone is not visible, so Emily's message/photo task cannot be confirmed or progressed in this frame.

47. Frame 24 phone-task

    Phone remains not visible, so Emily's message/photo task is not visibly addressed in this frame.

48. Frame 26 phone-task

    Phone remains not visible, so Emily's requested backyard photo/message task is not visibly completed.

49. Frame 26 phone-task

    Phone remains not visible, so Emily's message/photo task is not visibly progressed.

50. Frame 28 phone-task

    Phone is not visible, so Emily's message/photo task remains unresolved from the image evidence.

51. Frame 30 phone-task

    Phone is not visible, so Emily's message/photo request remains unresolved from visual evidence.

52. Frame 32 phone-task

    John's phone is not visible, so Emily's message/photo task remains unresolved in this frame.

53. Frame 34 phone-task

    Emily message task remains unresolved visually: John's phone is not visible, and there is no evidence of reading the message, taking a backyard photo, or sending it.

54. Frame 39 phone-task

    Phone is not visible, so Emily's message/photo task cannot be confirmed in this frame.

55. Frame 41 phone-task

    Emily's message/photo task remains unresolved; no phone is visible and no photo-taking or messaging is shown.

56. Frame 42 phone-task

    Phone is not visible, so Emily's requested backyard photo/message task remains unresolved in this frame.

57. Frame 43 phone-task

    Phone is not visible, so Emily's message/photo request remains unresolved in this frame.

58. Frame 43 phone-task

    Phone is not visible, so Emily's message/photo task cannot be confirmed completed in this frame.

59. Frame 44 phone-task

    Phone is not visible, so Emily's message/photo task cannot be verified as completed in this frame.

60. Frame 44 phone-task

    John's phone is not visible, so Emily's message/photo task remains unresolved in this frame.

61. Frame 44 phone-task

    Phone is not visible, so Emily's requested backyard photo/message follow-up is not shown as completed in this frame.

62. Frame 45 phone-task

    Phone is not visible, so Emily's message/photo task remains unresolved in this frame.

63. Frame 46 phone-task

    Phone is not visible, so Emily's message/photo task remains unresolved in this frame.

64. Frame 47 phone-task

    Phone is not visible, so Emily's message/photo task remains unresolved.

65. Frame 47 phone-task

    episode_overcompleted: beat_03:phone_photo_taken | beat_03:backyard_view_in_photo

66. Frame 47 phone-task

    message_evaluation: needs_repair; Complete the requested photo/camera evidence.

67. Frame 49 phone-task

    Phone state appears active/screen-on in hand, which differs from the expected locked phone state; no readable phone text is visible.

68. Frame 50 phone-task

    Phone content is not readable, so Emily's requested message/photo/send task is not visibly completed in this frame.

69. Frame 51 phone-task

    Phone content/thread with Emily is not readable, so the requested backyard photo/send action is not visibly completed.

70. Frame 51 phone-task

    Phone content cannot be read, so Emily's thread/message state is not visually confirmable.

71. Frame 51 phone-task

    John's identity, wardrobe, and phone-in-hand state remain consistent with the expected world state.

72. Frame 52 phone-task

    Emily message/photo task remains unresolved; no visible evidence that John has taken or sent the requested backyard photo.

73. Frame 53 phone-task

    Phone is visible, but Emily's thread/message content is not readable and no photo-taking or sending action is visible in this frame.

74. Frame 54 phone-task

    Emily message/backyard photo task remains unresolved visually because the phone screen is unreadable and no sent photo is shown.

75. Frame 56 phone-task

    Phone thread content is not readable from this frame, so Emily's message/photo task cannot be confirmed as completed.

76. Frame 57 phone-task

    Phone content is not legible, so Emily's message/thread state cannot be visually confirmed in this frame.

77. Frame 57 phone-task

    episode_overcompleted: beat_03:phone_photo_taken | beat_03:backyard_view_in_photo | beat_04:phone_screen_send

78. Frame 57 phone-task

    message_evaluation: needs_repair; Complete the requested photo/camera evidence.

79. Frame 58 phone-task

    John is expected to be walking forward while looking down at the phone; in this frame he appears paused/standing and looking toward the yard/fence.

80. Frame 59 phone-task

    Phone appears held in the left hand from this view, while expected state says right hand holding phone at waist level.

81. Frame 60 phone-task

    Phone task remains visually incomplete: John is holding the phone but is not clearly photographing or sending the backyard image in this frame.

82. Frame 61 phone-task

    Expected John to be holding a phone low in his left hand, but no phone is visible.

83. Frame 62 phone-task

    John's phone is not visible, so the expected camera/message task with Emily cannot be confirmed.

84. Frame 63 phone-task

    Expected rear view of John walking away across the driveway holding a phone low, but the frame shows only his legs/feet from a first-person or low viewpoint and no visible phone.

85. Frame 64 phone-task

    Expected state says John is holding the phone low in his left hand, but in this frame the visible phone appears to be in his right hand.

86. Frame 64 phone-task

    Expected pose says rear view walking away holding phone low, but this frame shows first-person hands holding the phone up while standing/paused.

87. Frame 64 phone-task

    Expected phone state is camera, but the phone is visibly on Emily Carter's message thread.

88. Frame 65 phone-task

    Expected prior phone state was Emily Carter message thread, but the visible phone is now in camera/photo mode; this is consistent with John acting on Emily's request if intentional.

89. Frame 65 phone-task

    The phone camera preview shows a backyard/fenced lawn while the surrounding real-world view is the driveway facing the street; this may be a perspective/preview mismatch unless John is viewing an existing image or the camera feed is not aligned with the physical scene.

90. Frame 65 phone-task

    episode_overcompleted: beat_04:phone_screen_send

91. Frame 65 phone-task

    message_evaluation: complete; complete

92. Frame 66 phone-task

    The phone preview shows a backyard/fenced lawn while the surrounding physical view is the driveway/front street, creating a perspective/location mismatch unless the phone is displaying a previously framed/captured backyard view.

93. Frame 66 phone-task

    Expected gray shoes and blue jeans are not visible due to close hand/phone framing.

94. Frame 67 phone-task

    Expected driveway location is not visually confirmed because the frame is dominated by the phone screen showing a backyard scene.

95. Frame 68 phone-task

    John's tan baseball cap, jeans, and gray shoes are not visible due to first-person phone-focused framing.

96. Frame 69 phone-task

    Expected phone state says locked with a Linda Carter message visible/unread, but the frame shows the phone unlocked on a photo sharing screen with no Linda message visible.

97. Frame 69 phone-task

    The current phone screen appears to continue the prior photo-sharing/camera task rather than the unresolved Linda Carter dinner reply thread.

98. Frame 69 phone-task

    John's tan baseball cap is not visible, but this is expected/acceptable from the first-person downward phone view.

99. Frame 69 phone-task

    Expected phone state listed as locked, but the frame shows the phone unlocked in a Messages conversation with the keyboard open.

100. Frame 69 phone-task

     Expected camera/phone-screen context from prior frame involved taking a photo, but this frame has shifted to Linda Carter's message thread, which aligns with the unresolved Linda reply task.

101. Frame 69 phone-task

     Phone was expected to be locked, but it is visibly unlocked and open to the Linda Carter Messages thread.

102. Frame 69 phone-task

     Expected phone thread state referenced thread_char_emily, but the visible active conversation is Linda Carter, matching the unresolved Linda dinner-message task.

103. Frame 70 phone-task

     Expected phone state included locked, but the frame shows the phone unlocked and open to a Messages conversation.

104. Frame 71 phone-task

     Expected phone state included locked, but the visible phone is unlocked and open to a Messages conversation.

105. Frame 71 phone-task

     The visible phone thread is Linda Carter, while the expected thread id references Emily; visible evidence supports Linda Carter here.

106. Frame 71 phone-task

     Driveway location is not visually confirmable due the tight phone-screen framing.

107. Frame 72 phone-task

     Expected world state says the phone is locked, but the phone is visibly unlocked in the Messages app.

108. Frame 73 phone-task

     Expected phone state referenced a locked Linda Carter text about Sunday dinner, but the visible phone is unlocked in an Emily thread with a delivered backyard-photo message.

109. Frame 73 phone-task

     Linda Carter's Sunday dinner message is not visible in this frame, so that unresolved thread remains unanswered.

110. Frame 73 phone-task

     Expected phone state said locked, but the frame shows the phone unlocked with the Linda Carter Messages thread open.

111. Frame 73 phone-task

     Expected wardrobe includes blue jeans and gray shoes, but only dark hoodie sleeves and hands are visible in this phone-screen framing; jeans and shoes cannot be confirmed.

112. Frame 73 phone-task

     Expected phone state said locked/unread, but the frame shows the phone unlocked with Linda Carter's message opened and read.

113. Frame 73 phone-task

     John's expected jeans, shoes, and tan baseball cap are not visible in this tight first-person phone view, so they cannot be confirmed.

114. Frame 74 phone-task

     Expected phone state lists the phone as locked, but the frame shows it unlocked in Linda Carter's Messages thread; this appears to be progress toward reading/replying rather than a hidden event.

115. Frame 74 phone-task

     fact_filter: dropped message_thread_opened, photo_sent because frame analysis did not visibly support them.

116. Frame 74 phone-task

     message_evaluation: complete; complete

117. Frame 75 phone-task

     Expected phone state says locked, but the phone is visibly unlocked in the Messages app.

118. Frame 75 phone-task

     Expected phone text/state mentions Linda Carter: done and thread_char_emily, but the visible active thread is Linda Carter with no typed/sent reply shown.

119. Frame 75 phone-task

     Prior beat indicates sending an outbound message to Emily, but the current visible phone screen shows Linda Carter's thread and no outbound message.

120. Frame 76 phone-task

     Expected phone state says locked, but the visible phone is unlocked with Messages open.

121. Frame 76 phone-task

     Expected active thread metadata references thread_char_emily, but the visible thread is Linda Carter.

122. Frame 76 phone-task

     The frame is too tightly focused on the phone to verify the garage/driveway location or nearby garage objects.

123. Frame 76 phone-task

     John's dark pickup truck is not visible due to the phone close-up; vehicle location, identity, damage, and repair status cannot be assessed.

124. Frame 77 phone-task

     Expected phone state was locked, but the phone is visibly unlocked in Messages.

125. Frame 77 phone-task

     Expected actor pose said standing on the driveway holding the phone with both hands; this frame shows John inside/at the garage, apparently seated or crouched, holding the phone mostly one-handed.

126. Frame 78 phone-task

     Expected pose says John is standing on the driveway holding the phone with both hands; this frame shows him inside the garage holding the phone with one visible hand.

127. Frame 78 phone-task

     Expected phone state includes a locked phone with a readable Linda Carter message, but the frame shows a lit blurred interface with no readable text and appears more like an unlocked screen.

128. Frame 78 phone-task

     John's tan baseball cap is not visible from this first-person phone view, so it cannot be confirmed.

129. Frame 78 phone-task

     Expected phone state says locked, but the image shows the phone unlocked with a Messages thread open.

130. Frame 78 phone-task

     Expected actor pose mentions holding the phone with both hands and thumbs near the keyboard, but the image shows one visible hand holding the phone and no visible keyboard.

131. Frame 78 phone-task

     John's tan baseball cap, blue jeans, and gray shoes are not visible from this first-person close phone view.

132. Frame 78 phone-task

     Phone expected state says locked, but the frame shows the phone unlocked in an open Messages thread with the keyboard visible.

133. Frame 78 phone-task

     Expected pose says John is on the driveway holding the phone with both hands; the frame shows him at/inside the garage threshold and only one visible hand holding the phone.

134. Frame 78 phone-task

     Expected phone state says locked, but the phone is visibly unlocked with the Messages thread open.

135. Frame 78 phone-task

     Expected pose says John is on the driveway holding the phone with both hands, but the frame shows him inside/at the garage threshold holding the phone with one visible hand.

136. Frame 78 phone-task

     Expected active thread metadata mentions thread_char_emily, but the visible phone thread is Linda Carter.

Vehicle Transport

1. Frame 1 vehicle-transport

   Persistent dark pickup truck is not visible in this frame, so its location/status and any damage cannot be assessed; this may conflict with expected vehicle presence in the driveway/garage area.

2. Frame 2 vehicle-transport

   The persistent dark pickup truck expected to be in the garage is not visible; vehicle location and any minor damage state cannot be assessed.

3. Frame 3 vehicle-transport

   Expected persistent dark pickup truck is supposed to be in the garage, but no pickup is visible in this frame; vehicle identity, damage, or repair status cannot be assessed.

4. Frame 4 vehicle-transport

   Expected persistent dark pickup truck is supposed to be current=garage, but no pickup is visible in this wide garage view; vehicle identity and damage status cannot be assessed.

5. Frame 5 vehicle-transport

   Persistent dark pickup truck is expected to be in the garage, but no pickup is visible; vehicle damage/status cannot be assessed.

6. Frame 6 vehicle-transport

   The dark pickup truck is not visible in this close-up; its garage presence, identity, and damage status cannot be assessed.

7. Frame 7 vehicle-transport

   Only a cropped portion of the dark vehicle is visible at the right edge, so persistent pickup identity and minor damage status cannot be fully verified.

8. Frame 8 vehicle-transport

   Persistent dark pickup is only partially visible at the far right edge; vehicle identity and damage status remain unresolved, with no obvious new damage visible from this limited view.

9. Frame 8 vehicle-transport

   The dark pickup truck is visible in the garage; it appears consistent with the persistent vehicle, but only a partial dusty side/rear view is shown, so minor damage status remains unresolved.

10. Frame 9 vehicle-transport

    The dark pickup truck is only partially visible on the right, so existing minor damage/status cannot be fully assessed; no obvious new damage or repair change is visible.

11. Frame 10 vehicle-transport

    The dark pickup truck is only partially visible at the right edge; minor damage status remains unresolved and no repair/change can be assessed.

12. Frame 11 vehicle-transport

    Pickup truck damage remains unresolved because only a partial side view is visible; no obvious new damage or repair change is seen.

13. Frame 12 vehicle-transport

    Pickup truck is only partially visible; no obvious damage or repair change is seen, but its minor damage status remains unresolved from this angle.

14. Frame 13 vehicle-transport

    Expected persistent dark pickup truck is not visible in this close-up frame; damage/status cannot be assessed.

15. Frame 14 vehicle-transport

    Expected persistent vehicle is John's dark pickup truck; this frame shows only a partial dark vehicle on the right, and its pickup identity is not clearly confirmable from the cropped side/front view.

16. Frame 14 vehicle-transport

    Vehicle damage status remains unresolved: no obvious damage or repair change is visible, but the vehicle is too partially shown to assess minor damage fully.

17. Frame 16 vehicle-transport

    John appears to be moving into the hallway before completing Emily Carter's unresolved request to take and send a quick backyard photo.

18. Frame 16 vehicle-transport

    Pickup truck is only partially visible on the right; no obvious new damage or repair change is visible, but minor damage status remains unresolved from this angle.

19. Frame 17 vehicle-transport

    The dark pickup truck is not visible in this frame despite prior/expected garage vehicle continuity; no vehicle damage, repair, or identity status can be assessed.

20. Frame 18 vehicle-transport

    The dark pickup truck is not visible due to tight framing; vehicle identity, damage, and repair status cannot be assessed.

21. Frame 19 vehicle-transport

    The dark pickup truck is only partially visible; damage status and repair change cannot be assessed.

22. Frame 20 vehicle-transport

    Expected pose/state said John was walking through the open interior doorway toward the hallway, but this frame shows him walking out through the raised garage opening toward the driveway/yard.

23. Frame 20 vehicle-transport

    The expected vehicle state has repeatedly placed the dark pickup in the garage; in this frame the pickup is partially visible on the right near the open garage/driveway edge and may be outside or only partly in view. No new damage or repair status can be confirmed from this angle.

24. Frame 20 vehicle-transport

    Pickup truck damage remains unresolved because only a partial side view is visible; no obvious new damage or repair change can be assessed.

25. Frame 21 vehicle-transport

    Pickup truck damage status remains unresolved because only a partial side/rear view is visible.

26. Frame 22 vehicle-transport

    Persistent dark pickup truck is not visible in this cropped garage view; vehicle identity, damage, and repair status cannot be assessed.

27. Frame 23 vehicle-transport

    Expected location/action indicated John at the interior door entering the house from the garage, but the frame shows him outside on the driveway walking away from the open garage toward the yard.

28. Frame 23 vehicle-transport

    Expected garage-anchored close framing near the interior door is not maintained; the scene has shifted to the driveway/exterior.

29. Frame 23 vehicle-transport

    Pickup truck is visible outside/on the driveway side rather than clearly inside the garage; this may conflict with prior vehicle placement in the garage, though the same dark pickup identity appears consistent.

30. Frame 23 vehicle-transport

    Pickup truck damage status remains unresolved because only a partial dusty side view is visible; no obvious new damage or repair change is assessable.

31. Frame 24 vehicle-transport

    Pickup truck damage status remains unresolved because only a partial side view is visible; no obvious new damage, repair progress, or identity change is apparent.

32. Frame 25 vehicle-transport

    The dark pickup truck is only partially visible on the right; no new damage or repair change can be assessed from this angle.

33. Frame 26 vehicle-transport

    Pickup truck damage remains unresolved because only a partial side/front view is visible; no obvious new damage or repair change can be assessed.

34. Frame 28 vehicle-transport

    Pickup truck is only partially visible on the right; no obvious new damage or repair change can be assessed from this angle.

35. Frame 29 vehicle-transport

    Expected state says John is in the garage facing the open doorway/hallway, but this frame shows him facing outward toward an exterior yard/driveway area; the interior hallway door is not visible.

36. Frame 29 vehicle-transport

    The raised garage door/open driveway connection is not visible from this framing, so its state cannot be confirmed.

37. Frame 30 vehicle-transport

    Pickup truck is only partially visible; no obvious new damage or repair change is seen, but the persistent minor damage status cannot be fully assessed from this angle.

38. Frame 31 vehicle-transport

    Pickup truck damage remains unresolved because only a partial side/front view is visible; no obvious new damage, repair progress, or vehicle identity drift is seen.

39. Frame 33 vehicle-transport

    The pickup truck is only partially visible, so its existing minor damage/repair status cannot be confirmed from this angle.

40. Frame 34 vehicle-transport

    Pickup truck damage status remains unresolved because only a partial side/front view is visible; no obvious new damage, repair progress, or vehicle identity drift is apparent.

41. Frame 35 vehicle-transport

    John is no longer at the closed/open interior doorway threshold described in the expected pose; he has moved to the raised garage door opening and is walking outward toward the driveway/yard.

42. Frame 35 vehicle-transport

    Pickup truck damage status remains unresolved because only a partial side/front view is visible; no obvious new damage, repair progress, or identity drift is visible.

43. Frame 37 vehicle-transport

    The dark pickup truck is only partially visible; no obvious new damage or repair progress can be assessed from this angle.

44. Frame 38 vehicle-transport

    Expected location was inside the garage near the interior door, but this frame shows John outside at the driveway/garage exterior looking toward the backyard.

45. Frame 38 vehicle-transport

    The dark pickup is visible only partially on the right and appears at the garage/driveway edge rather than clearly inside the garage; vehicle damage status remains unresolved from this angle.

46. Frame 38 vehicle-transport

    The pickup truck is only partially visible, so its prior minor damage/repair status cannot be fully assessed; no obvious new damage or identity drift is visible.

47. Frame 40 vehicle-transport

    Pickup truck damage/repair status remains unresolved because only a partial side/front view is visible; no obvious new damage, repair progress, or vehicle identity drift is visible.

48. Frame 41 vehicle-transport

    Expected actor state placed John near the interior door threshold moving into the hallway, but this frame shows him walking toward the raised open garage door and driveway.

49. Frame 41 vehicle-transport

    Expected actor pose/state said John was at the threshold of the interior door moving into the hallway, but the frame shows him walking toward the raised open garage door/driveway while the interior door remains closed.

50. Frame 42 vehicle-transport

    Pickup damage status remains unresolved because the vehicle is only partially visible; no obvious new damage or repair progress is visible.

51. Frame 43 vehicle-transport

    Pickup truck damage status remains unresolved because only a partial side/front view is visible; no obvious new damage or repair progress is visible.

52. Frame 43 vehicle-transport

    The dark pickup/vehicle is only partially visible on the right; no new damage or repair change can be assessed from this angle.

53. Frame 44 vehicle-transport

    Pickup truck damage status remains unresolved because only a partial side/front view is visible; no obvious new damage, repair progress, or identity change is visible.

54. Frame 44 vehicle-transport

    John is still in the garage rather than clearly leaving; he appears paused or just preparing to step toward the driveway.

55. Frame 44 vehicle-transport

    Vehicle damage remains unresolved because only a partial side/front view of the dark pickup is visible.

56. Frame 44 vehicle-transport

    The dark pickup truck remains only partially visible; vehicle damage status, repair progress, and exact identity details cannot be fully assessed, though no obvious new damage or identity drift is visible.

57. Frame 46 vehicle-transport

    The truck appears positioned inside or immediately beside the garage opening rather than clearly parked out on the driveway, so vehicle location remains visually ambiguous against the driveway expectation.

58. Frame 47 vehicle-transport

    Vehicle damage status remains unresolved because only a partial side/front view of the pickup is visible; no obvious new damage, repair progress, or identity change is visible.

59. Frame 48 vehicle-transport

    Pickup truck damage status remains unresolved because only a partial side/front view is visible; no obvious new damage, repair progress, or vehicle identity drift is visible.

60. Frame 48 vehicle-transport

    John's wardrobe and pose remain consistent with expected driveway continuity.

61. Frame 49 vehicle-transport

    John is positioned at the garage/driveway threshold rather than clearly farther out on the driveway, but the driveway location continuity is still plausible.

62. Frame 50 vehicle-transport

    Location remains anchored at the driveway/open garage area, consistent with expected driveway continuity.

63. Frame 50 vehicle-transport

    John's dark pickup truck is present and consistent in color/body placement from prior frames; only a partial side/front view is visible, so minor damage status remains unresolved and no repair progress can be assessed.

64. Frame 51 vehicle-transport

    Pickup remains partially visible and appears consistent with John's persistent dark truck, but only the side/front area is shown, so prior minor damage status cannot be confirmed or resolved.

65. Frame 51 vehicle-transport

    The pickup is only partially visible, so existing minor damage status cannot be fully assessed; no obvious new damage, repair progress, or vehicle identity drift is visible.

66. Frame 51 vehicle-transport

    John appears at the garage/driveway threshold rather than fully out in the driveway, but the location remains consistent with the expected driveway/open garage area.

67. Frame 51 vehicle-transport

    Location is consistent with the driveway/open garage area, though John is positioned at the garage threshold rather than fully out on the driveway.

68. Frame 51 vehicle-transport

    Vehicle placement appears ambiguous at the right side of the garage/driveway threshold, so exact driveway-versus-garage position cannot be confirmed from this frame.

69. Frame 53 vehicle-transport

    Pickup remains only partially visible; no obvious new damage, repair progress, or vehicle identity change can be assessed from this angle.

70. Frame 54 vehicle-transport

    Expected driveway continuity is preserved, though the open garage is not visible in this frame.

71. Frame 54 vehicle-transport

    Truck damage state remains unresolved because only a partial side/front view is visible; no obvious new damage, repair progress, or vehicle identity drift is visible.

72. Frame 54 vehicle-transport

    Truck is partly positioned at the garage/right-edge area while expected state says driveway; this may be the same vehicle at the garage-driveway boundary rather than a clear location change.

73. Frame 55 vehicle-transport

    Pickup truck damage remains unresolved because only a partial side/front view is visible; no new damage or repair change is apparent.

74. Frame 55 vehicle-transport

    John appears to be taking a small step forward rather than fully stationary, but this is consistent with the ongoing preparatory movement near the driveway/garage threshold.

75. Frame 56 vehicle-transport

    Pickup truck damage/repair status remains unresolved because only a partial side/front view is visible; no obvious new damage, repair progress, or vehicle identity drift is visible.

76. Frame 58 vehicle-transport

    Pickup truck remains partially visible on the right and appears consistent with the persistent dark pickup; no new damage or repair status can be confirmed from this angle.

77. Frame 59 vehicle-transport

    Truck is only partially visible at the open garage/right edge; no clear assessment of persistent minor damage or repair status is possible.

78. Frame 60 vehicle-transport

    Pickup damage state remains unresolved because only a partial side/front view is visible; no obvious new damage, repair progress, or vehicle identity drift is visible.

79. Frame 60 vehicle-transport

    The pickup appears at the right edge by the open garage/driveway; exact parked position is partially occluded and cannot be fully confirmed.

80. Frame 61 vehicle-transport

    John's dark pickup is only partially visible at the left edge; vehicle identity is broadly consistent, but damage/repair status remains unresolved from this angle.

81. Frame 62 vehicle-transport

    Expected close follow framing with John's hands and the same vehicle part visible, but this frame only shows his feet and lower legs.

82. Frame 62 vehicle-transport

    The dark pickup truck is absent from view; no vehicle damage, repair progress, or identity continuity can be assessed.

83. Frame 63 vehicle-transport

    John's persistent dark pickup truck is not visible, despite prior/expected driveway context; vehicle identity, position, damage, and repair status cannot be assessed in this frame.

84. Frame 63 vehicle-transport

    Camera framing no longer keeps the same vehicle part visible as expected.

85. Frame 66 vehicle-transport

    John's dark pickup truck is not clearly visible, so persistent vehicle identity, minor damage, and repair status remain unresolved from this frame.

86. Frame 67 vehicle-transport

    John's dark pickup truck is not visible; persistent vehicle identity, minor damage, and repair status cannot be assessed from this frame.

87. Frame 68 vehicle-transport

    Expected location is driveway with John's dark pickup truck nearby, but this frame primarily shows a backyard/lawn view and no pickup truck is visible.

88. Frame 68 vehicle-transport

    Pickup truck damage/repair status cannot be assessed because the vehicle is absent from the visible frame.

89. Frame 69 vehicle-transport

    Pickup damage remains unresolved because only a partial side/front view is visible; no obvious new damage, repair progress, or vehicle identity drift is seen.

90. Frame 69 vehicle-transport

    The persistent dark pickup is visible only partially at the garage/right edge; no new damage or repair progress can be assessed, and its exact driveway versus garage position remains ambiguous.

91. Frame 70 vehicle-transport

    Only a partial view of the pickup is visible, so the persistent minor damage state cannot be fully assessed; no obvious new damage, repair progress, or vehicle identity drift is visible.

92. Frame 71 vehicle-transport

    John's dark pickup truck is not visible in this frame, so vehicle identity, damage, and repair state cannot be assessed.

93. Frame 72 vehicle-transport

    Expected driveway state includes John's dark pickup truck nearby, but no pickup truck is visible in this frame; vehicle damage/repair/location status cannot be assessed.

94. Frame 73 vehicle-transport

    Vehicle damage remains unresolved: only a partial side/front view of the dark pickup is visible, with no clear view of the known minor damage area.

95. Frame 73 vehicle-transport

    Expected driveway context mentions an open garage, but the visible garage door appears closed.

96. Frame 73 vehicle-transport

    Pickup truck damage remains unresolved because only a partial side/front view is visible; no new damage or repair progress can be assessed.

97. Frame 74 vehicle-transport

    Pickup damage remains unresolved because only a partial side/front view is visible; no obvious new damage, repair progress, or vehicle identity change can be assessed.

98. Frame 75 vehicle-transport

    Expected location says garage with raised/open garage door, but the frame shows John outside on the driveway facing a closed garage door.

99. Frame 77 vehicle-transport

    Expected persistent vehicle is John's dark pickup truck; visible vehicle appears to be a dark SUV/crossover rear rather than a pickup, suggesting vehicle identity drift unless this is a different vehicle.

100. Frame 77 vehicle-transport

     Vehicle damage status cannot be assessed from the partial rear view; no obvious repair progress or new damage is visible.

101. Frame 78 vehicle-transport

     The pickup is visible in the garage/right side of frame, while some prior/expected state references place it on the driveway; vehicle location remains visually inconsistent across frames.

102. Frame 78 vehicle-transport

     Actor state text says John is standing on the driveway, but the image perspective appears inside the garage looking out through the open garage door.

103. Frame 78 vehicle-transport

     Persistent vehicle state says the pickup's home/current location is driveway, but this frame shows the dark pickup partially inside the garage on the right. Vehicle identity appears consistent, and damage remains not fully assessable.

104. Frame 78 vehicle-transport

     Pickup location remains ambiguous relative to expected driveway state: it is visible along the right side at the garage/driveway edge; no new damage or repair change is visible from this partial view.

105. Frame 78 vehicle-transport

     The dark pickup is partially visible in/at the garage on the right; expected vehicle location says driveway, so exact vehicle position remains ambiguous from this view.

Harness Validation

1. Frame 4 harness-validation

   harness_retry: macro_overcompleted; Rendered frame conflicts with the required beat or current state: macro_overcompleted.

2. Frame 8 harness-validation

   harness_retry: macro_overcompleted; Rendered frame conflicts with the required beat or current state: macro_overcompleted.

3. Frame 8 harness-validation

   harness_rejected: macro_overcompleted; Rendered frame conflicts with the required beat or current state: macro_overcompleted.

4. Frame 8 harness-validation

   hold_previous: macro_overcompleted - Rendered frame conflicts with the required beat or current state: macro_overcompleted.

5. Frame 20 harness-validation

   harness_retry: micro_target_not_reached; Rendered frame conflicts with the required beat or current state: micro_target_not_reached.

6. Frame 20 harness-validation

   harness_rejected: micro_target_not_reached; Rendered frame conflicts with the required beat or current state: micro_target_not_reached.

7. Frame 20 harness-validation

   hold_previous: micro_target_not_reached - Rendered frame conflicts with the required beat or current state: micro_target_not_reached.

8. Frame 20 harness-validation

   harness_retry: missing_required_beat, actor_missing_required_visibility, frame_advance_overrun; FrameAnalysis shows continuity issues: backyard view not visible, phone state inconsistent with evidence ledger; not meeting the required beat 'Go to a spot with a clear view of the backyard' before taking photo; interior door status and door orientation may conflict with macro action sequencing.

9. Frame 20 harness-validation

   harness_rejected: off_phase_visual; Frame shows John oriented toward the outside while the current beat expects a micro-movement toward a path; phone visibility is inconsistent with frame ledger (phone_taken_out noted in ledger but not visible), and the backyard view is not clearly captured. Repair needed to align frame with the beat and contract. Retry budget exhausted; holding prior accepted state.

10. Frame 20 harness-validation

    hold_previous: off_phase_visual - Frame shows John oriented toward the outside while the current beat expects a micro-movement toward a path; phone visibility is inconsistent with frame ledger (phone_taken_out noted in ledger but not visible), and the backyard view is not clearly captured. Repair needed to align frame with the beat and contract. Retry budget exhausted; holding prior accepted state.

11. Frame 20 harness-validation

    harness_retry: missing_required_beat, actor_missing_required_visibility; Current frame does not show the required next beat (John reading Emily's message and taking the backyard photo) and the phone is not visible, so progress cannot be verified. A repair is needed to show the phone visible with the message read and evidence of a backyard photo being taken or sent.

12. Frame 20 harness-validation

    harness_rejected: missing_required_beat, microstep_skipped; Frame shows John in the garage looking at his phone; the required immediate micro-beat (turn_toward_path) has not been observed. There are continuity issues (phone visibility state inconsistent with prior frame planning, interior door state). The frame cannot advance to the next macro action reliably without repair. Retry budget exhausted; holding prior accepted state.

13. Frame 20 harness-validation

    hold_previous: missing_required_beat, microstep_skipped - Frame shows John in the garage looking at his phone; the required immediate micro-beat (turn_toward_path) has not been observed. There are continuity issues (phone visibility state inconsistent with prior frame planning, interior door state). The frame cannot advance to the next macro action reliably without repair. Retry budget exhausted; holding prior accepted state.

14. Frame 20 harness-validation

    harness_retry: missing_required_beat; Frame shows John inside the garage facing the interior door with no evidence of the required next actions (checking/reading Emily’s message on the phone, moving to a position with a clear backyard view, or taking/sending the photo). Continuity notes also flag a mismatch between door state/John’s location and the expected beat progression, and the phone is not visible in this frame.

15. Frame 20 harness-validation

    harness_rejected: missing_required_beat, frame_advance_overrun, microstep_skipped; Frame shows micro-movement turning toward the path but does not advance to the required backyard-view/photo action; backyard and phone-thread visibility are missing according to the continuity notes. Retry budget exhausted; holding prior accepted state.

16. Frame 20 harness-validation

    hold_previous: missing_required_beat, frame_advance_overrun, microstep_skipped - Frame shows micro-movement turning toward the path but does not advance to the required backyard-view/photo action; backyard and phone-thread visibility are missing according to the continuity notes. Retry budget exhausted; holding prior accepted state.

17. Frame 23 harness-validation

    harness_retry: micro_target_not_reached; Rendered frame conflicts with the required beat or current state: micro_target_not_reached.

18. Frame 23 harness-validation

    harness_rejected: micro_target_not_reached; Rendered frame conflicts with the required beat or current state: micro_target_not_reached.

19. Frame 23 harness-validation

    hold_previous: micro_target_not_reached - Rendered frame conflicts with the required beat or current state: micro_target_not_reached.

20. Frame 23 harness-validation

    harness_retry: missing_required_beat; Phone is not visible in the frame and Emily's requested action (read message, take backyard photo) cannot be verified. The current micro-movement beat does not fulfill the required beat to make the phone visible and read the message.

21. Frame 25 harness-validation

    harness_retry: missing_required_beat, frame_advance_overrun; Frame shows John inside the garage stepping toward an open interior door into the house hallway, not crossing the threshold toward the driveway as the current micro-beat plan ('cross_threshold') requires. Also, the interior door is described as closed in the plan but is open in the render, indicating a door-state continuity drift. The frame does not display the backyard photo task or the backyard view yet. These factors indicate the current render may not correctly advance the intended frame choreography and should be repaired or adjusted.

22. Frame 26 harness-validation

    harness_retry: micro_target_not_reached; Rendered frame conflicts with the required beat or current state: micro_target_not_reached.

23. Frame 26 harness-validation

    harness_rejected: micro_target_not_reached; Rendered frame conflicts with the required beat or current state: micro_target_not_reached.

24. Frame 26 harness-validation

    hold_previous: micro_target_not_reached - Rendered frame conflicts with the required beat or current state: micro_target_not_reached.

25. Frame 26 harness-validation

    accept: missing_required_beat, off_phase_visual - Frame shows John performing the first micro-movement (turn toward path) within the garage and not yet at the target location, which aligns with the current micro-beat. However, Emily's messaging task (reading the message) and the phone visibility are not demonstrated in this frame, and there is a visual continuity issue regarding the phone state.

26. Frame 27 harness-validation

    accept: off_phase_visual - Frame shows John in garage near a closed interior door; this aligns with the 'take_first_steps' beat (first small step within current space). However, there is a continuity issue: prior frame summary suggested an open interior doorway; the closed door in this frame conflicts with that earlier condition.

27. Frame 28 harness-validation

    harness_retry: off_phase_visual; Continuity issue: interior door state inconsistent with expected frame; the current beat is a micro-threshold crossing and closure of the interior door should be maintained; the door appears open, conflicting with prior state that door is closed; also, the macro movement has not completed.

28. Frame 29 harness-validation

    harness_retry: micro_target_not_reached; Rendered frame conflicts with the required beat or current state: micro_target_not_reached.

29. Frame 29 harness-validation

    harness_rejected: micro_target_not_reached; Rendered frame conflicts with the required beat or current state: micro_target_not_reached.

30. Frame 29 harness-validation

    hold_previous: micro_target_not_reached - Rendered frame conflicts with the required beat or current state: micro_target_not_reached.

31. Frame 30 harness-validation

    harness_retry: missing_required_beat; The frame shows John advancing a micro-step toward the driveway, but the required beat to read Emily's message cannot occur because the phone is not visible and Emily's message is unread. The 'read message' beat is missing; thus the frame cannot advance to the next macro action until the phone is visible and the message read.

32. Frame 31 harness-validation

    harness_retry: off_phase_visual; Frame shows John crossing the interior doorway with the door visibly open, which conflicts with the planned phase of crossing a threshold toward the driveway and with the expectation that the interior door is closed during this micro-movement.

33. Frame 32 harness-validation

    harness_retry: micro_target_not_reached; Rendered frame conflicts with the required beat or current state: micro_target_not_reached.

34. Frame 32 harness-validation

    harness_rejected: micro_target_not_reached; Rendered frame conflicts with the required beat or current state: micro_target_not_reached.

35. Frame 32 harness-validation

    hold_previous: micro_target_not_reached - Rendered frame conflicts with the required beat or current state: micro_target_not_reached.

36. Frame 32 harness-validation

    harness_retry: frame_advance_overrun, missing_required_beat, microstep_skipped, micro_target_not_reached, actor_missing_required_visibility; The current frame shows John in the garage facing the interior door with no observable micro-movement toward the next path (turn_toward_path). The required beat is not demonstrated, and continuity indicates the interior doorway is open in the narrative but closed in the frame. This frame fails to render the current beat as required.

37. Frame 35 harness-validation

    harness_retry: micro_target_not_reached; Rendered frame conflicts with the required beat or current state: micro_target_not_reached.

38. Frame 35 harness-validation

    harness_rejected: micro_target_not_reached; Rendered frame conflicts with the required beat or current state: micro_target_not_reached.

39. Frame 35 harness-validation

    hold_previous: micro_target_not_reached - Rendered frame conflicts with the required beat or current state: micro_target_not_reached.

40. Frame 36 harness-validation

    harness_retry: actor_missing_required_visibility; Phone and messaging task require the device to be visible to progress Emily's request; in this frame the phone is not visible which prevents reading/acting on the message. Frame shows micro-movement but does not satisfy visibility requirement.

41. Frame 38 harness-validation

    harness_retry: micro_target_not_reached; Rendered frame conflicts with the required beat or current state: micro_target_not_reached.

42. Frame 38 harness-validation

    harness_rejected: micro_target_not_reached; Rendered frame conflicts with the required beat or current state: micro_target_not_reached.

43. Frame 38 harness-validation

    hold_previous: micro_target_not_reached - Rendered frame conflicts with the required beat or current state: micro_target_not_reached.

44. Frame 40 harness-validation

    harness_retry: off_phase_visual; Continuity issue: interior door is open but expected closed for this frame; phone not visible, hindering Emily's instruction; frame shows micro-movement but the state change to doorway is inconsistent with the beat; requires repair before advancing.

45. Frame 41 harness-validation

    harness_retry: micro_target_not_reached; Rendered frame conflicts with the required beat or current state: micro_target_not_reached.

46. Frame 41 harness-validation

    harness_rejected: micro_target_not_reached; Rendered frame conflicts with the required beat or current state: micro_target_not_reached.

47. Frame 41 harness-validation

    hold_previous: micro_target_not_reached - Rendered frame conflicts with the required beat or current state: micro_target_not_reached.

48. Frame 41 harness-validation

    harness_retry: missing_required_beat, microstep_skipped; The current frame shows John standing in front of the interior door, not yet turning toward the path or moving to the driveway as required by beat_02. Backyard view and phone visibility are also not demonstrated in this frame, failing to satisfy the next required beat and success criteria.

49. Frame 43 harness-validation

    harness_rejected: none; Evidence indicates the phone is not visible in the current frame, which prevents reading/sending Emily's message as required by the contract. Although the phone was taken out earlier, the frame does not show the backyard photo being taken or an outbound message sent, and the next macro action (crossing the threshold) cannot be cleanly advanced without resolving the continuity issue. Therefore, do not advance, and repair by rendering a frame in which the phone is visible, Emily's message is read, and the backyard photo is taken and sent before proceeding.

50. Frame 44 harness-validation

    harness_retry: micro_target_not_reached; Rendered frame conflicts with the required beat or current state: micro_target_not_reached.

51. Frame 44 harness-validation

    harness_rejected: micro_target_not_reached; Rendered frame conflicts with the required beat or current state: micro_target_not_reached.

52. Frame 44 harness-validation

    hold_previous: micro_target_not_reached - Rendered frame conflicts with the required beat or current state: micro_target_not_reached.

53. Frame 44 harness-validation

    harness_retry: missing_required_beat; Phone is not visible and Emily's message (the required backyard photo task) has not been progressed/read in this frame. The current micro-movement shows a turn toward the path but does not advance toward the backyard or reveal the phone; thus the essential task cannot advance.

54. Frame 44 harness-validation

    harness_rejected: actor_missing_required_visibility, missing_required_beat; Phone is not visible in current frame, preventing execution of the required beat 'Make the phone visible and read Emily's message'. The frame shows John pausing in garage, not yet moving to driveway; according to the plan, the next steps require using the phone to read the message and take a backyard photo, which cannot be demonstrated here. Retry budget exhausted; holding prior accepted state.

55. Frame 44 harness-validation

    hold_previous: actor_missing_required_visibility, missing_required_beat - Phone is not visible in current frame, preventing execution of the required beat 'Make the phone visible and read Emily's message'. The frame shows John pausing in garage, not yet moving to driveway; according to the plan, the next steps require using the phone to read the message and take a backyard photo, which cannot be demonstrated here. Retry budget exhausted; holding prior accepted state.

56. Frame 47 harness-validation

    harness_retry: micro_target_not_reached; Rendered frame conflicts with the required beat or current state: micro_target_not_reached.

57. Frame 49 harness-validation

    harness_retry: missing_required_beat, frame_advance_overrun, micro_location_overrun; Frame shows John on driveway (end-state of macro action) while the current beat is take_first_steps; phone not visible and Emily's required read/photo task not demonstrated; movement may exceed allowed micro-beat distance.

58. Frame 51 harness-validation

    harness_retry: micro_target_not_reached; Rendered frame conflicts with the required beat or current state: micro_target_not_reached.

59. Frame 51 harness-validation

    harness_rejected: micro_target_not_reached; Rendered frame conflicts with the required beat or current state: micro_target_not_reached.

60. Frame 51 harness-validation

    hold_previous: micro_target_not_reached - Rendered frame conflicts with the required beat or current state: micro_target_not_reached.

61. Frame 51 harness-validation

    harness_rejected: missing_required_beat, microstep_skipped; The current frame depicts John at the garage/driveway threshold looking at his phone, while the next required micro-movement of the beat is to turn toward the path without changing location. Additionally, backyard visibility is not clearly established in this frame, and the beat sequence appears to be ahead of the documented micro-movement progression. Holding the frame prevents incorrect advancement of world-state until the required data (e.g., backyard view, path orientation) is satisfied.

62. Frame 51 harness-validation

    hold_previous: missing_required_beat, microstep_skipped - The current frame depicts John at the garage/driveway threshold looking at his phone, while the next required micro-movement of the beat is to turn toward the path without changing location. Additionally, backyard visibility is not clearly established in this frame, and the beat sequence appears to be ahead of the documented micro-movement progression. Holding the frame prevents incorrect advancement of world-state until the required data (e.g., backyard view, path orientation) is satisfied.

63. Frame 51 harness-validation

    harness_retry: none; The current frame shows John at the driveway threshold holding/looking at his phone, not performing the required micro-beat turn_toward_path. The expected micro-movement to turn toward the next path is not evidenced; next frame should show a visible turn or movement toward the backyard for the backyard photo as per the beat plan.

64. Frame 54 harness-validation

    harness_retry: micro_target_not_reached; Rendered frame conflicts with the required beat or current state: micro_target_not_reached.

65. Frame 54 harness-validation

    harness_rejected: micro_target_not_reached; Rendered frame conflicts with the required beat or current state: micro_target_not_reached.

66. Frame 54 harness-validation

    hold_previous: micro_target_not_reached - Rendered frame conflicts with the required beat or current state: micro_target_not_reached.

67. Frame 64 harness-validation

    harness_retry: micro_target_not_reached; Rendered frame conflicts with the required beat or current state: micro_target_not_reached.

68. Frame 64 harness-validation

    harness_rejected: micro_target_not_reached; Rendered frame conflicts with the required beat or current state: micro_target_not_reached.

69. Frame 64 harness-validation

    hold_previous: micro_target_not_reached - Rendered frame conflicts with the required beat or current state: micro_target_not_reached.

70. Frame 69 harness-validation

    harness_retry: off_phase_visual, missing_required_beat; Observed frame shows an unlocked phone displaying a yard photo share interface with Linda's notification while the current beat expects a locked phone with Linda's unread text not yet opened. The required beat (open Linda's text) is not visibly satisfied; this frame cannot advance the intended macro action. Needs repair: read Linda's message and return to expected state, or adjust to match the current beat's observable state.

71. Frame 69 harness-validation

    harness_rejected: off_phase_visual, missing_required_beat; Current frame shows Linda's message reading not visible; instead, the phone shows a photo-sharing UI for Emily, which does not align with the required beat of reading Linda's unread text and replying. This indicates the frame may not advance to the next required state. A repair is needed to render a frame where Linda's message is visible and the user is about to respond, without showing delivery status. Retry budget exhausted; holding prior accepted state.

72. Frame 69 harness-validation

    hold_previous: off_phase_visual, missing_required_beat - Current frame shows Linda's message reading not visible; instead, the phone shows a photo-sharing UI for Emily, which does not align with the required beat of reading Linda's unread text and replying. This indicates the frame may not advance to the next required state. A repair is needed to render a frame where Linda's message is visible and the user is about to respond, without showing delivery status. Retry budget exhausted; holding prior accepted state.

73. Frame 69 harness-validation

    harness_retry: off_phase_visual, missing_required_beat; Continuity issues detected: the frame shows the phone as unlocked while the contract’s frame expects a locked phone; the active thread is Linda Carter whereas the task contract refers to Linda's message read state and Emily-thread context; no read action is evidenced yet. The micro-beat progression (steady phone for reply) has not clearly completed as required by the current beat.

74. Frame 69 harness-validation

    harness_rejected: missing_required_beat; Linda's unread message is visible and the contract requires that the incoming text be opened/viewed so it is visibly read. The frame shows the message is still unread, and no reply has been sent, so the required beat has not yet been completed. Retry budget exhausted; holding prior accepted state.

75. Frame 69 harness-validation

    hold_previous: missing_required_beat - Linda's unread message is visible and the contract requires that the incoming text be opened/viewed so it is visibly read. The frame shows the message is still unread, and no reply has been sent, so the required beat has not yet been completed. Retry budget exhausted; holding prior accepted state.

76. Frame 73 harness-validation

    harness_retry: macro_overcompleted, frame_advance_overrun; The frame shows a delivered outbound backyard photo appearing in Linda's thread, which conflicts with the planned micro-beat to send the backyard photo to Emily. This suggests the macro action completed in a frame where completesMacroAction is true, or that the evidence progressed beyond the allowed micro-beat. The frame also lacks a visible confirmation that a yes/no reply to Linda has been sent, indicating the next required beat (reply to Linda) is not fulfilled.

77. Frame 73 harness-validation

    harness_rejected: off_phase_visual, missing_required_beat, frame_advance_overrun, phone_overcompleted; The current frame shows Emily thread with a delivered backyard photo, which does not align with the planned action to read Linda's unread message and respond about Sunday dinner. The required Linda thread/read step is not visible, causing a mismatch in phase progression. The frame also displays delivered/outbound photo evidence that the spec prohibits in this beat. Retry budget exhausted; holding prior accepted state.

78. Frame 73 harness-validation

    hold_previous: off_phase_visual, missing_required_beat, frame_advance_overrun, phone_overcompleted - The current frame shows Emily thread with a delivered backyard photo, which does not align with the planned action to read Linda's unread message and respond about Sunday dinner. The required Linda thread/read step is not visible, causing a mismatch in phase progression. The frame also displays delivered/outbound photo evidence that the spec prohibits in this beat. Retry budget exhausted; holding prior accepted state.

79. Frame 73 harness-validation

    harness_retry: missing_required_beat, frame_advance_overrun; Continuity issues detected: phone state marked as locked in input but visible frame shows unlocked; garage door status inconsistent with description; current micro-movement beat is to steady the phone before sending, but the macro action (reading the message and replying) has not completed. Frame evidence does not clearly advance the expected beat, so a repair/retry is warranted before advancing.

80. Frame 73 harness-validation

    harness_rejected: off_phase_visual, missing_required_beat; Continuity issues noted: frame shows unlocked phone and open Linda thread contradicting the expected locked phone state; the frame does not clearly capture reading Linda's message or a completed read step as per the beat plan. Retry budget exhausted; holding prior accepted state.

81. Frame 73 harness-validation

    hold_previous: off_phase_visual, missing_required_beat - Continuity issues noted: frame shows unlocked phone and open Linda thread contradicting the expected locked phone state; the frame does not clearly capture reading Linda's message or a completed read step as per the beat plan. Retry budget exhausted; holding prior accepted state.

82. Frame 78 harness-validation

    harness_retry: macro_overcompleted; Rendered frame conflicts with the required beat or current state: macro_overcompleted.

83. Frame 78 harness-validation

    harness_rejected: macro_overcompleted; Rendered frame conflicts with the required beat or current state: macro_overcompleted.

84. Frame 78 harness-validation

    hold_previous: macro_overcompleted - Rendered frame conflicts with the required beat or current state: macro_overcompleted.

85. Frame 78 harness-validation

    harness_retry: macro_overcompleted; Rendered frame conflicts with the required beat or current state: macro_overcompleted.

86. Frame 78 harness-validation

    harness_rejected: macro_overcompleted; Rendered frame conflicts with the required beat or current state: macro_overcompleted.

87. Frame 78 harness-validation

    hold_previous: macro_overcompleted - Rendered frame conflicts with the required beat or current state: macro_overcompleted.

88. Frame 78 harness-validation

    harness_retry: macro_overcompleted; Rendered frame conflicts with the required beat or current state: macro_overcompleted.

89. Frame 78 harness-validation

    harness_rejected: macro_overcompleted; Rendered frame conflicts with the required beat or current state: macro_overcompleted.

90. Frame 78 harness-validation

    hold_previous: macro_overcompleted - Rendered frame conflicts with the required beat or current state: macro_overcompleted.

91. Frame 78 harness-validation

    harness_retry: macro_overcompleted; Rendered frame conflicts with the required beat or current state: macro_overcompleted.

92. Frame 78 harness-validation

    harness_rejected: macro_overcompleted; Rendered frame conflicts with the required beat or current state: macro_overcompleted.

93. Frame 78 harness-validation

    hold_previous: macro_overcompleted - Rendered frame conflicts with the required beat or current state: macro_overcompleted.

Spatial

1. Frame 5 spatial

   Expected pose described John from behind mid-step toward the interior door, but this frame is first-person with only hands/forearms visible.

2. Frame 14 spatial

   Raised/open garage door is not visible in this crop, so its open state cannot be confirmed.

3. Frame 15 spatial

   The raised/open garage door is expected but not visible in this framing, likely because the camera faces toward the interior door.

4. Frame 16 spatial

   Interior door was expected closed, but it is now visibly open with the hallway exposed; this may be a recent state change but the actual opening action is not shown in this frame.

5. Frame 17 spatial

   Camera/framing has shifted to a close hand-level view rather than the expected third-person rear view of John walking through the doorway.

6. Frame 18 spatial

   The open interior doorway/hallway transition is not visible, though the switch may be near that doorway.

7. Frame 19 spatial

   Expected a third-person rear view of John walking through the open interior doorway, but this frame shows only his hand/arm in a close view pressing a light switch.

8. Frame 20 spatial

   Expected actor pose indicated John was walking through the open interior doorway toward the hallway, but in this frame the interior door appears closed and John is oriented toward the open garage door/outside.

9. Frame 20 spatial

   Expected object state listed the interior door as open in recent nearby objects, but the visible white interior door appears closed.

10. Frame 20 spatial

    Expected actor pose described John walking through an open interior doorway, but this frame shows him approaching a closed white interior door and not yet passing through it.

11. Frame 20 spatial

    Expected state says John is walking through an open interior doorway into the hallway, but the frame shows him still inside the garage facing a closed white interior door.

12. Frame 21 spatial

    Interior door is still closed; John has not yet transitioned into the hallway.

13. Frame 22 spatial

    Interior hallway door was expected closed, but it is visibly open in this frame.

14. Frame 22 spatial

    John was expected to be walking toward the closed interior door; he now appears to be at/through an open doorway, indicating the door has been opened between frames or a continuity mismatch.

15. Frame 23 spatial

    The interior door to the hallway is not visible in this frame.

16. Frame 23 spatial

    Expected state describes John mid-step at an open interior doorway, but the frame shows him paused in the garage facing a closed interior door.

17. Frame 25 spatial

    The interior door expected to be closed is now visibly open, suggesting John has just opened it or a door-state change occurred between frames.

18. Frame 26 spatial

    Expected state says John is stepping through an open interior doorway, but the frame shows the white interior door closed and John still walking toward it from inside the garage.

19. Frame 26 spatial

    Expected state says John is walking through an open interior doorway with one foot lifted, but the frame shows the white interior door closed and John standing in front of it.

20. Frame 27 spatial

    The interior door is visibly closed in this frame, which conflicts with the prior summary that John had begun entering through an open interior doorway.

21. Frame 27 spatial

    John appears to be stepping toward or pausing at the closed door rather than already through the threshold.

22. Frame 28 spatial

    Interior door state appears open in this frame, while the expected actor state described John near a closed interior door; this is consistent with him having opened it or reached an already open doorway, but the visual state is now open.

23. Frame 29 spatial

    The visible interior door is closed in this frame, while the expected actor pose referenced John facing an open doorway/hallway; this frame supports the door being closed at the moment.

24. Frame 30 spatial

    Expected raised/open garage door is not visible in this close framing, but the view remains anchored inside the garage.

25. Frame 31 spatial

    The interior door is now visibly open whereas the expected state described it as closed; this appears to be a natural continuation of John entering the house rather than an identity/location error.

26. Frame 32 spatial

    Expected state says John is mid-step through an open interior doorway into the hallway, but the frame shows the white interior door closed and John still in the garage approaching it.

27. Frame 32 spatial

    Interior door is visibly closed in this frame, while the expected state says John is mid-step through an open interior doorway into the hallway.

28. Frame 32 spatial

    John has not crossed the threshold here; he appears to be standing in the garage facing the closed door.

29. Frame 33 spatial

    The interior door appears closed in this frame; this matches the current expected state, though it differs from the prior summary that described John stepping through an open doorway.

30. Frame 34 spatial

    Interior door was previously expected to be closed; in this frame it is visibly open and John is stepping through it, indicating a state change since the prior frame.

31. Frame 35 spatial

    The interior door to the hallway is not visible in this frame, so its current open/closed state cannot be confirmed.

32. Frame 35 spatial

    Expected actor state described John stepping through an open doorway into the hallway, but the visible frame shows the interior door closed and John still standing in the garage in front of it.

33. Frame 36 spatial

    John's pose is slightly more mid-step than the expected feet-planted stance, but remains consistent with a small preparatory movement near the same closed interior door.

34. Frame 37 spatial

    The interior door was expected to be closed, but in this frame it is open with the hallway visible, indicating a state change or continuity mismatch.

35. Frame 38 spatial

    The visible interior door is closed, while the expected actor state mentions John being angled into an open doorway/threshold; in this frame he appears to be approaching or pausing before the closed door instead.

36. Frame 40 spatial

    The interior door was expected to be closed, but it is visibly open in this frame; this may be a state change from John opening it between frames.

37. Frame 41 spatial

    The interior door to the house/hallway is not visible in this frame, so its open/closed state cannot be confirmed.

38. Frame 44 spatial

    John is still in the garage rather than visibly outside/backyard; connected outdoor area is visible only through the open garage door.

39. Frame 72 spatial

    Expected location mentions an open garage, but the visible garage door appears closed.

40. Frame 73 spatial

    Expected context described the garage as open, but the visible garage door appears closed.

41. Frame 73 spatial

    The garage door appears closed in this frame, while the expected location description mentions an open garage.

42. Frame 74 spatial

    Location description mentions an open garage, but the visible garage door appears closed in this frame.

Focus Insert

1. Frame 5 focus-insert

   focus_insert: 1/3 for phone; world clock did not advance.

2. Frame 5 focus-insert

   Focus Insert 1/3: phone; world clock did not advance.

3. Frame 6 focus-insert

   focus_insert: 2/3 for phone; world clock did not advance.

4. Frame 6 focus-insert

   Focus Insert 2/3: phone; world clock did not advance.

5. Frame 7 focus-insert

   focus_insert: 3/3 for phone; world clock did not advance.

6. Frame 7 focus-insert

   Focus Insert 3/3: phone; world clock did not advance.

7. Frame 12 focus-insert

   focus_insert: 1/3 for tool; world clock did not advance.

8. Frame 12 focus-insert

   Focus Insert 1/3: tool; world clock did not advance.

9. Frame 13 focus-insert

   focus_insert: 2/3 for tool; world clock did not advance.

10. Frame 13 focus-insert

    Focus Insert 2/3: tool; world clock did not advance.

11. Frame 14 focus-insert

    focus_insert: 3/3 for tool; world clock did not advance.

12. Frame 14 focus-insert

    Focus Insert 3/3: tool; world clock did not advance.

13. Frame 17 focus-insert

    focus_insert: 1/3 for light_switch; world clock did not advance.

14. Frame 17 focus-insert

    Focus Insert 1/3: light_switch; world clock did not advance.

15. Frame 18 focus-insert

    focus_insert: 2/3 for light_switch; world clock did not advance.

16. Frame 18 focus-insert

    Focus Insert 2/3: light_switch; world clock did not advance.

17. Frame 19 focus-insert

    focus_insert: 3/3 for light_switch; world clock did not advance.

18. Frame 19 focus-insert

    Focus Insert 3/3: light_switch; world clock did not advance.

19. Frame 61 focus-insert

    focus_insert: 1/3 for shoes; world clock did not advance.

20. Frame 61 focus-insert

    Focus Insert 1/3: shoes; world clock did not advance.

21. Frame 62 focus-insert

    focus_insert: 2/3 for shoes; world clock did not advance.

22. Frame 62 focus-insert

    Focus Insert 2/3: shoes; world clock did not advance.

23. Frame 63 focus-insert

    focus_insert: 3/3 for shoes; world clock did not advance.

24. Frame 63 focus-insert

    Focus Insert 3/3: shoes; world clock did not advance.

25. Frame 66 focus-insert

    focus_insert: 1/3 for object; world clock did not advance.

26. Frame 66 focus-insert

    Focus Insert 1/3: object; world clock did not advance.

27. Frame 67 focus-insert

    focus_insert: 2/3 for object; world clock did not advance.

28. Frame 67 focus-insert

    Focus Insert 2/3: object; world clock did not advance.

29. Frame 68 focus-insert

    focus_insert: 3/3 for object; world clock did not advance.

30. Frame 68 focus-insert

    Focus Insert 3/3: object; world clock did not advance.

31. Frame 70 focus-insert

    focus_insert: 1/3 for phone; world clock did not advance.

32. Frame 70 focus-insert

    Focus Insert 1/3: phone; world clock did not advance.

33. Frame 71 focus-insert

    focus_insert: 2/3 for phone; world clock did not advance.

34. Frame 71 focus-insert

    Focus Insert 2/3: phone; world clock did not advance.

35. Frame 72 focus-insert

    focus_insert: 3/3 for phone; world clock did not advance.

36. Frame 72 focus-insert

    Focus Insert 3/3: phone; world clock did not advance.

37. Frame 75 focus-insert

    focus_insert: 1/3 for phone; world clock did not advance.

38. Frame 75 focus-insert

    Focus Insert 1/3: phone; world clock did not advance.

39. Frame 76 focus-insert

    focus_insert: 2/3 for phone; world clock did not advance.

40. Frame 76 focus-insert

    Focus Insert 2/3: phone; world clock did not advance.

41. Frame 77 focus-insert

    focus_insert: 3/3 for phone; world clock did not advance.

42. Frame 77 focus-insert

    Focus Insert 3/3: phone; world clock did not advance.

Skipped

1. Frame 8 skipped

   Harness rejected rendered frame: macro_overcompleted

2. Frame 20 skipped

   Harness rejected rendered frame: micro_target_not_reached

3. Frame 20 skipped

   Harness rejected rendered frame: off_phase_visual

4. Frame 20 skipped

   Harness rejected rendered frame: missing_required_beat, microstep_skipped

5. Frame 20 skipped

   Harness rejected rendered frame: missing_required_beat, frame_advance_overrun, microstep_skipped

6. Frame 23 skipped

   Harness rejected rendered frame: micro_target_not_reached

7. Frame 26 skipped

   Harness rejected rendered frame: micro_target_not_reached

8. Frame 29 skipped

   Harness rejected rendered frame: micro_target_not_reached

9. Frame 32 skipped

   Harness rejected rendered frame: micro_target_not_reached

10. Frame 35 skipped

    Harness rejected rendered frame: micro_target_not_reached

11. Frame 38 skipped

    Harness rejected rendered frame: micro_target_not_reached

12. Frame 41 skipped

    Harness rejected rendered frame: micro_target_not_reached

13. Frame 43 skipped

    Harness rejected rendered frame: none

14. Frame 44 skipped

    Harness rejected rendered frame: micro_target_not_reached

15. Frame 44 skipped

    Harness rejected rendered frame: actor_missing_required_visibility, missing_required_beat

16. Frame 51 skipped

    Harness rejected rendered frame: micro_target_not_reached

17. Frame 51 skipped

    Harness rejected rendered frame: missing_required_beat, microstep_skipped

18. Frame 54 skipped

    Harness rejected rendered frame: micro_target_not_reached

19. Frame 64 skipped

    Harness rejected rendered frame: micro_target_not_reached

20. Frame 69 skipped

    Harness rejected rendered frame: off_phase_visual, missing_required_beat

21. Frame 69 skipped

    Harness rejected rendered frame: missing_required_beat

22. Frame 73 skipped

    Harness rejected rendered frame: off_phase_visual, missing_required_beat, frame_advance_overrun, phone_overcompleted

23. Frame 73 skipped

    Harness rejected rendered frame: off_phase_visual, missing_required_beat

24. Frame 78 skipped

    Harness rejected rendered frame: macro_overcompleted

25. Frame 78 skipped

    Harness rejected rendered frame: macro_overcompleted

26. Frame 78 skipped

    Harness rejected rendered frame: macro_overcompleted

27. Frame 78 skipped

    Harness rejected rendered frame: macro_overcompleted

Harness Invalid

1. Frame 8 harness-invalid

   Frame was rejected by the nano harness and did not advance world state.

2. Frame 20 harness-invalid

   Frame was rejected by the nano harness and did not advance world state.

3. Frame 20 harness-invalid

   Frame was rejected by the nano harness and did not advance world state.

4. Frame 20 harness-invalid

   Frame was rejected by the nano harness and did not advance world state.

5. Frame 20 harness-invalid

   Frame was rejected by the nano harness and did not advance world state.

6. Frame 23 harness-invalid

   Frame was rejected by the nano harness and did not advance world state.

7. Frame 26 harness-invalid

   Frame was rejected by the nano harness and did not advance world state.

8. Frame 29 harness-invalid

   Frame was rejected by the nano harness and did not advance world state.

9. Frame 32 harness-invalid

   Frame was rejected by the nano harness and did not advance world state.

10. Frame 35 harness-invalid

    Frame was rejected by the nano harness and did not advance world state.

11. Frame 38 harness-invalid

    Frame was rejected by the nano harness and did not advance world state.

12. Frame 41 harness-invalid

    Frame was rejected by the nano harness and did not advance world state.

13. Frame 43 harness-invalid

    Frame was rejected by the nano harness and did not advance world state.

14. Frame 44 harness-invalid

    Frame was rejected by the nano harness and did not advance world state.

15. Frame 44 harness-invalid

    Frame was rejected by the nano harness and did not advance world state.

16. Frame 51 harness-invalid

    Frame was rejected by the nano harness and did not advance world state.

17. Frame 51 harness-invalid

    Frame was rejected by the nano harness and did not advance world state.

18. Frame 54 harness-invalid

    Frame was rejected by the nano harness and did not advance world state.

19. Frame 64 harness-invalid

    Frame was rejected by the nano harness and did not advance world state.

20. Frame 69 harness-invalid

    Frame was rejected by the nano harness and did not advance world state.

21. Frame 69 harness-invalid

    Frame was rejected by the nano harness and did not advance world state.

22. Frame 73 harness-invalid

    Frame was rejected by the nano harness and did not advance world state.

23. Frame 73 harness-invalid

    Frame was rejected by the nano harness and did not advance world state.

24. Frame 78 harness-invalid

    Frame was rejected by the nano harness and did not advance world state.

25. Frame 78 harness-invalid

    Frame was rejected by the nano harness and did not advance world state.

26. Frame 78 harness-invalid

    Frame was rejected by the nano harness and did not advance world state.

27. Frame 78 harness-invalid

    Frame was rejected by the nano harness and did not advance world state.

Repair

1. Frame 11 repair

   Decision repaired: John performs the required local beat: move to driveway for backyard view.

2. Frame 15 repair

   Pickup damage status remains unresolved; only a partial side/rear view is visible with no obvious new damage or repair change.

3. Frame 20 repair

   The dark pickup remains only partially visible, so minor damage/repair status cannot be confirmed; no obvious new damage is visible.

4. Frame 20 repair

   Pickup damage status remains unresolved; only a partial side/rear view is visible and no obvious new damage or repair change can be assessed.

5. Frame 20 repair

   Decision repaired: John performs the required local beat: move to driveway for backyard view.

6. Frame 23 repair

   Pickup damage status remains unresolved from this partial rear/side view; no obvious new damage or repair change is visible.

7. Frame 26 repair

   Pickup damage status remains unresolved because only a partial view is visible; no obvious new damage or repair progress is seen.

8. Frame 26 repair

   Decision repaired: John performs the required local beat: move to driveway for backyard view.

9. Frame 27 repair

   Pickup damage status remains unresolved because only a partial side/front view is visible; no obvious new damage or repair change can be assessed.

10. Frame 29 repair

    Pickup damage status remains unresolved because only a partial side/front view is visible; no obvious new damage or repair change is seen.

11. Frame 32 repair

    The dark pickup is only partially visible; no obvious new damage or repair progress is visible, but minor damage status cannot be fully assessed from this angle.

12. Frame 32 repair

    Pickup damage status remains unresolved because only a partial side/front view is visible; no new damage or repair progress can be assessed.

13. Frame 32 repair

    Decision repaired: John performs the required local beat: move to driveway for backyard view.

14. Frame 35 repair

    Pickup damage remains unresolved because only a partial side/front view is visible; no obvious new damage or repair change is apparent.

15. Frame 35 repair

    Decision repaired: John performs the required local beat: move to driveway for backyard view.

16. Frame 36 repair

    Pickup damage status remains unresolved because only a partial side/rear view is visible; no obvious new damage or repair change can be assessed.

17. Frame 41 repair

    Pickup damage remains unresolved: only a partial side/rear view is visible, with no obvious new damage or repair progress assessable.

18. Frame 41 repair

    Pickup damage status remains unresolved because only a partial side view is visible; no obvious new damage or repair progress can be assessed.

19. Frame 44 repair

    Decision repaired: John performs the required local beat: move to driveway for backyard view.

20. Frame 45 repair

    Pickup damage status remains unresolved because only a partial side/front view is visible; no obvious new damage or repair progress is visible.

21. Frame 46 repair

    The pickup is only partially visible; no obvious new damage or repair progress can be assessed, and its damage status remains unresolved.

22. Frame 48 repair

    Decision repaired: John performs the required local beat: move to driveway for backyard view.

23. Frame 49 repair

    Pickup damage status remains unresolved because only a partial side/front view is visible; no obvious new damage or repair progress is assessable.

24. Frame 51 repair

    Decision repaired: John performs the required local beat: move to driveway for backyard view.

25. Frame 51 repair

    The dark pickup remains partially visible on the right with the Z71 badge; no obvious new damage or repair progress is visible, but the partial angle prevents full damage assessment.

26. Frame 54 repair

    Decision repaired: John performs the required local beat: move to driveway for backyard view.

27. Frame 57 repair

    Pickup damage/repair status remains unresolved because only a partial side/front view is visible; no obvious new damage or repair progress is visible.

28. Frame 58 repair

    Decision repaired: John performs the required local beat: move to driveway for backyard view.

29. Frame 64 repair

    Pickup damage/repair status remains unresolved because only a partial side/rear view is visible; no obvious new damage or repair progress is visible.

30. Frame 64 repair

    Pickup damage remains unresolved because only a partial side/front view is visible; no obvious new damage or repair progress can be assessed.

31. Frame 65 repair

    Pickup damage remains unresolved because only a partial side/front view is visible; no obvious new damage or repair progress can be assessed.

32. Frame 69 repair

    Pickup damage remains unresolved: only a partial dusty side/front view is visible, with no clear new damage or repair progress assessable.

33. Frame 73 repair

    Pickup damage remains unresolved: only a partial side/front view is visible, with no obvious new damage or repair progress assessable.

34. Frame 73 repair

    Decision repaired: John holds the phone steady and reads Linda Carter's text aordinary actiong if he is still coming for Sunday dinner.

35. Frame 73 repair

    Decision repaired: John performs the required local beat: send outbound message to emily.

36. Frame 78 repair

    Pickup damage cannot be fully assessed from the partial side/front view; no obvious new damage or repair progress is visible.

Social Identity

1. Frame 20 social-identity

   Pickup damage status remains unresolved because only a partial view is visible; no obvious new damage, repair, or identity drift is visible.

2. Frame 24 social-identity

   No non-John people are visible despite social context listing known characters.

3. Frame 50 social-identity

   No visible non-John people, consistent with expected social presence.

4. Frame 51 social-identity

   No non-John people are visible despite social context references; this is consistent with expectations.

5. Frame 51 social-identity

   No non-John people are visible; Emily is not present in the frame.

6. Frame 52 social-identity

   No visible non-John people or conversation.

7. Frame 52 social-identity

   Pickup damage status remains unresolved because only a partial side/front view is visible; no obvious new damage, repair progress, or identity drift is seen.

8. Frame 53 social-identity

   No non-John people are visible.

9. Frame 55 social-identity

   No visible non-John people despite no expected visitors.

10. Frame 57 social-identity

    No non-John people are visible; no conversation is occurring.

11. Frame 61 social-identity

    Expected rear-view follow framing with tan baseball cap visible, but this frame is a downward first-person/POV-like view showing legs, shoes, and hands only.

12. Frame 64 social-identity

    Tan baseball cap is expected but not visible from this first-person framing.

13. Frame 69 social-identity

    John's tan baseball cap is expected but not visible due the first-person downward framing; this is not necessarily a wardrobe change.