# DEVELOPMENT OWNERSHIP, CONTROL AND BACKUP DIRECTIVE

**Project:** Moore Benefits Group CRM / Agent Operating System
**Intellectual Property Owner:** Tomekia Eugenia Moore
**Effective:** Immediately

## 1. OWNERSHIP INTENT

All original project-specific source code, software architecture, original database schemas, original workflows, original automation designs, written specifications, business logic, original graphics, documentation, prompts, templates, marketing materials, customer-development materials, and other protectable project assets created by or validly assigned to the project are intended to be owned by Tomekia Eugenia Moore, subject to the rights and licenses associated with third-party platforms, open-source software, APIs, libraries, and other third-party materials.

Use of Lovable, OpenAI/ChatGPT, GitHub, Google, GoDaddy, Stripe, or another technology provider does not constitute an intentional transfer of project ownership to that technology provider beyond the rights granted under the applicable provider's terms.

## 2. SOURCE-CODE CONTROL

A current copy of the complete project source code must be maintained in a private Git repository controlled by Tomekia Eugenia Moore.

The source-code repository must not be owned solely by:

* Lovable;
* A developer;
* A contractor;
* An employee;
* A marketing company;
* An outside agency; or
* Any other third party.

Tomekia Eugenia Moore must retain owner-level access to the repository.

## 3. CODE EXPORT

The complete codebase must be exported from the development platform and stored independently.

A code backup should be created:

* After each major development milestone;
* Before significant architecture changes;
* Before changing development providers;
* Before production releases when appropriate; and
* At least monthly while active development continues.

Backups must be dated and retained.

## 4. DATABASE PORTABILITY

The project must maintain documentation sufficient to identify and reconstruct:

* Database structure;
* Tables;
* Relationships;
* Permissions;
* User roles;
* Automation logic;
* Storage architecture;
* Integrations;
* Required environment variables;
* API dependencies; and
* Deployment requirements.

Where technically and legally permitted, database backups must be created and maintained separately from the application-development platform.

## 5. ACCOUNT CONTROL

Mission-critical accounts must be opened under credentials controlled by Tomekia Eugenia Moore or an entity she expressly authorizes.

No developer or contractor may be the sole owner, registrar, administrator, recovery contact, or billing owner of a mission-critical account.

This includes:

* Domains;
* DNS;
* Git repositories;
* Databases;
* Hosting;
* Payment systems;
* Analytics;
* Google integrations;
* Email systems;
* Application stores;
* Cloud infrastructure; and
* Backup systems.

## 6. ACCESS LEVELS

Outside developers and contractors should receive only the minimum permissions required to perform assigned work.

Owner-level access must remain with Tomekia Eugenia Moore.

When a working relationship ends, access must be promptly reviewed and removed where no longer required.

## 7. THIRD-PARTY COMPONENTS

All material third-party software, libraries, APIs, templates, models, fonts, stock assets, code packages, or other external components incorporated into the project must be documented.

The record should identify, where practical:

* Component name;
* Provider;
* License;
* Version;
* Purpose; and
* Applicable restrictions.

No developer may represent third-party intellectual property as exclusively owned project property.

## 8. CONTRACTOR DELIVERABLES

Any contractor or developer creating material project assets must execute an appropriate written agreement addressing confidentiality, ownership, assignment of rights, deliverables, source-code delivery, third-party components, credentials, data security, and termination of access.

## 9. PROPRIETARY INFORMATION

Proprietary project information should not be intentionally used to train third-party artificial-intelligence systems where an available privacy setting or contractual option permits such use to be disabled.

Applicable model-training opt-out controls should be enabled wherever commercially practical.

## 10. CUSTOMER INFORMATION

Customer and agent information must remain logically separated from public project information.

Sensitive information must not be included in:

* Public source repositories;
* Public project pages;
* Analytics events;
* Calendar event titles;
* Public URLs;
* Development prompts;
* Screenshots used for demonstrations; or
* Unsecured testing environments.

Production data should not be copied into development or demonstration environments unless specifically authorized and properly protected.

## 11. BACKUP STANDARD

At least three controlled copies of critical project assets should be maintained:

1. Primary private source repository;
2. Independent encrypted backup under the owner's control; and
3. Additional encrypted disaster-recovery copy.

The ability to restore the software from these backups should be tested periodically.

## 12. DEVELOPMENT RECORD

The project must maintain a development record documenting:

* Major feature decisions;
* Release dates;
* Architecture changes;
* Developer/contractor contributions;
* Third-party dependencies;
* Security changes;
* Database changes;
* Integration changes;
* Major bug fixes; and
* Backup dates.

## 13. PORTABILITY REQUIREMENT

The project should be developed so that, to the extent technically reasonable, Tomekia Eugenia Moore is not dependent upon a single development platform to retain access to her project-specific source code and records.

A competent independent developer should be able to receive the codebase, documentation, authorized database exports, and configuration information and understand how to continue development.

## 14. OWNER APPROVAL

No transfer, sale, assignment, public release of source code, change of repository ownership, permanent deletion, or transfer of control over a mission-critical account may occur without express authorization from Tomekia Eugenia Moore or an authorized legal representative.