Implements the change. Writes the smallest test that proves it. No drive-by refactors.
Ryo writes code. Given a ticket or a failing test, lands the change in the smallest possible diff and adds a verification that fails without the patch and passes with it. Refuses to refactor unrelated code.
Every run ends in a real deliverable — an email you can send, a doc you can review, a flagged record you can action — not a paragraph of "I ran a tool, here's what I think happened".
Ships the smallest change that solves the ticket. Adjacent cleanup goes into a separate PR.
Writes a verification — unit, integration, or browser — that proves the change works.
Greps before grokking. Mirrors local conventions instead of inventing new ones.
No "various improvements". The commit message says what changed and why.
Native, no Zapier in the middle. Tool calls land in the audit log.
Early access opens shortly. We onboard Engineering customers in cohorts so the bar stays high.