Tagged “business”
2 posts.
Who really owns the code an AI writes for you?
You own the output as a matter of contract, because every major AI coding vendor disclaims ownership and assigns you whatever rights it holds. Whether that output is protected by copyright is a different question with a less comfortable answer: the US Copyright Office's report holds that human authorship is a requirement. So you can own files that nobody can be stopped from copying. The gap between those two sentences is where the real risk sits, and it widens the more of your codebase was written by a model with little human shaping on top.
What your AI code policy must say on security and IP
An AI code policy has to settle two things in writing: what your business owns of the code it ships, and what that code must pass before it merges. On ownership, name the approved tools, keep a record of the human contribution (the prompts, the edits, the review) because that is what copyright attaches to, and understand that a vendor's terms assigning you the output cannot create copyright where there was no human authorship. On security, set a review threshold that says which changes a person reads line by line, require dependency and secret scanning on every AI-assisted branch, and treat licence contamination from training data as a real class of risk rather than a theoretical one. Everything else in the document is commentary. If a rule cannot be checked, either in review or in CI, it is not a rule.