Skip to content

Commit c777825

Browse files
marklearstmarklearst
committed
feat(license): add CC BY-ND 4.0 with Standards Integrity Addendum
- Replace CC BY 4.0 with CC BY-ND 4.0 base license - Add Standards Integrity Addendum with AI laundering restrictions - Define conformance tiers (Conformant vs Compatible) - Add automatic termination and enforcement provisions - Create JSON Schema v1 for variable validation - Add 6 technical conformance tests - Add W3C-style metadata table to homepage - Update FAQ to remove "open source" claim BREAKING CHANGE: License updated from CC BY 4.0 to CC BY-ND 4.0 with additional restrictions on derivative standards and AI-generated content.
1 parent 41978ba commit c777825

9 files changed

Lines changed: 1117 additions & 8 deletions

File tree

‎LICENSE‎

Lines changed: 170 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,173 @@
1-
Creative Commons Attribution 4.0 International
1+
VARIABLES CONTRACT SPECIFICATION LICENSE
22

3-
This work is licensed under the Creative Commons Attribution 4.0 International License.
3+
Copyright (c) 2021-2026 Mark Learst
44

5-
To view a copy of this license, visit:
5+
================================================================================
6+
PART I. BASE LICENSE (CC BY-ND 4.0)
7+
================================================================================
68

7-
https://creativecommons.org/licenses/by/4.0/
9+
This Specification is licensed under the Creative Commons Attribution-
10+
NoDerivatives 4.0 International License (CC BY-ND 4.0).
11+
12+
You are free to:
13+
14+
- Share: Copy and redistribute the Specification in any medium or format
15+
- Implement: Build software that conforms to the Specification
16+
17+
Under the following terms:
18+
19+
- Attribution: You must give appropriate credit, provide a link to the
20+
license, and indicate if changes were made.
21+
- NoDerivatives: If you remix, transform, or build upon the Specification,
22+
you may not distribute the modified specification as an alternative standard.
23+
24+
Full license text: https://creativecommons.org/licenses/by-nd/4.0/legalcode
25+
26+
================================================================================
27+
PART II. ADDITIONAL TERMS (STANDARDS INTEGRITY ADDENDUM)
28+
================================================================================
29+
30+
The following additional terms apply to uses of this Specification beyond
31+
personal reference and internal implementation. These terms are designed to
32+
prevent ecosystem fragmentation and protect standards integrity.
33+
34+
By using this Specification in any public-facing capacity, you agree to these
35+
additional terms.
36+
37+
---
38+
39+
## A. DEFINITIONS
40+
41+
"Specification" means the Variables Contract protocol, including all documentation,
42+
JSON schemas, naming conventions, governance rules, architectural patterns, and
43+
code examples published at the Canonical Source.
44+
45+
"Canonical Source" means https://variables-contract.vercel.app
46+
47+
"Synthetic Derivative" means any work produced by inputting the Specification
48+
into a Generative AI system, Large Language Model, or similar automated system
49+
for the purpose of generating rephrased, restructured, or "original" content
50+
that replicates the structure, methodology, or technical approach of the
51+
Specification.
52+
53+
"Conformant Implementation" means software that fully implements the Specification:
54+
Variable Anatomy (Base, Alias, Component), Mode resolution, Reference syntax,
55+
DTCG-aligned JSON structure, and Naming conventions.
56+
57+
---
58+
59+
## B. ATTRIBUTION REQUIREMENTS
60+
61+
B.1 PUBLIC TOOLING
62+
Any public-facing software claiming compatibility with the Specification must
63+
include attribution visible to end users:
64+
65+
"Built on the Variables Contract Specification
66+
https://variables-contract.vercel.app"
67+
68+
B.2 METADATA ATTRIBUTION
69+
JSON files claiming conformance should include:
70+
71+
"$schema": "https://variables-contract.vercel.app/schema/v1.json"
72+
73+
---
74+
75+
## C. CONFORMANCE CLAIMS
76+
77+
C.1 "VARIABLES CONTRACT CONFORMANT"
78+
To claim conformance, an implementation must:
79+
a. Support full Variable Anatomy (Base, Alias, Component)
80+
b. Support Mode resolution and inheritance
81+
c. Support Reference syntax and resolution
82+
d. Output valid DTCG-aligned JSON with references (not flattened values)
83+
e. Enforce or validate Naming conventions
84+
85+
C.2 "VARIABLES CONTRACT COMPATIBLE"
86+
To claim compatibility, an implementation must:
87+
a. Not corrupt Specification-compliant data
88+
b. Include Attribution per Section B
89+
90+
C.3 FALSE CLAIMS
91+
Claiming conformance or compatibility while failing to meet requirements
92+
constitutes fraud and breach of these terms.
93+
94+
---
95+
96+
## D. PROHIBITED ACTS
97+
98+
D.1 SYNTHETIC DERIVATIVES (AI LAUNDERING)
99+
You may NOT use the Specification as input to AI systems to:
100+
a. Generate competing standards or protocols
101+
b. Produce "original" content replicating the Specification without attribution
102+
c. Create AI training data for generating standards-related content
103+
104+
PERMITTED: Using AI to write code that implements the Specification.
105+
PROHIBITED: Using AI to rewrite or obscure the origin of the Specification.
106+
107+
D.2 COMPETING STANDARDS
108+
You may NOT publish a competing standard incorporating substantial elements
109+
of this Specification without:
110+
a. Written permission from the Copyright Holder, OR
111+
b. Clear attribution linking to the Canonical Source
112+
113+
D.3 FALSE COMPATIBILITY
114+
You may NOT market a tool as "Variables Contract compatible" if it:
115+
a. Omits required structural elements (Anatomy, Modes, References)
116+
b. Outputs non-conformant data (flattened hex values instead of references)
117+
c. Contradicts the governance principles of the Specification
118+
119+
D.4 NAME MISAPPROPRIATION
120+
You may NOT use "Variables Contract" or "VCSL" to imply endorsement or
121+
affiliation without written permission.
122+
123+
---
124+
125+
## E. ENFORCEMENT
126+
127+
E.1 AUTOMATIC TERMINATION
128+
Your rights under this license terminate immediately upon:
129+
a. Creating or distributing a Synthetic Derivative
130+
b. Publishing a Competing Standard without permission/attribution
131+
c. Making false conformance claims
132+
d. Misappropriating the Variables Contract name
133+
134+
E.2 EFFECT OF TERMINATION
135+
Upon termination:
136+
a. All rights cease immediately
137+
b. Continued use constitutes copyright infringement
138+
c. You must cease all public conformance claims
139+
140+
E.3 NO AUTOMATIC REINSTATEMENT
141+
Termination is not cured by ceasing violation. Reinstatement requires
142+
written permission from the Copyright Holder.
143+
144+
E.4 RESERVED RIGHTS
145+
The Copyright Holder reserves the right to:
146+
a. Publicly identify non-conformant implementations
147+
b. Issue takedown requests to platforms hosting infringing content
148+
c. Pursue legal remedies for infringement or misrepresentation
149+
d. Request evidence of independent development where substantial
150+
similarity exists
151+
152+
---
153+
154+
## F. NO TRADEMARK GRANT
155+
156+
This license grants no trademark rights. "Variables Contract" may only be used
157+
for truthful conformance statements per Section C.
158+
159+
---
160+
161+
## G. WARRANTY DISCLAIMER
162+
163+
THE SPECIFICATION IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. THE
164+
COPYRIGHT HOLDER SHALL NOT BE LIABLE FOR ANY DAMAGES ARISING FROM USE OF
165+
THE SPECIFICATION.
166+
167+
================================================================================
168+
169+
Canonical Source: https://variables-contract.vercel.app
170+
Schema: https://variables-contract.vercel.app/schema/v1.json
171+
License Inquiries: https://variables-contract.vercel.app/license
172+
173+
================================================================================

