Skip to content

Personal AI agent for macOS, Windows, Linux, Android & iOS. Set a goal, it works alone: coding (Skales Code), desktop + browser automation, autonomous scheduled Tasks. Teams of agents and humans across paired desktops. Agent2Agent, MCP, computer use, voice, local LLMs (Ollama), Agent Skills (SKILL.md). 26 AI providers, BYOK. No Docker, no terminal.

The documents here are the ones from the build, not a second set

Mario Simic553ff87785e8
diff --git a/COMMERCIAL-LICENSE.md b/COMMERCIAL-LICENSE.md
index 85ef8e0..5e6907f 100755
--- a/COMMERCIAL-LICENSE.md
+++ b/COMMERCIAL-LICENSE.md
@@ -1,42 +1,72 @@
# Commercial Licensing - Skales
-Skales is proprietary software, supplied under the **Skales End User Licence
-Agreement** ([LICENSE](./LICENSE), published with every earlier version at
-[skales.app/licence](https://skales.app/licence)).
+Skales is proprietary software, licensed and not sold, under the
+[Skales End User Licence Agreement](./LICENSE), version 1.2 of 14 September
+2026. It is not open source, and no source code is provided or promised. This
+page is the short reading of the licence; where the two could be read
+differently, the licence decides. The current version of the agreement is
+published at https://skales.app/licence.
## Free Use
-The following uses are **free of charge** and require no license agreement:
+The following uses are **free of charge** and require no licence agreement:
- **Private individuals** using Skales for personal, non-commercial purposes
-- **Students and educational institutions** using Skales for learning or academic work
+- **Students, teachers and non-commercial educational institutions** using
+ Skales for learning or academic work
-## Commercial Use Requires a License
+## Evaluation
-Any of the following activities require a **written commercial license** from the author:
+Any organisation may install Skales to **evaluate it for thirty (30) days**.
+After that, the use is either covered by a written commercial licence or it
+ends.
-- Use by a company, organization, or team in a professional or business context
-- Offering Skales or a derivative as a hosted service (SaaS)
-- Redistributing or reselling Skales as part of a commercial product
-- Any use generating direct or indirect commercial revenue
+## Commercial Use Requires a Licence
-Using Skales commercially without a licence is outside the agreement. It was
-outside the Business Source Licence 1.1 that governed releases up to and
-including 12.9.27 as well, whose Additional Use Grant covered personal use,
-learning and non-commercial internal testing only.
+Any of the following requires a **written commercial licence** from the author:
+
+- Use by or for a company, a business, a team, or a public body
+- Offering Skales, or any service built on it, as a hosted, managed or
+ software-as-a-service offering
+- Rebranding, white-labelling, reselling, sublicensing, renting or
+ redistributing Skales, in whole or in part
+- Bundling Skales with another product, brokering access to it, or submitting
+ it to an app store or any other distribution channel
+- Managed distribution of the mobile application inside an organisation
+- Any use in exchange for money or other consideration
+
+Using Skales in any of these ways without a written licence is a breach of the
+licence and ends it.
+
+## What No Licence Covers
+
+Some things are outside the free use above and cannot be bought as a commercial
+licence either, because they are not a question of scale:
+
+- Running Skales in a modified form, or removing or bypassing its integrity,
+ attestation, licence or authentication mechanisms
+- Operating Skales as a component, backend, agent engine or library of another
+ program: a wrapper around its local server, another tool launching its
+ command-line interface, a third-party client against its relay or online
+ services, or bulk collection of its output, including for training models
+- Re-signing, side-loading or redistributing the mobile application package
+- Presenting yourself as a partner, reseller, certified provider, co-developer
+ or spokesperson of Skales or Mario Simic, or claiming that Skales is part of,
+ based on, or endorses another product
+
+Using Skales' own tools on your own device stays free, and you may always say
+factually that your setup runs or installs Skales.
## Contact
-To obtain a commercial license or inquire about pricing:
+To obtain a commercial licence or inquire about pricing:
**Mario Simic**
Website: https://skales.app
-Commercial licensing starts with an evaluation licence: free of charge, the
-full scope, no seat limit, confirmed in writing with an end date. The commercial
-terms after it are set with the first design partners, so write and tell us what
-you need.
+Pricing is determined individually based on use case and scale. Contact us to
+discuss your needs.
---
diff --git a/PROOF_OF_AUTHORSHIP.md b/PROOF_OF_AUTHORSHIP.md
index 6ebe407..0528fa2 100644
--- a/PROOF_OF_AUTHORSHIP.md
+++ b/PROOF_OF_AUTHORSHIP.md
@@ -6,19 +6,59 @@ Skales is the original work of Mario Simic, Vienna, Austria.
- **Original Author**: Mario Simic
- **First Commit**: January 2026
-- **Licence**: Skales End User Licence Agreement (proprietary)
+- **Licence**: the Skales End User Licence Agreement, version 1.2 of 14 September 2026 ([LICENSE](./LICENSE)) - proprietary, never open source; the current version is published at https://skales.app/licence
- **Apple Developer ID**: Mario Simic (Q5ASU2DB6P)
- **Domain**: skales.app (registered 2025)
- **GitHub**: github.com/skalesapp/skales
- **Portfolio**: mariosimic.at
- **Current Version**: 12.9.30 (September 2026)
+- **Brand terms**: [TRADEMARK.md](./TRADEMARK.md) (the name, logo and product names are not granted by the licence)
## Integrity
Skales binaries are signed and verified.
+### Source watermarks
+
+The source carries authorship markers that must not be stripped:
+
+- Named DNA markers: `orchestrator.ts` (calculate_entropy_offset=2) and `chat.ts` (_responseQuality=5).
+- A zero-width authorship watermark in the header comment of several source files: a repeating unit of U+200B / U+200C / U+200D / U+FEFF. The same unit appears in `orchestrator.ts`, `chat.ts`, `themes.ts`, `cron-scheduler.ts`, `layout.tsx`, and `memory/page.tsx`, and has been present since the initial snapshot. This is intentional and original; it is the single sanctioned exception to the house rule against literal invisible characters in source. Never add new invisible characters elsewhere.
+
+### Shipped-artifact marks
+
+Valid from release **12.9.30** (desktop) and **2.9.30** (mobile), recorded
+2026-09-13.
+
+The markers above prove authorship of the **source**. They say nothing to
+somebody who only ever received a **binary**, because a minifier renames local
+identifiers and strips comments, so none of them survives a build. From the
+releases named above, a shipped artifact carries marks of its own. Listed here
+by class only:
+
+1. **Attestation manifest** - each package records what its own packaged files
+ are, and the app reads that record back after it starts.
+2. **Bytecode** - part of the desktop half ships compiled rather than as text,
+ bound to the engine version and processor architecture it was built for.
+3. **Build stamp on the wire** - every build has an identity of its own and
+ presents it, together with its own integrity verdict, wherever it talks to
+ our services. An artifact that is not in our release record is not ours.
+4. **Data-value marks** - marks that survive minification because they are
+ values rather than names, carried in shipped data rather than in code.
+5. **Private register** - the authoritative list of which mark sits where, with
+ its value, its check command, its build-in date and its first release, is
+ kept **outside every repository**. Its shape is
+ `_koordination/MARKEN-REGISTER.local.md.template` in the workspace.
+
+Neither the values nor the locations of any mark are written down here, in any
+repository, in any code comment, in any test name, or in any changelog. This
+document is the statement that they exist and from which release they apply;
+the register is the evidence, and it is produced on request in a dispute, not
+published.
+
## Copyright
2025-2026 Mario Simic. All rights reserved.
-Licensed free of charge for private and educational use.
-Commercial use requires a written licence.
\ No newline at end of file
+Licensed under the Skales End User Licence Agreement: free for private and
+educational use, thirty days of evaluation for an organisation, everything else
+by written commercial licence. See [LICENSE](./LICENSE).
\ No newline at end of file
diff --git a/README.md b/README.md
index c0a5b64..dca679f 100644
--- a/README.md
+++ b/README.md
@@ -43,20 +43,15 @@ An AI agent that runs on your own computer, with access to your files, browser,
**[⬇ Download](https://skales.app)** · **[📖 Docs](https://docs.skales.app)** · **[🎬 Demo](https://www.youtube.com/watch?v=k83NlptVmfc)** · **[📝 Changelog](./CHANGELOG.md)** · **[💬 Community](https://github.com/skalesapp/skales/discussions)**
> **About this repository.** This is where Skales is *distributed*: releases,
-> the changelog, install guides and the issue tracker. Skales is proprietary
-> software, and the product is the signed application you download from
-> [skales.app](https://skales.app).
+> the changelog, install guides and the issue tracker. Skales itself is
+> proprietary and stays proprietary, and the product is the signed application
+> you download from [skales.app](https://skales.app).
>
-> A **v7 source snapshot** stood in this repository until 12.9.30 and was
-> removed with that release. Its last code commit was 26 July 2026 and it had
-> long stopped describing the product: 138 TypeScript files against 984 in the
-> tree that is built, 70 API routes against 225. It drew four security reports
-> about code the shipped application does not contain.
->
-> From 12.9.30 onward Skales is supplied under the Skales End User Licence
-> Agreement. Releases up to and including 12.9.27 were supplied under the
-> Business Source Licence 1.1, and a copy supplied under it keeps what that
-> licence granted.
+> A **v7 source snapshot** stood here until 12.9.30 and was removed with that
+> release. Its last code commit was 26 July 2026 and it had long stopped
+> describing the product: 138 TypeScript files against 984 in the tree that is
+> built, 70 API routes against 225. It drew four security reports about code the
+> shipped application does not contain.
>
> Reporting a security issue? Please read
> [SECURITY.md](https://github.com/skalesapp/skales/blob/main/SECURITY.md) first. It says what is in scope, and it will save
@@ -408,9 +403,17 @@ No vendor lock-in. Bring your own key, or run locally for free.
## 📜 License
-Skales is **proprietary software**: free of charge for private and educational use, commercial use by written licence. Hosting it for other people, rebranding it, reselling it and reverse engineering it are outside the licence. See [LICENSE](./LICENSE) for the full terms, or the published copy of every version at [skales.app/licence](https://skales.app/licence).
-
-Releases up to and including 12.9.27 were supplied under the Business Source Licence 1.1, and a copy supplied under it keeps what that licence granted.
+**Skales End User Licence Agreement**: proprietary software, licensed and not
+sold. Free for private and educational use, thirty days of evaluation for an
+organisation; company use, hosting, white-labelling and redistribution need a
+written commercial licence. Skales is not open source and will not become open
+source. See [LICENSE](./LICENSE) for the full terms, [TRADEMARK.md](./TRADEMARK.md)
+for the brand half and [COMMERCIAL-LICENSE.md](./COMMERCIAL-LICENSE.md) for the
+short reading. Every version is published at
+[skales.app/licence](https://skales.app/licence).
+
+Releases up to and including 12.9.27 were supplied under the Business Source
+Licence 1.1, and a copy supplied under it keeps what that licence granted.
WordPress Plugin: **MIT**, [github.com/skalesapp/wordpress](https://github.com/skalesapp/wordpress)
diff --git a/TRADEMARK.md b/TRADEMARK.md
new file mode 100644
index 0000000..44844f1
--- /dev/null
+++ b/TRADEMARK.md
@@ -0,0 +1,7 @@
+Skales Trademark Notice
+
+"Skales", the Skales logo, and the names Skales Desktop, Skales Mobile, Skales Code, Skales IQ, Skales Relay, Skales Local, Skales Pocket, Iris Orbit, and Lio are trademarks of Mario Simic, Vienna, Austria.
+
+You may refer to Skales by name to describe, review, or link to the unmodified original software. You may not use these names or the logo on a modified, rebranded, or redistributed copy, in a product name, domain, app-store listing, or company name, or in any way that suggests endorsement by or affiliation with Skales.
+
+Questions and permissions: [email protected]
diff --git a/docs/skales-guide.html b/docs/skales-guide.html
index 7b557bc..883e83b 100644
--- a/docs/skales-guide.html
+++ b/docs/skales-guide.html
@@ -1,50 +1,4 @@
<!DOCTYPE html>
-<!--
-summary: "The chaptered end-user guide rendered inside the app: what every feature is and how a user drives it."
-read_when:
- - you shipped a user-visible feature and the guide must describe it
- - you need the established wording for a feature as users see it, not as the code names it
--->
-<!--
- THIS IS USER HELP. RELEASE NOTES BELONG IN CHANGELOG.md AND IN THE CHANGELOG
- VIEW, NEVER HERE.
-
- Written into the file because saying it elsewhere has not worked: release
- chapters have grown back into this guide three times, and by 12.5.76 there
- were five of them ("What's New in 12.5.7", "12.5.6", "12.5.1 to 12.5.5",
- "12.5.0", "12.4.5"). They were removed in 12.5.8 after checking that every one
- of those versions is in CHANGELOG.md.
-
- The distinction is not bookkeeping. This document answers "how do I do X" and
- is read by someone with a question in front of them; a changelog answers "what
- changed in version N" and is read once, by someone who already knows the
- product. A guide that carries both ages badly in a specific way - the newest
- release chapter sits at the top, so the first thing a new user reads is a list
- of things they have no idea they were missing.
-
- If a release adds something worth explaining, explain it in the CHAPTER FOR
- THAT FEATURE. That is the change the guide should carry.
-
- ---------------------------------------------------------------------------
- STRUCTURE (12.7.2). One file, on purpose, and the reasons are load-bearing:
-
- * fetch_skales_docs (actions/orchestrator.ts) reads exactly
- public/docs/skales-guide.html and splits it on h1-h3. Splitting the guide
- into chapter files would take the app's own manual away from the app.
- * docs.skales.app and the public repo carry this single file too.
-
- So the chapters are inside it. Every chapter is a <section data-lead> landing
- page followed by its own <section id>s; the sidebar is the table of contents;
- one chapter is on screen at a time; the search at the top of the sidebar
- indexes every heading and every paragraph of every chapter, including the
- ones that are not currently shown. Pure CSS and inline script, nothing
- fetched, so it behaves identically inside the app and in a browser, online or
- off.
-
- Adding a chapter: add a <div class="section-label" data-chapter="x"> plus its
- links to the nav, and give the sections the same ids. Everything else - the
- routing, the search index, the prev/next footer - follows from the nav.
--->
<html lang="en">
<head>
<meta charset="UTF-8" />