COLLABORATIVE DEVELOPMENT LICENSING TECHNOLOGY (CDLT) (c) TERMS OF LICENSE Version 1.0 Copyright (c) 2026 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 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 Absent explicit external license, all works of a CDLT distribution are Licensed under the included copy, path, or link to this License. Works under external license may be included in a CDLT Distribution only if the external license is CDLT compatible. 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. Future versions of this license do not invalidate earlier versions, and may be issued to refine issues capable of misinterpretation or to address new issues that arise from changes in the technological and legal landscape. All versions of this CDLT License are under full Copyright of Imagtek Publishing LLC. Free, unrestricted use of this License is irrevocably guaranteed in perpetuity. 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. 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, then the external work may not be included in a CDLT distribution. ASSERTION OF SEVERABILITY If any provision of this CDLT License is found to be unenforceable, all remaining provisions are unaffected and remain fully enforceable. INSPECTION You may not inspect a CDLT distribution pursuant to placing its content under more restrictive License, Copyright or Patent. DEFINITIONS A 'software application' is an executable computer program. A 'compatible work' permits free copying, distribution, installation, use, and modification without exposure to viral or explicit coercive liabilities beyond Copyright Law; or can be rendered compatible by payment of a fee. 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 [libraries], text fonts, documentation, data, etc. distributed under CDLT, or compatible 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 work, or payment of a designated fee. 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. A 'License' dictates legally binding terms of use and distribution for IP that are in conformance with statutory and Copyright Law. 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 legally encumber a 'software application' except under explicit License requiring payment of a fee. 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 facilitates creation of Derivative Works. Or, it may release FOSS source code for general, unrestricted, collaborative use. Or, it may be a standalone, closed-source application. A 'Derivative Work' is a software application that utilizes the services, API, and Source Code published by a Kernel Application, to re-host the Kernel Application as a new distribution with additional functionality absent in the original work. A 'Collaborative Work' is a software application that utilizes Kernel Application source code components in an unrelated, independent work. A 'Kernel Developer' is the developer of a Kernel Application. A 'Collaborative Developer' is a developer who creates a Derivative Work of a Kernel Application, or uses source code components of a Kernel Application to create a Collaborative Work. A 'bug-fix' is a correction of defective source code. A 'bug-fix' is considered software maintenance rather than new development. A 'CDLT key' is an encrypted string that enables access to a software application consisting of a Kernel work, and optionally a Collaborative 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. A 'work for hire' is development performed for-fee under contract, which becomes the IP of signatories of the contract, under the contract terms. USE The grant or purchase of this License is the grant or purchase of the right to inspect, copy, install, modify, and use IP under these terms. This License does not convey ownership or control over this IP under any theory of Law, nor may any component under external License claim such conveyance or control. You may not be a party to litigation involving CDLT content distributed under lawful Copyright, License or Patent. Legal disputes involving CDLT content under this clause will be resolved via arbitration under the rules of the American Arbitration Association (AAA), in the jurisdiction of the Kernel Developer. COPYING, DISTRIBUTION AND INSTALLATION You may copy and distribute a valid CDLT Distribution via any media or network and install it on any system. CDLT LICENSING ADMINISTRATION Access control is optional for both the Kernel Application, and any Derivative Work based upon it. CDLT offers an access control mechanism, but does not disqualify any CDLT compatible access control mechanism. Disabling a CDLT access control mechanism is prohibited. There may be only one access control mechanism. There are 4 run-time licensing modes for CDLT executables; 'Free', 'Evaluation', 'Kernel' and 'Derivative'. A CDLT 'Free' License means there is no access control. The Application may be freely used, but the Developer may solicit a voluntary donation. Only the Copyright holder may implement access control to Copyrighted work. If access control is implemented, the Kernel defines an 'Evaluation Term'. If this term is greater than zero, a CDLT 'Evaluation License' will be automatically created upon first successful activation. An Evaluation License provides access to 'Evaluation' level functionality for the Evaluation Term. If the application is a Derivative Work, the Collaborative developer defines 'Evaluation' level functionality, if any, for the Derivative Work. If the Kernel Evaluation Term is zero, Derivative Work evaluation is not supported. A CDLT 'Kernel License' must be acquired from the Kernel Developer. A Kernel License specifies the term of Kernel access, and one of multiple levels of Kernel functionality. If a Derivative Work implements access control, a CDLT 'Derivative License' must be purchased from the Collaborative Developer. This defines the level of Kernel access, and in addition the level of Derivative Work access, for the term of the Kernel License. The Collaborative Developer then purchases a Kernel License from the Kernel Developer, providing proprietary information required to unlock Derivative Work functionality. Upon receipt, the License is relayed to an end user. If a Kernel Application lacks access control, a Derivative Work may implement access control only to functionality absent in the Kernel Application. A Kernel Developer, and a Collaborative Developer, are legally separate and distinct business interests. There is no 'implied' relationship. A 'Kernel Application' and a 'Derivative Work' based upon it 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 record for the work. Absent either, the work is presumed in the Public Domain. Work that is in the Public Domain has no restrictions on access, use or distribution [see: Source Code Release], but cannot be placed under more restrictive License except by its creator or Copyright owner. The Copyright owner of a work may freely distribute the work independent of any CDLT application. Similarly, a work released under external non-restrictive FOSS licensing, or released under 'CDLT Source Code Release' may be freely distributed. Otherwise, a Copyrighted CDLT work may be released only as a component of an application. Only the Copyright holder may dictate 'CDLT Source Code Release', or operational equivalent to the following. This release DOES NOT void Copyright. ------------ 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 assertions of compliance, correctness or utility. Use of this Source Code is at your own risk and you assume all liability associated with its distribution and use. -------------------------------------------------- Only the Copyright holder may release a work into the Public Domain by appending: -------------------------------------------------- Copyright (c) DeveloperEntity 'Released into the Public Domain' -------------------------------------------------- The Copyright owner of a work may change licensing and 'Source Code Release' for a work, however neither may be changed retroactively. Altering either is equivalent to releasing a new version of the work and re-defines licensing only for future distributions of the work. CDLT distributions prior to the date of Re-Licensing retain original terms of License and use. Copyright holders are required to be aware of, understand, and agree to this clause when including works under CDLT. The original Copyright owner of Source Code retains Copyright to all source code modified by Collaborative Developers. A Collaborative Developer may modify copyrighted source code distributed as part of a Kernel software application, to implement new and unique functionality. Collaborative developers retain Copyright to unique enhancements and extensions not included in the original work. They may distribute a binary application using the modified Source Code and retain the modifications as Trade Secrets. A 'bug-fix' of Kernel Application source code by a Collaborative Developer may not be Copyrighted as new development, nor held as 'trade secrets'. A 'bug fix' is considered normal software maintenance and will become part of the Maintenance Log for the source code. The purpose of this clause is to permit collaborative maintenance of a Kernel Application without piecewise transfer of Kernel IP. A Collaborative Developer may not distribute modified Copyrighted Source Code apart from the application that uses the modified Source Code. The purpose of this clause is to prevent unauthorized forking of an application Source Code base. There are no restrictions for source code under 'CDLT Source Code Release'. A Copyright holder may require a citation advising presence of their work in another work. A Copyrighted work modified by others should include a maintenance log containing date, description of changes, and developer ID. The Copyright holder of Source Code may maintain a repository for modified copies of Copyrighted Source Code submitted by Collaborative Developers, which should include a log of modifications to the work. Maintenance of a repository, and submission of modified source to the repository, is voluntary. PROHIBITIONS Prohibited content renders a CDLT Distribution Invalid, Null and Void. An Invalid CDLT distribution has no legal exposure beyond a requirement to cease distribution and inform users of a legal responsibility to cease use and delete all copies. You are prohibited from implementing access control upon a FOSS application to which you do not hold Copyright. You may implement access control to your specific modifications of such a work. 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 License that asserts a propagating viral obligation, liability, or claim against the recipient. You are prohibited from distributing software that, by conscious design, performs an undisclosed, invasive, viral, or harmful action. You are prohibited from disassembling any executable program included with this distribution, modifying or disabling functionality of a CDLT access control mechanism, or interfacing with the application by any means other than the public API and / or FOSS 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. DERIVATIVE WORKS AND COLLABORATIVE DEVELOPMENT You may utilize the API published by a CDLT Kernel Application, modify Source Code included with the application, or add new Source Code and shared objects to create a Collaborative Work with functionality absent in the Kernel Application. The Collaborative Developer may optionally control access to the Collaborative Work via an extension of the CDLT Kernel Access control, or open-source the Collaborative Work. A 'bug-fix' of a Kernel Application does not qualify as a Derivative Work. A Collaborative Developer may freely distribute a Derivative Work based upon a Kernel Application, however if the Kernel Application has implemented access control a Kernel License will be required to access the Derivative Work. A Collaborative Developer implementing CDLT access control provides a proprietary code with the CDLT key order for the Kernel Application. The code unlocks the Derivative Work via an extension of the Kernel CDLT key. The Collaborative Developer may charge any price for a CDLT key that an end user is willing to pay. The Kernel Developer is under no obligation to relay a CDLT key to a Third Party. Keys are fulfilled only as a direct reply to the originator of a key order. The fee for use of a Kernel Application by a derivative Work is the GREATER OF the standard fee charged for a Kernel License, or 1/2 the fee charged for a CDLT License to the Collaborative Work based upon it. The Kernel Developer may not charge differential Kernel License fees based upon the Collaborative Work. The Kernel Developer may change the standard fee charged for Kernel Application access at any time to address market variability. A Kernel Developer, and a Collaborative Developer, may make alternative fee arrangements via contract. A Collaborative Developer may make no claim upon IP of a Kernel Application hosting the Derivative Work. The Kernel Application developer, or their agent, is the sole distributor of CDLT keys that unlock a Kernel Application and its Collaborative Works. A Kernel Developer may create a CDLT key implementing a Derivative Work CDLT access code only as specified by a single License order for the Kernel work. A Kernel Developer may create derivative works of the Kernel Application to access diverse markets. A Kernel Developer is prohibited from distributing a Derivative Work to which they do not hold Copyright, or storing, distributing, or unauthorized use of a proprietary Derivative Work CDLT access code. A Kernel Developer is under no liability or obligation to investigate specifics of a Derivative Work, beyond correctly filling a CDLT key order exactly as specified. However, by providing a full refund within 7 business days the Kernel Developer may decline to create a CDLT Key to a Derivative Work that is in violation of specific and enumerated CDLT terms, or introduces no 'significant new functionality'. Legal disputes involving licensing under this clause will be resolved via arbitration under the rules of the American Arbitration Association (AAA), in the jurisdiction of the Kernel Developer. If CDLT access control is implemented, rigorous pre-release testing and verification of the access control mechanism is the sole responsibility of the Collaborative 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 or Collaborative Works based upon it. All works Licensed for use by a Kernel Application, including Copyrighted 'Fee- For-Use' works, are also Licensed for use by any derivative Work based on the Kernel Application. A Collaborative 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. The Kernel Developer's obligation to perform product support is limited to the original, unmodified Kernel Application. The Collaborative Developer's obligation to perform product support is for the entire Collaborative Work, including the Kernel Application. The reason for this discrepancy is that a Collaborative Work may introduce subtle flaws [bugs] that only the Collaborative 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 Collaborative Works, however these changes are the IP of the Kernel Developer. There is no 'implied contract' or relationship between a Kernel Application developer and a Collaborative Developer. A Collaborative Work may not encumber future development of a Kernel Application, except as defined by Copyright Law. INVALID CDLT DISTRIBUTIONS AND RECOURSE Copyright of contents of a CDLT Distribution is not influenced by status of the Distribution as Valid or Invalid. A CDLT Distribution is not rendered Invalid by defects and bugs, however if the CDLT Distribution charges a fee for use then the Developer is liable to correct such issues within a reasonable time and field a corrected version for download. Any CDLT Distribution proved 'invalid' under these terms has no legal existence. All rights of distribution, copying, installation, use, and litigation for direct or consequential damages, 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 fees paid for access to the Distribution, or its prompt replacement with a valid Distribution. If the CDLT Distribution proved invalid is a Kernel Application, the Kernel developer is liable for refund of License fees to all holders of a Kernel License. An invalid Kernel Distribution impacts all Collaborative Works based upon it and the Kernel Developer is liable for full refund of the standard Kernel License fee to all Collaborative Developers holding a Kernel License. If the CDLT Distribution proved invalid is a Collaborative Work, the Collaborative Work developer is liable for refund of License fees to all holders of a Collaborative Work License. The Kernel Developer is not liable for refund of fees to a Derivative work developer unless it can be demonstrated that the Collaborative Work is invalid as a direct consequence of defects in the Kernel CDLT distribution. LIMITED KERNEL DEVELOPER LIABILITY THE KERNEL DEVELOPER MAKES NO WARRANTY OF FUNCTIONALITY OR NON-INFRINGEMENT. THE COLLABORATIVE 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 COLLABORATIVE 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 CDLT NON-COMPLIANT DERIVATIVE WORKS. RESOLUTION OF LIABILITY IS STRICTLY BETWEEN THE COLLABORATIVE DEVELOPER AND THIRD PARTIES. The Collaborative Developer unconditionally assumes all liability for conforming to local laws and ordinances related to legality of use, taxation and regulation of commerce at the point of distribution of the Collaborative Work. WARNING: ENCRYPTION PERMANENT DATA LOSS HAZARD Any use of Encryption exposes users to Permanent Data-Loss Hazard. Any user of CDLT Licensed Encryption software acknowledges and accepts full responsibility for secure un-encrypted backup of important content, verification of correct end-to- end Encryption software operation, and secure crypto-key management. There is no claim of compatibility across different Crypto systems. Under no 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 Collaborative Works based upon this software, or its components. The Kernel Developer makes no warranties or representations whatsoever regarding the kernel application or any Collaborative Works, and is not liable for defective, illegal, malicious, fraudulent or infringing Collaborative 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 beyond refund of License fees. BUSINESS ENTITIES: CDLT DERIVATIVE WORK CONTRACTED AS A 'WORK FOR HIRE' Business entities wishing to implement enhancements to a Kernel Application for re-distribution as a separate work, or for internal use, may contract for such development with any party as a 'work for hire'. Disposition of unique source code, trade secrets, and distribution rights to the Collaborative Work under CDLT License, are as specified by terms of Contract. CDLT terms of License unconditionally supersede Work for Hire contract terms. Transfer of IP of a 'work for hire' is strictly limited to new and unique development described by 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' may require transfer of pre-existing Kernel Application IP in any form, including Kernel IP developed outside contract necessary to host a Collaborative Work-for-hire. Unless the Kernel Application developer is a direct Contract signatory, they are not legally encumbered and do not fall under any liability or obligation as the result of any 'work for hire' involving the Kernel Application. There is no 'implied support'. However, there is no prohibition upon voluntary support. Existence of a Derivative Work or 'work for hire' does not encumber existing Kernel Application development or distribution, nor any concurrent or future Kernel Application development, except as constrained by explicit Contract terms to which the Kernel Developer is a signatory, or by Copyright Law.