Awake Background IP and Dependency Schedule
Record actual ownership, exclusions and licenses for contributed materials.
- Entity and jurisdiction fit
- US software companies; state-specific adaptation required
- Binding posture
- Binding when completed and signed
- Variants
- Complete the stated selections
- Before use
- Each party’s own counsel must review and approve the document.
Awake Background IP and Dependency Schedule
Commercial Terms
Parties/main agreement: [names/version]. Schedule date and custodian: [details].
Asset record
Repeat for each item: [description/version; actual owner; contributor chain; preexisting/new work; assignment or license instrument; allowed uses/modifications/sublicenses; restrictions; consent evidence; liens/prior grants; transfer date]. State none where genuinely absent, rather than leaving an ambiguous blank.
Dependencies
[Open-source components/licenses; third-party software; datasets; AI models/tools; generated-material rights limits; disclosure/security restrictions]. Record intended uses against actual rights. No ownership is inferred merely from possession or AI-assisted creation.
Control and gaps
[Company repository/domain/cloud control evidence; handover owner/date; unresolved rights and remedial action]. Never include passwords, API keys or private customer data. Identify prior-business assets separately. This inventory alone is not an assignment or license.
Companion documents
Data-room records: 04-02, 04-04, 04-06. See the mapping.