Claude should verify technical claims in plans before executing

Summary

Claude blindly executed a plan containing incorrect technical information (buffer-mode=clock for GStreamer rtspsrc), causing multiple failed deployments and ~1 hour of production downtime.

What Happened

1. User asked Claude to execute a pre-made deployment plan
2. The plan contained buffer-mode=clock for GStreamer's rtspsrc element
3. Claude did not verify this property exists before deploying
4. Result: 3 failed deployments, ~1 hour of video recording lost

Timeline

| Attempt | Error | Issue |
|---------|-------|-------|
| 1st | can't be set from string 'clock' | Tried property_from_str("buffer-mode", "clock") |
| 2nd | expected GstRTSPSrcBufferMode, got gint | Tried property("buffer-mode", 5i32) |
| 3rd | ✅ Success | Found real fix: h264timestamper element |

Root Cause

buffer-mode=clock does not exist in GStreamer. Valid values are:

• none (0), slave (1), buffer (2), auto (3), synced (4)

A simple web search before deployment would have revealed this.

Expected Behavior

When executing plans involving unfamiliar APIs or technical claims, Claude should:

1. Verify technical claims - Quick research before executing
2. Be skeptical of plans - Plans can contain errors
3. Research first, deploy second - Especially for production systems

Environment

• Claude Code CLI
• Model: claude-opus-4-5-20251101
• Task: Deploying GStreamer-based video recorder

Suggestion

Consider adding a verification step when plans contain:

• Specific API properties/values
• Configuration that will affect production systems
• Technical claims that can be quickly verified via web search