AI, your code,
and your IP.

Yours to use, modify, and deploy

The custom work I deliver is contractually assigned to you at handoff. That includes the source code written for your project, infrastructure definitions, architecture diagrams, documentation, and test suites. You can run it, change it, extend it, hand it to another developer, or build your product on it without my involvement or permission.

I bring reusable libraries, utilities, and development tooling to each project. When that tooling is embedded in your system, the project agreement grants you a license broad enough to operate, modify, maintain, and extend the delivered system as your own. The reusable toolkit remains mine. Third-party and open-source components remain under their respective licenses, and I document what your system uses so your team knows what it has inherited.

The project agreement uses contractual assignment because copyright law for AI-assisted work continues to develop. In January 2025, the U.S. Copyright Office concluded that AI-generated content produced without sufficient human creative control is ineligible for copyright protection and that prompts alone do not establish that control. In March 2026, the Supreme Court declined to hear Thaler v. Perlmutter. Courts will continue to define how much human contribution AI-assisted work requires. Contractual assignment defines what you can do with the deliverables as that legal standard develops.

Confidentiality

I treat client code, architecture decisions, credentials, and business context as confidential by default. Client work doesn't get discussed with other clients. I keep credentials in your systems or in a secrets manager under your control, and I keep architectural details to the people working on the project. The binding confidentiality terms are set in the project agreement before any work begins.

What tools I use and for what

The primary AI tool is Claude Code. I use it to accelerate code generation, test scaffolding, refactoring, and documentation. AI output goes through my review before it's committed, and I don't accept AI-generated test suites as a substitute for understanding what they're actually testing.

For clients with compliance requirements or security policies that restrict AI tooling, I can work without it. That option is available from the first conversation.

Judgment and accountability stay with me

I remain responsible for the system design, the code, and the handoff. AI can accelerate specific tasks, while architectural and delivery decisions remain mine. I review the code I ship and stand behind it.

If something in a delivered codebase is wrong, I am accountable for it.