> For the complete documentation index, see [llms.txt](https://admin-services.docs.intersectmbo.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://admin-services.docs.intersectmbo.org/procurement/statement-of-work-sow-ip-ownership-election-scenario-a.md).

# Statement of Work (SoW) - IP Ownership Election (Scenario A)

**1. IP Ownership Election**

For the purposes of clause 8.2 of the Master Services Agreement, the Parties elect Scenario A (Customer Ownership Regime) under clause 8.3 as the applicable IP Ownership Election for this Statement of Work accordingly:

(a) all Foreground IP created under this Statement of Work shall vest in and be owned by the Customer (Cardano Development Holdings) automatically upon creation, and the Supplier assigns such Foreground IP to the Customer in accordance with clause 8.3(i);

(b) the Supplier shall, at the Customer’s request, execute such further documents and take such steps as are reasonably required to perfect, record or enforce that assignment in accordance with clause 8.3(ii); and

(c) the only Background IP licensed to the Customer under clause 8.3(iii) is the Background IP listed in the Background IP Schedule below. Any Background IP not so listed shall, in accordance with clause 8.2, be treated as Foreground IP and owned by the Customer.

**2. Background IP Schedule**

The following Background IP of the Supplier is identified and scheduled for the purposes of clause 8.2 of the Master Services Agreement. The Supplier grants the Customer a perpetual, irrevocable, worldwide, fully paid-up, non-exclusive, royalty-free licence to use, reproduce, modify, distribute and sub-licence the Background IP listed below to the extent incorporated in or necessary for the use of the Deliverables (clause 8.3(iii)).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://admin-services.docs.intersectmbo.org/procurement/statement-of-work-sow-ip-ownership-election-scenario-a.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
