Employee Center Origin, Authorship, and Development History

No Raw Database Data Claim

For clarity, this document does not claim that Quintin N. Mahan owns raw facts, raw database rows, independent outside source records, CRS-owned operational records, customer-owned records, third-party-owned records, or customer relationships merely because such information is entered into, stored in, processed by, displayed through, backed up with, or exported from EC.

This document protects EC Protected Materials: the application, software, source code, schemas, database design, data model, relationships, indexes, workflows, dashboards, reports, queries, automations, integrations, APIs, access controls, credentials, hardware, infrastructure, legal records, certificate records, hashes, metadata systems, audit systems, methods, processes, techniques, trade secrets, documentation, and EC-created structural organization.

Version: 1.0
Effective Date: June 1, 2026
Platform: Employee Center / EC
Owner / Author: Quintin N. Mahan
Legal Hub: /legal
Policy URL: /legal/origin-authorship-development-history

1. Purpose

This Origin, Authorship, and Development History page documents the origin story, authorship position, development history, repository control, and ownership position for Employee Center (“EC”).

This page is intended to make clear that EC was independently initiated, designed, built, hosted, maintained, and controlled by Quintin N. Mahan before being offered for CRS operational use.

This page is not intended to transfer ownership of EC to CRS. It is intended to preserve the historical record that EC was created by Quintin N. Mahan and that CRS received access to EC as a permitted user/beneficiary of the platform, not as owner of the platform.

2. Short Ownership Statement

Employee Center was self-initiated and self-built by Quintin N. Mahan.

EC was not originally assigned to Quintin N. Mahan by CRS as a company-owned software-development project.

EC was started outside office hours, built by Quintin N. Mahan, privately controlled by Quintin N. Mahan, and maintained through a private self-hosted Git repository controlled by Quintin N. Mahan.

EC was running before Quintin N. Mahan offered CRS the ability to use it.

CRS use of EC does not transfer ownership of EC, EC source code, EC infrastructure, EC database design, EC workflows, EC automations, EC dashboards, EC reports, EC legal records, EC certificates, EC backups, or the EC Protected Materials.

3. Origin of the Project

EC arose out of a practical operational need to access, organize, and use specific data that CRS owned or lawfully used, which had initially existed in Microsoft CRM from Allied.

The original problem was not that CRS lacked ownership of certain outside source records. The original problem was that the data needed to be made usable, accessible, organized, searchable, and operationally practical.

Quintin N. Mahan took it upon himself to create EC as a tool to solve that problem.

4. Initial Data Work

As part of the early EC work, Quintin N. Mahan pulled, merged, structured, organized, and built records to make the data easier to use and simpler to maintain.

This included transforming outside source data into EC-maintained operational records.

The EC version of the data includes EC-created structure, relationships, metadata, organization, workflows, reports, dashboards, audit history, derived records, backups, and operational context.

5. Source Records vs. EC Protected Materials

This page does not claim that every independent outside source record automatically belongs exclusively to Quintin N. Mahan.

Independent source records may exist outside EC.

Examples may include records from:

• Microsoft CRM;
• Allied records;
• Zoho;
• Google Workspace;
• Google Voice;
• paper files;
• accounting systems;
• customer systems;
• payment systems;
• other non-EC source systems.

However, the EC version of records is part of the EC Protected Materials.

The EC Protected Materials includes:

• EC-created records;
• EC-maintained records;
• EC-normalized records;
• EC-merged records;
• EC-enriched records;
• EC-linked records;
• EC-derived records;
• EC metadata;
• EC audit history;
• EC reports;
• EC dashboards;
• EC workflows;
• EC automations;
• EC legal records;
• EC certificate records;
• EC backups;
• EC generated outputs;
• EC operational history.

A lawful right to an outside source record does not create ownership of EC or the EC Protected Materials.

6. Independent Development

Quintin N. Mahan started EC outside office hours and built it himself.

The project was not originally placed into a CRS-owned public repository, CRS-owned GitHub account, CRS-owned source-control system, or CRS-controlled development environment.

The development history is preserved through a private self-hosted Git repository controlled by Quintin N. Mahan.

A substantial majority of pushes, syncs, and development activity occurred outside CRS business hours.

7. Repository Control

The EC Git repository is self-hosted on infrastructure controlled by Quintin N. Mahan.

The repository is not a public GitHub repository.

The repository is not public-facing.

The repository is not hosted by CRS.

The repository is not owned or administered by CRS.

Repository control, server control, backup control, credential control, and development history are maintained by Quintin N. Mahan.

8. EC Was Running Before CRS Use

EC was already running before Quintin N. Mahan offered CRS the ability to use it.

CRS later received use of EC as a permitted operational user/beneficiary.

CRS use of EC does not mean CRS commissioned EC, owns EC, controls EC, may seize EC, may clone EC, may demand source code, may demand credentials, may demand backups, or may transfer EC to a buyer or successor.

