Copyright © 2025 Kenneth Carter
This project is licensed under a dual-license model:
You may use, copy, modify, and distribute this software for educational, research, personal, or nonprofit projects, provided that such use does not directly or indirectly contribute to revenue generation.
Revenue Generation includes, but is not limited to:
- Paid services or products
- Grant-funded research
- Fundraising activities
- Inclusion in monetized platforms or consulting deliverables
- Any deployment that results in financial benefit, even if the software itself is not sold
If your use case touches revenue in any way, it is considered commercial.
To use this software in a commercial environment, you must obtain a paid license from the copyright holder.
Licensing is per application, where an "application" is defined as any deployed software component that performs coordination using this DOC Library.
- Whether labeled as a service, backend, orchestration unit, or embedded module
- Regardless of the number of instances, containers, or internal-only usage
- Includes any system where coordination logic is expressed through this library's abstractions
Note on Microservice Environments
In distributed systems or microservice architectures, each deployed component that performs coordination using this DOC Library is considered a separate “application” for licensing purposes.
This includes:
- Services that directly invoke coordination logic
- Embedded coordination modules within otherwise distinct services
- Any unit whose behavior depends on coordination abstractions provided by this library
Centralized orchestration layers are licensed independently from downstream services, even if coordination is delegated.
Note on Hosted Services and Desktop Applications
For hosted services—including load-balanced web servers, containerized deployments, and Kubernetes environments—there is no limit on the number of instances per licensed application.
However, for desktop applications, licensing may be enforced on a per-seat basis, where each end-user installation requires a separate license.
Site licenses may be available for organizations seeking broader deployment terms.
Contact the copyright holder to acquire a commercial license.
This software is provided “as-is”, without any express or implied warranties. The author is not liable for any damages, including but not limited to:
- Data loss
- Business interruptions
- Security breaches
- Compliance failures
- Any other negative consequences resulting from use
Licensees using this software in a production or commercial environment are responsible for:
- Thorough testing and validation within their own systems
- Ensuring compliance with internal quality control, security, and regulatory procedures
- Conducting regular penetration testing to identify and mitigate vulnerabilities
- Promptly reporting any discovered vulnerabilities to the author, including steps taken to mitigate or resolve the issue
The author is not liable for any issues, failures, or losses arising from commercial use.
This license does not include support, bug fixes, or feature modifications. Requests for such services require a separate paid support agreement, which will define:
- Scope of work
- Compensation terms
- Delivery timelines
- Communication protocols and escalation paths for critical issues
- Security-related support, including vulnerability triage and patching assistance
No work will commence without a signed agreement.
By submitting code, pull requests, or other contributions, you agree to license your work under this project’s dual-license model, including commercial distribution.
- Contributions are voluntary and do not entitle you to compensation unless a separate agreement is made
- The copyright holder may include contributions in any distribution
- Contributors may be asked to sign a Contributor License Agreement (CLA) to clarify rights and responsibilities