⚖️ Legal/IP Debt

Legal/IP Debt: Risks arising from code that cannot be copyrighted, patented, or legally protected because it lacks sufficient human authorship. It also includes "GPL contamination" and other licensing violations caused by AI training data.

Characteristics

  • Core IP is 100% AI-generated and effectively in the public domain.
  • Competitors can legally scrape and reproduce your product's logic.
  • Code contains patterns or snippets from incompatible open-source licenses (GPL).
  • Breach of contract with clients who expect "human-authored" work.
  • Inability to file patents for AI-generated technical inventions.

The Legal Standard

Under current US Copyright Office and EU AI Act frameworks, AI-only output is not copyrightable. To own your code, you must demonstrate "substantial human creative contribution." Vibe Coding (blindly accepting AI output) fails this standard.

Examples

1. The "Disposable" MVP Trap

A founder builds their entire product logic using a single prompt. Three years later, they cannot sell the company because the technical due diligence reveals they don't own their own code.

2. GPL Contamination

AI assistant, trained on open-source code, suggests a pattern that is characteristic of a GPL-licensed library. Merging this into a proprietary project creates a "viral" license risk.

3. Patent Impossibility

The core innovation of a startup is a new compression algorithm generated by an AI agent. The startup cannot file for a patent because there is no human inventor.

Severity Levels

| Level | Impact | Legal Risk | |-------|--------|------------| | 🔴 Critical | Product is unownable; competitors clone it. | Litigation / Market Exit | | 🟠 High | Fails Due Diligence; valuation slashed. | Series A Failure | | 🟡 Medium | Compliance gaps; remediation needed. | Contractual Penalties | | 🟢 Low | Minor documentation issues. | Low |

Remediation Strategies

  1. Human-Led Design: Document the architectural decisions before prompting to prove human authorship.
  2. IP Segregation: Clearly separate AI "scaffolding" (non-core) from human "Core IP" logic.
  3. License Audits: Use forensic tools to scan for license contamination.
  4. Contractual Transparency: Explicitly define AI usage in client and employee agreements.

Related Vibe-Code Smells

Book Reference

Legal and IP risks are explored in:

  • Primary: Chapter 11: Can You Patent This?
  • Audit: Chapter 10: The Audit.
  • Appendix A: Full debt catalog.

Build an asset, not a liability

Get Clean Vibe Code