COLLABORATIVE DEVELOPMENT LICENSING TECHNOLOGY (CDLT) (c) TERMS OF LICENSE Version 1.0 Copyright (c) 2025 Imagtek Publishing LLC USA All Rights Reserved Free Use and Distribution Modification Prohibited This is a legally binding document. This CDLT Software License protects the Intellectual Private Property (IP) of all Contributors to this distribution while facilitating Collaborative, Free-Open-Source-Software (FOSS) Development. This license dictates Terms of Access and Use; both as an individual work, and as an aggregation of works. 'Intellectual Slavery is not Freedom' NOTIFICATION Any work claiming protection under this license must contain a notification providing a web-link, local path, or full copy of this license. Example: Licensed under CDLT See: https://imagtek.com/documents/CDLTlicense.txt or Licensed under CDLT See: ~imagtek/doc/CDLTlicense.txt or Licensed under CDLT. Full text of license follows: All works licensed under CDLT are licensed under the most recent version of CDLT, or a valid version of CDLT specified in the Notification. All works of a named CDLT distribution are presumed licensed under CDLT in the absense of any other explicit licensing or Copyright claims. INSPECTION You may not inspect this distribution with the intent to place its content under more restrictive license, nor as discovery for litigation against its content, absent a Court order empowering inspection specifically for such purposes. EXTERNAL LICENSE COMPATIBILITY CDLT content licensing is fully compatible with: Apache License 2.0 https://www.apache.org/licenses/LICENSE-2.0 MIT License https://opensource.org/licenses/MIT BSD License https://www.freebsd.org Creative Commons https://creativecommons.org/licenses/by/4.0/ Only components licensed under the above, or similar, non-restrictive license may be included as components of a CDLT Distribution. 'For-Fee' proprietary components may be included if their licensing permits unrestricted distribution and use upon payment of a fee. Any components distributed as compiled binaries [apps, libraries, shared objects] with no restrictions on distribution or use may be included as components of a CDLT distribution. DEFINITIONS A 'software application' is an executable computer program. A 'compatible work' permits free copying, distribution, installation, use, and modification without exposure to stealth or explicit coercive liabilities; or can be rendered compatible by payment of a fee. Work under separate license is 'compatible' if it is not at variance with any terms of this CDLT License. An 'invalid work' is content that does not meet the definition of a 'compatible work'. A 'distribution' consists of a software application, support applications, computer source code, scripts, compiled shared-objects or libraries, text fonts, documentation, data, etc. distributed under these, or compatible, terms of license. A distribution may be a single work, or an aggregation of works. Any valid CDLT distribution may be a component of a CDLT distribution. An 'invalid distribution' contains 'invalid work' and has no legal existence under CDLT. An invalid distribution may be recovered as a valid distribution by removal of all invalid works, or payment of a fee that removes all liabilities. A 'version' of a distribution is the unique set of content that distinguishes it from a different version. A version may be designated via a unique code. A 'copyright' is legally recognized ownership of IP. Only the copyright owner may dictate terms of licensing, access, use, modification, and distribution. A 'license' dictates legally binding terms of use and distribution for IP. Only the copyright holder of a work may dictate terms of license. A license is not a contract. 'Source code' is human readable and modifiable text written in a language that a computer can compile into an executable program, or interpret at run-time, to cause a computer to perform specific operations defined by the source code. A 'source code component' is an instance of source code that compiles without error as a subset of a 'software application'. A source code component cannot host a derivative work, and it cannot legally encumber a 'software application' except under explicit contract. An 'Applications Programming Interface' (API) is a public description of accessible internal control structures of a 'software application'. A 'kernel application' is a software application that may optionally provide source code and an API that provides services to a derivative work. A 'derivative work' is a software application that utilizes the API published by a 'kernel application', that hosts additional functionality. A 'kernel developer' is the developer of a kernel application. A 'derivative work developer' aka a 'collaborative developer' is a developer who creates a derivative work using the API provided by a kernel application, and possibly other source code and shared-object [library] components. A 'CDLT key' is an encrypted string that enables access to a software application consisting of a kernel work, and optionally a derivative work based upon the kernel work, via a single key. A 'trade secret' is any unique source code, script, data, or documentation that is held as IP and not subject to free distribution. USE The grant or purchase of this license is the grant or purchase of the right to inspect, copy, install, modify, and use this IP under these terms. This license does not convey or imply conveyance of IP under any theory of Law, nor may any component under different license claim such a conveyance. You may not be a party to litigation challenging access or control of CDLT content distributed under lawful copyright, patent or license. This prohibition extends to any organization of which you are an employee, contractor, agent or familiar. Copying or Installation of this distribution asserts unconditional acceptance of all terms of CDLT license. COPYING, DISTRIBUTION AND INSTALLATION You may copy and distribute this work via any media or network and install it on any system only under these terms of license. CDLT LICENSING A CDLT software Application may control access and require payment of a fee for use, or it may be distributed entirely as FOSS. No component of a CDLT distribution may dictate IP forfeit, exernal control, litigation exposure, or any other coercive measure beyond payment of a fee, and the user has been fully informed of the specifics of any such fee. No license expiration date is recognized for any component of a CDLT distribution, however expiration of 'for fee' licensing renders a CDLT distribution invalid from the date of use contract expiration. Re-enstatement of a for-fee license by payment of the fee restores the original CDLT distribution to valid status. CDLT terms of license do not supercede terms of license of non-CDLT works, however terms of license of non-CDLT works shall not supercede terms of license of a CDLT distribution hosting such works. If license terms of an external work are in conflict with CDLT terms of license, and this conflict cannot be removed via payment of a fee, the work may not be included in a CDLT distribution. Absence of these terms of license with a work does not invalidate these terms of license, nor their original scope, if it is demonstrable that the work originated under these terms. There are 4 run-time licensing modes for CDLT executables; 'Free', 'Evaluation', 'Kernel' and 'Derivative'. A CDLT 'Free license' grants free and unrestricted access to the kernel executable CDLT application; either at no cost or by soliciting a voluntary donation. If access control is implemented, a CDLT 'Evaluation license' may optionally be granted from the date of first successful activation of a CDLT application. An evaluation license provides access to evaluation functionality of the kernel application version licensed. An 'evaluation license' has a limited duration defined by the kernel developer, and may be zero. If the software application is a derivative work, the evaluation access term is the same as that for the kernel license. The collaborative developer defines evaluation functionality. A CDLT 'Kernel license' requires purchase from the kernel developer. A Kernel license provides access to full functionality of the kernel application version, and access level, licensed. A kernel license has an extended duration and defines multiple access levels. If the software application is a derivative work, and the derivative work has not implemented CDLT access control, a 'Kernel license' provides full access to derivative work functionality. A CDLT 'Derivative license' is an optional extension of the kernel license. It provides access to full functionality of a Derivative Work version, and access level, licensed. It also provides full access to services of the Kernel Application version, and access level, licensed. A Derivative License defines multiple access levels with access duration equal to the Kernel license. Access control is optional. CDLT offers an access control mechanism, but does not disqualify any CDLT compatible access control mechanism. If CDLT access control is present in the kernel application, a derivative work may implement access control ONLY via the existing CDLT control mechanism. A derivative work may not disable CDLT access control, if present. If a kernel application lacks access control, a derivative work may implement access control only to non-kernel functionality. A kernel developer, and a derivative work developer, are legally separate and distinct business interests. There is no 'implied' relationship. A 'kernel work' and a 'derivative work' are 'separate works' that exchange information across an interface described by a public API. The Legal relationship is the same as an application running on an operating system. These terms of license shall be administered under the legal jurisdiction in which the Kernel application developer is Incorporated or, absent legal incorporation, legally resides. COPYRIGHTED MATERIAL Copyrighted material shall display a copyright notice as below or similar; ------------------------------------------ Copyright (c) DeveloperEntity ------------------------------------------ Absent a Copyright notice, Copyright is presumed held by the creator of the work. A licensed work presumes existence of a Copyright holder. In the absence of a License or Copyright notice, the work is presumed in the Public Domain until such time as a verifiable Copyright holder comes forward. Work that is in the Public Domain has no restrictions on use or distribution, and cannot be placed under more restrictive license. Only the Copyright holder may include a Copyrighted work into a CDLT distribution, unless the work is released under compatible, non-restrictive FOSS licensing [see above: External License Compatibility], or CDLT Source Code Release. Only the Copyright holder may dictate 'CDLT Source Code Release', or operational equivalent to the following: ------------ CDLT SOURCE CODE RELEASE ------------ This source code, and modified copies, is licensed for unrestricted use and distribution and may not, in full or in part, be placed under more restrictive license. This source code comes with no warranty, nor any assertion of compliance or utility. Use of this source code is at your own risk and you assume all liability associated with its distribution. -------------------------------------------------- Source code release does not remove Copyright to a work. Only the copyright holder may dissolve copyright by appending the following notice: -------------------------------------------------- Copyright (c) DeveloperEntity 'Released into the Public Domain' -------------------------------------------------- Such release is equivalent to 'CDLT Source Code Release'. The Copyright owner of a work may change licensing for a work, however licensing may not be changed retroactively. Changing licensing of a work is equivalent to releasing a new version of the work. Altering terms of license of a work re-defines licensing only for future distributions of the work. CDLT distribution versions prior to the date of Licensing change retain original terms of license and use. Copyright holders are required to be aware of, understand, and agree to this clause before including a work as a CDLT component. The Copyright owner of a work retains Copyright to all versions of the work that have been modified by derivative work Developers. However, derivative work developers retain Copyright to their unique modifications of the work. A derivative work developer may use, and modify, Copyrighted source code distributed in a CDLT Distribution and distribute the modified source code as part of a software application. They may also privately hold modifications to copyrighted source code as 'trade secrets' and distribute a binary application absent the source code. A Copyright holder cannot coerce release of modifications to their work held as copyrighted 'Trade Secrets', nor make any claim against IP hosting the work. The Copyright holder may require a citation advising presence of their work in another work. A copyrighted work modified by others will include a log containing date, description of modifications, and modifier; even if the modifications are held as 'trade secrets'. A derivative work developer may not distribute modified copyrighted source code lacking a 'CDLT Source Code Release' or equivalent, apart from an application that uses the source code. The purpose of this prohibition is to prevent unauthorized forking of an application source code base, or distribution of corrupted code. The copyright holder of source code may maintain a repository for modified copies of copyrighted source code submitted by derivative work developers, which shall include a log of modifications to the work. Maintenance of a repository, and submission of modified source to the repository, is voluntary. In the absence of a repository controlled by the copyright holder, any developer in the development lineage of a work may copy it to a repository with written permission of the Copyright holder; but there may be only a single repository. PROHIBITIONS You are prohibited from including in a CDLT Distribution any computer source code licensed under any version or variant of the GNU General Public License (GNU GPL) aka 'CopyLeft', or similar viral Communist license. Presence of any such source code, in full or in part, renders a CDLT distribution Invalid, NULL, and Void. You are prohibited from distributing software that, by conscious design, performs any undisclosed, invasive, or harmful action; or that attempts to impose a legal obligation, liability, or claim against the user. You are prohibited from disassembling any executable program included with this distribution, modifying or disabling functionality of the CDLT access control mechanism, or interfacing with the application by any means other than the public API or CDLT source code distributed with the application. You are prohibited from using any capability supported by this application in support of a criminal enterprise as defined by Law in the jurisdiction of use. You are prohibited from distributing a work that knowingly infringes the IP of an individual or organization, or violates terms of license for externally acquired IP. DERIVATIVE WORKS AND COLLABORATIVE DEVELOPMENT You may utilize the API published by a CDLT kernel application to create a derivative work with functionality absent in the original work. The added functionality is the IP of the collaborative developer who may optionally control access to the derivative work via an extension of the CDLT Kernel Access control. The developer may also open-source their derivative work. Kernel modifications required to host a derivative work are the IP of the kernel developer; even if created as a work for hire. There shall not be more than one access control mechanism or key for a CDLT application. CDLT licensed material may be used as a FOSS component to any software application under compatible license. A Kernel Application, and a Derivative Work based upon it, are legally separate and distinct works. Access levels of a kernel application and a derivative work are specified separately and are operationally distinct. A derivative work developer may make no claim upon IP of a Kernel Application, nor to modifications to a Kernel Application required to host a derivative work. There is no financial obligation of a Kernel Developer to refund Kernel License fees paid by a derivative work developer in the event the derivative work is found to be an Invalid work. All works licensed for use by a Kernel Application, including copyrighted 'Fee- For-Use' works, are also licensed for any derivative Work based on the Kernel Application. If access control is implemented, the kernel application developer is the sole distributor of CDLT keys that unlock the Kernel Application. Derivative works implementing access control must acquire CDLT keys only from the developer of the kernel application upon which the derivative work is based, or their agent. A derivative work developer may purchase a CDLT key from a kernel application developer, on behalf of an end user, for the purpose of enabling access to a derivative work. The derivative work developer may charge any price for a CDLT key that the end user is willing to pay. The fee for use of a Kernel Application in a derivative Work is the GREATER OF the fee charged for an Extended License to the Kernel Application, or 1/2 the fee charged for an Extended License to the Derivative Work based upon it. A Kernel developer, and a Derivative Work developer, may make alternative arrangements regarding fees via contract. The kernel developer may decline to provide a CDLT key enabling a derivative work if the derivative work is merely a clone of the kernel application that introduces no 'significant new functionality'. The kernel developer is the sole judge of what constitutes 'significant new functionality'. A derivative works may only be distributed by the derivative work developer, or their agent. The kernel developer is prohibited from creating a CDLT key implementing a derivative work CDLT access code, except as specified by a license order for the kernel work, and then only for that single order. All source code of a derivative work absent in the kernel distribution, and created by the derivative work developer, are copyrighted IP of the derivative work developer. All other works retain their original ownership and terms of licensing, distribution and use. If CDLT access control is implemented, rigorous pre-release testing and verification of the access control mechanism is the sole responsibility of the derivative work developer. The Kernel Application developer makes no warranties or representations regarding the efficacy or functionality of the access control mechanism, nor any other feature or capability of the Kernel Application, nor any derivative work based upon it. A derivative work developer may not represent themself as being legally affiliated with the kernel developer, unless such a legal affiliation is entered into mutually via explicit written contract. A kernel developer may distribute unique derivative works that are of their own creation; as in fielding specialized derivative works of a kernel application to address niche markets. The kernel developer's obligation to perform product support is limited to the original, unmodified kernel application. The derivative work developer's obligation to perform product support is for the entire derivative work, including the kernel application. The reason for this discrepancy is that a derivative work may introduce subtle flaws that only the derivative work developer has the resources to diagnose and correct. The kernel application developer may optionally, at their discretion, make changes to the kernel application to resolve known issues with derivative works, however these changes are the IP of the kernel developer. The kernel developer's sole obligation to a derivative work is to accurately fill a license order for a derivative work exactly as specified, and convey the license to the provided contact. The kernel developer is under no obligation to verify or research the identity, motive or legality of any license purchase. The kernel developer may adjust pricing of the kernel application at any time and for any reason to address market variability. Pricing may not be adjusted retroactively. Neither the kernel application developer, nor the derivative work developer, are obligated to reveal trade secrets or software internals to any party. There is no implied contract or relationship between a kernel application developer and a derivative work developer. A derivative work may not encumber future development of a kernel application, except as defined by IP Law. WARNING: GNU GPL SOURCE CODE AND CDLT The GNU GPL is a network-crawling Communist klepto-algorithm that litigates for control of user's IP. GNU GPL licensed source code (Link: ~/doc/GNUlicensing.txt) is explicitly and unconditionally prohibited in a CDLT Distribution. The only defined legal relationship between source code of a GNU GPL 'covered work' and CDLT licensed source code, is a relationship where a GNU GPL covered work is 'based on' or represents a 'modified version' of a CDLT component. The GNU GPL work is a 'work based on the Program' of the CDLT work, as defined under the GNU GPL, and is subsumed under terms of 'CDLT Source Code Release'. Terms of GNU GPL contagion are imposed against all GNU GPL licensed works tracable through a viral network association with the compromised work. All compromised works are subsumed under terms of 'CDLT Source Code Release'. If a forensic scan of compromised GNU GPL works leads to the Linux O/S, then the entire Linux O/S source code base is subsumed under 'CDLT Source Code Release'. These terms are equally enforcable to terms of the GNU GPL. INVALID CDLT DISTRIBUTIONS AND RECOURSE Any CDLT Distribution proved 'invalid' under these terms has no legal existence. All rights of distribution, copying, installation and use are Null and Void. Persons in possession of an invalid CDLT distribution must promptly cease use and distribution, destroy any physical copies, and delete its contents from any system where it is installed. Scope of damages due end users of an invalid CDLT Distribution are limited to refund of money paid for access to the Distribution. There is no recourse for direct or consequential damages. If the CDLT Distribution proved invalid is a Kernel application, the Kernel developer is liable for refund of money paid to all Kernel License holders. If the CDLT Distribution proved invalid is a Derivative Work, the Derivative work developer is solely liable for refund of money to end users. The kernel developer has no financial or other obligations whatsoever to Derivative Work Developers of an invalid Distribution, nor to impacted users. LIMITED KERNEL DEVELOPER LIABILITY THE KERNEL DEVELOPER MAKES NO WARRANTY OF FUNCTIONALITY OR NON-INFRINGEMENT. THE DERIVATIVE WORK DEVELOPER SHALL PERFORM DUE DILIGENCE IN PURSUING DERIVATIVE WORK DEVELOPMENT AND UNCONDITIONALLY ASSUMES ALL LIABILITY FOR A DERIVATIVE WORK, INCLUDING KERNEL FUNCTIONALITY, AS A CONDITION OF ACCESS TO THE KERNEL WORK. UNDER NO CIRCUMSTANCE OR THEORY OF LAW SHALL THE KERNEL DEVELOPER BE LIABLE FOR DERIVATIVE WORKS THAT INFRINGE THE INTELLECTUAL PROPERTY OF THIRD PARTIES, OR CAUSE LOSS OR HARM TO USERS. ALL SUCH LIABILITY IS EXPLICITLY ASSUMED IN FULL BY THE DERIVATIVE WORK DEVELOPER. THE SOLE LIABILITY OF A KERNEL DEVELOPER UPON WRITTEN NOTIFICATION OF INFRINGEMENT OR HARM IS TO CEASE GRANTING CDLT KERNEL LICENSES AND SUPPORT TO INFRINGING DERIVATIVE WORKS. RESOLUTION OF OTHER LIABILITY IS STRICTLY BETWEEN THE DERIVATIVE WORK DEVELOPER AND THIRD PARTYS. The derivative work developer unconditionally assumes all liability for conforming to local laws and ordinances related to legality of use, taxation and the regulation of commerce at the point of distribution of the derivative work. WARNING: ENCRYPTION PERMANENT DATA LOSS HAZARD Use of Encryption exposes users to a Permanent Data-Loss Hazard. Any user of Encryption software licensed under CDLT acknowledges and accepts full responsibility for secure un-encrypted backup of important content, verification of correct Encryption software operation, and crypto-key management. There is no claim of compatibility across different Crypto systems. Under no circumstance or theory of Law will developers of CDLT licensed software be liable for Decryption failure and/or loss of Encrypted content. DISCLAIMER & NO END-USER WARRANTY Any user of this software acknowledges that they use this software freely and entirely their own risk. No party to the development of this software makes any representations or warranties, expressed or implied, about the suitability of this software; including but not limited to any implied warranties regarding defects, merchantability, fitness for a particular purpose, or non-infringement. To the extent allowed by Law, Developers shall not be liable under any theory of liability for damages suffered by users or other parties as a result of errors, installation, use, or abuse of this software; nor for damages caused by derivative works based upon this software, or its components. The Kernel Developer makes no warranties or representations whatsoever regarding the kernel application or any derivative works, and is not liable for defective, illegal, malicious, fraudulent or infringing derivative works. Any use of this software is done entirely at the risk of the user, with the knowledge that this software may contain experimental algorithms that have not been tested and certified for Life/Property critical applications. There shall be no recourse for direct or consequential damages from use or abuse of this software under any theory of Law. BUSINESS ENTITIES: CDLT DERIVATIVE WORK CONTRACTED AS A 'WORK FOR HIRE' Business entities wishing to specify enhancements to a kernel application for re- distribution and sale as a separate work, or for internal use, may contract for such development with any party as a 'work for hire'. Unique source code developed under contract, trade secrets, and distribution rights to the derivative work, are exclusively owned by the contracting entity. A 'work for hire' contract may not invoke violation of any CDLT Terms of License. Transfer of IP of a 'work for hire' is strictly limited to new and unique development explicitly described in a contract. Nothing is 'implied or presumed'. Any 'work for hire' involving a Kernel application is, by definition, for creation of a Derivative Work of the kernel application. No 'work for hire' involves transfer of Kernel application IP in any form, including Kernel IP concurrently developed outside contract to host a Derivative Work. Unless they are a direct contract signatory, a kernel application developer is not legally encumbered, and does not fall under any liability or obligation as the result of a 'work for hire' involving the kernel application. There is no 'implied support'. Existence of a 'work for hire' does not encumber a kernel developer from pursuing any concurrent or future course of product development or distribution, except as constrained by explicit contract terms to which they are a signatory, or by Copyright Law.