# 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-ORIGINAL-PLACEHOLDER>`  <!-- Replace with local artifact hash -->
- SHA256 (Microsoft Official): `<SHA256-MICROSOFT-PLACEHOLDER>`  <!-- Replace with official upstream hash -->

## Commit Email
vitrixlabph@gmail.com

## 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-CONTRI-PLACEHOLDER>`
- **SHA256 (Microsoft Official):** `<SHA256-MICROSOFT-PLACEHOLDER>`

### Commit Email
`vitrixlabph@gmail.com`

Create HOTEL RESERVATION APP MICROSERVICE ARCHITECTURE.md

Create BASIC INFRA REQS.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.

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.

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.

LICENSE contributor VitrixLab, VitrixLab Internship Initiative Program 
and Jason "Soo Ji" Dano | "Peper Cruz" Et.al

adding License contributors: VitrixLab, VitrixLab Internship Initiative Program and Jason "Soo Ji" Dano | "Peper Cruz" Et.al