Reorganize CLA files into CLA/version_1 directory

- Move CLA.md to CLA/version_1/CLA.md
- Move .github/CLA_SIGNATORIES.md to CLA/version_1/CLA_SIGNATORIES.md
- Update all references in:
  - .github/workflows/cla.yml
  - .github/CLA_SETUP.md
  - README.md
  - CONTRIBUTING.md
  - CLA.md (self-references)
  - CLA_SIGNATORIES.md (relative links)

Author: claude

.github/CLA_SETUP.md

@@ -6,7 +6,7 @@ This document explains how to set up the CLA Assistant GitHub Action to automati
 
 The CLA Assistant GitHub Action (`.github/workflows/cla.yml`) automatically:
 - Comments on new pull requests asking contributors to sign the CLA
-- Tracks who has signed the CLA in `.github/CLA_SIGNATORIES.json`
+- Tracks who has signed the CLA in `CLA/version_1/CLA_SIGNATORIES.md`
 - Updates PR status checks based on CLA signature status
 - Allows contributors to sign by commenting on their PR
 
@@ -65,7 +65,7 @@ To verify the CLA Assistant is working:
    I have read the CLA Document and I hereby sign the CLA
    ```
 
-4. **Verify signature tracking**: After signing, a new commit should be added to the main branch updating `.github/CLA_SIGNATORIES.json`
+4. **Verify signature tracking**: After signing, a new commit should be added to the main branch updating `CLA/version_1/CLA_SIGNATORIES.md`
 
 5. **Check PR status**: The PR status check should update to show "All contributors have signed the CLA ✅"
 
@@ -76,15 +76,15 @@ To verify the CLA Assistant is working:
 When a contributor opens a pull request:
 
 1. The CLA Assistant bot comments with a link to the CLA and instructions
-2. The contributor reads the CLA at `/CLA.md`
+2. The contributor reads the CLA at `/CLA/version_1/CLA.md`
 3. The contributor signs by commenting: `I have read the CLA Document and I hereby sign the CLA`
-4. The bot records the signature in `.github/CLA_SIGNATORIES.json`
+4. The bot records the signature in `CLA/version_1/CLA_SIGNATORIES.md`
 5. The bot updates the PR status to indicate CLA is signed
 6. Future PRs from the same contributor don't require re-signing
 
 ### Signature Storage
 
-Signatures are stored in `.github/CLA_SIGNATORIES.json` in the following format:
+Signatures are stored in `CLA/version_1/CLA_SIGNATORIES.md` in the following format:
 
 ```json
 {
@@ -160,7 +160,7 @@ Recommended rotation period: Every 12 months
 
 - [CLA Assistant GitHub Action Documentation](https://github.com/contributor-assistant/github-action)
 - [GitHub Personal Access Tokens Guide](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)
-- [DeepWork CLA](../CLA.md)
+- [DeepWork CLA](../CLA/version_1/CLA.md)
 - [DeepWork License](../LICENSE.md)
 
 ## Support

.github/workflows/cla.yml

@@ -25,8 +25,8 @@ jobs:
           # This should be a Personal Access Token with repo scope
           PERSONAL_ACCESS_TOKEN: ${{ secrets.CLA_ASSISTANT_PAT }}
         with:
-          path-to-signatures: '.github/CLA_SIGNATORIES.json'
-          path-to-document: 'https://github.com/${{ github.repository }}/blob/main/CLA.md'
+          path-to-signatures: 'CLA/version_1/CLA_SIGNATORIES.md'
+          path-to-document: 'https://github.com/${{ github.repository }}/blob/main/CLA/version_1/CLA.md'
           # Branch where CLA signatures will be stored
           branch: 'IMPT_cla_signatures'
           allowlist: 'dependabot[bot],github-actions[bot]'

CLA.md CLA/version_1/CLA.mdCLA.md renamed to CLA/version_1/CLA.md

@@ -102,7 +102,7 @@ By signing this Agreement, You accept and agree to the terms and conditions cont
 
 ### For Individual Contributors
 
-To sign this CLA, please add your GitHub username to the list of signatories by creating a pull request that adds your name to the `.github/CLA_SIGNATORIES.md` file, or alternatively, sign the CLA through our automated CLA Assistant when you submit your first pull request.
+To sign this CLA, please add your GitHub username to the list of signatories by creating a pull request that adds your name to the `CLA/version_1/CLA_SIGNATORIES.md` file, or alternatively, sign the CLA through our automated CLA Assistant when you submit your first pull request.
 
 When you submit a pull request, the CLA Assistant bot will automatically check if you have signed the CLA and guide you through the process if you haven't.
 

.github/CLA_SIGNATORIES.md CLA/version_1/CLA_SIGNATORIES.md.github/CLA_SIGNATORIES.md renamed to CLA/version_1/CLA_SIGNATORIES.md

@@ -24,4 +24,4 @@ Organizations that have signed the Corporate CLA are tracked separately. If you
 
 ---
 
-For questions about the CLA, see [CLA.md](../CLA.md) or contact legal@unsupervised.com.
+For questions about the CLA, see [CLA.md](CLA.md) or contact legal@unsupervised.com.

CONTRIBUTING.md

@@ -39,7 +39,7 @@ The CLA ensures that:
 **For First-Time Contributors:**
 
 1. **Submit your pull request** - When you open your first PR, the CLA Assistant bot will automatically comment on it
-2. **Read the CLA** - Review the [Contributor License Agreement (CLA)](CLA.md)
+2. **Read the CLA** - Review the [Contributor License Agreement (CLA)](CLA/version_1/CLA.md)
 3. **Sign electronically** - Comment on your PR with: `I have read the CLA Document and I hereby sign the CLA`
 4. **Verification** - The bot will verify your signature and update the PR status
 
@@ -57,7 +57,7 @@ Our CLA:
 - Acknowledges the Business Source License 1.1 restrictions
 - Is based on the Apache Software Foundation's CLA with modifications for BSL 1.1
 
-For the full text, see [CLA.md](CLA.md).
+For the full text, see [CLA.md](CLA/version_1/CLA.md).
 
 ## Development Setup
 
@@ -524,7 +524,7 @@ echo $NIX_PATH
 
 By contributing to DeepWork, you agree that your contributions will be licensed under the project's current license. The licensor (Unsupervised.com, Inc.) reserves the right to change the project license at any time at its sole discretion.
 
-You must sign the [Contributor License Agreement (CLA)](CLA.md) before your contributions can be accepted. See the CLA section above for details.
+You must sign the [Contributor License Agreement (CLA)](CLA/version_1/CLA.md) before your contributions can be accepted. See the CLA section above for details.
 
 ---
 

README.md

@@ -266,7 +266,7 @@ DeepWork is licensed under the Business Source License 1.1 (BSL 1.1). See [LICEN
 - **Free for non-competing use**: You can use DeepWork freely for internal workflow automation, education, research, and development
 - **Change Date**: On January 14, 2030, the license will automatically convert to Apache License 2.0
 - **Prohibited Uses**: You cannot use DeepWork to build products that compete with DeepWork or Unsupervised.com, Inc. in workflow automation or data analysis
-- **Contributing**: Contributors must sign our [Contributor License Agreement (CLA)](CLA.md)
+- **Contributing**: Contributors must sign our [Contributor License Agreement (CLA)](CLA/version_1/CLA.md)
 
 For commercial use or questions about licensing, please contact legal@unsupervised.com