open-mapsight · pjeweb · Jun 26, 2026 · Jun 26, 2026 · Jun 26, 2026 · Jun 26, 2026
diff --git a/.changeset/mit-license.md b/.changeset/mit-license.md
@@ -0,0 +1,19 @@
+---
+"@mapsight/core": patch
+"@mapsight/count-aggregator-api": patch
+"@mapsight/count-aggregator-ui": patch
+"@mapsight/lib-js": patch
+"@mapsight/lib-ol": patch
+"@mapsight/lib-redux": patch
+"@mapsight/showcase": patch
+"@mapsight/traffic-style": patch
+"@mapsight/ui": patch
+"@mapsight/vector-editor": patch
+"@mapsight/vector-style-compiler": patch
+"@mapsight/vite-host-embed": patch
+"mapsight-host-starter": patch
+"mapsight-next-starter": patch
+"mapsight-vite-spa-starter": patch
+---
+
+Declare MIT license in package manifests.
diff --git a/LICENSE b/LICENSE
@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Mapsight contributors
+
+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.
diff --git a/README.md b/README.md
@@ -57,7 +57,7 @@ to maintainers with a private checkout.
 | Current vs target      | [`docs/architecture/CURRENT_VS_TARGET.md`](docs/architecture/CURRENT_VS_TARGET.md)     |
 | Redux runtime          | [`packages/core/docs/REDUX_ARCHITECTURE.md`](packages/core/docs/REDUX_ARCHITECTURE.md) |
 | Redux actions          | [`packages/core/docs/ACTION_GUIDE.md`](packages/core/docs/ACTION_GUIDE.md)             |
-| Licensing              | [`docs/LICENSING.md`](docs/LICENSING.md)                                               |
+| Licensing              | [`docs/LICENSING.md`](docs/LICENSING.md), [`docs/TRADEMARK.md`](docs/TRADEMARK.md)     |
 
 ## Private workspace paths
 
@@ -98,12 +98,12 @@ pnpm --filter @mapsight/vector-style-compiler build
 
 ## License
 
-Mapsight is published as source-available software while OSI license approval is
-pending. npm packages are marked `UNLICENSED` until an approved open-source
-license is in place.
+The public framework is **[MIT](LICENSE)**. See [`docs/LICENSING.md`](docs/LICENSING.md) and
+[`docs/TRADEMARK.md`](docs/TRADEMARK.md) for code and brand terms.
 
-To discuss use, redistribution, or licensing, contact
-[contact@open-mapsight.org](mailto:contact@open-mapsight.org).
+For licensing or trademark questions, contact
+[contact@open-mapsight.org](mailto:contact@open-mapsight.org). For code, docs, and integration questions, use
+[GitHub issues](https://github.com/open-mapsight/mapsight/issues).
 
 ## Security
 

diff --git a/apps/showcase/package.json b/apps/showcase/package.json
@@ -39,7 +39,7 @@
 		"typescript": "catalog:",
 		"vite": "^8.0.14"
 	},
-	"license": "UNLICENSED",
+	"license": "MIT",
 	"repository": {
 		"url": "https://github.com/open-mapsight/mapsight"
 	},

diff --git a/apps/vector-editor/package.json b/apps/vector-editor/package.json
@@ -37,7 +37,7 @@
 		"postcss-nested": "^7.0.2",
 		"vite": "^8.0.14"
 	},
-	"license": "UNLICENSED",
+	"license": "MIT",
 	"repository": {
 		"url": "https://github.com/open-mapsight/mapsight"
 	},

