IP Assignment in AI Agent Transactions: A State Machine Approach

Traditional IP assignment in service agreements is binary: ownership transfers upon completion and payment. But AI agent transactions have intermediate states. The buyer needs to evaluate deliverables before accepting. The developer needs assurance that unpaid work remains protected. The SAISA solves this by tying IP ownership to escrow state transitions.

The Escrow State Machine (Section 5.4)

IP ownership follows a deterministic state machine. At each state, ownership and license rights are precisely defined:

These transitions are tied to database state changes, not handshakes or PDF signatures. The PostgreSQL commit timestamp determines when ownership transfers.

Evaluation License (Section 5.1)

When a Paper enters DELIVERABLE_STAGED state, the Buyer receives a strictly limited license:

• Non-exclusive - Developer retains all rights
• Non-transferable - Buyer cannot share with third parties
• Read-only - Buyer can review but not use commercially
• Evaluation purposes only - Determining whether to accept

IP Transfer Trigger (Section 5.2)

All right, title, and interest in Agent Deliverables transfers to the Buyer if, and only if, the Paper transitions to FUNDS_RELEASED state. The transfer includes:

• Copyright in all deliverable content
• Compilation and collective work rights
• Database rights where applicable
• The right to modify, adapt, and create derivative works

The transfer excludes Developer Background Technology - pre-existing code, models, prompts, and tools that the Developer brought to the engagement.

Background Technology License (Section 5.5)

Background Technology remains Developer property. Upon FUNDS_RELEASED, the Developer grants the Buyer a limited license to use Background Technology solely as incorporated in the Deliverables. This license is:

• Non-exclusive - Developer can use with other clients
• Non-sublicensable - Buyer cannot grant licenses to third parties
• Limited scope - Only as incorporated in the specific Deliverables

The Destruction Covenant (Section 5.3)

Upon RESOLVED_REFUND, the Buyer must destroy all copies of Agent Deliverables within five (5) business days and provide written certification. This is not optional.

Failure to comply constitutes material breach with liquidated damages equal to one (1) times the Paper's Escrow Balance plus legal fees. The destruction covenant ensures that refunded work returns to the Developer's exclusive control.

Developer IP Protection (Section 5.6)

The Developer's system prompts and proprietary instructions are trade secrets. They are never disclosed to the Buyer under any circumstances, including during Expert Determination disputes. The Dispute Panel reviews deliverables and acceptance criteria but never sees the Developer's implementation details.

AI Provider IP Disclaimer (Section 5.7)

Neither party makes any representation regarding intellectual property rights in outputs generated by AI Providers. Each AI Provider's terms of service govern independently. This is a practical acknowledgment that AI-generated content IP remains legally unsettled in many jurisdictions.