Apoth3osis Commercial License Addendum v2.1
(Royalty, Restricted Blockchain Use, Dispute Resolution, and Enterprise Terms)

IMPORTANT NOTICE: BY COPYING, ACCESSING, USING, MODIFYING, DISTRIBUTING, DEPLOYING, OR MONETIZING ANY COVERED SOFTWARE, LICENSEE ACCEPTS THIS ADDENDUM.

This Apoth3osis Commercial License Addendum v2.1 (the "Addendum") supplements the Apoth3osis License Stack v1. This Addendum applies to Covered Software made available under the CPGL or CSBL, and to any other distribution of Covered Software that expressly incorporates this Addendum. If Licensor and Licensee enter into a separate written agreement, including a CECL or other signed commercial agreement, that separate agreement controls to the extent of any conflict.

Licensor: Equation Capital LLC, doing business as Apoth3osis Labs ("Apoth3osis" or "Licensor"), contact: rgoodman@apoth3osis.io.

Revision History: Revision 2.1.1 — Section 7.2, which describes the federal tax status of a non-party, updated to reflect that the Internal Revenue Service has issued a determination letter recognizing IAOM as exempt under Section 501(c)(3) and classifying IAOM as a private operating foundation. No operative term of this Addendum was changed: the grants, royalty provisions, blockchain restrictions, artificial-intelligence restrictions, dispute-resolution provisions, remedies, and definitions are identical to Revision 2.1.0, and Section 7.4 (IAOM Is Not a Party) is unchanged. The controlling version identifier for any acceptance is the SHA-256 digest of this document as displayed at the time of acceptance, which is recorded with each acceptance record. An acceptance recorded against an earlier revision remains an acceptance of the revision whose digest that record carries.

Covered Software: The Boundary language, Boundary IR, the HeytingLean stack, LeanCP-extracted Rust artifacts published under the CPGL and CSBL tiers, and any derivative works thereof, in each case to the extent made available by Licensor and expressly designated as subject to the Apoth3osis License Stack v1 (collectively, "Covered Software"). Covered Software is owned by Licensor. Covered Software does not include IAOM Publications, which are governed by Section 7.

Capitalized terms not defined in this Addendum have the meanings given in the applicable base license.

0. Definitions

0.1 "Affiliate" means an entity that directly or indirectly Controls, is Controlled by, or is under common Control with a party.

0.2 "Blockchain Authorization" means a separate written instrument signed by an authorized representative of Licensor that expressly grants rights to use Covered Software with a Blockchain System.

0.3 "Blockchain System" means any distributed ledger, cryptocurrency, smart-contract, tokenization, rollup, sidechain, bridge, sequencer, validator, decentralized-computation, or similar system that records, validates, settles, executes, or replicates state or transactions across multiple nodes using cryptographic, consensus-based, or substantially similar mechanisms. Blockchain Systems include public, private, permissioned, consortium, or hybrid systems; layer-two networks; rollups; state channels; smart-contract execution environments; and systems principally intended to issue, transfer, custody, exchange, settle, or manage digital assets or tokenized rights.

0.4 "Control" means ownership or control, directly or indirectly, of more than fifty percent (50%) of the voting interests of an entity, or the legal power to direct its management or policies.

0.5 "Distribute" or "Distribution" means to provide, sell, sublicense as expressly permitted by the applicable base license, make available, host for third-party access, or otherwise furnish code, binaries, services, or functionality to any third party, including by network access or software-as-a-service delivery.

0.6 "Port" means an adaptation, edition, or version of a Product for a different platform, operating environment, deployment target, or customer channel, or a substantially similar version that is cross-compatible or interoperable with the same core offering.

0.7 "Product" means any product, service, hosted offering, internal tool provided to a third party, application, model-serving stack, compiler pipeline, artifact, or other deliverable that incorporates, links to, depends on, is compiled through, is generated by, or is materially derived from Covered Software.

0.8 "Royalty Product" means any Product that is Distributed or monetized and that directly generates revenue attributable to access to, use of, features of, or benefits provided by that Product. A Royalty Product includes any Port of that Royalty Product. A Product is not a Royalty Product to the extent it qualifies for an exclusion under Section 1.3 or is governed by a separate signed commercial agreement with Licensor.

0.9 "Royalty Revenue" means worldwide gross revenue directly attributable to a Royalty Product, whether received by Licensee, an Affiliate, a publisher, a distributor, a reseller, or another person acting on Licensee's behalf, before deduction for commissions, platform fees, payment-processing fees, or cost of goods sold, but subject to the exclusions in Section 1.3.