9. CRS Operational Benefit Does Not Equal Ownership

CRS may have benefited from EC.

CRS may have used EC for operational workflows.

CRS may have relied on EC for convenience, organization, reporting, access, evidence preservation and authorized transition support, and simplified data use.

That benefit does not transfer ownership.

Operational reliance does not create ownership.

Business value does not create ownership.

Use by CRS employees does not create ownership.

Data entry into EC does not create ownership.

Feature requests do not create ownership.

Testing EC does not create ownership.

Wage payment does not create ownership.

Company need does not create ownership.

10. Conditional Use by CRS

CRS access to EC is conditional.

CRS receives access only as authorized by Quintin N. Mahan and only under the Employee Center Terms and Conditions and applicable EC policies.

CRS does not receive ownership of:

• EC source code;
• EC repositories;
• EC infrastructure;
• EC database schemas;
• EC data model;
• EC reports;
• EC dashboards;
• EC workflows;
• EC automations;
• EC integrations;
• EC legal records;
• EC certificates;
• EC backups;
• EC credentials;
• EC deployment systems;
• EC Protected Materials.

11. No Transfer to Buyer or Successor

EC is not automatically included in any CRS sale, transfer, merger, acquisition, ownership change, asset sale, successor transaction, or buyer transition.

A buyer or successor does not receive EC by buying CRS, buying CRS assets, buying CRS customer relationships, buying CRS goodwill, or hiring CRS employees.

Any buyer or successor requires a separate written license or agreement signed by Quintin N. Mahan.

12. Authorship Evidence

EC authorship, control, and development history may be supported by evidence including:

• Git repository history;
• first commit records;
• branch history;
• commit author records;
• commit timestamps;
• push/sync records;
• self-hosted Git server logs;
• SSH logs;
• system authentication logs;
• repository filesystem metadata;
• deployment history;
• backup history;
• private server records;
• screenshots;
• architecture notes;
• development notes;
• generated hashes;
• archived evidence bundles;
• EC legal records;
• EC policy records;
• EC certificate records.

13. Preservation of Development History

EC development history should be preserved.

The repository history should not be rewritten, squashed, force-pushed, altered, destroyed, or cleaned in a way that damages evidence of authorship, timing, or control.

Where appropriate, EC may preserve:

• full repository mirrors;
• Git bundles;
• commit logs;
• author/committer reports;
• server access logs;
• deployment logs;
• backup manifests;
• SHA-256 hashes;
• evidence packages;
• owner/admin declarations;
• archived snapshots.

14. Relationship to Terms and Policies

This page works together with:

• Employee Center Terms and Conditions;
• Copyright and Proprietary Notice;
• EC Ownership and Protected Materials Policy;
• Source Records vs. EC Protected Materials Policy;
• Conditional License to CRS Policy;
• No Work-Made-for-Hire / Paid-Time Development Policy;
• No Seizure, No Self-Help, and No Lockout Policy;
• Sale, Buyer, Successor, and Change-of-Control Policy;
• Credentials, Infrastructure, and Hosting Ownership Policy;
• Evidence, Certificates, and Legal Artifact Control Policy;
• CRS Operational Dependency Disclaimer;
• Policy Order of Precedence Policy.

If this page conflicts with the Employee Center Terms and Conditions, the Terms and Conditions control unless Quintin N. Mahan signs a separate written agreement stating otherwise.

15. No Waiver

This page does not waive any ownership right, copyright right, trade-secret right, contract right, license right, data-estate right, repository right, infrastructure right, backup right, legal right, or remedy held by Quintin N. Mahan.

This page does not grant CRS any right to seize, copy, clone, transfer, export, migrate, publish, reverse engineer, or control EC.

16. Current Ownership Position

Quintin N. Mahan’s ownership position is:

EC is mine.

CRS may have rights in certain independent outside source records.

The EC software, EC repository, EC structure, EC data model, EC workflows, EC dashboards, EC reports, EC automations, EC integrations, EC legal records, EC certificates, EC audit logs, EC backups, EC generated outputs, and EC Protected Materials are mine to the maximum extent permitted by law.

CRS use of EC is conditional and does not transfer ownership.

CRS cannot take EC away from me, lock me out of EC, force transfer EC, or give EC to a buyer or successor without my signed written agreement.

17. Changes to This Page

Quintin N. Mahan may update this Origin, Authorship, and Development History page by publishing a new active version in EC.

The current active version will be displayed through the Legal hub.

Older versions may remain stored in Postgres for audit, evidence, ownership history, legal history, and historical review.

18. Contact / Owner

Employee Center is owned by Quintin N. Mahan.

Legal and policy documents are available from:

/legal

The current Terms and Conditions are available from:

/legal/terms-and-conditions

The full policy library may be available from:

/legal/policies

End of Employee Center Origin, Authorship, and Development History.