playground
Explore a boundary
Change the integration and license facts. The analysis updates as you edit.
Architecture assumptions
Build a hypothetical architecture. A license selection is an assumption for this experiment. Changing transport does not by itself change communication semantics.
Project boundary
5 components| From → to | Connection | Semantics |
|---|---|---|
| app → library | intimate | |
| frontend → app | independent | |
| app → shared | intimate | |
| library → client | independent |
Source scope reflects this scenario’s facts. An unresolved boundary requires further evidence.
Supplied facts
- Distribution
- Network interaction
- Intended use
- commercial-service
- Evaluation date
- 2026-10-24
- Policy
These facts define the simulation. Evidence declarations stand in for actual corresponding source, relinkable objects and release materials.
Components
- Declared license
- LicenseRef-Proprietary
- Modified files
- None
- Artifact
- code
Third-party grants remain fixed unless this scenario supplies authority to change them.
Project artifacts
Evidence artifact format
Source offers contain “component: id” and “source: https://…” on separate lines. Covered-file offers also list the covered paths. Relinking declarations contain “replace-compatible-library” for dynamic linking or “relink-object-files” for static linking, and “reverse-engineering-permitted”. These declarations model supplied release artifacts.
License reference
- permissions
- commercial-use, modifications, distribution, private-use
- conditions
- include-copyright, include-license
- limitations
- liability, warranty
Expression builder
| Alternative | Required licenses |
|---|---|
| 1 | MIT AND LGPL-3.0-only |
| 2 | Apache-2.0 AND LGPL-3.0-only |
Findings and evidence
9 violations · 0 need review · 1 scope records
boundaries · obligation · combined-source
Source obligations cover the modeled combined work: app, library, shared.
app · library · shared · api-shared · app-library
Mere aggregation and communication semantics ↗boundaries · violation · source-offer
Supply the corresponding-source location for app.
sources/app.txt · app · library · shared · api-shared · app-library
Mere aggregation and communication semantics ↗boundaries · violation · source-offer
Supply the corresponding-source location for library.
sources/library.txt · app · library · shared · api-shared · app-library
Mere aggregation and communication semantics ↗boundaries · violation · source-offer
Supply the corresponding-source location for shared.
sources/shared.txt · app · library · shared · api-shared · app-library
Mere aggregation and communication semantics ↗attribution · violation · copyright
Preserve Copyright 2026 frontend contributors.
ThirdPartyNotices.txt · LICENSES/frontend.txt · frontend
License terms ↗attribution · violation · copyright
Preserve Copyright 2026 shared contributors.
ThirdPartyNotices.txt · LICENSES/shared.txt · shared
License terms ↗boundaries · violation · library-source
Provide the corresponding library source location.
sources/shared.txt · shared
4. Combined Works ↗boundaries · violation · relink
Provide replace-compatible-library evidence and permission to debug library modifications.
relink/app.txt · app · shared · api-shared
4. Combined Works ↗attribution · violation · copyright
Preserve Copyright 2026 client contributors.
ThirdPartyNotices.txt · LICENSES/client.txt · client
License terms ↗licensing · violation · release-terms
The combined work includes proprietary-only app; choose compatible release terms or establish a separate work.
app · library · shared · api-shared · app-library
Mere aggregation and communication semantics ↗