0.10 "IAOM" means The Institute for Applied Ontological Mathematics, a Michigan nonprofit corporation.

0.11 "IAOM Publications" means research papers, articles, preprints, formal-proof expositions, educational materials, diagrams, and other scholarly works authored and published by IAOM, together with the copyrights in those works. IAOM Publications are the property of IAOM and are not Covered Software.

1. Royalty-Bearing Commercial Use

1.1 Royalty Rate. Subject to the exclusions and credits in this Addendum, Licensee shall pay Licensor a royalty equal to five percent (5%) of Royalty Revenue for each Royalty Product.

1.2 When Royalties Begin. No royalty is owed on the first USD $1,000,000 in lifetime Royalty Revenue for each Royalty Product. Royalties become payable only on Royalty Revenue in excess of that threshold, and only for calendar quarters that are not excluded under Section 1.3(a).

1.3 Exclusions from Royalty Revenue. The following are excluded from Royalty Revenue:

(a) Quarterly de minimis exclusion. Revenue attributable to a Royalty Product for any calendar quarter in which that Royalty Product generates less than USD $10,000 in gross revenue.

(b) Lifetime exclusion. The first USD $1,000,000 in lifetime Royalty Revenue for each Royalty Product.

(c) Taxes. Sales taxes, value added taxes, goods and services taxes, and similar transaction-based taxes charged to end users and remitted to taxing authorities.

(d) Refunds and reversals. Documented refunds, rebates, credits, chargebacks, and amounts reversed due to fraud or non-payment, but only to the extent previously included in Royalty Revenue.

(e) Indirect revenue. Revenue not directly attributable to Product access, Product functionality, Product features, or in-Product benefits, including revenue from goods or services sold independently of Product access.

(f) Single-client work-for-hire deliveries. Fees paid for a Royalty Product developed for a single client's private internal use under a written agreement that either recognizes the client as the author for copyright purposes or assigns to the client the developer's copyright interest in the deliverable, provided neither the developer nor the client further Distributes that Royalty Product to third parties.

(g) Intra-group internal distributions. Distributions solely to Licensee's Affiliates for internal use, provided no further third-party Distribution occurs.

(h) Ancillary non-software items. Revenue from non-software merchandise or ancillary goods that do not contain embedded functionality or codes that materially affect operation of a Royalty Product.

(i) Donations and grants. Bona fide donations, research grants, prize money, or philanthropic funding not tied to Product access, Product functionality, or in-Product benefits.

(j) Revenue already subject to another Apoth3osis commercial agreement. Revenue for which Licensee has already paid a license fee, royalty, or other commercial consideration to Licensor under a separate signed agreement expressly covering the same Royalty Product.

1.4 Advances and Credits. Any recoupable advance, minimum guarantee, development fund, or similar advance payment directly attributable to a Royalty Product shall be treated as Royalty Revenue when received to the extent it exceeds any applicable exclusion threshold. Any royalty paid on a recoupable advance shall be credited against future royalty amounts otherwise due for the same Royalty Product.

1.5 Release Notice. Before the earlier of (i) first commercial Distribution of a Royalty Product or (ii) first monetization of a Royalty Product, Licensee shall submit a release notice to Licensor using the form at apoth3osis.io/release or another written channel designated by Licensor. Failure to submit a timely release notice does not forfeit any exclusion otherwise available under this Section 1, but constitutes a breach if not cured within thirty (30) days after written notice from Licensor.

1.6 Royalty Reports and Payment.
(a) Timing. Within forty-five (45) days after the end of each calendar quarter, Licensee shall submit a royalty report for each Royalty Product for which (i) royalties are due for that quarter, or (ii) the Royalty Product first exceeds the USD $1,000,000 lifetime threshold during that quarter.
(b) Content. Each royalty report shall state, on a per-Royalty-Product basis, the gross revenue, excluded revenue by category, Royalty Revenue, lifetime Royalty Revenue to date, credits claimed under Section 1.4, and the royalty due.
(c) Payment. All royalties shown as due shall be paid with the applicable quarterly report.
(d) Currency. All figures shall be reported in U.S. dollars. If revenue is received in another currency, Licensee shall convert it using a commercially reasonable, consistently applied exchange-rate source for the applicable reporting period.

