Verify before you publish - and say you do

The correctness bar is a stated responsibility, so a 90-day plan that includes "I'll verify claims by reading the SDK source before I publish them" signals fit directly. Concretely: before writing that a CLI flag behaves a certain way, you run it and read the code path, rather than copying what an older doc or a model said. That habit is the difference between teaching a developer correctly and teaching them a bug.

When asked about the first 90 days, give the sequence with a concrete first artifact named. "Week one I'd live in the full surface and build something small with each piece. By week three I'd ship a reference automation - say, an agent that triages my own GitHub issues - plus the write-up and use the response to start a feedback loop back to Product." Specificity reads as someone who's already started.