Recognition
Featured at the Anthropic Built with Opus showcase, San Francisco.
Submission
The Anthropic Built with Opus hackathon ran in February 2026. We submitted CCX: the dual-process runtime that sits between the model and the work, runs the per-mission RPTIV loop, and gates output through the 8-point acceptance check. At submission time the runtime was already powering one production deployment. The case for the work was that the runtime was the thing making the deployment ship, not the model on its own.
Result
Over 100,000 applications entered the program. The shortlist took it to 500 entries. The final placement was 4th overall. The work was featured at the Claude Code 1st Birthday event in San Francisco, demoed alongside the engineering teams behind the model itself.
The placement matters less than the audience. The room was the team that builds the substrate we work above.
Being demonstrated as a credible piece of work in that room is not a marketing number. It is operational signal. The runtime was reviewed by the people most qualified to find its failure modes. The failure modes they surfaced went into the v2 work that landed in March.
What changed
The first v2 shipping milestone landed 2026·03·04. Manager, Worker, and Hub as three operational layers. The feedback gathered at the SF showcase directly informed the Hub-layer scope and the cross-instance coordination work that became Grove.
What did not change
The lab's positioning did not change after the placement. The work continued at the same cadence. The inbound surface stayed inbound-only. The priority order (research, deployments, releases, writing) did not shift in response to the result.
The discipline matters because the alternative is to chase the next hackathon as a function of placing in this one. We did not, and have not. The next submission, Built with 4.7 applied in April, is a different scope with a different release behind it, judged on its own merits.
Standing reference
The SF recognition is the canonical proof point for the runtime's external review. It sits alongside the operational record (five instances running, two products published, one client deployment in continuous production) as evidence that the work survives external scrutiny, not just internal review.
The runtime is documented on its own page and ships as MoujahidAnas/CCX on GitHub under Apache 2.0.
Contact
If something on this page is relevant to work you are running, write to us. The form is on the landing page. We come back within two working days.
Book a discovery call →