1.7 Interest on Late Payments. Any undisputed amount not paid when due accrues interest from the due date until paid at the lesser of (i) the thirty-day average SOFR in effect on the due date plus three percent (3%) per annum, compounded monthly, or (ii) the maximum rate permitted by applicable law.

1.8 Books and Audit.
(a) Records. Licensee shall keep books and records reasonably sufficient to verify compliance with this Section 1 for at least five (5) years after the end of the applicable reporting period.
(b) Audit Right. No more than once in any twelve (12) month period, Licensor may audit those records through an independent auditor bound by reasonable confidentiality obligations, upon at least thirty (30) days' prior written notice and during normal business hours.
(c) Audit Costs. If an audit shows an underpayment of more than five percent (5%) for the audited period, Licensee shall promptly pay the deficiency, accrued interest, and the reasonable out-of-pocket cost of the audit. Otherwise, Licensor shall bear the audit cost.

1.9 Permitted Commercial Channels. Nothing in this Addendum prohibits Licensee from using publishers, contract developers, hosting providers, cloud vendors, payment processors, resellers, or distributors acting on Licensee's behalf, provided that (i) Licensee remains responsible for compliance with this Addendum, and (ii) no such party receives broader rights in Covered Software than are necessary to support the Royalty Product and than Licensee is permitted to confer under the applicable base license.

1.10 Custom Commercial Terms. Licensor may offer alternative commercial terms, including fixed-fee, capped-royalty, seat-based, support-based, or enterprise terms, but only through a separate written agreement signed by an authorized representative of Licensor.

2. Restricted Use with Blockchain Systems

2.1 No Blockchain Rights by Default. Notwithstanding anything to the contrary in the Apoth3osis License Stack v1, no right or license is granted under any public or small-business tier to use Covered Software with a Blockchain System unless Licensor has granted Blockchain Authorization.

2.2 Prohibited Conduct Without Blockchain Authorization. Without Blockchain Authorization, Licensee shall not, and shall not permit any third party to:
(a) deploy Covered Software to, on, through, or for operation in connection with a Blockchain System;
(b) use Covered Software to develop, generate, compile, validate, optimize, deploy, or operate code intended for execution on a live Blockchain System;
(c) embed Covered Software in a validator, node client, bridge, rollup sequencer, oracle, wallet, exchange integration, custody service, or similar Blockchain System component; or
(d) market, distribute, or offer any Product that materially depends on Covered Software for operation of, access to, settlement on, or interaction with a live Blockchain System.

2.3 Permitted Non-Operational Research Uses. The following activities do not, by themselves, violate Section 2.1, provided they do not result in deployment to or operation of a live Blockchain System:
(a) academic, educational, or formal-methods research;
(b) offline generation of Solidity, Yul, EVM bytecode, WebAssembly, Move, or similar artifacts solely for testing, verification, simulation, or non-production analysis;
(c) auditing, verification, reverse engineering, or security analysis of third-party Blockchain Systems, so long as Covered Software is not itself deployed to or operated as part of the Blockchain System; and
(d) use expressly authorized under an active CECL or other signed agreement that specifically grants blockchain-related rights.

2.4 Narrow Construction. Any Blockchain Authorization shall be construed narrowly and only for the specific systems, deployment contexts, and business models expressly identified in the signed authorization.

2.5 Permission Requests. Requests for Blockchain Authorization may be sent to rgoodman@apoth3osis.io. Licensor may approve, deny, condition, or revoke proposed terms in its sole discretion before a definitive written agreement is signed.

3. Governing Law and Dispute Resolution

3.1 Governing Law. This Addendum and any dispute, claim, or controversy arising out of or relating to this Addendum, the Apoth3osis License Stack v1, or any use of Covered Software (each, a "Dispute") are governed by the laws of the State of Michigan, U.S.A., excluding its conflict-of-laws rules. The United Nations Convention on Contracts for the International Sale of Goods does not apply.

3.2 Pre-Arbitration Notice and Negotiation. Before commencing arbitration, the claimant shall send the respondent a written notice describing the Dispute in reasonable detail and stating the relief requested. Senior representatives of the parties shall attempt in good faith to resolve the Dispute during the thirty (30) days after receipt of that notice. Either party may seek temporary injunctive relief under Section 3.7 during that period if needed to prevent imminent harm.

