diff --git a/lab/development/us-gov-east-1/vpc/platform-eng-eks-mcm/notes.txt b/lab/development/us-gov-east-1/vpc/platform-eng-eks-mcm/notes.txt
deleted file mode 100644
index 71c3774..0000000
--- a/lab/development/us-gov-east-1/vpc/platform-eng-eks-mcm/notes.txt
+++ /dev/null
@@ -1,68 +0,0 @@
-Provider Configuration Changes and Cluster Lifecycle Management
-==========================================================
-
-Problem:
---------
-The original provider configuration in root.hcl had issues handling different cluster lifecycle states:
-1. When no cluster exists - terragrunt run-all plan would fail
-2. When cluster is being created - terragrunt run-all apply needed to work
-3. When cluster is being destroyed - terragrunt run-all destroy needed to work
-
-The main issue was that the provider configurations were using data sources that required the cluster to exist, causing failures during planning when the cluster didn't exist.
-
-Solution:
----------
-1. Moved provider configurations to separate files in _envcommon/:
-   - helm-provider.hcl
-   - kube-provider.hcl
-
-2. Added conditional data source lookup using count:
-   data "aws_eks_cluster" "this" {
-     count = var.create_eks ? 1 : 0
-     name  = local.cluster_name
-   }
-
-3. Used try() function with empty fallback values:
-   host = try(data.aws_eks_cluster.this[0].endpoint, "")
-   cluster_ca_certificate = try(base64decode(data.aws_eks_cluster.this[0].certificate_authority[0].data), "")
-
-4. Added create_eks variable control:
-   - Added to root.hcl locals block
-   - Controlled via TERRAGRUNT_CREATE_EKS environment variable
-   - Defaults to "true"
-   - Generated as a variable in each module
-
-How it works:
-------------
-1. No cluster exists:
-   - Set TERRAGRUNT_CREATE_EKS=false
-   - Data source won't be created (count = 0)
-   - Provider configurations fall back to empty values
-   - Plan succeeds as providers are configured but not used
-
-2. Creating cluster:
-   - TERRAGRUNT_CREATE_EKS=true (default)
-   - As soon as cluster exists, data source becomes available
-   - Provider configurations get real values
-   - Apply continues with working providers
-
-3. Destroying cluster:
-   - Set TERRAGRUNT_CREATE_EKS=false before destroy
-   - Providers fall back to empty values
-   - Resources can be destroyed without needing cluster access
-
-Usage:
-------
-1. For initial plan with no cluster:
-   export TERRAGRUNT_CREATE_EKS=false
-   terragrunt run-all plan
-
-2. For creating cluster and resources:
-   export TERRAGRUNT_CREATE_EKS=true (or don't set it)
-   terragrunt run-all apply
-
-3. For destroying everything:
-   export TERRAGRUNT_CREATE_EKS=false
-   terragrunt run-all destroy
-
-This solution allows Terragrunt to handle the full lifecycle of the cluster and its dependent resources without failing on provider initialization when the cluster doesn't exist.
\ No newline at end of file
diff --git a/platform-tg-infra.code-workspace b/platform-tg-infra.code-workspace
deleted file mode 100644
index dec7709..0000000
--- a/platform-tg-infra.code-workspace
+++ /dev/null
@@ -1,29 +0,0 @@
-{
-	"folders": [
-		{
-			"path": "."
-		},
-		{
-			"path": "../terraform-provider-github/website/docs/d",
-			"name": "provider/aws/data-sources"
-		},
-		{
-			"path": "../terraform-provider-github/website/docs/r",
-			"name": "provider/aws/resources"
-		},
-		{
-			"path": "../terraform/website/docs/language/tests",
-			"name": "terraform/tests"
-		},
-		{
-			"path": "../terraform/website/docs/language/syntax",
-			"name": "terraform/syntax"
-		},
-		{
-			"path": "../terragrunt"
-		}
-	],
-	"settings": {
-		
-	}
-}