Licensing

Reuse, notices and fonts

The authoritative terms are in LICENSE.md at v1.1.0 and the notices delivered with your package or copy bundle. The material is split by category:

Material	Repository license boundary
Code, tokens, schemas, scripts and generated machine JSON/CSS	MIT
Specification prose and specimens	CC BY 4.0
Reference screenshots and captures	Reference-only; not licensed for reuse or redistribution
Fonts	Not distributed; obtain from the publisher under their own terms
Historical third-party/source material	Its original source license; cataloguing does not relicense it

When copying components

Keep the complete bundle's LICENSE.md and notices with the copied runtime, styling and specimen markup. Preserve MIT copyright/license notices. For adapted prose/specimens, follow the repository's attribution guidance: identify j3w1 UI Theme Spec, link the source and CC BY 4.0 license, and indicate changes. Do not discard notices when extracting a small snippet.

Package/copy mode does not grant rights to reference screenshots, purchased templates or unrelated assets. The demo's independently authored implementation is part of the code distribution; external reference material is a separate boundary.

Fonts and identity

The preferred family and source are named in theme.json. A fallback monospace stack is provided; no font binary is embedded. Obtain optional fonts from their publisher rather than copying workstation files into an app release.

The name j3w1 identifies the owner. The repository's license does not grant permission to present derived work as the owner's own theme release. Keep your application's identity and modifications clear.

For exact terms, read the linked license and delivered notices. Next: Package and copy · Versioning.