LTL_f monitors for manipulation rollout safety
Task success alone is a weak release gate for household manipulation policies. A deployment evaluation can add LTL_f monitors over rollout traces and report success-and-safe, success-but-unsafe, violation category, and unsafe-state exposure. SafeManip shows why this is needed: on 50 RoboCasa365 tasks, pi_0.5 raised task success from 8.1% to 9.3% over pi_0, while its safety violation rate rose from 69.7% to 82.8%.
A practical first build is a trace logger that records contacts, object poses, gripper state, fixture state, and task events, then binds those signals to task-specific checks such as Collision, StableGrasp, Sanitized, Contained, and FixOpen. Kitchen and home-robot teams would use the output during model selection and regression testing, especially for contamination, release stability, and access-to-fixture tasks where unsafe behavior can occur before the final state looks correct.