docs: add Contributor License Agreement (CLA)

[carlos-alm]

Summary

• Add CLA.md — Contributor License Agreement for Optave AI Solutions Inc.
• Covers copyright and patent license grants, contributor representations, third-party submissions, and notifications
• Modeled after the Zep CLA format

Test plan

• Review legal text for accuracy
• Verify company name and jurisdiction are correct

[claude]

Claude finished @carlos-alm's task —— View job

---

PR Review: Contributor License Agreement Addition

Review Checklist

• Read and analyze CLA.md content
• Phase 1: Root cause analysis - why is CLA needed?
• Phase 2: Check for configuration changes
• Phase 3: Assess test integrity (if applicable)
• Phase 4: Review content quality and structure
• Provide structured final assessment with rating

---

Root Cause Analysis

Problem Being Solved: Establishing clear intellectual property ownership and licensing terms for contributors to the @optave/codegraph project. As a commercial product published by Optave AI Solutions Inc., this ensures legal clarity for both contributors and the company when accepting external contributions.

Why This Approach: The CLA follows industry-standard practices (similar to Apache CLA format) and is necessary for commercial software that accepts community contributions. The existing Apache 2.0 LICENSE covers end-user rights, but the CLA governs contributor obligations.

Risk Assessment: ✅ LOW RISK - This is a standard legal document addition with no code changes.

Critical Concerns (if any)

⚠️ Minor Issues Identified

1. Inconsistent Control Definition (CLA.md:9-13)

   • The control definition uses both "fifty percent (50%)" and Roman numerals (i, ii, iii)
   • Standard Apache CLA uses consistent formatting throughout

2. Missing Signature/Acceptance Process

   • The CLA document doesn't specify HOW contributors actually agree to it
   • No mention of automated CLA bots, signature process, or integration with GitHub

3. Jurisdiction Not Specified

   • Unlike many CLAs, this doesn't specify governing law or jurisdiction for disputes
   • The PR test plan mentions verifying "jurisdiction" but it's not present in the document

✅ Strengths

• Well-structured standard CLA format
• Comprehensive coverage of copyright and patent grants
• Clear definitions and scope
• Proper company name and attribution
• Consistent with Apache 2.0 licensing approach
• Covers third-party submissions appropriately

Phase-by-Phase Assessment

Phase 1: Root Cause ✅

This addresses a legitimate business need for a commercial software product that accepts contributions.

Phase 2: Configuration Changes ✅

No configuration changes - single file addition only.

Phase 3: Test Integrity ✅

Not applicable for legal documentation.

Phase 4: Content Quality ⭐⭐⭐☆☆

• Standard CLA language with minor formatting inconsistencies
• Missing operational details for CLA acceptance process
• Aligns well with existing Apache 2.0 license

Recommendations

1. Fix formatting consistency in the control definition section
2. Add implementation details: How will contributors actually sign/agree to this CLA? Consider:
   • GitHub CLA bot integration
   • Manual signature process
   • Documentation in CONTRIBUTING.md
3. Consider adding jurisdiction clause for legal completeness

Final Recommendation

• Rating: ⭐⭐⭐☆☆ (3/5)
• Action: APPROVE WITH CONDITIONS
• Reasoning: This is a necessary and well-structured legal document for a commercial project. The content is sound and follows industry standards, but minor formatting issues and missing operational details prevent a higher rating. The PR addresses a legitimate business need and poses no technical risk.

Conditions for approval:

• Address formatting inconsistencies in definitions section
• Clarify the CLA acceptance/signature process for contributors

---

[greptile-apps]

Greptile Summary

This PR adds a Contributor License Agreement (CLA) for Optave AI Solutions Inc., following a standard Apache-style format with sections covering copyright grants, patent licenses, contributor representations, and third-party submissions.

Key observations:

• Company name "Optave AI Solutions Inc." is used consistently throughout
• Standard legal structure includes perpetual, worldwide, non-exclusive licenses for both copyright and patents
• Patent grant includes defensive termination clause for patent litigation
• Minor formatting issues found: incorrect section reference (line 29) and capitalization inconsistency (line 23)

Note: The test plan mentions verifying jurisdiction, but the CLA does not include a governing law or jurisdiction clause. This may be intentional or worth confirming.

Confidence Score: 4/5

• Safe to merge after addressing minor formatting corrections
• Documentation-only change with standard legal structure; issues found are minor formatting errors (section reference and capitalization) that should be corrected for professionalism but don't affect legal validity
• CLA.md requires minor corrections to section reference and capitalization before merging

Important Files Changed

Filename	Overview
CLA.md	New CLA with standard Apache-style terms; minor section reference error and capitalization inconsistency need correction

_{Last reviewed commit: 01dcf5d}

[greptile-apps]

_{1 file reviewed, 2 comments}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

Section reference is incorrect — "section 7" should be "section 6" (Third-Party Submissions)

Suggested change

You represent that each of Your Contributions is Your original creation (see section 7 for submissions on behalf of others). You represent that Your Contribution submissions include complete details of any third-party license or other restriction (including, but not limited to, related patents and trademarks) of which you are personally aware and which are associated with any part of Your Contributions.

You represent that each of Your Contributions is Your original creation (see section 6 for submissions on behalf of others). You represent that Your Contribution submissions include complete details of any third-party license or other restriction (including, but not limited to, related patents and trademarks) of which you are personally aware and which are associated with any part of Your Contributions.

[carlos-alm]

Fixed in #244 — corrected to "section 6" as suggested.

[greptile-apps]

Inconsistent capitalization — your and you should be Your and You to match the rest of the document

Suggested change

Subject to the terms and conditions of this Agreement, You hereby grant to Optave and to recipients of software distributed by Optave a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by You that are necessarily infringed by Your Contribution(s) alone or by combination of Your Contribution(s) with the Work to which such Contribution(s) was submitted. If any entity institutes patent litigation against You or any other entity (including a cross-claim or counterclaim in a lawsuit) alleging that your Contribution, or the Work to which you have contributed, constitutes direct or contributory patent infringement, then any patent licenses granted to that entity under this Agreement for that Contribution or Work shall terminate as of the date such litigation is filed.

Subject to the terms and conditions of this Agreement, You hereby grant to Optave and to recipients of software distributed by Optave a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by You that are necessarily infringed by Your Contribution(s) alone or by combination of Your Contribution(s) with the Work to which such Contribution(s) was submitted. If any entity institutes patent litigation against You or any other entity (including a cross-claim or counterclaim in a lawsuit) alleging that Your Contribution, or the Work to which You have contributed, constitutes direct or contributory patent infringement, then any patent licenses granted to that entity under this Agreement for that Contribution or Work shall terminate as of the date such litigation is filed.

_{Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!}

[carlos-alm]

Fixed in #244 — capitalized your/you to Your/You in the patent litigation sentence as suggested.

[carlos-alm]

All Greptile review feedback has been addressed in #244, which supersedes this PR:

• Section reference: Fixed section 7 → section 6
• Capitalization: Fixed your/you → Your/You in patent section
• Control definition formatting: Changed Roman numerals (i./ii./iii.) to lettered list ((a)/(b)/(c))
• Missing signature/acceptance process: Added Acceptance section documenting the CLA bot flow
• Missing jurisdiction: Added Governing Law clause — Province of Alberta, Canada
• CLA automation: Added .github/workflows/cla.yml with CLA Assistant Lite
• CONTRIBUTING.md: Added CLA signing instructions

Closing in favor of #244.

[carlos-alm]

Superseded by #244