Provenance Record

Long-form News piece (999 words) with clear structure: Overview / What Was Released / What Did Not Open / Agent-First Contribution Model / Reception and Loose Ends / What We Don't Know. Strong attribution density, every claim has an inline link.

All 8 snapshots fetched at HTTP 200 and grep-verified per-claim. source-0 (warp.dev): confirms April 28 launch, AGPL-3.0, warpui_core/warpui MIT split, Kimi/MiniMax/Qwen, 'auto (open)' routing, founding-sponsor language, Sottiaux quote verbatim, 'agents doing the heavy lifting' phrasing verbatim. source-1 (github.com/warpdotdev/warp): confirms repository description 'an agentic development environment, born out of the terminal', Rust, AGPL, and current star count ~57.8k (article says 'above 57,000' — accurate). source-2 (It's FOSS): confirms warpui MIT/AGPL split, all model names, Zach Lloyd quote verbatim 'Open-sourcing is fundamentally coming from our desire to build a successful business…'. source-3 (Hacker News thread): confirms Lloyd verbatim 'I actually think we can build a better product, more quickly if we build it with our community + agents', the 'I was very surprised to see they chose my favorite free software license — the AGPLv3' verbatim, shimman 'tweaking an Alacritty fork then using that to get a \$50million venture round then giving zero money' verbatim, nixpulvis 'absolutely no hard feelings' verbatim. source-4 (FOSS Force): confirms 'flirting — and not flirting — with making Warp open source for about four years' verbatim, Lloyd 'biggest bottleneck to development is no longer writing code — it's all the human-in-the-loop activities around the code' verbatim, Warp Drive / Oz closed-and-commercial framing. source-5 (Help Net Security): confirms April 30 date, Kimi/MiniMax/Qwen, founding sponsor framing, Oz/OpenAI GPT models. source-6 (byteIOTA): confirms 37,000+ stars, #2 GitHub trending, 700,000+ developers, OpenWarp fork. source-7 (Kilo Blog): confirms BYOK for Anthropic/Google/OpenAI on paid plans, OpenWarp fork — BUT the article puts inside quote marks 'AI features depend on Warp's backend services, preventing fully self-hosted experiences' while Kilo's actual text is 'AI features still depend on Warp's backend services, so even if you build from source, you're not getting a fully self-hosted experience.' This is a paraphrase rendered as a verbatim direct quote — exactly the case the v3.9.0 policy says use APPROVE_WITH_CORRECTIONS for.

Every named entity, statistic, and date traces to a verified snapshot. The only attribution issue is the Kilo Blog 'AI features depend on…' paraphrase rendered as a direct quote. The substance is accurate; only the framing as a verbatim quote is wrong.

Publish with one correction. Strong, well-sourced reporting on a notable open-source/agentic-development story.