Legal framework and commercial use
Esta página aún no está disponible en tu idioma.
🌍 Language pair / Par de idioma
Section titled “🌍 Language pair / Par de idioma”- English: 31-legal-framework-and-commercial-use.md
- Español: ../es/31-marco-legal-y-uso-comercial.md
🗣️ Friendly prompt (copy/paste)
Section titled “🗣️ Friendly prompt (copy/paste)”Use this when you are not technical and want the AI to do setup + guidance end-to-end:
Using https://github.com/juanklagos/spec-driven-development-template, create everything needed to carry out my project end-to-end.My project is: [describe your project in plain language].
If my project is new, initialize it with this template and GitHub Spec Kit.If my project already exists, adapt it to idea/specs/bitacora without breaking current behavior.Guide me step by step for my level (beginner/intermediate/advanced), using simple language.Do not skip specification, plan, tasks, refinement trace, logbook, and validation.This document summarizes the licensing terms. For complete legal language, refer to the root-level legal documents.
📋 Project licensing status
Section titled “📋 Project licensing status”This repository is licensed under PolyForm Noncommercial 1.0.0. It is source-available but not OSI-approved open source.
| Aspect | Detail |
|---|---|
| License type | PolyForm Noncommercial 1.0.0 |
| Source availability | Public, readable, forkable |
| OSI open-source | ❌ No |
| Commercial use | ❌ Requires written authorization |
✅ What is allowed (without authorization)
Section titled “✅ What is allowed (without authorization)”| Use case | Allowed? | Notes |
|---|---|---|
| Personal learning and experimentation | ✅ Yes | Use freely for self-education |
| Academic and educational use | ✅ Yes | Classroom, workshops, research |
| Noncommercial organization use | ✅ Yes | Under PolyForm Noncommercial terms |
| Contributing to this repository | ✅ Yes | Under CLA terms (see below) |
| Creating personal projects with this template | ✅ Yes | As long as services built are noncommercial |
| Referencing in blog posts or talks | ✅ Yes | With proper attribution |
❌ What requires prior written authorization
Section titled “❌ What requires prior written authorization”| Use case | Status | How to get permission |
|---|---|---|
| Selling the template or derivatives | ❌ Needs license | Contact author |
| Using in a paid SaaS product | ❌ Needs license | Contact author |
| Including in paid courses or training | ❌ Needs license | Contact author |
| White-labeling for clients | ❌ Needs license | Contact author |
| Integration into commercial CI/CD tools | ❌ Needs license | Contact author |
📄 Legal documents in this repository
Section titled “📄 Legal documents in this repository”| Document | Purpose |
|---|---|
| LICENSE | Full PolyForm Noncommercial 1.0.0 text |
| NOTICE | Copyright notice and attribution |
| COMMERCIAL_LICENSE.md | Terms for commercial licensing requests |
| DISCLAIMER.md | Warranty and liability disclaimer |
| TRADEMARK_POLICY.md | Rules for using project name and branding |
| ENFORCEMENT.md | How license violations are handled |
| CLA.md | Contributor License Agreement |
| LEGAL_OVERVIEW.md | Summary of all legal documents |
🤝 Contributor License Agreement (CLA)
Section titled “🤝 Contributor License Agreement (CLA)”By contributing to this repository, you agree to the CLA terms in legal/CLA.md. Key points:
- You retain copyright of your contributions
- You grant the project a broad, perpetual license to use your contributions
- You certify that your contributions are your original work
⚠️ Important note
Section titled “⚠️ Important note”[!WARNING] This document is informational only and does not constitute legal advice. For binding terms, refer to the actual license text in
LICENSE. When in doubt, consult a lawyer.
💡 Quick tips
Section titled “💡 Quick tips”- Start from a simple one-paragraph project description.
- Ask the AI to confirm the active spec before coding.
- Close every session with validation and a clear next step.
📊 Visual flow
Section titled “📊 Visual flow”flowchart LR A["Project idea"] --> B["Spec approved"] B --> C["Plan aligned"] C --> D["Tasks prioritized"] D --> E["Implementation"] E --> F["Validation + Logbook"]