The practice
I work across research tooling, agent systems, and interface design. The common job is turning a messy source, unreliable workflow, or drifting product surface into a finished artifact with a boundary someone can inspect.
The work is async by default. Writing carries the scope, decisions, evidence, and handoff. A call can help when it removes ambiguity, but it is not the product.
The method
Before I start, we write down the finish line and what is out of scope. A successful first run is not enough to ship. I run the agreed checks, leave the limits visible, and send the manual with the files.
Done is a verification event, not a feeling.
How AI is used
AI helps me collect source material, get a draft moving, generate code, run tests, and format deliverables. I still resolve source conflicts, decide what access is warranted, review security, and make the final call on quality.
I do not sell detector evasion or unreviewed output. A model can suggest; I am accountable for where the work stops and whether it is ready.
Seller identity
Wild Manual is the independent practice and brand of Kiren Srinivasan. Payment documents name the legal seller shown in the written scope and invoice.
A written scope, invoice, or marketplace agreement controls the project-specific seller, price, payment schedule, start condition, and deliverables.