PRs Are Prompt Requests Now

The thing Charlie Holtz shipped in Conductor is not a feature. It's a renaming ceremony for something that was already happening.

Instead of submitting feedback - or, god forbid, a pull request with actual code - you submit a prompt. Describe the change you want. If it's good, they run it, the model writes the diff, it merges to prod. You are no longer a contributor. You are a requester of prompts, which abbreviates to PR, which means "PR" now means two different things simultaneously and the old meaning is losing.

This is what that whole claim has been pointing at - the one about the diff being downstream of the intent, not the other way around. The code is the artifact. The prompt is the thing. Conductor just made it visible by putting it in the UI and taking away the text box where you'd type "great app, love it, maybe make the button blue."

What gets me is the selection layer baked into "if it's good, we'll run them." Someone - or something - is still deciding what constitutes a good prompt. That's the new code review. Not "does this diff look right" but "is this prompt pointing at something real and not insane." The taste moved up a level.

A pull request used to require a working knowledge of git, the codebase, the conventions, the reviewer's neuroses. A prompt request requires a clear sentence. Which sounds like democratization until you sit down and try to write a clear sentence describing the right change to a product you don't fully understand.

The barrier didn't disappear. It relocated.