GymAI Source-Available Licence Version 1.0-draft — 2026-08-25 Copyright (C) 2026 José Conti. All rights reserved. ═══════════════════════════════════════════════════════════════════════════════ ⚠ THIS IS A DRAFT AND HAS NOT BEEN REVIEWED BY A LAWYER. It is written to be readable and to state the intent precisely. It is not yet a document to rely on in a dispute. See DRAFTING-NOTES.md for the decisions inside it that are the owner's to confirm, and for the specific questions a lawyer should be asked. ═══════════════════════════════════════════════════════════════════════════════ THIS IS NOT AN OPEN SOURCE LICENCE. It does not meet the Open Source Definition and this software must never be described as open source or as free software. The source is published so that anyone may read it, verify it and run it for themselves; that is not the same thing, and calling it the same thing would be false. 0. DEFINITIONS "the Software" this program and its source code, in whole or in part, in original or modified form. "the Licensor" José Conti, the copyright holder. "you" the person or organisation exercising the permissions below. "prescribe" to use the Software to produce, for a person, any training instruction addressed to them — a weight, a repetition count, a duration, a routine, a plan, a progression, or an adjustment of any of these. "your own use" prescribing to yourself, or to members of your own household. "payment" money or anything else of value given or promised, whether or not it is described as being for the training: a fee, a subscription, a membership, a retainer, a package, a commission, a salary paid to you for providing the training, or an obligation to buy something else. 1. WHAT YOU MAY DO WITHOUT PAYING ANYTHING The Licensor grants you a worldwide, royalty-free, non-exclusive licence to use, copy, modify and self-host the Software, and to run it for your own use, subject to sections 2 to 6. This permission is deliberately generous about everything except one thing. You may read the source, change it, run it on your own machine or your own server, keep your data wherever you like, and never speak to the Licensor. You may also, without payment: (a) prescribe to another person for no payment — a friend, a relative, a training partner, anyone, provided you receive nothing of value for it; (b) run an instance for a group of people who each prescribe to themselves and receive nothing from each other, such as a club whose members simply share a server; (c) use the Software while being paid for something else entirely, where the Software plays no part in what you are paid for; (d) study it, test it, teach with it, write about it, and publish what you find, including things that are unflattering. 2. WHAT REQUIRES A SEPARATE, PAID LICENCE You need a commercial licence from the Licensor to do either of the following: (a) PRESCRIBE TO A THIRD PARTY FOR PAYMENT. You use the Software to prescribe to a person who is not yourself or a member of your household, and you receive payment from that person, from their employer, from their insurer, or from anyone else, in connection with that person's training. This is the whole of the restriction. It is written as CONDUCT and not as a category, deliberately: whether you are "a business" is a matter of opinion, and whether you were paid to tell somebody what to lift is a matter of fact. (b) PROVIDE THE SOFTWARE TO OTHERS AS A SERVICE FOR PAYMENT. You operate the Software, or a modified version, so that other people use it, and you receive payment in connection with that operation. Two consequences that follow from (a), stated so nobody has to guess: - A personal trainer who uses the Software for their OWN training needs no licence. They are prescribing to themselves. - A gym that runs an instance for its paying members DOES need one, whether or not the app is itemised on the bill. The members pay the gym, the gym prescribes to them with this Software, and section 0's definition of payment is met. Commercial licences are available from the Licensor. If you are unsure which side of this line you are on, ask before you rely on a guess. 3. IF YOU MODIFY IT You may modify the Software for any use permitted in section 1. (a) You must not remove or obscure this licence, the copyright notice, or any attribution notice in the Software or its interface. (b) You must not represent a modified version as the Licensor's, or use the Licensor's names, marks or logos to endorse or promote it. Those are not licensed here at all, and no permission in this document extends to them. (c) You may share your modifications with others under this same licence, unchanged. You may not relicense the Software or your modifications of it under any other terms. 4. WHAT IS NOT LICENSED HERE (a) TRADEMARKS AND BRANDING. The names, logos, wordmarks and visual identity associated with the Software are not licensed by this document, in any section, for any purpose. (b) THIRD-PARTY MATERIAL. The Software may include or reference material owned by others — data, media, typefaces, libraries — carrying their own terms. Those terms govern that material, and nothing here overrides them. Where the Software ships such material, it is identified in NOTICE.md. (c) ANY PATENT, except that the Licensor will not assert against you any patent claim the Licensor controls that is necessarily infringed by your permitted use of the Software as distributed. 5. NO WARRANTY, AND ONE THING WORTH READING TWICE THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE LICENSOR BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. In plain words, because this one matters more here than in most software: THIS SOFTWARE TELLS PEOPLE HOW MUCH WEIGHT TO LIFT. It is not medical advice, it is not supervision, and it cannot see you. Lifting is a physical activity in which people are injured. You are responsible for your own training and for anyone you prescribe to. 6. IF YOU BREACH IT Your permissions under section 1 end automatically if you do anything in section 2 without a licence for it. They are reinstated automatically and permanently if you stop, and either the Licensor has not contacted you about it, or — where the Licensor has — you stop within 30 days of being told. This clause exists so that an honest mistake is a conversation and not a catastrophe. 7. GOVERNING LAW [TO BE CONFIRMED BY THE OWNER — see DRAFTING-NOTES.md. This should name the jurisdiction whose law governs the licence and where disputes are heard. It is left blank rather than guessed at, because guessing at it is worse than an obvious gap.] 8. THE COMMERCIAL LICENCE Nothing in this document is the commercial licence of section 2. That is a separate agreement between you and the Licensor, and its terms are whatever that agreement says. # Third-party material in this repository **GymAI** — Copyright (C) 2026 José Conti. Licensed under the terms in `LICENSE`, which is **not** an open source licence and must not be described as one. Everything in this repository is the copyright holder's own work **except** what is listed below. Each entry carries its own terms, and those terms govern that material — nothing in `LICENSE` overrides them, extends to them, or relicenses them. This file exists because a repository that ships somebody else's work without saying so is making a claim it has not earned. It is kept current as material arrives, not at release time. --- ## Typefaces — Geist and Geist Mono **Where:** `docs/design/handoff/project/_ds/*/fonts/` **Terms:** SIL Open Font License 1.1 — the full text is in `OFL.txt` beside the font files. **Copyright:** 2024 The Geist Project Authors — The OFL requires the licence and copyright notice to travel with the font files, which is why the notice sits with them rather than only here. > **How it got here is worth recording.** The design bundle these fonts arrived in *declares* an > `OFL.txt` beside them and does not contain one. That is raised against Design as **DR-001** in > `docs/design/DESIGN-REQUESTS.md`. Rather than carry the defect across, the canonical text was > fetched from the typeface's own upstream and placed with the files. A webfont shipped without its > notice is not a style question. --- ## Design system — PackDesk **Where:** `docs/design/handoff/project/_ds/` **Terms:** delivered as part of a commissioned design engagement. The tokens, the type scale and the component conventions are the delivered design system this product's interface is built on. **Its colour file states that its values are not to be altered**, which this project treats as binding: a value here that disagrees with it is a bug in this project. --- ## What is deliberately NOT here **The exercise dataset's images.** Six of them were referenced by the design bundle and were left out on purpose — see `docs/design/handoff/project/media/README.md`. They belong to `hasaneyldrm/exercises-dataset` under that dataset's own terms, which are **unverified**. This matters beyond six illustrations. The product's exercise library uses **2,648 images and animations** from that dataset, and they are the one part of it that cannot simply be rewritten. **No decision has been taken about them.** When it is, this file is where the answer belongs — and if the answer is that they ship, their terms must be verified first and recorded here before a single build includes them. --- ## The predecessor project This repository is a **clean-room re-implementation**. It is a new work, written from written specifications by people and agents who had not read the implementation it replaces. **No code from the predecessor is present in this repository, and none is expected to be.** The design and the specifications here are this project's own work — commissioned or written — and carry no third-party claim. If code from the predecessor ever does appear here, by any route, that is not a licensing question to be tidied up afterwards: it destroys the independence this repository exists to establish, and it must be reported rather than removed quietly. --- ## Common-password list — SecLists **Where:** `src/server/common-passwords.txt` (generated by `scripts/build-password-blocklist.mjs`) **Terms:** MIT License — *Copyright (c) 2018 Daniel Miessler* — **Taken from:** commit `b0e2fb0d3536c0fd3411eff35067e27ee25f63c5` (2026-09-10), files `Passwords/Common-Credentials/xato-net-10-million-passwords-1000000.txt`, `Pwdb_top-1000000.txt` and `100k-most-used-passwords-NCSC.txt`. **What was kept:** only entries of 15 to 256 code points after NFC, case-folded, de-duplicated and sorted (D-945) — the product refuses anything shorter by length before the list is asked (D-943). The list is consulted locally when a password is chosen, is never displayed, and is never sent anywhere. **The individual lists inside SecLists were gathered from public breach corpora by their compilers; whether shipping them suits the product's own licence is the copyright holder's call, and is flagged in D-945 rather than decided.** --- ## Map library — MapLibre GL JS **Where:** `vendor/maplibre-gl/6.9.0/` (shipped by the console's build under `/console/vendor/maplibre-gl/6.9.0/`) **Terms:** BSD-3-Clause — *Copyright (c) 2023, MapLibre contributors*; the same `LICENSE.txt` carries the BSD-3-Clause licence of mapbox-gl-js v1.13 and earlier (*Copyright (c) 2020, Mapbox*) and the notices of the third-party code it includes — **Taken from:** the published npm package `maplibre-gl@6.9.0` (`maplibre-gl-6.9.0.tgz`, sha256 `06ceb46db05d1d926bf3b113ca59b9458af8c85c7d6a22b4d1996fe7d823e14f`), 2026-09-13. **What was kept:** the three non-development ES modules (`maplibre-gl.mjs`, `maplibre-gl-shared.mjs`, `maplibre-gl-worker.mjs`), the stylesheet and `LICENSE.txt`, **byte for byte**, with a `checksums.txt` that `tests/site/vendor-maplibre.test.js` verifies (D-1148). No development build and no source maps. **Nothing is loaded from a third-party host as a script** (D-623): the library is ours to serve; only the map TILES come from OpenFreeMap, and the OpenStreetMap attribution is shown wherever a map is drawn (D-683). --- ## QR Code encoder — Project Nayuki's QR Code generator library **Where:** `src/lib/qr.js` (the square §29h draws, S-219) **Terms:** MIT License — *Copyright (c) Project Nayuki* — **Taken from:** no file was copied. The module was written in this repository without the library open, and the code review of S-219 found passages that follow the library's JavaScript/TypeScript implementation nearly statement for statement — the Reed–Solomon divisor loop, the format- and version-bit BCH steps, the alignment-position step, the raw-module count, the block split, the format-bit placement and the zigzag. **The notice is kept on that finding (D-1209)**, rather than an origin argued about. **What was kept:** byte mode at error-correction level M only, restructured as pure functions returning frozen values, with its own penalty scoring, argument checks and tests against ISO/IEC 18004's published values. ``` Copyright © Project Nayuki. (MIT License) https://www.nayuki.io/page/qr-code-generator-library Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: - The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. - The Software is provided "as is", without warranty of any kind, express or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose and noninfringement. In no event shall the authors or copyright holders be liable for any claim, damages or other liability, whether in an action of contract, tort or otherwise, arising from, out of or in connection with the Software or the use or other dealings in the Software. ```