‎docmd.config.js‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -345,12 +345,22 @@ module.exports = {
345345
path: "reference/conformance",
346346
icon: "check-circle",
347347
},
348+
{
349+
title: "JSON Schema",
350+
path: "schema",
351+
icon: "code",
352+
},
348353
],
349354
},
350355
{
351356
title: "FAQ",
352357
icon: "help-circle",
353358
path: "faq",
354359
},
360+
{
361+
title: "License",
362+
icon: "file-text",
363+
path: "license",
364+
},
355365
],
356366
};

‎docs/faq.md‎

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -100,7 +100,9 @@ See [Anatomy](contract/anatomy) for details.
100100

101101
## Can I contribute?
102102

103-
Yes. Variable Contract is open source. Contributions welcome. See [Contributors](meta/contributors) for details.
103+
Yes. Contributions welcome. See [Contributors](meta/contributors) for details.
104+
105+
See [License](license) for usage terms.
104106

105107
## Is Variable Contract production-ready?
106108

‎docs/index.md‎

Lines changed: 12 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,18 @@ title: Variables Contract
44

55
# Variables Contract
66

7-
Public spec for design variables: JSON shape, naming, references, modes, and change control.
7+
| | |
8+
| -------------- | ---------------------------------- |
9+
| **Status** | Draft Standard |
10+
| **Version** | 0.3.7 |
11+
| **Editor** | Mark Learst |
12+
| **Compliance** | DTCG 2025.10 |
13+
| **Schema** | [v1.json](schema/v1.json) |
14+
| **License** | [CC BY-ND 4.0 + Addendum](license) |
15+
16+
A deterministic protocol for design-to-code variable governance. JSON shape, naming, references, modes, and change control.
17+
18+
This specification is protected under the [Variables Contract License](license). Usage for AI-generated derivative standards, false compatibility claims, or ecosystem fragmentation is prohibited.
819

920
## Start here
1021

‎docs/introduction/why-variables.md‎

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,10 @@ title: Why Variables
44

