product

Same Process

Pillar ③ · The new PR is intent + chat, not just diff.

What’s wrong with the current PR

Code review today is a re-derivation problem. The reviewer reads the diff and tries to figure out why. They look at the description (often two lines), they look at the linked ticket (often vague), they go back to the diff. They form a mental model of the author’s intent from the artifact left behind.

This worked when the artifact was the only record. It doesn’t work when there’s a richer record available.

What a Vibe PR contains

When a Thread produces a change worth shipping, the PR that opens contains:

  1. The diff (as today).
  2. The intent — the prompt or set of prompts that initiated the Thread.
  3. The conversation — the back-and-forth that shaped the result.
  4. The Thread recap — a summary the agent itself produces, of what it did and why.

Reviewers see all four. The mental-model-reconstruction step is mostly gone.

Git and Perforce, both

Manifoldone does not invent a new VCS. The diff lands in Git or Perforce, depending on what the project uses. The Vibe PR is layered on top — it lives in Manifoldone, references the underlying commit, and degrades gracefully (a developer who only looks at the Git PR sees a clean commit message that reads “what” + “why”).

What this pillar enables that wasn’t possible before

  • Replay a PR. Re-run the Thread that produced the change against a different branch.
  • Fork an intent. Take someone’s prompt, modify it, and run it on your Node.
  • Audit a decision. When a critical change goes wrong months later, the reasoning is recoverable.