|
1 | | -MIT License |
2 | | - |
3 | | -Copyright (c) 2026 BeyondNet Code |
4 | | - |
5 | | -Permission is hereby granted, free of charge, to any person obtaining a copy |
6 | | -of this software and associated documentation files (the "Software"), to deal |
7 | | -in the Software without restriction, including without limitation the rights |
8 | | -to use, copy, modify, merge, publish, distribute, sublicense, and/or sell |
9 | | -copies of the Software, and to permit persons to whom the Software is |
10 | | -furnished to do so, subject to the following conditions: |
11 | | - |
12 | | -The above copyright notice and this permission notice shall be included in all |
13 | | -copies or substantial portions of the Software. |
14 | | - |
15 | | -THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR |
16 | | -IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, |
17 | | -FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE |
18 | | -AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER |
19 | | -LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, |
20 | | -OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE |
21 | | -SOFTWARE. |
| 1 | +# UMS Dual License |
| 2 | + |
| 3 | +Copyright (c) 2026 BeyondNet Tech / BeyondNet Code. |
| 4 | +Author: Alberto Arroyo Raygada. |
| 5 | +All rights reserved except as expressly granted under this Dual License. |
| 6 | + |
| 7 | +UMS is a real corporate/enterprise reference application built on top of Evolith ARCH32. UMS is an applied implementation example of Evolith architectural principles, governance, patterns, standards, security, multi-tenancy, parametrization, authentication, authorization, and documentation practices. |
| 8 | + |
| 9 | +UMS does not represent the entirety of Evolith ARCH32 and must not be interpreted as the only possible system derived from Evolith. UMS, its source code, documentation, architecture decisions, modules, menus, domain resources, actions, profiles, permissions, seeds, authentication graph, parametrization model, UI/UX patterns, workbooks, diagrams, and derived assets are intellectual property of BeyondNet Tech / BeyondNet Code. |
| 10 | + |
| 11 | +This repository is made available under a dual licensing model. |
| 12 | + |
| 13 | +## 1. Open Source Components |
| 14 | + |
| 15 | +Specific files, folders, examples, or components may be designated by BeyondNet Tech as open source components. |
| 16 | + |
| 17 | +When a file, folder, example, or component is explicitly marked as open source, it may be used under the Apache License, Version 2.0, unless that asset declares a different license notice. |
| 18 | + |
| 19 | +Use under the open source component license requires that you: |
| 20 | + |
| 21 | +- Preserve the original copyright notice. |
| 22 | +- Preserve the applicable license notice. |
| 23 | +- Preserve attribution to BeyondNet Tech / BeyondNet Code and Alberto Arroyo Raygada. |
| 24 | +- Preserve the `NOTICE` file and any attribution notices included in the repository. |
| 25 | +- Clearly indicate any modifications made. |
| 26 | +- Do not remove references to UMS, Evolith ARCH32, BeyondNet Tech, BeyondNet Code, or the original author where they are part of the original notices, documentation, headers, or attribution files. |
| 27 | + |
| 28 | +The open source component license does not grant ownership over the UMS name, Evolith ARCH32 name, BeyondNet Tech brand, BeyondNet Code brand, logos, trademarks, commercial materials, private implementations, proprietary modules, confidential documentation, or restricted enterprise assets. |
| 29 | + |
| 30 | +## 2. Commercial / Proprietary License |
| 31 | + |
| 32 | +A separate commercial license or prior written authorization from BeyondNet Tech is required for any use that is not expressly covered by an open source component notice, including but not limited to: |
| 33 | + |
| 34 | +- Commercial exploitation of UMS or derived works. |
| 35 | +- Use in proprietary enterprise platforms. |
| 36 | +- Use in SaaS, PaaS, hosted services, internal corporate platforms, or client-facing commercial systems. |
| 37 | +- Resale, sublicensing, consulting packages, implementation services, or derivative products based on UMS or Evolith ARCH32. |
| 38 | +- Creation of private commercial forks or derivative frameworks. |
| 39 | +- Use of UMS as a commercial product, enterprise accelerator, identity platform, authorization engine, or implementation template. |
| 40 | +- Use of BeyondNet Tech templates, governance models, architectural standards, diagrams, ADRs, workbooks, or implementation patterns as part of a paid product or service. |
| 41 | + |
| 42 | +Commercial use may be subject to separate commercial terms, fees, support agreements, or partnership conditions. |
| 43 | + |
| 44 | +## 3. Default Restriction |
| 45 | + |
| 46 | +Unless a file, folder, component, or example is explicitly marked as open source, all rights remain reserved by BeyondNet Tech / BeyondNet Code. |
| 47 | + |
| 48 | +No permission is granted by default to copy, modify, distribute, sublicense, publish, rebrand, sell, host, or commercially exploit UMS, Evolith ARCH32 reference assets, or derived enterprise assets without prior written authorization. |
| 49 | + |
| 50 | +## 4. Protected Intellectual Property |
| 51 | + |
| 52 | +The following assets are considered protected intellectual property of BeyondNet Tech / BeyondNet Code: |
| 53 | + |
| 54 | +- UMS source code and product implementation. |
| 55 | +- UMS architecture, domain model, bounded contexts, modules, menus, resources, actions, profiles, permissions, templates, seeds, auth graph, parametrization model, and documentation. |
| 56 | +- UMS API, web application, UI/UX patterns, tests, mocks, local database scripts, production configuration patterns, and operational documentation. |
| 57 | +- Evolith ARCH32 architecture framework and inherited standards. |
| 58 | +- Governance standards, ADRs, diagrams, workbooks, executive presentations, implementation patterns, and reusable templates. |
| 59 | +- Any child application, derivative system, or enterprise implementation created under the BeyondNet Tech ecosystem. |
| 60 | + |
| 61 | +No license is granted to use the names, brands, trademarks, logos, or identity of BeyondNet Tech, BeyondNet Code, Evolith ARCH32, or UMS except where strictly necessary to preserve attribution notices required by the applicable license. |
| 62 | + |
| 63 | +## 5. Attribution Requirement |
| 64 | + |
| 65 | +Any permitted use, copy, modification, distribution, publication, or derivative work must retain clear attribution to: |
| 66 | + |
| 67 | +BeyondNet Tech / BeyondNet Code |
| 68 | +Author: Alberto Arroyo Raygada |
| 69 | +Project: Evolith ARCH32 |
| 70 | +Reference Application: UMS |
| 71 | + |
| 72 | +Attribution must not imply endorsement, sponsorship, partnership, or authorization for commercial use unless explicitly granted in writing by BeyondNet Tech. |
| 73 | + |
| 74 | +## 6. Documentation and Non-Code Assets |
| 75 | + |
| 76 | +Documentation, diagrams, presentations, workbooks, ADRs, templates, visual assets, governance materials, and product implementation materials may be subject to more restrictive terms than source code. |
| 77 | + |
| 78 | +Unless explicitly marked otherwise, non-code assets are provided for reference, learning, evaluation, and authorized collaboration only. They may not be reused commercially, republished, rebranded, sublicensed, or incorporated into third-party commercial materials without prior written authorization from BeyondNet Tech. |
| 79 | + |
| 80 | +## 7. No Warranty |
| 81 | + |
| 82 | +This project is provided "as is", without warranty of any kind, express or implied, including but not limited to warranties of merchantability, fitness for a particular purpose, and non-infringement. |
| 83 | + |
| 84 | +BeyondNet Tech, BeyondNet Code, and the author are not liable for any claim, damages, or other liability arising from the use of this project. |
| 85 | + |
| 86 | +## 8. License Precedence |
| 87 | + |
| 88 | +If a specific file, folder, module, or component includes its own license notice, that notice takes precedence for that specific asset. |
| 89 | + |
| 90 | +If there is any doubt about whether a use case is permitted under an open source component notice or requires a commercial license, written authorization from BeyondNet Tech is required before use. |
| 91 | + |
| 92 | +## 9. Contact |
| 93 | + |
| 94 | +For commercial licensing, enterprise use, partnerships, authorization requests, or clarification: |
| 95 | + |
| 96 | +BeyondNet Tech / BeyondNet Code |
| 97 | +Email: beyondnet.peru@gmail.com |
0 commit comments