From 91d21faa9a376541432645667a61821f5f481e94 Mon Sep 17 00:00:00 2001 From: Nrupal Akolkar <51525601+nrupala@users.noreply.github.com> Date: Mon, 12 Oct 2026 21:54:15 -0600 Subject: [PATCH 1/2] docs: document licence position and add product terms --- LICENSING.md | 34 ++++++++++++++++++++++++++++++++++ TERMS.md | 43 +++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 77 insertions(+) create mode 100644 LICENSING.md create mode 100644 TERMS.md diff --git a/LICENSING.md b/LICENSING.md new file mode 100644 index 0000000..ce15924 --- /dev/null +++ b/LICENSING.md @@ -0,0 +1,34 @@ +# Licensing — axiomcode + +## Current position retained + +Current licence record: **Proprietary licence (root LICENSE)**. + +Existing proprietary licence is retained; no Apache interface carve-out is inferred. + +The existing licence file remains the controlling licence record for this repository in this sweep. This document adds a common place to record that position and connects it to the standard product terms. It does not relicence prior releases and does not reduce rights granted by the existing licence. + +## Standard product terms + +`TERMS.md` contains the portfolio’s standard terms for an official packaged or supplied product: licensor **2351485 ALBERTA INC.**, liability capped at the product price paid, excluded indirect and consequential damages, user-environment responsibility, no absolute security guarantee, consumer-law preservation and severability, and Calgary, Alberta as the venue for litigation, mediation, or arbitration. + +Those product terms supplement an official product supply only to the extent consistent with the repository licence and applicable law. + +## Owner decision recorded for morning review + +This repository is listed as a licence exception in the sweep report. The decision still required is whether the existing licence should remain, or whether a future, repository-specific change should adopt the proprietary-core + Apache-interface split in whole or in part. + +## Access model — documentation only + +Where `axiomcode` is supplied as a runnable product, its supported access modes are documented and governed according to need: + +- **Human access:** the product’s user interface or other human-facing surface. +- **Machine access:** documented command-line, automation, or system-integration surfaces. +- **Agent access:** access by an authorized software agent, only where the product implements it. +- **Software access:** documented embedding, plug-in, library, or integration surfaces. +- **API access:** a documented programmatic interface, where provided. + +Agent authorization, where implemented, uses a key-value record keyed by agent ID. The value contains only a hashed agent token, permitted scopes, expiry, and an enabled/disabled state. A human administrator enrolls, narrows, disables, or revokes an agent; the agent does not receive the human’s master credential. Agent activity is recorded in a tamper-evident, hash-chained audit log where the product provides one. + +This section describes the portfolio access standard. It does not claim that every access mode is implemented in the current release. + diff --git a/TERMS.md b/TERMS.md new file mode 100644 index 0000000..0c6a14e --- /dev/null +++ b/TERMS.md @@ -0,0 +1,43 @@ +# Product Terms — axiomcode + +These Product Terms govern the official packaged or distributed version of **axiomcode** supplied by **2351485 ALBERTA INC.** (the “Company”). They supplement the licence or licences identified in `LICENSING.md`. If a separate written agreement with the Company applies to a particular supply, that agreement controls to the extent of any conflict. + +> **Licence note:** These Product Terms supplement the official product supply only to the extent consistent with the repository licence identified in `LICENSING.md`. They do not reduce rights granted by that licence. + +## 1. Responsible use and user environment + +You are responsible for the devices, networks, operating systems, accounts, credentials, configurations, integrations, and other systems on or with which you choose to use the product. You are also responsible for maintaining suitable backups and security controls for your environment. + +To the maximum extent permitted by applicable law, the Company is not liable for loss or damage to the extent it arises from your action, inaction, or oversight, including exposing the product or its data to a malicious, compromised, unsafe, or otherwise detrimental system or environment. + +## 2. No absolute security guarantee + +The product is designed with defined and limited capabilities. Although security features may be included, the Company does not warrant or guarantee that the product is unbreakable or that it will prevent every compromise, including compromise caused by ransomware, viruses, other malware, a compromised operating system or device, stolen credentials, or attacks outside the product’s control. + +## 3. Your decisions remain yours + +The product is a tool. It does not make business, professional, financial, legal, safety, or operational decisions for you. You must independently evaluate any output or result before acting on it. To the maximum extent permitted by applicable law, the Company is not liable for a business or other decision made solely in reliance on use of the product. + +## 4. Warranty disclaimer + +Except as expressly stated in a separate written agreement and to the maximum extent permitted by applicable law, the product is provided “as is” and “as available,” without warranties of any kind, whether express, implied, statutory, or otherwise, including implied warranties or conditions of merchantability, fitness for a particular purpose, title, non-infringement, uninterrupted operation, or freedom from errors or harmful components. + +## 5. Excluded damages + +To the maximum extent permitted by applicable law, neither the Company nor its suppliers will be liable for indirect, incidental, special, exemplary, punitive, or consequential damages, or for lost profits, lost revenue, lost savings, lost goodwill, loss of use, loss of data, business interruption, or substitute goods or services, even if advised of the possibility of those damages. + +## 6. Aggregate liability cap + +To the maximum extent permitted by applicable law, the Company’s total aggregate liability arising from or relating to the product and these Product Terms is limited to the amount you actually paid the Company for the product or licence giving rise to the claim. If no amount was paid for that product or licence, the cap is zero, except where applicable law prohibits that limitation. + +## 7. Consumer protection and severability + +Nothing in these Product Terms excludes or limits a right or liability that cannot lawfully be excluded or limited. These terms respect applicable consumer-protection laws. If any provision is held unenforceable, it will be modified only to the minimum extent necessary to make it enforceable, or severed if modification is not possible, and the remaining provisions will continue in effect. + +## 8. Governing law and exclusive venue + +These Product Terms are governed by the laws of Alberta and the federal laws of Canada applicable in Alberta. Any litigation concerning the product or these terms must be brought exclusively in the courts located in Calgary, Alberta. Any mediation or arbitration concerning the product or these terms, if used, must be seated and conducted solely in Calgary, Alberta, unless the Company agrees otherwise in writing or applicable law requires otherwise. + +## 9. Contact + +Questions about these Product Terms may be sent to info@pipavia.com. From 6fbe0649c636cc273396435bd7971160eb98ae23 Mon Sep 17 00:00:00 2001 From: Nrupal Akolkar <51525601+nrupala@users.noreply.github.com> Date: Mon, 12 Oct 2026 22:00:39 -0600 Subject: [PATCH 2/2] docs: limit sweep to standard product terms --- LICENSING.md | 34 ---------------------------------- TERMS.md | 4 +--- 2 files changed, 1 insertion(+), 37 deletions(-) delete mode 100644 LICENSING.md diff --git a/LICENSING.md b/LICENSING.md deleted file mode 100644 index ce15924..0000000 --- a/LICENSING.md +++ /dev/null @@ -1,34 +0,0 @@ -# Licensing — axiomcode - -## Current position retained - -Current licence record: **Proprietary licence (root LICENSE)**. - -Existing proprietary licence is retained; no Apache interface carve-out is inferred. - -The existing licence file remains the controlling licence record for this repository in this sweep. This document adds a common place to record that position and connects it to the standard product terms. It does not relicence prior releases and does not reduce rights granted by the existing licence. - -## Standard product terms - -`TERMS.md` contains the portfolio’s standard terms for an official packaged or supplied product: licensor **2351485 ALBERTA INC.**, liability capped at the product price paid, excluded indirect and consequential damages, user-environment responsibility, no absolute security guarantee, consumer-law preservation and severability, and Calgary, Alberta as the venue for litigation, mediation, or arbitration. - -Those product terms supplement an official product supply only to the extent consistent with the repository licence and applicable law. - -## Owner decision recorded for morning review - -This repository is listed as a licence exception in the sweep report. The decision still required is whether the existing licence should remain, or whether a future, repository-specific change should adopt the proprietary-core + Apache-interface split in whole or in part. - -## Access model — documentation only - -Where `axiomcode` is supplied as a runnable product, its supported access modes are documented and governed according to need: - -- **Human access:** the product’s user interface or other human-facing surface. -- **Machine access:** documented command-line, automation, or system-integration surfaces. -- **Agent access:** access by an authorized software agent, only where the product implements it. -- **Software access:** documented embedding, plug-in, library, or integration surfaces. -- **API access:** a documented programmatic interface, where provided. - -Agent authorization, where implemented, uses a key-value record keyed by agent ID. The value contains only a hashed agent token, permitted scopes, expiry, and an enabled/disabled state. A human administrator enrolls, narrows, disables, or revokes an agent; the agent does not receive the human’s master credential. Agent activity is recorded in a tamper-evident, hash-chained audit log where the product provides one. - -This section describes the portfolio access standard. It does not claim that every access mode is implemented in the current release. - diff --git a/TERMS.md b/TERMS.md index 0c6a14e..824febe 100644 --- a/TERMS.md +++ b/TERMS.md @@ -1,8 +1,6 @@ # Product Terms — axiomcode -These Product Terms govern the official packaged or distributed version of **axiomcode** supplied by **2351485 ALBERTA INC.** (the “Company”). They supplement the licence or licences identified in `LICENSING.md`. If a separate written agreement with the Company applies to a particular supply, that agreement controls to the extent of any conflict. - -> **Licence note:** These Product Terms supplement the official product supply only to the extent consistent with the repository licence identified in `LICENSING.md`. They do not reduce rights granted by that licence. +These Product Terms govern the official packaged or distributed version of **axiomcode** supplied by **2351485 ALBERTA INC.** (the “Company”). They are additive: they do not change, replace, or limit the licence that applies to this repository’s source code or content. If a separate written agreement with the Company applies to a particular supply, that agreement controls to the extent of any conflict. ## 1. Responsible use and user environment