From ecc8631ad7eb5a8455b977c81b580da5c73755e2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?abstract=E2=81=B7?= Date: Fri, 16 Jan 2026 03:37:41 +0800 Subject: [PATCH 01/15] Create BASIC INFRA REQS.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit # PR: SC-MVP-01 Cluster Setup — Basic Infra Reqs ## Branch `sc-mvp/cluster-setup` ## Commit Message Add BASIC INFRA REQS.md + lightweight logging ## Snippet / ETL-Friendly Description - SC-MVP-01: Provision k3/kind cluster, 1 control-plane + 1 worker node - Namespace `sc-mvp-test` for app deployment - Capture stdout/stderr logs in **CSV/JSON** for SQLite ETL - Record timestamps, pod status, and resource usage - Optional cleanup: delete cluster on failure - Documentation includes `kind-config.yaml` and reproducibility steps - SHA256 (Original Artifact): `` - SHA256 (Microsoft Official): `` ## Commit Email vitrixlabph@gmail.com --- sanity-check/BASIC INFRA REQS.md | 80 ++++++++++++++++++++++++++++++++ 1 file changed, 80 insertions(+) create mode 100644 sanity-check/BASIC INFRA REQS.md diff --git a/sanity-check/BASIC INFRA REQS.md b/sanity-check/BASIC INFRA REQS.md new file mode 100644 index 00000000..797a3cd7 --- /dev/null +++ b/sanity-check/BASIC INFRA REQS.md @@ -0,0 +1,80 @@ +# Super MVP — sc-mvp/cluster-setup + +## 1️⃣ Goal +Spin up a **lightweight, reproducible Kubernetes cluster** using **k3s or kind**, forming the foundation for the SC-MVP pipeline. + +--- + +## 2️⃣ Requirements + +| Requirement | Details | +| ----------- | ------- | +| **Cluster Type** | k3s (lightweight Kubernetes) or kind (Kubernetes in Docker) | +| **Nodes** | 1 control-plane + 1 worker node minimum | +| **Resource Limits** | CPU: 500m, Memory: 512Mi per node | +| **Namespace Isolation** | Optional namespace `sc-mvp-test` for app deployments | +| **Tools Required** | Docker, kubectl, kind or k3s CLI | +| **Reproducibility** | Cluster should be reproducible on any contributor machine | + +--- + +## 3️⃣ Deployment Steps (Kind Example) + +1. **Create a kind configuration file** + +`kind-config.yaml`: + +2. **Create the cluster** + +`kind create cluster --name sc-mvp --config kind-config.yaml` + +3. **Verify cluster status** + +` +kubectl cluster-info --context kind-sc-mvp +kubectl get nodes +` + +4. **Opt: Create namespace for testing** + +`kubectl create namespace sc-mvp-test` + +5. **Check namespace** + +`kubectl get ns` + +4️⃣ Logging & Verification + +1. Capture stdout/stderr of `kind create cluster`. + +2. Record `kubectl get nodes` output. + +3. Timestamp logs for reproducibility. + +4. Ensure nodes are `Ready` before proceeding to app deployment. + +5️⃣ Optional Safety Features + +1. Delete cluster on failure or cleanup: + +2. `kind delete cluster --name sc-mvp` + +3. Set resource constraints in Docker for nodes if machine resources are limited. + +4. Verify Docker daemon is running before cluster creation. + +6️⃣ Deliverables + +1. `kind-config.yaml` → Cluster configuration manifest + +2. Deployment logs → `sc-mvp-cluster-setup.log` + +3. Optional namespace `sc-mvp-test` for app deployment + +4. Documentation of steps for reproducibility +```yaml +kind: Cluster +apiVersion: kind.x-k8s.io/v1alpha4 +nodes: + - role: control-plane + - role: worker From bc63f33c441c685e5f6a8417c555aab291595fe4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?abstract=E2=81=B7?= Date: Fri, 16 Jan 2026 17:22:22 +0800 Subject: [PATCH 02/15] Create HOTEL RESERVATION APP MICROSERVICE ARCHITECTURE.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit ## SC-MVP-02: Checkpoint Definition — App Deployment & Rollout Verification ### Branch `sc-mvp/app-deploy` ### Commit Message Define app deployment checkpoint with idempotent rollout verification ### Snippet **SC-MVP-02: Deploy Hotel Reservation App** - Deploy **hotel reservation app** into `sc-mvp-test` namespace - Ensure **idempotent deployment** (safe re-apply with no side effects) - Use declarative manifests (Deployment, Service, optional Ingress) - Verify successful rollout via: - `kubectl rollout status` - Pod readiness & availability checks - Service endpoint accessibility - Capture deployment metadata: - Timestamps (apply/start/ready) - Pod status & restart count - Image digest / tag used - Log stdout/stderr and rollout results in **CSV/JSON** (SQLite-ready ETL) - Failure handling: - Automatic rollback or explicit failure state - Preserve logs and cluster state for audit - Documentation includes: - Deployment manifests - Rollout verification steps - Re-run / idempotency validation notes ### Artifact Integrity - **SHA256 (Original Artifact):** `` - **SHA256 (Microsoft Official):** `` ### Commit Email `vitrixlabph@gmail.com` --- ...SERVATION APP MICROSERVICE ARCHITECTURE.md | 89 +++++++++++++++++++ 1 file changed, 89 insertions(+) create mode 100644 sanity-desk/HOTEL RESERVATION APP MICROSERVICE ARCHITECTURE.md diff --git a/sanity-desk/HOTEL RESERVATION APP MICROSERVICE ARCHITECTURE.md b/sanity-desk/HOTEL RESERVATION APP MICROSERVICE ARCHITECTURE.md new file mode 100644 index 00000000..5c9b9cb6 --- /dev/null +++ b/sanity-desk/HOTEL RESERVATION APP MICROSERVICE ARCHITECTURE.md @@ -0,0 +1,89 @@ +# Super MVP — sc-mvp/app-deploy + +## 1️⃣ Goal +Deploy a **hotel reservation application** onto the SC-MVP Kubernetes cluster and validate that the deployment is **idempotent, observable, and verifiably successful**, forming **Checkpoint SC-MVP-02** in the pipeline. + +--- + +## 2️⃣ Requirements + +| Requirement | Details | +| ----------- | ------- | +| **Target Cluster** | Existing SC-MVP cluster (from SC-MVP-01) | +| **Namespace** | `sc-mvp-test` | +| **Deployment Method** | Declarative Kubernetes manifests | +| **Idempotency** | Re-applying manifests must not cause errors or drift | +| **Verification Tools** | kubectl | +| **Logging Format** | CSV / JSON (SQLite ETL compatible) | +| **Rollback Strategy** | Automatic or manual rollback on failure | + +--- + +## 3️⃣ Deployment Steps + +### 3.1 Application Manifests +- Kubernetes **Deployment** manifest for the hotel reservation app +- Kubernetes **Service** manifest for internal/external access +- Optional **Ingress** manifest (environment-dependent) + +--- + +### 3.2 Apply Deployment +- Apply manifests to the `sc-mvp-test` namespace +- Ensure repeated `kubectl apply` operations are safe and consistent + +--- + +### 3.3 Rollout Verification +- Validate rollout completion using: + - `kubectl rollout status` + - Pod readiness and availability checks +- Confirm service endpoint accessibility + +--- + +### 3.4 Idempotency Validation +- Re-apply manifests +- Confirm: + - No unintended restarts + - No configuration drift + - Stable pod state + +--- + +## 4️⃣ Logging & Verification +- Capture stdout/stderr from deployment commands +- Record: + - Deployment timestamps (apply / start / ready) + - Pod status and restart counts + - Image tag and/or digest used +- Store logs in **CSV/JSON** format for SQLite ingestion +- Mark checkpoint as **PASS** only if rollout completes successfully + +--- + +## 5️⃣ Failure Handling & Safety +- On failure: + - Trigger rollback or enter explicit failed state + - Preserve cluster state and logs for audit +- Do not auto-delete resources unless explicitly configured + +--- + +## 6️⃣ Deliverables +- Application deployment manifests +- Rollout verification logs (CSV/JSON) +- Idempotency validation evidence +- Documentation describing: + - Deployment procedure + - Verification steps + - Re-run behavior and constraints + +--- + +## Checkpoint Summary + +**Checkpoint ID:** SC-MVP-02 +**Branch:** `sc-mvp/app-deploy` +**Purpose:** App Deployment & Rollout Verification +**Status:** ☐ PASS / ☐ FAIL (to be recorded during execution) From 4ff9bd77aa59a5139628ef50f6b2c8fe916862f2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?abstract=E2=81=B7?= Date: Mon, 19 Jan 2026 23:48:02 +0800 Subject: [PATCH 03/15] Create VitrixLab Add repository roles and permissions governance document This change introduces a clear, auditable definition of repository access roles to enforce least-privilege access and contributor governance. The document defines: - Read, Triage, and Write roles with explicit permissions - Usage guidance for each role - Governance principles for access control and auditability Purpose: ensure secure, compliant, and traceable access management aligned with AIOpsLab quality and safety standards. --- VitrixLab | 55 +++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 55 insertions(+) create mode 100644 VitrixLab diff --git a/VitrixLab b/VitrixLab new file mode 100644 index 00000000..bad6afa3 --- /dev/null +++ b/VitrixLab @@ -0,0 +1,55 @@ +# Repository Roles & Permissions + +This document defines the standard access roles used to manage permissions and governance for this repository. + +--- + +## Purpose + +Ensure clear ownership, least-privilege access, and auditable contribution paths. + +--- + +## Pre-Defined Roles + +### Read + +- Read and clone repositories +- Open and comment on issues +- Open and comment on pull requests + +**Use for:** Viewers, auditors, and observers + +--- + +### Triage + +Includes all **Read** permissions, plus: + +- Manage issues +- Manage pull requests + +**Use for:** QA reviewers, documentation stewards, and maintainers in training + +--- + +### Write + +Includes all **Triage** permissions, plus: + +- Push to repositories + +**Use for:** Core contributors and maintainers + +--- + +## Governance Principles + +- Apply **least privilege** by default +- Grant Write access only after governance review +- All role changes must be auditable + +--- + +> Framework Alignment: AIOpsLab, CMARC-2026, AI Safe Engineering +> Status: Active From e25806f9c0e94bc0a8dd0378a3a70134cf2a3425 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?abstract=E2=81=B7?= Date: Tue, 20 Jan 2026 01:06:23 +0800 Subject: [PATCH 04/15] Create README Add repository roles and permissions governance document This change introduces a clear, auditable definition of repository access roles to enforce least-privilege access and contributor governance. The document defines: - Read, Triage, and Write roles with explicit permissions - Usage guidance for each role - Governance principles for access control and auditability Purpose: ensure secure, compliant, and traceable access management aligned with AIOpsLab quality and safety standards. --- README | 55 +++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 55 insertions(+) create mode 100644 README diff --git a/README b/README new file mode 100644 index 00000000..bad6afa3 --- /dev/null +++ b/README @@ -0,0 +1,55 @@ +# Repository Roles & Permissions + +This document defines the standard access roles used to manage permissions and governance for this repository. + +--- + +## Purpose + +Ensure clear ownership, least-privilege access, and auditable contribution paths. + +--- + +## Pre-Defined Roles + +### Read + +- Read and clone repositories +- Open and comment on issues +- Open and comment on pull requests + +**Use for:** Viewers, auditors, and observers + +--- + +### Triage + +Includes all **Read** permissions, plus: + +- Manage issues +- Manage pull requests + +**Use for:** QA reviewers, documentation stewards, and maintainers in training + +--- + +### Write + +Includes all **Triage** permissions, plus: + +- Push to repositories + +**Use for:** Core contributors and maintainers + +--- + +## Governance Principles + +- Apply **least privilege** by default +- Grant Write access only after governance review +- All role changes must be auditable + +--- + +> Framework Alignment: AIOpsLab, CMARC-2026, AI Safe Engineering +> Status: Active From 8f61c1a24c637ff661ceb69878dc8a887be30837 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?abstract=E2=81=B7?= Date: Tue, 20 Jan 2026 01:07:45 +0800 Subject: [PATCH 05/15] Delete VitrixLab --- VitrixLab | 55 ------------------------------------------------------- 1 file changed, 55 deletions(-) delete mode 100644 VitrixLab diff --git a/VitrixLab b/VitrixLab deleted file mode 100644 index bad6afa3..00000000 --- a/VitrixLab +++ /dev/null @@ -1,55 +0,0 @@ -# Repository Roles & Permissions - -This document defines the standard access roles used to manage permissions and governance for this repository. - ---- - -## Purpose - -Ensure clear ownership, least-privilege access, and auditable contribution paths. - ---- - -## Pre-Defined Roles - -### Read - -- Read and clone repositories -- Open and comment on issues -- Open and comment on pull requests - -**Use for:** Viewers, auditors, and observers - ---- - -### Triage - -Includes all **Read** permissions, plus: - -- Manage issues -- Manage pull requests - -**Use for:** QA reviewers, documentation stewards, and maintainers in training - ---- - -### Write - -Includes all **Triage** permissions, plus: - -- Push to repositories - -**Use for:** Core contributors and maintainers - ---- - -## Governance Principles - -- Apply **least privilege** by default -- Grant Write access only after governance review -- All role changes must be auditable - ---- - -> Framework Alignment: AIOpsLab, CMARC-2026, AI Safe Engineering -> Status: Active From 67c75fdc77a90ca61e1fd0d04e8e79a3ca23fb60 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?abstract=E2=81=B7?= Date: Tue, 20 Jan 2026 01:08:42 +0800 Subject: [PATCH 06/15] Create README.md Add repository roles and permissions governance document This change introduces a clear, auditable definition of repository access roles to enforce least-privilege access and contributor governance. The document defines: - Read, Triage, and Write roles with explicit permissions - Usage guidance for each role - Governance principles for access control and auditability Purpose: ensure secure, compliant, and traceable access management aligned with AIOpsLab quality and safety standards. --- vitrixlab/README.md | 55 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 55 insertions(+) create mode 100644 vitrixlab/README.md diff --git a/vitrixlab/README.md b/vitrixlab/README.md new file mode 100644 index 00000000..bad6afa3 --- /dev/null +++ b/vitrixlab/README.md @@ -0,0 +1,55 @@ +# Repository Roles & Permissions + +This document defines the standard access roles used to manage permissions and governance for this repository. + +--- + +## Purpose + +Ensure clear ownership, least-privilege access, and auditable contribution paths. + +--- + +## Pre-Defined Roles + +### Read + +- Read and clone repositories +- Open and comment on issues +- Open and comment on pull requests + +**Use for:** Viewers, auditors, and observers + +--- + +### Triage + +Includes all **Read** permissions, plus: + +- Manage issues +- Manage pull requests + +**Use for:** QA reviewers, documentation stewards, and maintainers in training + +--- + +### Write + +Includes all **Triage** permissions, plus: + +- Push to repositories + +**Use for:** Core contributors and maintainers + +--- + +## Governance Principles + +- Apply **least privilege** by default +- Grant Write access only after governance review +- All role changes must be auditable + +--- + +> Framework Alignment: AIOpsLab, CMARC-2026, AI Safe Engineering +> Status: Active From bccb0106d7563491499e107d1c5647459620b2be Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?abstract=E2=81=B7?= Date: Tue, 20 Jan 2026 01:09:54 +0800 Subject: [PATCH 07/15] Create BASIC INFRA REQs.md --- vitrixlab/BASIC INFRA REQs.md | 80 +++++++++++++++++++++++++++++++++++ 1 file changed, 80 insertions(+) create mode 100644 vitrixlab/BASIC INFRA REQs.md diff --git a/vitrixlab/BASIC INFRA REQs.md b/vitrixlab/BASIC INFRA REQs.md new file mode 100644 index 00000000..797a3cd7 --- /dev/null +++ b/vitrixlab/BASIC INFRA REQs.md @@ -0,0 +1,80 @@ +# Super MVP — sc-mvp/cluster-setup + +## 1️⃣ Goal +Spin up a **lightweight, reproducible Kubernetes cluster** using **k3s or kind**, forming the foundation for the SC-MVP pipeline. + +--- + +## 2️⃣ Requirements + +| Requirement | Details | +| ----------- | ------- | +| **Cluster Type** | k3s (lightweight Kubernetes) or kind (Kubernetes in Docker) | +| **Nodes** | 1 control-plane + 1 worker node minimum | +| **Resource Limits** | CPU: 500m, Memory: 512Mi per node | +| **Namespace Isolation** | Optional namespace `sc-mvp-test` for app deployments | +| **Tools Required** | Docker, kubectl, kind or k3s CLI | +| **Reproducibility** | Cluster should be reproducible on any contributor machine | + +--- + +## 3️⃣ Deployment Steps (Kind Example) + +1. **Create a kind configuration file** + +`kind-config.yaml`: + +2. **Create the cluster** + +`kind create cluster --name sc-mvp --config kind-config.yaml` + +3. **Verify cluster status** + +` +kubectl cluster-info --context kind-sc-mvp +kubectl get nodes +` + +4. **Opt: Create namespace for testing** + +`kubectl create namespace sc-mvp-test` + +5. **Check namespace** + +`kubectl get ns` + +4️⃣ Logging & Verification + +1. Capture stdout/stderr of `kind create cluster`. + +2. Record `kubectl get nodes` output. + +3. Timestamp logs for reproducibility. + +4. Ensure nodes are `Ready` before proceeding to app deployment. + +5️⃣ Optional Safety Features + +1. Delete cluster on failure or cleanup: + +2. `kind delete cluster --name sc-mvp` + +3. Set resource constraints in Docker for nodes if machine resources are limited. + +4. Verify Docker daemon is running before cluster creation. + +6️⃣ Deliverables + +1. `kind-config.yaml` → Cluster configuration manifest + +2. Deployment logs → `sc-mvp-cluster-setup.log` + +3. Optional namespace `sc-mvp-test` for app deployment + +4. Documentation of steps for reproducibility +```yaml +kind: Cluster +apiVersion: kind.x-k8s.io/v1alpha4 +nodes: + - role: control-plane + - role: worker From 8c7e6557fbd04c8aaef1a3a34a822d80069f652e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?abstract=E2=81=B7?= Date: Tue, 20 Jan 2026 01:12:07 +0800 Subject: [PATCH 08/15] Create HOTEL RESERVATION APP MICROSERVICE ARCHITECTURE.md --- ...SERVATION APP MICROSERVICE ARCHITECTURE.md | 89 +++++++++++++++++++ 1 file changed, 89 insertions(+) create mode 100644 vitrixlab/HOTEL RESERVATION APP MICROSERVICE ARCHITECTURE.md diff --git a/vitrixlab/HOTEL RESERVATION APP MICROSERVICE ARCHITECTURE.md b/vitrixlab/HOTEL RESERVATION APP MICROSERVICE ARCHITECTURE.md new file mode 100644 index 00000000..5c9b9cb6 --- /dev/null +++ b/vitrixlab/HOTEL RESERVATION APP MICROSERVICE ARCHITECTURE.md @@ -0,0 +1,89 @@ +# Super MVP — sc-mvp/app-deploy + +## 1️⃣ Goal +Deploy a **hotel reservation application** onto the SC-MVP Kubernetes cluster and validate that the deployment is **idempotent, observable, and verifiably successful**, forming **Checkpoint SC-MVP-02** in the pipeline. + +--- + +## 2️⃣ Requirements + +| Requirement | Details | +| ----------- | ------- | +| **Target Cluster** | Existing SC-MVP cluster (from SC-MVP-01) | +| **Namespace** | `sc-mvp-test` | +| **Deployment Method** | Declarative Kubernetes manifests | +| **Idempotency** | Re-applying manifests must not cause errors or drift | +| **Verification Tools** | kubectl | +| **Logging Format** | CSV / JSON (SQLite ETL compatible) | +| **Rollback Strategy** | Automatic or manual rollback on failure | + +--- + +## 3️⃣ Deployment Steps + +### 3.1 Application Manifests +- Kubernetes **Deployment** manifest for the hotel reservation app +- Kubernetes **Service** manifest for internal/external access +- Optional **Ingress** manifest (environment-dependent) + +--- + +### 3.2 Apply Deployment +- Apply manifests to the `sc-mvp-test` namespace +- Ensure repeated `kubectl apply` operations are safe and consistent + +--- + +### 3.3 Rollout Verification +- Validate rollout completion using: + - `kubectl rollout status` + - Pod readiness and availability checks +- Confirm service endpoint accessibility + +--- + +### 3.4 Idempotency Validation +- Re-apply manifests +- Confirm: + - No unintended restarts + - No configuration drift + - Stable pod state + +--- + +## 4️⃣ Logging & Verification +- Capture stdout/stderr from deployment commands +- Record: + - Deployment timestamps (apply / start / ready) + - Pod status and restart counts + - Image tag and/or digest used +- Store logs in **CSV/JSON** format for SQLite ingestion +- Mark checkpoint as **PASS** only if rollout completes successfully + +--- + +## 5️⃣ Failure Handling & Safety +- On failure: + - Trigger rollback or enter explicit failed state + - Preserve cluster state and logs for audit +- Do not auto-delete resources unless explicitly configured + +--- + +## 6️⃣ Deliverables +- Application deployment manifests +- Rollout verification logs (CSV/JSON) +- Idempotency validation evidence +- Documentation describing: + - Deployment procedure + - Verification steps + - Re-run behavior and constraints + +--- + +## Checkpoint Summary + +**Checkpoint ID:** SC-MVP-02 +**Branch:** `sc-mvp/app-deploy` +**Purpose:** App Deployment & Rollout Verification +**Status:** ☐ PASS / ☐ FAIL (to be recorded during execution) From 40d67409c4e6e8accf18017abbca0c6aace22f82 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?abstract=E2=81=B7?= Date: Tue, 20 Jan 2026 01:20:05 +0800 Subject: [PATCH 09/15] Create LICENSE --- vitrixlab/LICENSE | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 vitrixlab/LICENSE diff --git a/vitrixlab/LICENSE b/vitrixlab/LICENSE new file mode 100644 index 00000000..55c7317f --- /dev/null +++ b/vitrixlab/LICENSE @@ -0,0 +1,21 @@ +MIT License + +Copyright (c) 2026 VitrixLab Internship Initiative Program and Jason "Soo Ji" Dano | Peper Cruz + +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. From 6942f4c2330fb22dab82825be9a45362cf4f8758 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?abstract=E2=81=B7?= Date: Tue, 20 Jan 2026 01:20:37 +0800 Subject: [PATCH 10/15] Update LICENSE --- vitrixlab/LICENSE | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/vitrixlab/LICENSE b/vitrixlab/LICENSE index 55c7317f..70439c36 100644 --- a/vitrixlab/LICENSE +++ b/vitrixlab/LICENSE @@ -1,6 +1,6 @@ MIT License -Copyright (c) 2026 VitrixLab Internship Initiative Program and Jason "Soo Ji" Dano | Peper Cruz +Copyright (c) 2026 VitrixLab Internship Initiative Program, Jason "Soo Ji" Dano | Peper Cruz, et.al Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal From dd94d02316d0e7b8adf1cbea652c4276f9a8eeff Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?abstract=E2=81=B7?= Date: Tue, 20 Jan 2026 01:53:39 +0800 Subject: [PATCH 11/15] Update LICENSE.txt --- LICENSE.txt | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/LICENSE.txt b/LICENSE.txt index 63447fd8..e7281235 100644 --- a/LICENSE.txt +++ b/LICENSE.txt @@ -1,4 +1,5 @@ -Copyright (c) Microsoft Corporation. +Copyright (c) 2026 Microsoft, VitrixLab, VitrixLab Internship Initiative Program +and Jason "Soo Ji" Dano | "Peper Cruz" Et.al MIT License @@ -18,4 +19,4 @@ 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. \ No newline at end of file +SOFTWARE. From 3ca21137e2cb5c721c6b0ec690ee4915e95af132 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?abstract=E2=81=B7?= Date: Tue, 20 Jan 2026 01:58:14 +0800 Subject: [PATCH 12/15] Update README.md LICENSE contributor VitrixLab, VitrixLab Internship Initiative Program and Jason "Soo Ji" Dano | "Peper Cruz" Et.al --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index cdf87afd..264f8635 100644 --- a/README.md +++ b/README.md @@ -473,7 +473,7 @@ This project has adopted the [Microsoft Open Source Code of Conduct](https://ope ## License -Copyright (c) Microsoft Corporation. All rights reserved. +Copyright (c) Microsoft Corporation, , VitrixLab, VitrixLab Internship Initiative Program and Jason "Soo Ji" Dano | "Peper Cruz" Et.al. All rights reserved. Licensed under the [MIT](LICENSE.txt) license. From 93daefb1556aa3b4498ada6371b09c542e46f35d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?abstract=E2=81=B7?= Date: Tue, 20 Jan 2026 01:59:28 +0800 Subject: [PATCH 13/15] Update README.md adding License contributors: VitrixLab, VitrixLab Internship Initiative Program and Jason "Soo Ji" Dano | "Peper Cruz" Et.al --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 264f8635..810fef48 100644 --- a/README.md +++ b/README.md @@ -473,7 +473,7 @@ This project has adopted the [Microsoft Open Source Code of Conduct](https://ope ## License -Copyright (c) Microsoft Corporation, , VitrixLab, VitrixLab Internship Initiative Program and Jason "Soo Ji" Dano | "Peper Cruz" Et.al. All rights reserved. +Copyright (c) Microsoft Corporation, VitrixLab, VitrixLab Internship Initiative Program and Jason "Soo Ji" Dano | "Peper Cruz" Et.al. All rights reserved. Licensed under the [MIT](LICENSE.txt) license. From c0e53b35f2d3382a72906c78464921c2c80e243b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?abstract=E2=81=B7?= Date: Tue, 20 Jan 2026 13:37:02 +0800 Subject: [PATCH 14/15] Create LICENSE --- LICENSE | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 LICENSE diff --git a/LICENSE b/LICENSE new file mode 100644 index 00000000..a1f6c0e1 --- /dev/null +++ b/LICENSE @@ -0,0 +1,21 @@ +MIT License + +Copyright (c) 2026 Peper Cruz(ORCID#: 0009-0001-4034-0056) + +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. From a8fe5ed4b81e7df5492c78dd73817c9197d21db1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?abstract=E2=81=B7?= Date: Tue, 20 Jan 2026 13:38:29 +0800 Subject: [PATCH 15/15] Update LICENSE --- LICENSE | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/LICENSE b/LICENSE index a1f6c0e1..6af69692 100644 --- a/LICENSE +++ b/LICENSE @@ -1,6 +1,7 @@ MIT License -Copyright (c) 2026 Peper Cruz(ORCID#: 0009-0001-4034-0056) +Copyright (c) 2026 Microsoft, VitrixLab, VitrixLab Internship Initiative Program +and Jason "Soo Ji" Dano | "Peper Cruz" Et.al Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal