# Client Ownership Framework

## Purpose

The Client Ownership Framework establishes a clear separation between client-owned business assets and JLT-Lane-owned platform assets.

The goal is to eliminate ambiguity regarding operational responsibilities and intellectual property rights.

---

## Client-Owned Assets

Clients retain ownership of:

* Company identity
* Brand assets
* Logos
* Content
* Customer information
* Business records
* Payment accounts
* Email accounts
* Marketing materials

---

## JLT-Lane-owned Assets

JLT-Lane Blueprint Studio retains ownership of:

* Platform architecture
* Blueprint definitions
* Registry models
* Provisioning frameworks
* Deployment automation
* Operational governance models
* Engineering Mesh assets
* Platform manifests
* Source code

---

## Administrative Access

Clients may receive access to:

* Website administration interfaces
* Email administration portals
* Payment processor dashboards
* Reporting interfaces

Administrative access does not imply ownership of platform infrastructure.

---

## Infrastructure Ownership

Infrastructure may be operated by JLT-Lane on behalf of clients.

Infrastructure components may include:

* Hosting platforms
* Deployment systems
* Monitoring systems
* Security controls
* Automation systems

Infrastructure administration remains the responsibility of JLT-Lane unless otherwise agreed.

---

## Source Code Access

Source code access is not included as part of standard platform delivery.

Source code licensing or transfer requires a separate written agreement.

---

## Operational Responsibility

Clients are responsible for:

* Business operations
* Content management
* Customer interactions
* Regulatory compliance
* Business decisions

JLT-Lane is responsible for:

* Platform operation
* Technical maintenance
* Platform governance
* Technical support within agreed scope