Submission declined on 10 April 2026 by Flexagoon (talk). This draft's references do not show that the subject meets Wikipedia's criteria for inclusion for organizations and companies. The draft requires multiple published secondary sources that: provide significant coverage: discuss the subject in detail, excluding routine coverage like product launches, staff appointments, or financial reports and listings in databases or listicles; are reliable: from reputable outlets with editorial oversight; are independent: not connected to the subject, such as press releases, the subject's own website, or sponsored content. Please add references that meet all three of these criteria. If none exist, the subject is not yet suitable for Wikipedia. If you would like to continue working on the submission, click on the "Edit" tab at the top of the window. If you have not resolved the issues listed above, your draft will be declined again and potentially deleted. If you need extra help, please ask us a question at the AfC Help Desk or get live help from experienced editors. Please do not remove reviewer comments or this notice until the submission is accepted. Where to get help If you need help editing or submitting your draft, please ask us a question at the AfC Help Desk or get live help from experienced editors. These venues are only for help with editing and the submission process, not to get reviews. If you need feedback on your draft, or if the review is taking a lot of time, you can try asking for help on the talk page of a relevant WikiProject. Some WikiProjects are more active than others so a speedy reply is not guaranteed. How to improve a draft Wikipedia:Contributing to Wikipedia – a basic overview on how to edit Wikipedia. Help:Wikitext – how to use the markup Help:Referencing for beginners – how to include references Wikipedia:Article development – how to develop your article Wikipedia:Writing better articles – how to improve your article Wikipedia:Verifiability – make sure your article includes reliable third-party sources You can also browse Wikipedia:Featured articles and Wikipedia:Good articles to find examples of Wikipedia's best writing on topics similar to your proposed article. Improving your odds of a speedy review To improve your odds of a faster review, tag your draft with relevant WikiProject tags using the button below. This will let reviewers know a new draft has been submitted in their area of interest. For instance, if you wrote about a female astronomer, you would want to add the Biography, Astronomy, and Women scientists tags. Add tags to your draft Editor resources Easy tools: Citation bot (help) | Advanced: Fix bare URLs Declined by Flexagoon 4 months ago. Last edited by OpalYosutebito 2 months ago. Reviewer: Inform author. Resubmit Please note that if the issues are not fixed, the draft will be declined again.

• Comment: Three of the sources are WP:CORPTRIV funding announcements, the fourth is an interview (non independent) 🍅 fx (talk) 14:41, 10 April 2026 (UTC)

Reflection AI is an American artificial intelligence company founded in 2024 by former Google DeepMind researchers Misha Laskin and Ioannis Antonoglou. The company develops AI systems designed to automate and assist with software development and programming tasks.^[1][2]

Reflection AI was founded in 2024 by Misha Laskin and Ioannis Antonoglou, both former researchers at DeepMind.^[2][3] Antonoglou had previously worked on AlphaGo, the DeepMind program that defeated a professional Go champion in 2016.^[3]

The company focuses on using machine learning to automate parts of the software engineering process, including writing and maintaining code.^[1][4]

Reflection AI develops AI systems intended to function as autonomous coding agents that can understand software projects and assist engineers in writing or modifying code.^[3][4] The company's research focuses on combining machine learning, reinforcement learning, and large language models to automate software development tasks.^[3]

One system developed by the company, called Asimov, was designed to analyze not only source code but also documentation and internal communications to better understand how software systems are built and maintained.^[3]