55
# Why Variables
66

7+
::: callout info Part of the Variables Contract Specification
8+
This page is part of the [Variables Contract](../contract/variable-contract) governed specification. See [License](../license) for usage terms.
9+
:::
10+
711
Variables are variables. CSS variables, JavaScript variables, Figma variables. They're all variables.
812

913
If you call them "design tokens" or "style properties" or "design constants," you create confusion. Developers know variables. Designers know variables. Variable Contract uses the term everyone understands.
@@ -97,4 +101,3 @@ If you use confusing terminology:
97101
- Changing industry terminology (we use "variables" internally)
98102
- Convincing others to use "variables" (they can call them what they want)
99103
- Tool naming (tools can use their own terms)
100-

‎docs/license.md‎

Lines changed: 126 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,126 @@
1+
---
2+
title: License
3+
---
4+
5+
# License
6+
7+
The Variables Contract Specification is dual-licensed:
8+
9+
1. **CC BY-ND 4.0** — Legally recognized base license
10+
2. **Standards Integrity Addendum** — Additional terms for public use
11+
12+
## Part I: Base License (CC BY-ND 4.0)
13+
14+
This Specification is licensed under [Creative Commons Attribution-NoDerivatives 4.0 International](https://creativecommons.org/licenses/by-nd/4.0/).
15+
16+
**You are free to:**
17+
18+
- **Share** — Copy and redistribute in any medium or format
19+
- **Implement** — Build software that conforms to the Specification
20+
21+
**Under these terms:**
22+
23+
- **Attribution** — You must give appropriate credit and link to the license
24+
- **NoDerivatives** — You may not distribute modified versions of the Specification as an alternative standard
25+
26+
## Part II: Standards Integrity Addendum
27+
28+
Additional terms apply to public-facing uses. These prevent ecosystem fragmentation.
29+
30+
### Conformance Tiers
31+
32+
**Variables Contract Conformant** requires:
33+
34+
- Full Variable Anatomy (Base, Alias, Component)
35+
- Mode resolution and inheritance
36+
- Reference syntax and resolution
37+
- Valid DTCG-aligned JSON with references (not flattened values)
38+
- Naming convention enforcement
39+
40+
**Variables Contract Compatible** requires:
41+
42+
- Data format that does not corrupt Specification-compliant data
43+
- Attribution to the Canonical Source
44+
45+
### Attribution
46+
47+
Public-facing tooling must include:
48+
49+
```text
50+
Built on the Variables Contract Specification
51+
https://variables-contract.vercel.app
52+
```
53+
54+
JSON files should include:
55+
56+
```json
57+
{
58+
"$schema": "https://variables-contract.vercel.app/schema/v1.json"
59+
}
60+
```
61+
62+
### Prohibited Acts
63+
64+
**AI Laundering (Synthetic Derivatives)**
65+
66+
You may NOT use the Specification as AI input to:
67+
68+
- Generate competing standards
69+
- Produce "original" content replicating the Specification without attribution
70+
- Create AI training data for standards-related content
71+
72+
PERMITTED: Using AI to write code implementing the Specification.
73+
PROHIBITED: Using AI to rewrite or obscure the Specification's origin.
74+
75+
**False Compatibility Claims**
76+
77+
You may NOT claim compatibility if your tool:
78+
79+
- Omits required structural elements (Anatomy, Modes, References)
80+
- Outputs non-conformant data (flattened hex values instead of references)
81+
- Contradicts governance principles
82+
83+
**Name Misappropriation**
84+
85+
"Variables Contract" and "VCSL" may only be used for truthful conformance statements.
86+
87+
### Enforcement
88+
89+
**Automatic Termination** occurs upon:
90+
91+
- Creating/distributing Synthetic Derivatives
92+
- Publishing Competing Standards without permission/attribution
93+
- Making false conformance claims
94+
- Misappropriating the name
95+
96+
**Upon termination:**
97+
98+
- All rights cease immediately
99+
- Continued use = copyright infringement
100+
- Reinstatement requires written permission
101+
102+
**Reserved Rights:**
103+
104+
- Publicly identify non-conformant implementations
105+
- Issue takedown requests
106+
- Pursue legal remedies
107+
- Request evidence of independent development
108+
109+
## Why This Structure?
110+
111+
**CC BY-ND 4.0** is legally recognized and court-tested. It prevents forks of the specification text.
112+
113+
**The Addendum** adds specific protections against:
114+
115+
- AI-assisted plagiarism ("laundering")
116+
- False compatibility claims from "vibe tools"
117+
- Name/brand confusion
118+
119+
## Full License
120+
121+
The complete license is in the repository [LICENSE](https://github.com/marklearst/variables-contract/blob/main/LICENSE) file.
122+
123+
## Contact
124+
125+
For licensing inquiries, conformance certification, or permission requests:
126+
https://variables-contract.vercel.app/license

0 commit comments

Comments
 (0)