READER BOUNDARY
Institutional draft and public corpus route; not proof of external validation or scientific acceptance.
16. Licensing System and Use Restrictions
This section provides the introductory context and foundational overview for this document.
16.1 Purpose of the Licensing System
The GILC licensing system defines how GILC, Digital Fabrica Theory, scrolls, kernels, protocols, documents, code, legal templates, scientific materials, and deployment systems may be used.
Licensing is necessary because GILC contains several categories of protected material: institutional documents, research frameworks, software infrastructure, legal scrolls, governance protocols, educational content, scientific compendia, and applied system designs.
The licensing system has three purposes.
First, it protects authorship and custodianship. Second, it enables legitimate research, institutional, and commercial use. Third, it prevents uses that conflict with the ethical, legal, or public-benefit purpose of GILC.
Licensing is not treated as a static PDF agreement. It is treated as a scroll-governed permission structure.
A license is Thus, represented as a scroll:
This ensures that licensing terms can be versioned, reviewed, amended, revoked, and linked to the broader semantic braid.
16.2 Licensing Principles
GILC licensing is based on several principles.
The first principle is attribution. Authorship and institutional custodianship must remain visible and verifiable.
The second principle is ethical use. A license cannot authorize activity that violates GILC€™s ethical constraints.
The third principle is scope discipline. A license must define what is permitted, what is prohibited, who may use the material, under what conditions, and for how long.
The fourth principle is revocability for breach. A license that is materially violated may be revoked through defined procedures.
The fifth principle is scroll inheritance. Derivative works must preserve licensing metadata and parent lineage.
The sixth principle is jurisdictional compatibility. Licenses must remain interpretable under both semantic jurisdiction and applicable geographic law.
16.3 Licensing Authority
Licenses may be issued only by authorized entities.
The primary licensing authority is the legal custodian, NextFuze EOOD, unless a specific licensing authority has been delegated to GILC USA DAO LLC, a recognized GILC body, or an authorized licensing officer.
This can be represented as:
Where
A license issued by an unauthorized party is invalid within the GILC framework.
16.4 License Metadata
Every license scroll must include clear metadata.
Minimum metadata should include:
| Field | Meaning |
|---|---|
| License Class | Type of license granted |
| Issuer | Authorized entity issuing license |
| Licensee | Person or institution receiving license |
| Scope | Materials or systems covered |
| Term | Duration or epoch of license |
| Territory | Geographic or semantic jurisdiction |
| Permitted Uses | Allowed activities |
| Prohibited Uses | Restricted activities |
| Attribution Requirements | Required credit and references |
| Derivative Rules | Conditions for modification or extension |
| Revocation Conditions | Events that terminate license |
| Dispute Mechanism | ScrollCourt or external legal forum |
| Registry Anchor | Scroll identity and verification |
License metadata must be embedded into the scroll header and registry entry.
16.5 License Classes
GILC uses several license classes.
The main classes are:
| License | Primary Use |
|---|---|
| DFT-PRL-1.0 | Public Research License |
| DFT-PL-1.0 | Proprietary License |
| DFT-PVL-1.0 | Private Research and Institutional License |
| DF-SL v1.0 | Default Scroll License |
| ELUL | Ethics-Limited Use License |
These classes may be expanded through governance, but any new license class must be itself issued as a scroll.
16.6 DFT-PRL-1.0 €" Public Research License
The DFT-PRL-1.0 Public Research License permits non-commercial academic, educational, and research use of designated GILC or DFT materials.
It is intended for universities, researchers, students, public-interest reviewers, and academic institutions.
Permitted use may include reading, citation, academic discussion, non-commercial research, classroom use, and limited prototyping for evaluation.
It does not permit commercial deployment, sublicensing, monetized integration, proprietary derivative products, removal of attribution, or use in prohibited domains.
The Public Research License should preserve open intellectual examination while protecting the integrity and authorship of the underlying work.
A basic condition can be expressed as:
provided that attribution, non-commercial status, and ethics restrictions are satisfied.
16.7 DFT-PL-1.0 €" Proprietary License
The DFT-PL-1.0 Proprietary License governs commercial, enterprise, or institutional deployment.
It may apply to software, kernels, CodexStation systems, ScrollChain integrations, enterprise validator tooling, governance systems, AI safety infrastructure, or applied DFT architecture.
A proprietary license requires formal agreement, scope definition, custodian approval, ethics review, and registry entry.
It may include fees, royalties, equity, service terms, audit requirements, confidentiality conditions, and deployment limitations.
A proprietary license must not permit prohibited use.
The proprietary license is represented as:
Activation requires legal and ethics validation.
16.8 DFT-PVL-1.0 €" Private Research and Institutional License
The DFT-PVL-1.0 Private Research and Institutional License permits restricted internal evaluation, secure institutional research, confidential review, pilot testing, or pre-commercial experimentation.
It may be used by government bodies, universities, research institutes, enterprise R&D teams, or strategic partners.
This license is appropriate where materials are not public, but commercial deployment has not yet been authorized.
It may require:
- NDA;
- restricted access;
- limited term;
- no public release;
- no derivative publication without authorization;
- internal-use-only conditions;
- validator oversight;
- upgrade pathway to DFT-PL-1.0 if commercial use begins.
This license allows serious institutional engagement while protecting the corpus and infrastructure from premature or unauthorized deployment.
16.9 DF-SL v1.0 €" Default Scroll License
The DF-SL v1.0 Default Scroll License applies automatically to GILC or DFT scrolls that do not carry another explicit license.
Its purpose is protective.
By default, no reproduction, redistribution, commercial use, AI training, transformation, sublicensing, or derivative integration is permitted unless a superseding license has been issued.
This prevents accidental open licensing.
A default rule may be expressed as:
The Default Scroll License protects unclassified or newly issued materials until a more specific license is assigned.
16.10 ELUL €" Ethics-Limited Use License
The Ethics-Limited Use License, or ELUL, restricts use based on ethical considerations.
ELUL may be attached to any license class. It functions as an ethics overlay.
A scroll may be licensed for research or commercial use but still restricted under ELUL.
ELUL may prohibit:
- weaponized use;
- mass surveillance;
- discriminatory deployment;
- behavioral manipulation;
- exploitative financial engineering;
- unauthorized AI training;
- harmful automation;
- deployment without human oversight;
- use contrary to public-interest constraints.
An ELUL condition may be represented as:
ELUL is central to GILC€™s claim that ethics is structurally embedded.
16.11 Platform-Specific Licensing Extensions
Some applied systems may require platform-specific licenses.
Examples include licenses for CitizenSolar, BSA, YellowChain, CodexStation, national nodes, validator tooling, or other derivative infrastructure.
A platform license must define:
- system covered;
- permitted deployment environment;
- technical access rights;
- data rights;
- validator requirements;
- service obligations;
- legal custodian;
- revocation terms.
A platform license is valid only if linked to the root license structure and registered as a scroll.
16.12 Licensing Inheritance
Derivative works must preserve license lineage.
If
The derivative must include parent license metadata unless explicitly waived by authorized custodians.
A derivative cannot remove attribution, erase lineage, or claim independent origin where it depends on protected GILC materials.
This is essential for preventing unauthorized forks, misattribution, and AI-generated laundering of protected frameworks.
16.13 AI Training Restrictions
GILC materials may not be used for AI training, fine-tuning, embedding, dataset construction, model distillation, or automated derivative generation unless explicitly licensed.
This restriction applies to:
- scroll texts;
- kernel code;
- scientific manuscripts;
- legal templates;
- proof materials;
- governance structures;
- datasets;
- diagrams;
- metadata;
- proprietary terminology.
Unauthorized AI training is treated as a licensing and ethics violation.
A model-use restriction can be represented as:
unless:
where
An authorized AI license must specify model identity, training scope, retention rules, derivative rights, attribution, audit access, and revocation conditions.
16.14 Prohibited Use Domains
GILC prohibits use of its materials, scrolls, kernels, and systems in certain domains.
Prohibited domains include autonomous weapon systems, targeting systems, mass surveillance, discriminatory AI, unlawful behavioral manipulation, exploitative financial infrastructure, unauthorized biometric profiling, malicious cyber operations, and systems designed to bypass accountability.
This does not mean that all public-sector or security-related uses are prohibited. It means that uses violating ethical or legal constraints cannot be authorized.
Prohibited use may be expressed as:
No commercial agreement can override this condition without formal governance amendment, and some restrictions should be non-waivable.
16.15 Attribution Requirements
All permitted uses must preserve attribution.
Attribution should identify the author, custodian, license class, scroll anchor where applicable, and institutional context.
A standard attribution may include:
- author or originator;
- GILC institutional reference;
- NextFuze EOOD custodianship where relevant;
- license class;
- scroll anchor;
- publication date or epoch;
- source registry reference.
Attribution is not only reputational. It is part of legal and semantic integrity.
16.16 License Activation
A license becomes active only after required steps are complete.
The activation sequence is:
A license without registry entry is not fully active within the GILC framework.
16.17 License Revocation
A license may be revoked if the licensee violates terms.
Revocation triggers may include unauthorized sublicensing, prohibited use, failure to attribute, AI training misuse, non-payment, breach of confidentiality, ethics violation, anchor tampering, or refusal to comply with dispute resolution.
Revocation may be represented as:
The revocation must be recorded as a scroll.
Revocation should identify the reason, authority, effective date, affected materials, appeal rights, and enforcement consequences.
16.18 License Expiry
Some licenses expire automatically.
Expiration may be based on calendar time, epoch, completion of pilot, breach event, or failure to renew.
Expiration is different from revocation. Expiration is ordinary termination. Revocation is usually breach-based.
A license term may be represented as:
only if:
unless the license is perpetual.
16.19 Licensing Disputes
Licensing disputes are handled through ScrollCourt or designated external legal processes.
A licensing dispute may involve breach, scope ambiguity, derivative rights, attribution, AI misuse, sublicensing, or commercial terms.
The dispute must produce a decision scroll.
A licensing dispute may be represented as:
16.20 Licensing and National Nodes
CodexStation National Nodes require specific licensing.
A national node license must define:
- host institution;
- Public Hand entity;
- Operational Hand service relationship;
- node rights;
- corpus access;
- validator responsibilities;
- data governance;
- public interface obligations;
- reporting requirements;
- termination conditions;
- brand usage;
- local legal compliance.
No national node should operate without a valid node license or institutional agreement.
16.21 Licensing and Validators
Validators require authorization.
A validator license or certification scroll should define:
- validator identity;
- scope of authority;
- domain competence;
- term;
- conflict-of-interest rules;
- audit obligations;
- revocation conditions;
- compensation or incentive terms;
- confidentiality duties.
Validator authority is not automatic. It is licensed and revocable.
16.22 Licensing and the Operational Hand
The Operational Hand may receive rights to deploy and maintain infrastructure, but these rights are conditional.
The Operational Hand does not own the scientific corpus, does not control validator decisions, does not override Public Hand ethics authority, and does not possess unlimited rights to GILC marks or IP.
Its rights depend on compliance with the institutional firewall.
If it violates the firewall:
This protects GILC€™s public-benefit structure.
16.23 Licensing and Public Hand
The Public Hand may receive rights to operate a national or institutional GILC entity, manage public-facing research activities, host validator processes, and interface with local institutions.
The Public Hand must preserve the GILC mission, ethics rules, and knowledge governance standards.
It may not independently commercialize protected IP outside its authority.
16.24 Licensing Registry
All licenses should be registered.
The licensing registry records:
- license scroll anchor;
- license class;
- issuer;
- licensee;
- term;
- scope;
- status;
- restrictions;
- revocation state;
- dispute history.
A license is easier to enforce when its status is transparent.
16.25 Licensing System Summary
The GILC licensing system protects the intellectual, institutional, and ethical integrity of the ecosystem.
It enables legitimate research, institutional collaboration, commercial deployment, and public benefit use, while preventing unauthorized exploitation, misattribution, unethical deployment, and commercial capture.
Licensing is not an afterthought. It is part of the scroll architecture.