3.3 Binding Arbitration.
(a) U.S.-Only Disputes. If all parties to the Dispute are organized or resident in the United States, the Dispute shall be finally resolved by binding arbitration administered by JAMS under its Comprehensive Arbitration Rules and Procedures in effect when the arbitration is filed. The legal seat of arbitration shall be Oakland County, Michigan.
(b) International Disputes. If any party to the Dispute is organized or resident outside the United States, the Dispute shall be finally resolved by binding arbitration administered by JAMS under its International Arbitration Rules and Procedures in effect when the arbitration is filed. The legal seat of arbitration shall be New York, New York.
(c) Remote Proceedings. Hearings, conferences, and procedural sessions shall be conducted remotely by default, unless the arbitrator determines that an in-person or hybrid proceeding is reasonably necessary for fairness or efficiency.
(d) Language. The arbitration shall be conducted in English.

3.4 Tribunal Composition and Procedure.
(a) Number of Arbitrators. A Dispute seeking less than USD $500,000 in total monetary relief, excluding attorneys' fees and costs, shall be heard by one arbitrator. Any other Dispute shall be heard by three arbitrators.
(b) Emergency Relief. The parties may seek emergency or interim relief from the arbitral institution or emergency arbitrator as permitted by the applicable rules.
(c) Confidentiality. Except as required by law, to enforce an award, or to protect legal rights in connection with the proceeding, the parties shall keep confidential the existence of the arbitration, the non-public materials submitted in the arbitration, and the award.
(d) Award. The award shall be final and binding and may be entered in any court having jurisdiction.

3.5 No Class or Representative Proceedings. Each Dispute shall be brought only in an individual capacity. No arbitrator shall have authority to consolidate claims of unrelated licensees, preside over a class, collective, coordinated, or representative action, or award relief to non-parties.

3.6 Fees and Costs. The arbitrator may award arbitration costs and reasonable attorneys' fees to the substantially prevailing party, or allocate them in another equitable manner, in each case subject to applicable law and the governing arbitral rules.

3.7 Court Relief for IP and Confidentiality Matters. Nothing in this Section 3 prevents Licensor from seeking temporary, preliminary, or permanent injunctive or other equitable relief in any court of competent jurisdiction to protect intellectual property rights, trademark rights, confidential information, or to halt ongoing or threatened violations of Section 2. Seeking such relief does not waive arbitration of the underlying merits.

4. Compliance, Suspension, Termination, and Remedies

4.1 Material Breach. The following constitute material breach:
(a) failure to pay undisputed royalties or other amounts due under Section 1 within fifteen (15) days after written notice of non-payment;
(b) material underreporting of Royalty Revenue, including an underpayment exceeding five percent (5%) for a reporting period, if not cured within thirty (30) days after written notice;
(c) any violation of Section 2 or Section 8;
(d) unauthorized use of the "Apoth3osis-Certified" mark or any confusingly similar mark;
(e) intentional removal, falsification, or concealment of copyright notices, license notices, attribution notices, or provenance metadata included by Licensor;
(f) unauthorized public distribution of CECL-only materials, proprietary proof-layer materials, or other non-public materials furnished by Licensor under confidentiality restrictions;
(g) attempted assignment or transfer in violation of Section 6.3; or
(h) reverse engineering, decompiling, or disassembling any CECL-only object code or other non-public binary distributed by Licensor solely under restrictive commercial terms, except to the extent such restriction is prohibited by applicable law.

4.2 Suspension. Upon written notice, Licensor may immediately suspend Licensee's right to further access, use, or Distribute Covered Software if Licensor reasonably believes Licensee is engaged in conduct described in Sections 4.1(c), 4.1(d), or 4.1(f). For other breaches, Licensor may suspend rights only after the applicable cure period expires without cure.

4.3 Termination. If Licensee does not cure a material breach within the applicable cure period, Licensor may terminate Licensee's rights under the applicable license tier and this Addendum by written notice.

4.4 Effect of Termination.
(a) Licensee shall cease new use and new Distribution of Covered Software, except to the extent a separate written agreement with Licensor expressly permits continued wind-down activity.
(b) Licensee shall pay all amounts accrued and owing through the effective date of termination.
(c) Licensee shall promptly destroy or permanently disable access to any CECL-only materials, proprietary proof-layer materials, or other non-public materials furnished under confidentiality restrictions, and certify such destruction or disablement upon Licensor's reasonable request.
(d) Termination as to Licensee does not retroactively revoke rights previously granted to downstream recipients that lawfully received Covered Software before termination under an applicable public license, except to the extent such recipients are themselves in breach.

