Drafted with AI assistance, then checked and revised by the author. The judgements and the errors are the author’s. How this site is written sets out what is declared on every piece, who checks it, and where the per-piece record lives.
What this publication does not claim, and what is outstanding against it in the register.
A question this rests on is parked: What do we do with an application that refuses to run inside the boundary?
We do not claim that a member's existing applications can be made to run inside the boundary. We claim only that the boundary reveals which ones cannot.
What this publication rests on, and how solid each part of it is. What happened to your software is an essay, and this page describes it as one.
No external citations. This publication cites no studies, no reports and no outside sources, and this page does not manufacture any. Its claims either derive from the constitution this project is built on, or from evidence recorded inside the corpus, or they are the reasoning of the document itself. Each is separated below.
Foundational documents. These are positions this project has taken, not findings.
| Record | What it is | Status |
|---|---|---|
CON-01 |
Purpose | draft v0.1 |
Records of things checked or observed. Every evidence record in this corpus is currently a draft at version 0.1 — the marker below is not decoration.
| Record | What it covers | Status |
|---|---|---|
EVD-06 |
Software repricing and forced migration, 2024-2026 | draft v0.1 ⚠️ |
| Record | What it is | Status |
|---|---|---|
CON-29 |
Third-party AI in the data path is discoverable | draft v0.1 |
STR-12 |
Who this is for | draft v0.1 |
Generated from the corpus, not written by hand: this page cannot claim a source the corpus does not hold, and it changes when the records do.
Alongside: the publication · questions and answers · glossary