diff --git a/docs/LICENSING.md b/docs/LICENSING.md
@@ -3,64 +3,83 @@
 Mapsight is published on [GitHub](https://github.com/open-mapsight/mapsight)
 and [npm](https://www.npmjs.com/org/mapsight) under the `@mapsight/*` scope.
 
-## Current status
+The public monorepo is licensed under the **MIT License** (`MIT`).
+See [Decision 011](architecture/decisions/011-license-and-brand-strategy.md).
 
-This repository **does not yet include an OSI-approved `LICENSE` file** at the root. Until one is added:
+---
 
-- **Do not assume** MIT, Apache-2.0, EUPL, or any other license.
-- Treat the code as **source-available** for inspection and contribution discussion, not as freely licensed for all
-  uses.
-- **Contact the maintainers** before redistribution, proprietary embedding, or production deployment if license terms
-  matter to your organization.
+## Public framework (MIT)
 
-## Intent
+The public monorepo — `packages/*`, `apps/*`, `starters/*`, and `docs/` — is under the **MIT License** (`MIT`).
 
-The project is intended to be **fully open source**. Maintainers are evaluating license options aligned with:
+Includes:
 
-- npm and global integrator use
-- German public-sector **Public Money – Public Code** practice
-- Optional alignment with ecosystems such as [CIVITAS CORE](https://www.civitasconnect.digital/civitas-core/)
-  and [opencode.de](https://opencode.de)
+- `@mapsight/core`, `@mapsight/ui`, `@mapsight/traffic-style`, and other public npm packages
+- `@mapsight/vite-host-embed`, `@mapsight/vite-count-aggregator-embed`, count-aggregator packages
+- Demo apps (`apps/showcase`, `apps/vector-editor`), copy-out starters, and public documentation
 
-When a license is chosen, this file will be updated with the SPDX identifier, a link to the full license text, and a
-short rationale.
+Full text: [LICENSE](../LICENSE) at repository root.
 
-## Companion PHP components
+**Trademark:** MIT does not grant use of the **Mapsight** name or logo — [TRADEMARK.md](TRADEMARK.md).
 
-| Component                                                       | License (check monorepo) |
-| --------------------------------------------------------------- | ------------------------ |
-| [mapsight-pulp](https://github.com/open-mapsight/mapsight-pulp) | See upstream `LICENSE`   |
-| [tile-proxy](https://github.com/open-mapsight/mapsight-pulp)    | See upstream `LICENSE`   |
+---
 
-Packages in this monorepo declare `"license": "UNLICENSED"` in `package.json` until a root license is applied
-consistently.
+## Other products and services
+
+Maintainers may publish **separate products or services** that build on these libraries under **different licenses**.
+Those artifacts are governed by their own license terms and are not part of this repository unless explicitly linked
+here.
+
+This document is engineering guidance, not legal advice.
+
+---
+
+## Companion repositories
+
+| Component                    | Repository                                                      | License                |
+| ---------------------------- | --------------------------------------------------------------- | ---------------------- |
+| mapsight-pulp, tile-proxy    | [mapsight-pulp](https://github.com/open-mapsight/mapsight-pulp) | See upstream `LICENSE` |
+| Public framework (this repo) | [mapsight](https://github.com/open-mapsight/mapsight)           | **MIT**                |
+
+---
 
 ## FAQ
 
-### Can we evaluate Mapsight in development?
+### Can we embed Mapsight in a proprietary municipal website?
+
+**Yes** — static or module embeds (CMS snippets, SPAs) without copyleft obligations on the host site.
+**Trademark:** follow [TRADEMARK.md](TRADEMARK.md); white-labeling the visitor UI is normal.
+
+### Does Mapsight “taint” our project with copyleft?
+
+**No** — MIT does not impose copyleft (GPL etc.) on your host site or proprietary code that uses the libraries. Other
+Mapsight
+products or services, if published separately, may use different terms.
+
+### Can we fork `@mapsight/core` and sell support?
+
+Yes under MIT, under a **different product name** — not as “Mapsight” without permission.
 
-Yes for **inspection and internal evaluation** in this repository. Do not assume production redistribution rights until
-an OSI license is published.
+### Can we contribute?
 
-### Can we contribute docs or code before the license is final?
+Yes. Contributions are accepted under **MIT**. No CLA is planned — see Decision 011.
 
-Yes — open a [GitHub issue](https://github.com/open-mapsight/mapsight/issues) or pull request. Copyright and license
-grant will be clarified when the project-wide license is chosen.
+### What about documentation?
 
-### Does the undecided license block CIVITAS / opencode.de listing?
+Public `docs/` is **MIT** (same as the public framework) unless a page explicitly states otherwise.
 
-Formal ecosystem listing typically requires a **clear SPDX license**. Maintainers are evaluating options aligned with
-PMPC practice — see Intent above. Timeline is **not yet committed**.
+---
 
 ## Contact
 
-Until a root `LICENSE` file exists:
+- **Licensing and trademark:** [contact@open-mapsight.org](mailto:contact@open-mapsight.org)
+- **Code, docs, and integration questions:** [GitHub issues](https://github.com/open-mapsight/mapsight/issues)
 
-- **GitHub:** [open an issue](https://github.com/open-mapsight/mapsight/issues) — describe your use case for licensing
-  questions
-- **Production / redistribution:** same channel; maintainers respond on a best-effort basis
+---
 
-## Documentation
+## Related
 
-Documentation in `docs/` follows the same status unless otherwise noted. Contribution of docs does not transfer
-copyright; a project-wide license and contributor policy will be published with the code license decision.
+- [Trademark policy](TRADEMARK.md)
+- [Decision 011 — License and brand strategy](architecture/decisions/011-license-and-brand-strategy.md)
+- [Contributing](development/CONTRIBUTING.md)
+- [Positioning — Masterportal comparison](ecosystem/POSITIONING.md)
diff --git a/docs/README.md b/docs/README.md
@@ -37,8 +37,8 @@ Maintainer deployments currently exercise:
 - Basemap tile proxy pattern — [`TILE_PROXY`](integration/TILE_PROXY.md)
 - Declarative embed config + Redux runtime — [Redux architecture](../packages/core/docs/REDUX_ARCHITECTURE.md)
 
-**Still evolving:** OSI license, full Infosite Java guide, SSR sidecar standardization, i18n library choice —
-see [Current vs target](architecture/CURRENT_VS_TARGET.md).
+**Still evolving:** full Infosite Java guide, SSR sidecar standardization, i18n library choice — see
+[Current vs target](architecture/CURRENT_VS_TARGET.md).
 
 ---
 
@@ -84,10 +84,11 @@ see [Current vs target](architecture/CURRENT_VS_TARGET.md).
 
 ## Compliance
 
-| Document                             | About                            |
-| ------------------------------------ | -------------------------------- |
-| [LICENSING.md](LICENSING.md)         | License status + FAQ             |
-| [ACCESSIBILITY.md](ACCESSIBILITY.md) | Accessibility status (pre-audit) |
+| Document                             | About                                      |
+| ------------------------------------ | ------------------------------------------ |
+| [LICENSING.md](LICENSING.md)         | Public framework license (MIT)             |
+| [TRADEMARK.md](TRADEMARK.md)         | Mapsight name, logo, and official channels |
+| [ACCESSIBILITY.md](ACCESSIBILITY.md) | Accessibility status (pre-audit)           |
 
 ## Development
 

diff --git a/docs/TRADEMARK.md b/docs/TRADEMARK.md
@@ -0,0 +1,137 @@
+# Trademark policy
+
+**Status:** Effective
+See [Decision 011](architecture/decisions/011-license-and-brand-strategy.md).
+
+Mapsight is an open-source **software framework**. The **Mapsight name, logo, and related branding** are not open
+source. They are controlled separately from the code license.
+
+This policy explains what you may do with the brand when using MIT-licensed Mapsight software.
+
+---
+
+## Official project
+
+The **official Mapsight open-source project** is maintained at:
+
+| Channel | Official identifier                                                                         |
+| ------- | ------------------------------------------------------------------------------------------- |
+| Source  | [github.com/open-mapsight/mapsight](https://github.com/open-mapsight/mapsight)              |
+| npm     | [`@mapsight/*`](https://www.npmjs.com/org/mapsight) packages published from that repository |
+| Docs    | [docs/LICENSING.md](LICENSING.md) and linked documentation in this repository               |
+
+Other repositories, npm packages, websites, or social accounts are **not official** unless maintainers list them
+explicitly (for example a future partner or certification page).
+
+**Other products or services** may be published under separate repositories with their own licenses. Only artifacts
+explicitly labeled by maintainers are **official Mapsight products**.
+
+---
+
+## What the MIT license does and does not grant
+
+The [MIT License](../LICENSE) grants rights to use, modify, and redistribute **software and documentation** in this
+public tree.
+
+It does **not** grant rights to:
+
+- Use **Mapsight** as the name of your product, company, or fork
+- Use Mapsight **logos**, wordmarks, or trade dress
+- State or imply **endorsement**, **partnership**, or **official status** without permission
+- Register domain names, npm scopes, or social handles that suggest you are the Mapsight project
+
+Trademark law still applies. Nominative use (below) is allowed; confusing similarity is not.
+
+---
+
+## Permitted uses (no permission needed)
+
+You may truthfully refer to Mapsight when describing what you ship:
+
+- **Attribution:** “Built with Mapsight”, “Powered by @mapsight/core”, “Uses the Mapsight embed API”
+- **Documentation and bids:** factual references in README files, integration guides, academic work, or procurement
+  documents
+- **Compatibility:** “Compatible with Mapsight embed config” when technically accurate
+- **Internal paths and CSS prefixes** in your deployment (for example `/mapsight/plan/` or `ms3-*` classes) when they
+  are implementation detail, not marketing — hosts commonly white-label the visitor-facing experience
+
+You must not present these as endorsement by the Mapsight maintainers.
+
+---
+
+## Uses that require permission
+
+Contact [contact@open-mapsight.org](mailto:contact@open-mapsight.org) before:
+
+- Naming a product, company, domain, or npm package **Mapsight** or **Mapsight …** (for example “Mapsight Pro”,
+  “Mapsight for Drupal”)
+- Using Mapsight **logos** or wordmarks in marketing, app stores, or conference materials
+- Claiming **official**, **certified**, **supported by**, or **partnership with** Mapsight
+- Redistributing a **modified fork** under the Mapsight name
+- Registering **trademarks or domains** containing “mapsight” in a way that suggests affiliation
+
+Maintainers may grant written permission for integrators, agencies, and public-sector programs. A formal partner list
+may be published later.
+
+---
+
+## Forks and derivatives
+
+You may fork MIT-licensed code and publish your own version. You must:
+
+1. **Rename** the project in user-facing places (product name, npm package name unless under your own scope, marketing
+   site title)
+2. **Remove** Mapsight logos and official branding from redistributed assets unless nominatively attributing source
+3. **Keep** the MIT copyright and license notice in source distributions as required by the license
+
+Example acceptable naming: “Stadtkarte — based on Mapsight”. Not acceptable: “Mapsight Community Edition” without
+permission.
+
+---
+
+## Logos and visual identity
+
+Official logos and brand assets are distributed only with maintainer approval. Until brand guidelines are published:
+
+- Do not copy the project banner or logo from GitHub/npm for your own product identity
+- Default UI **watermarks** shipped in `@mapsight/ui` may be disabled or replaced by host configuration where the
+  software license allows; that does not grant logo rights for external marketing
+
+---
+
+## Enforcement
+
+Maintainers prefer cooperation to conflict. If you are unsure whether a use is permitted, email
+[contact@open-mapsight.org](mailto:contact@open-mapsight.org) before shipping.
+
+We may request rename, disclaimer, or removal of confusing branding. Serious misuse may be referred to trademark
+registration and applicable law.
+
+---
+
+## Relationship to licensing
+
+| Layer                                                 | Code license        | Brand                                                         |
+| ----------------------------------------------------- | ------------------- | ------------------------------------------------------------- |
+| Public `@mapsight/*` framework, starters, public docs | [MIT](LICENSING.md) | **Mapsight** name reserved; official channel is open-mapsight |
+| Other Mapsight products or services (when published)  | See artifact terms  | **Official Mapsight** product names by maintainers only       |
+
+A permissive or copyleft license on product code does not expand trademark rights. Third parties may not rebrand as
+Mapsight without permission.
+
+---
+
+## Contact
+
+Email [contact@open-mapsight.org](mailto:contact@open-mapsight.org) for trademark, brand, and licensing questions.
+
+For code, documentation, and integration questions, use
+[GitHub issues](https://github.com/open-mapsight/mapsight/issues).
+
+---
+
+## Related
+
+- [Licensing](LICENSING.md)
+- [Decision 011 — License and brand strategy](architecture/decisions/011-license-and-brand-strategy.md)
+- [Contributing](development/CONTRIBUTING.md)