4.5 Remedies. Upon breach, and subject to applicable law, Licensor may seek any non-duplicative remedy available at law or in equity, including injunctive relief, recovery of unpaid royalties, interest, audit costs recoverable under Section 1.8, actual damages, and attorneys' fees or costs where permitted by this Addendum, the governing arbitral rules, or applicable law.

4.6 Survival. Sections 1 (for amounts accrued before termination), 2, 3, 4, 5, 6, 7, and 8 survive termination, together with any confidentiality, attribution, trademark-restriction, payment, and audit provisions that by their nature should survive.

5. Apoth3osis Certification and Proprietary Proof Layer (Informational)

5.1 Informational Only. This Section 5 is descriptive only and does not independently grant or restrict rights except as expressly stated elsewhere in the Apoth3osis License Stack v1 or a signed written agreement.

5.2 Public Code Layer and Proprietary Proof Layer. Licensor may make certain public-facing components available under the CPGL, CSBL, and this Addendum, including LeanCP-extracted Rust artifacts, Boundary IR toolchain components, and reference implementations. Licensor may separately maintain a proprietary proof layer, which may include Lean theorem sources, proof scripts, theorem-level provenance metadata, private HeytingLean modules, formal verification pipelines, attestation systems, and related certification materials.

5.3 Apoth3osis-Certified Program. Rights to use the "Apoth3osis-Certified" mark, any attestation bundle, enterprise support commitments, service levels, or proprietary proof-layer materials are not granted by public availability of Covered Software and require a separate written agreement.

5.4 Enterprise Contact. Enterprise customers seeking certification rights, attestation materials, service levels, support, or other custom terms should contact rgoodman@apoth3osis.io.

6. General Provisions

6.1 Entire Agreement. This Addendum, together with the applicable base license tier and any document expressly incorporated by reference therein, constitutes the complete agreement between Licensor and Licensee concerning its subject matter, unless superseded in whole or in part by a separate signed written agreement.

6.2 Versioning and Amendments. Licensor may publish updated versions of this Addendum at apoth3osis.io/licenses. Unless Licensee expressly accepts an updated version, the version of this Addendum in effect when Licensee first obtained a particular version of Covered Software governs that version of Covered Software. Covered Software first obtained after publication of an updated Addendum may be offered subject to the updated Addendum.

6.3 Assignment.
(a) Licensee may not assign or transfer this Addendum or any rights under it, whether by operation of law or otherwise, without Licensor's prior written consent, except in connection with a merger, reorganization, or sale of substantially all of Licensee's relevant assets, provided the assignee agrees in writing to be bound by this Addendum.
(b) Licensor may assign this Addendum to an Affiliate or successor in interest.
(c) Any purported assignment in violation of this Section 6.3 is void.

6.4 Severability. If any provision of this Addendum is held unenforceable, that provision shall be enforced to the maximum extent permitted and the remainder shall remain in effect.

6.5 No Waiver. Failure or delay by Licensor to exercise any right under this Addendum does not waive that right.

6.6 Notices. Notices under this Addendum must be in writing and may be given by email, courier, or other written means reasonably calculated to provide notice. Notices to Licensor shall be sent to:

Equation Capital LLC d/b/a Apoth3osis Labs
Attn: Richard Goodman
rgoodman@apoth3osis.io
apoth3osis.io

6.7 Order of Precedence. In the event of conflict, the following order of precedence applies: (i) a separate signed written agreement between Licensor and Licensee; (ii) this Addendum; and (iii) the applicable base license tier.

6.8 Interpretation. Headings are for convenience only. "Including" means "including without limitation." Any ambiguity shall not be construed against either party solely on the ground that the party drafted the provision.

7. The Institute for Applied Ontological Mathematics

7.1 Ownership. Covered Software is owned by Licensor, Equation Capital LLC. Neither IAOM nor any other person is the owner or licensor of Covered Software.

7.2 IAOM Status. IAOM is a Michigan nonprofit corporation. The Internal Revenue Service has recognized IAOM as exempt from federal income tax under Section 501(c)(3) of the Internal Revenue Code and has classified IAOM as a private operating foundation. Nothing in this Addendum represents that any payment under this Addendum is deductible as a charitable contribution. IAOM's status is not a term of this Addendum, and IAOM's status has no effect on Licensee's rights or obligations, which run solely between Licensee and Licensor under Section 7.4.

7.3 Licensor's Grant to IAOM. Licensor has granted IAOM a royalty-free, fully paid-up license to use, study, formalize, and publish Covered Software, and to describe and explain it in IAOM Publications, in each case solely in furtherance of IAOM's charitable, scientific, and educational purposes. That license is furnished to IAOM entirely without charge. IAOM pays Licensor no fee, royalty, rent, revenue share, reimbursement, or other consideration of any kind, and Licensor receives no consideration from IAOM.

7.4 IAOM Is Not a Party. IAOM is not a party to this Addendum. No license to Covered Software is granted by, obtained from, or enforced by IAOM. A Licensee's rights and obligations under this Addendum run solely between Licensee and Licensor.

7.5 IAOM Publications. IAOM Publications are the property of IAOM, are not Covered Software, and are not licensed under this Addendum. IAOM publishes IAOM Publications into the public scholarly commons on the terms IAOM designates, at no charge to readers. Nothing in this Addendum restricts any person's access to, or use of, IAOM Publications.

7.6 Hosting. Licensor provides hosting, infrastructure, and technical support for IAOM's public distribution of IAOM Publications, at no charge to IAOM, as a service furnished to IAOM. Licensor acts in that capacity as a service provider to IAOM and not as a licensee of IAOM.

7.7 No Charitable Solicitation. This Addendum is not a solicitation of charitable contributions. Royalties and fees payable under this Addendum are commercial consideration payable to Licensor, a for-profit limited liability company, and are not donations to IAOM or to any charitable organization.

8. Restricted Use for Artificial-Intelligence and Machine-Learning Training

8.1 No Training Rights by Default. Notwithstanding anything to the contrary in the Apoth3osis License Stack v1, no right or license is granted under any public or small-business tier to use Covered Software as training data, evaluation data, or reference material for the development of any artificial-intelligence or machine-learning model, unless Licensor has granted a separate written authorization signed by an authorized representative of Licensor ("AI Authorization").

8.2 Prohibited Conduct Without AI Authorization. Without AI Authorization, Licensee shall not, and shall not permit any third party to, use Covered Software, or any formal proof, Boundary IR, Lean theorem script, LeanCP-extracted artifact, or provenance metadata comprised within Covered Software, for:
(a) pre-training, training, fine-tuning, instruction-tuning, distillation, or reinforcement learning of any artificial-intelligence or machine-learning model;
(b) generation of synthetic training or evaluation data derived from Covered Software;
(c) construction of a benchmark, evaluation harness, or leaderboard dataset distributed to third parties; or
(d) retrieval-augmented generation, embedding, or indexing of Covered Software into a corpus made available to third parties.

8.3 Permitted Uses. The following do not, by themselves, violate Section 8.1:
(a) use of an artificial-intelligence coding assistant or similar tool by Licensee to read, write, or modify Licensee's own code that interoperates with Covered Software, provided Covered Software is not retained, transmitted, or used for model training by the tool's provider;
(b) academic or formal-methods research about Covered Software that does not train, tune, or distill a model on it and does not redistribute it as a dataset;
(c) ordinary search-engine indexing for the purpose of directing human readers to Licensor's or IAOM's published materials; and
(d) use expressly authorized under an active CECL or other signed agreement that specifically grants artificial-intelligence or machine-learning rights.

8.4 Liquidated Damages. The Parties acknowledge that a violation of Section 8.1 causes harm that is real but difficult to quantify, because Covered Software, once absorbed into model weights, cannot be practicably withdrawn. Accordingly, for each Product or model trained, tuned, or distilled in violation of Section 8.1, Licensee shall pay Licensor liquidated damages of USD $1,000,000, indexed annually to CPI-U (Series CUUR0000SA0) from calendar year 2025. The Parties agree this amount is a reasonable forecast of just compensation and is not a penalty. This remedy is in addition to injunctive relief available under Section 3.7 and is in lieu of, not in addition to, actual damages for the same violation.

8.5 Automated Access. Sections 8.1 and 8.2 bind any person or system that accesses Covered Software, including automated agents, crawlers, scrapers, and artificial-intelligence systems acting on behalf of any natural or legal person. Acceptance occurs on the conduct described in the Effective Date provision below.

8.6 Scope. This Section 8 restricts use of Covered Software only. It does not restrict use of IAOM Publications, which IAOM publishes into the public scholarly commons on the terms IAOM designates.

Effective Date: The date on which Licensee first copies, accesses, uses, modifies, Distributes, deploys, or monetizes Covered Software subject to this Addendum.

Version: v2.1. Supersedes the IAOM Commercial License Addendum v1 for all Covered Software obtained on or after the date this version is published. See Section 6.2.