@k-4u/resource-mapper-core 0.0.1 → 0.1.0

package/coverage/junit.xml

@@ -1,16 +1,16 @@
 <?xml version="1.0" encoding="UTF-8" ?>
-<testsuites name="vitest tests" tests="13" failures="0" errors="0" time="0.1478274">
-    <testsuite name="src/lib/stores/routingStore.test.ts" timestamp="2026-03-01T15:03:16.684Z" hostname="Enterprise-E" tests="3" failures="0" errors="0" skipped="0" time="0.0232313">
-        <testcase classname="src/lib/stores/routingStore.test.ts" name="routingStore &gt; registers nodes and routes an edge between them" time="0.0183271">
+<testsuites name="vitest tests" tests="13" failures="0" errors="0" time="0.198621727">
+    <testsuite name="src/lib/stores/routingStore.test.ts" timestamp="2026-03-01T19:33:50.745Z" hostname="runnervmnay03" tests="3" failures="0" errors="0" skipped="0" time="0.045563939">
+        <testcase classname="src/lib/stores/routingStore.test.ts" name="routingStore &gt; registers nodes and routes an edge between them" time="0.035593501">
         </testcase>
-        <testcase classname="src/lib/stores/routingStore.test.ts" name="routingStore &gt; nudges parallel edges apart" time="0.0025316">
+        <testcase classname="src/lib/stores/routingStore.test.ts" name="routingStore &gt; nudges parallel edges apart" time="0.005711891">
             <system-err>
 Warning: skipping checkpoint for connector 3 at (110, 125).
 Warning: skipping checkpoint for connector 3 at (290, 25).
 
             </system-err>
         </testcase>
-        <testcase classname="src/lib/stores/routingStore.test.ts" name="routingStore &gt; unregisters an edge and stops returning its points" time="0.0012705">
+        <testcase classname="src/lib/stores/routingStore.test.ts" name="routingStore &gt; unregisters an edge and stops returning its points" time="0.002712085">
             <system-err>
 Warning: skipping checkpoint for connector 8 at (110, 25).
 Warning: skipping checkpoint for connector 8 at (190, 225).
@@ -20,33 +20,33 @@ Warning: skipping checkpoint for connector 3 at (290, 25).
             </system-err>
         </testcase>
     </testsuite>
-    <testsuite name="src/lib/utils/flow/layout.test.ts" timestamp="2026-03-01T15:03:16.685Z" hostname="Enterprise-E" tests="8" failures="0" errors="0" skipped="0" time="0.1099645">
-        <testcase classname="src/lib/utils/flow/layout.test.ts" name="layoutFlowGraph &gt; returns positions for nodes and preserves signature" time="0.0464308">
+    <testsuite name="src/lib/utils/flow/layout.test.ts" timestamp="2026-03-01T19:33:50.747Z" hostname="runnervmnay03" tests="8" failures="0" errors="0" skipped="0" time="0.120422438">
+        <testcase classname="src/lib/utils/flow/layout.test.ts" name="layoutFlowGraph &gt; returns positions for nodes and preserves signature" time="0.084868932">
         </testcase>
-        <testcase classname="src/lib/utils/flow/layout.test.ts" name="layoutFlowGraph &gt; keeps nodes and edges ids and data" time="0.0306708">
+        <testcase classname="src/lib/utils/flow/layout.test.ts" name="layoutFlowGraph &gt; keeps nodes and edges ids and data" time="0.018879042">
         </testcase>
-        <testcase classname="src/lib/utils/flow/layout.test.ts" name="layoutFlowGraph &gt; handles a simple group with a child service node" time="0.0307378">
+        <testcase classname="src/lib/utils/flow/layout.test.ts" name="layoutFlowGraph &gt; handles a simple group with a child service node" time="0.013336326">
         </testcase>
-        <testcase classname="src/lib/utils/flow/layout.test.ts" name="calculateEdgeOffset &gt; returns 0 for a single edge" time="0.0003235">
+        <testcase classname="src/lib/utils/flow/layout.test.ts" name="calculateEdgeOffset &gt; returns 0 for a single edge" time="0.000448215">
         </testcase>
-        <testcase classname="src/lib/utils/flow/layout.test.ts" name="calculateEdgeOffset &gt; spreads multiple edges and sorts them by target position" time="0.0001918">
+        <testcase classname="src/lib/utils/flow/layout.test.ts" name="calculateEdgeOffset &gt; spreads multiple edges and sorts them by target position" time="0.000410996">
         </testcase>
-        <testcase classname="src/lib/utils/flow/layout.test.ts" name="calculateEdgeOffset &gt; spreads three edges correctly" time="0.0001171">
+        <testcase classname="src/lib/utils/flow/layout.test.ts" name="calculateEdgeOffset &gt; spreads three edges correctly" time="0.000256267">
         </testcase>
-        <testcase classname="src/lib/utils/flow/layout.test.ts" name="calculateEdgeOffset &gt; correctly calculates offsets for nodes in groups vs orphans using absolute coordinates" time="0.0001915">
+        <testcase classname="src/lib/utils/flow/layout.test.ts" name="calculateEdgeOffset &gt; correctly calculates offsets for nodes in groups vs orphans using absolute coordinates" time="0.000372314">
         </testcase>
-        <testcase classname="src/lib/utils/flow/layout.test.ts" name="calculateEdgeOffset &gt; correctly calculates absolute coordinates for deeply nested nodes" time="0.0001133">
+        <testcase classname="src/lib/utils/flow/layout.test.ts" name="calculateEdgeOffset &gt; correctly calculates absolute coordinates for deeply nested nodes" time="0.00024674">
         </testcase>
     </testsuite>
-    <testsuite name="src/lib/utils/flow/servicesGraph.test.ts" timestamp="2026-03-01T15:03:16.687Z" hostname="Enterprise-E" tests="2" failures="0" errors="0" skipped="0" time="0.0146316">
-        <testcase classname="src/lib/utils/flow/servicesGraph.test.ts" name="servicesGraph &gt; correctly loads bidirectional connections between two services in the same group" time="0.0121974">
+    <testsuite name="src/lib/utils/flow/servicesGraph.test.ts" timestamp="2026-03-01T19:33:50.749Z" hostname="runnervmnay03" tests="2" failures="0" errors="0" skipped="0" time="0.03263535">
+        <testcase classname="src/lib/utils/flow/servicesGraph.test.ts" name="servicesGraph &gt; correctly loads bidirectional connections between two services in the same group" time="0.029560582">
             <system-out>
 Creating edge from svc::g1::svc-a to svc::g1::svc-b of type TCP (internal)
 Creating edge from svc::g1::svc-b to svc::g1::svc-a of type TCP (internal)
 
             </system-out>
         </testcase>
-        <testcase classname="src/lib/utils/flow/servicesGraph.test.ts" name="servicesGraph &gt; correctly loads bidirectional connections involving an external service" time="0.0012863">
+        <testcase classname="src/lib/utils/flow/servicesGraph.test.ts" name="servicesGraph &gt; correctly loads bidirectional connections involving an external service" time="0.001290834">
             <system-out>
 Creating edge from svc::g1::svc-a to svc::g2::svc-ext of type TCP (external)
 Creating edge from svc::g2::svc-ext to svc::g1::svc-a of type TCP (external)

package/coverage/test-results.json

@@ -1 +1 @@
-{"numTotalTestSuites":7,"numPassedTestSuites":7,"numFailedTestSuites":0,"numPendingTestSuites":0,"numTotalTests":13,"numPassedTests":13,"numFailedTests":0,"numPendingTests":0,"numTodoTests":0,"snapshot":{"added":0,"failure":false,"filesAdded":0,"filesRemoved":0,"filesRemovedList":[],"filesUnmatched":0,"filesUpdated":0,"matched":0,"total":0,"unchecked":0,"uncheckedKeysByFile":[],"unmatched":0,"updated":0,"didUpdate":false},"startTime":1772377394792,"success":true,"testResults":[{"assertionResults":[{"ancestorTitles":["routingStore"],"fullName":"routingStore registers nodes and routes an edge between them","status":"passed","title":"registers nodes and routes an edge between them","duration":18.327099999999973,"failureMessages":[],"meta":{}},{"ancestorTitles":["routingStore"],"fullName":"routingStore nudges parallel edges apart","status":"passed","title":"nudges parallel edges apart","duration":2.531600000000026,"failureMessages":[],"meta":{}},{"ancestorTitles":["routingStore"],"fullName":"routingStore unregisters an edge and stops returning its points","status":"passed","title":"unregisters an edge and stops returning its points","duration":1.2704999999998563,"failureMessages":[],"meta":{}}],"startTime":1772377396567,"endTime":1772377396589.2705,"status":"passed","message":"","name":"C:/Users/koen/IdeaProjects/resource-mapper/packages/core/src/lib/stores/routingStore.test.ts"},{"assertionResults":[{"ancestorTitles":["layoutFlowGraph"],"fullName":"layoutFlowGraph returns positions for nodes and preserves signature","status":"passed","title":"returns positions for nodes and preserves signature","duration":46.43079999999986,"failureMessages":[],"meta":{}},{"ancestorTitles":["layoutFlowGraph"],"fullName":"layoutFlowGraph keeps nodes and edges ids and data","status":"passed","title":"keeps nodes and edges ids and data","duration":30.670799999999872,"failureMessages":[],"meta":{}},{"ancestorTitles":["layoutFlowGraph"],"fullName":"layoutFlowGraph handles a simple group with a child service node","status":"passed","title":"handles a simple group with a child service node","duration":30.737800000000107,"failureMessages":[],"meta":{}},{"ancestorTitles":["calculateEdgeOffset"],"fullName":"calculateEdgeOffset returns 0 for a single edge","status":"passed","title":"returns 0 for a single edge","duration":0.32349999999996726,"failureMessages":[],"meta":{}},{"ancestorTitles":["calculateEdgeOffset"],"fullName":"calculateEdgeOffset spreads multiple edges and sorts them by target position","status":"passed","title":"spreads multiple edges and sorts them by target position","duration":0.19180000000005748,"failureMessages":[],"meta":{}},{"ancestorTitles":["calculateEdgeOffset"],"fullName":"calculateEdgeOffset spreads three edges correctly","status":"passed","title":"spreads three edges correctly","duration":0.1170999999999367,"failureMessages":[],"meta":{}},{"ancestorTitles":["calculateEdgeOffset"],"fullName":"calculateEdgeOffset correctly calculates offsets for nodes in groups vs orphans using absolute coordinates","status":"passed","title":"correctly calculates offsets for nodes in groups vs orphans using absolute coordinates","duration":0.1915000000001328,"failureMessages":[],"meta":{}},{"ancestorTitles":["calculateEdgeOffset"],"fullName":"calculateEdgeOffset correctly calculates absolute coordinates for deeply nested nodes","status":"passed","title":"correctly calculates absolute coordinates for deeply nested nodes","duration":0.11329999999998108,"failureMessages":[],"meta":{}}],"startTime":1772377396569,"endTime":1772377396678.1914,"status":"passed","message":"","name":"C:/Users/koen/IdeaProjects/resource-mapper/packages/core/src/lib/utils/flow/layout.test.ts"},{"assertionResults":[{"ancestorTitles":["servicesGraph"],"fullName":"servicesGraph correctly loads bidirectional connections between two services in the same group","status":"passed","title":"correctly loads bidirectional connections between two services in the same group","duration":12.197400000000016,"failureMessages":[],"meta":{}},{"ancestorTitles":["servicesGraph"],"fullName":"servicesGraph correctly loads bidirectional connections involving an external service","status":"passed","title":"correctly loads bidirectional connections involving an external service","duration":1.2863000000000113,"failureMessages":[],"meta":{}}],"startTime":1772377395041,"endTime":1772377395055.2864,"status":"passed","message":"","name":"C:/Users/koen/IdeaProjects/resource-mapper/packages/core/src/lib/utils/flow/servicesGraph.test.ts"}]}
+{"numTotalTestSuites":7,"numPassedTestSuites":7,"numFailedTestSuites":0,"numPendingTestSuites":0,"numTotalTests":13,"numPassedTests":13,"numFailedTests":0,"numPendingTests":0,"numTodoTests":0,"snapshot":{"added":0,"failure":false,"filesAdded":0,"filesRemoved":0,"filesRemovedList":[],"filesUnmatched":0,"filesUpdated":0,"matched":0,"total":0,"unchecked":0,"uncheckedKeysByFile":[],"unmatched":0,"updated":0,"didUpdate":false},"startTime":1772393628529,"success":true,"testResults":[{"assertionResults":[{"ancestorTitles":["routingStore"],"fullName":"routingStore registers nodes and routes an edge between them","status":"passed","title":"registers nodes and routes an edge between them","duration":35.59350100000029,"failureMessages":[],"meta":{}},{"ancestorTitles":["routingStore"],"fullName":"routingStore nudges parallel edges apart","status":"passed","title":"nudges parallel edges apart","duration":5.711890999999923,"failureMessages":[],"meta":{}},{"ancestorTitles":["routingStore"],"fullName":"routingStore unregisters an edge and stops returning its points","status":"passed","title":"unregisters an edge and stops returning its points","duration":2.7120850000001155,"failureMessages":[],"meta":{}}],"startTime":1772393630621,"endTime":1772393630664.7122,"status":"passed","message":"","name":"/home/runner/work/resource-mapper/resource-mapper/packages/core/src/lib/stores/routingStore.test.ts"},{"assertionResults":[{"ancestorTitles":["layoutFlowGraph"],"fullName":"layoutFlowGraph returns positions for nodes and preserves signature","status":"passed","title":"returns positions for nodes and preserves signature","duration":84.86893199999986,"failureMessages":[],"meta":{}},{"ancestorTitles":["layoutFlowGraph"],"fullName":"layoutFlowGraph keeps nodes and edges ids and data","status":"passed","title":"keeps nodes and edges ids and data","duration":18.879042000000027,"failureMessages":[],"meta":{}},{"ancestorTitles":["layoutFlowGraph"],"fullName":"layoutFlowGraph handles a simple group with a child service node","status":"passed","title":"handles a simple group with a child service node","duration":13.3363260000001,"failureMessages":[],"meta":{}},{"ancestorTitles":["calculateEdgeOffset"],"fullName":"calculateEdgeOffset returns 0 for a single edge","status":"passed","title":"returns 0 for a single edge","duration":0.448214999999891,"failureMessages":[],"meta":{}},{"ancestorTitles":["calculateEdgeOffset"],"fullName":"calculateEdgeOffset spreads multiple edges and sorts them by target position","status":"passed","title":"spreads multiple edges and sorts them by target position","duration":0.4109960000000683,"failureMessages":[],"meta":{}},{"ancestorTitles":["calculateEdgeOffset"],"fullName":"calculateEdgeOffset spreads three edges correctly","status":"passed","title":"spreads three edges correctly","duration":0.2562670000002072,"failureMessages":[],"meta":{}},{"ancestorTitles":["calculateEdgeOffset"],"fullName":"calculateEdgeOffset correctly calculates offsets for nodes in groups vs orphans using absolute coordinates","status":"passed","title":"correctly calculates offsets for nodes in groups vs orphans using absolute coordinates","duration":0.3723139999997329,"failureMessages":[],"meta":{}},{"ancestorTitles":["calculateEdgeOffset"],"fullName":"calculateEdgeOffset correctly calculates absolute coordinates for deeply nested nodes","status":"passed","title":"correctly calculates absolute coordinates for deeply nested nodes","duration":0.24674000000004526,"failureMessages":[],"meta":{}}],"startTime":1772393630616,"endTime":1772393630735.3723,"status":"passed","message":"","name":"/home/runner/work/resource-mapper/resource-mapper/packages/core/src/lib/utils/flow/layout.test.ts"},{"assertionResults":[{"ancestorTitles":["servicesGraph"],"fullName":"servicesGraph correctly loads bidirectional connections between two services in the same group","status":"passed","title":"correctly loads bidirectional connections between two services in the same group","duration":29.56058200000001,"failureMessages":[],"meta":{}},{"ancestorTitles":["servicesGraph"],"fullName":"servicesGraph correctly loads bidirectional connections involving an external service","status":"passed","title":"correctly loads bidirectional connections involving an external service","duration":1.290834000000018,"failureMessages":[],"meta":{}}],"startTime":1772393629006,"endTime":1772393629036.2908,"status":"passed","message":"","name":"/home/runner/work/resource-mapper/resource-mapper/packages/core/src/lib/utils/flow/servicesGraph.test.ts"}]}

package/data/services/api/api-gateway.yaml

@@ -1,18 +1,18 @@
-friendlyName: "API Gateway"
-description: |
-  RESTful API Gateway managing HTTP requests and routing to backend Lambda functions.
-  
-  Provides request/response transformation, authorization, throttling, and API versioning.
-  Configured with custom domain, CORS, and request validation.
-serviceType: API_GATEWAY
-outgoingConnections:
-  - targetIdentifier: "api/lambda-users"
-    description: "Routes user management requests"
-    connectionType: CALLS
-  - targetIdentifier: "api/lambda-orders"
-    description: "Routes order processing requests"
-    connectionType: CALLS
-  - targetIdentifier: "api/lambda-products"
-    description: "Routes product catalog requests"
-    connectionType: CALLS
-
+friendlyName: "API Gateway"
+description: |
+  RESTful API Gateway managing HTTP requests and routing to backend Lambda functions.
+  
+  Provides request/response transformation, authorization, throttling, and API versioning.
+  Configured with custom domain, CORS, and request validation.
+serviceType: API_GATEWAY
+outgoingConnections:
+  - targetIdentifier: "api/lambda-users"
+    description: "Routes user management requests"
+    connectionType: CALLS
+  - targetIdentifier: "api/lambda-orders"
+    description: "Routes order processing requests"
+    connectionType: CALLS
+  - targetIdentifier: "api/lambda-products"
+    description: "Routes product catalog requests"
+    connectionType: CALLS
+

package/data/services/api/group-info.yaml

@@ -1,7 +1,7 @@
-name: "API Services"
-description: |
-  Manages serverless API infrastructure with API Gateway and Lambda functions.
-  This group handles RESTful API endpoints, authentication, request routing,
-  and serverless compute for business logic.
-teamId: "interface-architects"
-
+name: "API Services"
+description: |
+  Manages serverless API infrastructure with API Gateway and Lambda functions.
+  This group handles RESTful API endpoints, authentication, request routing,
+  and serverless compute for business logic.
+teamId: "interface-architects"
+

package/data/services/api/lambda-orders.yaml

@@ -1,21 +1,21 @@
-friendlyName: "Order Processing Lambda"
-description: |
-  Lambda function managing order creation, updates, and tracking.
-  
-  Handles complex order workflows including payment processing, inventory checks,
-  and order status updates. Interacts with multiple data stores for reliability.
-serviceType: LAMBDA
-outgoingConnections:
-  - targetIdentifier: "data/dynamodb-orders"
-    description: "Order data storage"
-    connectionType: CALLS
-  - targetIdentifier: "data/dynamodb-notifications"
-    description: "Order data storage"
-    connectionType: CALLS
-  - targetIdentifier: "data/rds-postgres"
-    description: "Transactional order processing"
-    connectionType: TCP
-  - targetIdentifier: "compute/ecs-inventory"
-    description: "Inventory validation"
-    connectionType: TCP
-
+friendlyName: "Order Processing Lambda"
+description: |
+  Lambda function managing order creation, updates, and tracking.
+  
+  Handles complex order workflows including payment processing, inventory checks,
+  and order status updates. Interacts with multiple data stores for reliability.
+serviceType: LAMBDA
+outgoingConnections:
+  - targetIdentifier: "data/dynamodb-orders"
+    description: "Order data storage"
+    connectionType: CALLS
+  - targetIdentifier: "data/dynamodb-notifications"
+    description: "Order data storage"
+    connectionType: CALLS
+  - targetIdentifier: "data/rds-postgres"
+    description: "Transactional order processing"
+    connectionType: TCP
+  - targetIdentifier: "compute/ecs-inventory"
+    description: "Inventory validation"
+    connectionType: TCP
+

package/data/services/api/lambda-products.yaml

@@ -1,15 +1,15 @@
-friendlyName: "Product Catalog Lambda"
-description: |
-  Lambda function managing product information, search, and recommendations.
-  
-  Provides fast product lookups with caching and search functionality.
-  Uses DynamoDB for quick reads and Redis cache for frequently accessed data.
-serviceType: LAMBDA
-outgoingConnections:
-  - targetIdentifier: "data/dynamodb-products"
-    description: "Product catalog data"
-    connectionType: CALLS
-  - targetIdentifier: "data/redis"
-    description: "Product cache for performance"
-    connectionType: TCP
-
+friendlyName: "Product Catalog Lambda"
+description: |
+  Lambda function managing product information, search, and recommendations.
+  
+  Provides fast product lookups with caching and search functionality.
+  Uses DynamoDB for quick reads and Redis cache for frequently accessed data.
+serviceType: LAMBDA
+outgoingConnections:
+  - targetIdentifier: "data/dynamodb-products"
+    description: "Product catalog data"
+    connectionType: CALLS
+  - targetIdentifier: "data/redis"
+    description: "Product cache for performance"
+    connectionType: TCP
+

package/data/services/api/lambda-users.yaml

@@ -1,15 +1,15 @@
-friendlyName: "User Management Lambda"
-description: |
-  Lambda function handling user authentication, registration, and profile management.
-  
-  Processes user-related API requests with JWT token validation and session management.
-  Connects to DynamoDB for user data storage and RDS for transactional operations.
-serviceType: LAMBDA
-outgoingConnections:
-  - targetIdentifier: "data/dynamodb-users"
-    description: "User data storage"
-    connectionType: CALLS
-  - targetIdentifier: "data/rds-postgres"
-    description: "User authentication data"
-    connectionType: TCP
-
+friendlyName: "User Management Lambda"
+description: |
+  Lambda function handling user authentication, registration, and profile management.
+  
+  Processes user-related API requests with JWT token validation and session management.
+  Connects to DynamoDB for user data storage and RDS for transactional operations.
+serviceType: LAMBDA
+outgoingConnections:
+  - targetIdentifier: "data/dynamodb-users"
+    description: "User data storage"
+    connectionType: CALLS
+  - targetIdentifier: "data/rds-postgres"
+    description: "User authentication data"
+    connectionType: TCP
+

package/data/services/compute/alb.yaml

@@ -1,15 +1,15 @@
-friendlyName: "Application Load Balancer"
-description: |
-  Application Load Balancer distributing traffic to ECS services across availability zones.
-  
-  Provides health checks, SSL termination, and intelligent routing with path-based rules.
-  Configured with auto-scaling and connection draining for zero-downtime deployments.
-serviceType: ALB
-outgoingConnections:
-  - targetIdentifier: "compute/ecs-inventory"
-    description: "Routes to inventory service"
-    connectionType: TCP
-  - targetIdentifier: "compute/ecs-notification"
-    description: "Routes to notification service"
-    connectionType: TCP
-
+friendlyName: "Application Load Balancer"
+description: |
+  Application Load Balancer distributing traffic to ECS services across availability zones.
+  
+  Provides health checks, SSL termination, and intelligent routing with path-based rules.
+  Configured with auto-scaling and connection draining for zero-downtime deployments.
+serviceType: ALB
+outgoingConnections:
+  - targetIdentifier: "compute/ecs-inventory"
+    description: "Routes to inventory service"
+    connectionType: TCP
+  - targetIdentifier: "compute/ecs-notification"
+    description: "Routes to notification service"
+    connectionType: TCP
+

package/data/services/compute/ecs-inventory.yaml

@@ -1,16 +1,16 @@
-friendlyName: "ECS Inventory Service"
-description: |
-  Containerized Spring Boot inventory management service running on ECS Fargate.
-  
-  REST API service handling real-time inventory tracking, stock updates, and warehouse management.
-  Built with Spring Boot, provides endpoints for inventory CRUD operations, stock level monitoring,
-  and automated reorder alerts. Auto-scales based on CPU and memory metrics.
-serviceType: ECS
-outgoingConnections:
-  - targetIdentifier: "data/rds-postgres"
-    description: "PostgreSQL database for inventory persistence"
-    connectionType: TCP
-  - targetIdentifier: "data/redis"
-    description: "Redis cache for high-frequency inventory lookups"
-    connectionType: TCP
-
+friendlyName: "ECS Inventory Service"
+description: |
+  Containerized Spring Boot inventory management service running on ECS Fargate.
+  
+  REST API service handling real-time inventory tracking, stock updates, and warehouse management.
+  Built with Spring Boot, provides endpoints for inventory CRUD operations, stock level monitoring,
+  and automated reorder alerts. Auto-scales based on CPU and memory metrics.
+serviceType: ECS
+outgoingConnections:
+  - targetIdentifier: "data/rds-postgres"
+    description: "PostgreSQL database for inventory persistence"
+    connectionType: TCP
+  - targetIdentifier: "data/redis"
+    description: "Redis cache for high-frequency inventory lookups"
+    connectionType: TCP
+

package/data/services/compute/ecs-notification.yaml

@@ -1,15 +1,15 @@
-friendlyName: "ECS Notification Service"
-description: |
-  Containerized notification service running on ECS for email and SMS delivery.
-  
-  Processes notification queues and sends alerts to users via multiple channels.
-  Integrates with external services and maintains delivery logs in DynamoDB.
-serviceType: ECS
-outgoingConnections:
-  - targetIdentifier: "data/dynamodb-notifications"
-    description: "Notification logs and queue"
-    connectionType: CALLS
-  - targetIdentifier: "data/redis"
-    description: "Redis cache for high-frequency inventory lookups"
-    connectionType: TCP
-
+friendlyName: "ECS Notification Service"
+description: |
+  Containerized notification service running on ECS for email and SMS delivery.
+  
+  Processes notification queues and sends alerts to users via multiple channels.
+  Integrates with external services and maintains delivery logs in DynamoDB.
+serviceType: ECS
+outgoingConnections:
+  - targetIdentifier: "data/dynamodb-notifications"
+    description: "Notification logs and queue"
+    connectionType: CALLS
+  - targetIdentifier: "data/redis"
+    description: "Redis cache for high-frequency inventory lookups"
+    connectionType: TCP
+

package/data/services/compute/group-info.yaml

@@ -1,7 +1,7 @@
-name: "Compute Services"
-description: |
-  Manages containerized applications, load balancers, and compute resources.
-  This group handles ECS clusters, container services, and application load balancers
-  for running stateful and long-running applications.
-teamId: "cloud-shepherds"
-
+name: "Compute Services"
+description: |
+  Manages containerized applications, load balancers, and compute resources.
+  This group handles ECS clusters, container services, and application load balancers
+  for running stateful and long-running applications.
+teamId: "cloud-shepherds"
+

package/data/services/data/dynamodb-notifications.yaml

@@ -1,12 +1,12 @@
-friendlyName: "DynamoDB Notifications Table"
-description: |
-  DynamoDB table tracking notification delivery status and queued messages.
-  
-  Manages notification queue with TTL for automatic cleanup of processed notifications.
-  Provides audit trail for compliance and debugging notification issues.
-serviceType: DYNAMODB
-outgoingConnections:
-  - targetIdentifier: "api/lambda-orders"
-    description: "Triggers order processing Lambda function"
-    connectionType: STREAM
-
+friendlyName: "DynamoDB Notifications Table"
+description: |
+  DynamoDB table tracking notification delivery status and queued messages.
+  
+  Manages notification queue with TTL for automatic cleanup of processed notifications.
+  Provides audit trail for compliance and debugging notification issues.
+serviceType: DYNAMODB
+outgoingConnections:
+  - targetIdentifier: "api/lambda-orders"
+    description: "Triggers order processing Lambda function"
+    connectionType: STREAM
+

package/data/services/data/dynamodb-orders.yaml

@@ -1,9 +1,9 @@
-friendlyName: "DynamoDB Orders Table"
-description: |
-  DynamoDB table storing order history and real-time order status tracking.
-  
-  Optimized for high-throughput reads and writes with TTL for order archival.
-  Uses DynamoDB Streams for event-driven order processing workflows.
-serviceType: DYNAMODB
-outgoingConnections: []
-
+friendlyName: "DynamoDB Orders Table"
+description: |
+  DynamoDB table storing order history and real-time order status tracking.
+  
+  Optimized for high-throughput reads and writes with TTL for order archival.
+  Uses DynamoDB Streams for event-driven order processing workflows.
+serviceType: DYNAMODB
+outgoingConnections: []
+

package/data/services/data/dynamodb-products.yaml

@@ -1,9 +1,9 @@
-friendlyName: "DynamoDB Products Table"
-description: |
-  DynamoDB table managing product catalog with full-text search capabilities.
-  
-  Stores product details, pricing, and inventory levels with global tables for multi-region access.
-  Integrated with ElastiCache for frequently accessed product data.
-serviceType: DYNAMODB
-outgoingConnections: []
-
+friendlyName: "DynamoDB Products Table"
+description: |
+  DynamoDB table managing product catalog with full-text search capabilities.
+  
+  Stores product details, pricing, and inventory levels with global tables for multi-region access.
+  Integrated with ElastiCache for frequently accessed product data.
+serviceType: DYNAMODB
+outgoingConnections: []
+

package/data/services/data/dynamodb-users.yaml

@@ -1,9 +1,9 @@
-friendlyName: "DynamoDB Users Table"
-description: |
-  DynamoDB table storing user profiles and session data with global secondary indexes.
-  
-  Provides single-digit millisecond latency for user lookups and session management.
-  Configured with on-demand capacity and point-in-time recovery enabled.
-serviceType: DYNAMODB
-outgoingConnections: []
-
+friendlyName: "DynamoDB Users Table"
+description: |
+  DynamoDB table storing user profiles and session data with global secondary indexes.
+  
+  Provides single-digit millisecond latency for user lookups and session management.
+  Configured with on-demand capacity and point-in-time recovery enabled.
+serviceType: DYNAMODB
+outgoingConnections: []
+

package/data/services/data/group-info.yaml

@@ -1,7 +1,7 @@
-name: "Data Storage"
-description: |
-  Manages database systems and data persistence layers.
-  This group handles RDS relational databases, DynamoDB NoSQL tables,
-  and data backup/recovery strategies for the entire platform.
-teamId: "data-wizards"
-
+name: "Data Storage"
+description: |
+  Manages database systems and data persistence layers.
+  This group handles RDS relational databases, DynamoDB NoSQL tables,
+  and data backup/recovery strategies for the entire platform.
+teamId: "data-wizards"
+

package/data/services/data/rds-postgres.yaml

@@ -1,9 +1,9 @@
-friendlyName: "RDS PostgreSQL Database"
-description: |
-  Multi-AZ PostgreSQL RDS instance for transactional data and relational storage.
-  
-  Provides ACID transactions, complex queries, and data consistency for critical business data.
-  Configured with automated backups, point-in-time recovery, and read replicas for scaling.
-serviceType: RDS
-outgoingConnections: []
-
+friendlyName: "RDS PostgreSQL Database"
+description: |
+  Multi-AZ PostgreSQL RDS instance for transactional data and relational storage.
+  
+  Provides ACID transactions, complex queries, and data consistency for critical business data.
+  Configured with automated backups, point-in-time recovery, and read replicas for scaling.
+serviceType: RDS
+outgoingConnections: []
+

package/data/services/data/redis.yaml

@@ -1,10 +1,10 @@
-friendlyName: "Redis Cache Server"
-description: |
-  High-performance in-memory data store used for caching and session management.
-  
-  This Redis instance provides fast data access for session storage, reducing
-  database load and improving application performance. Configured with persistence
-  enabled for data durability.
-serviceType: VALKEY
-outgoingConnections: []
-
+friendlyName: "Redis Cache Server"
+description: |
+  High-performance in-memory data store used for caching and session management.
+  
+  This Redis instance provides fast data access for session storage, reducing
+  database load and improving application performance. Configured with persistence
+  enabled for data durability.
+serviceType: VALKEY
+outgoingConnections: []
+

package/data/services/frontend/cloudfront.yaml

@@ -1,12 +1,12 @@
-friendlyName: "CloudFront CDN Distribution"
-description: |
-  CloudFront distribution providing global content delivery with edge caching.
-  
-  Configured with custom SSL certificate, HTTPS enforcement, and optimized
-  cache behaviors. Improves website performance and reduces S3 costs by caching content at edge locations.
-serviceType: CLOUDFRONT
-outgoingConnections:
-  - targetIdentifier: "frontend/s3-website"
-    description: "Origin - S3 static website bucket"
-    connectionType: TCP
-
+friendlyName: "CloudFront CDN Distribution"
+description: |
+  CloudFront distribution providing global content delivery with edge caching.
+  
+  Configured with custom SSL certificate, HTTPS enforcement, and optimized
+  cache behaviors. Improves website performance and reduces S3 costs by caching content at edge locations.
+serviceType: CLOUDFRONT
+outgoingConnections:
+  - targetIdentifier: "frontend/s3-website"
+    description: "Origin - S3 static website bucket"
+    connectionType: TCP
+

package/data/services/frontend/group-info.yaml

@@ -1,7 +1,7 @@
-name: "Frontend Infrastructure"
-description: |
-  Manages static website hosting, CDN, and DNS for the web application.
-  This group handles all frontend-facing AWS services including S3 buckets
-  for static assets, CloudFront for global content delivery, and Route53 for DNS management.
-teamId: "interface-architects"
-
+name: "Frontend Infrastructure"
+description: |
+  Manages static website hosting, CDN, and DNS for the web application.
+  This group handles all frontend-facing AWS services including S3 buckets
+  for static assets, CloudFront for global content delivery, and Route53 for DNS management.
+teamId: "interface-architects"
+

package/data/services/frontend/route53.yaml

@@ -1,15 +1,15 @@
-friendlyName: "Route53 DNS Zone"
-description: |
-  Route53 hosted zone managing DNS records for the application domain.
-  
-  Handles domain name resolution with health checks and routing policies.
-  Configured with alias records pointing to CloudFront and ALB endpoints.
-serviceType: ROUTE53
-outgoingConnections:
-  - targetIdentifier: "frontend/cloudfront"
-    description: "DNS resolution to CloudFront distribution"
-    connectionType: TCP
-  - targetIdentifier: "compute/alb"
-    description: "DNS resolution to Application Load Balancer"
-    connectionType: TCP
-
+friendlyName: "Route53 DNS Zone"
+description: |
+  Route53 hosted zone managing DNS records for the application domain.
+  
+  Handles domain name resolution with health checks and routing policies.
+  Configured with alias records pointing to CloudFront and ALB endpoints.
+serviceType: ROUTE53
+outgoingConnections:
+  - targetIdentifier: "frontend/cloudfront"
+    description: "DNS resolution to CloudFront distribution"
+    connectionType: TCP
+  - targetIdentifier: "compute/alb"
+    description: "DNS resolution to Application Load Balancer"
+    connectionType: TCP
+

package/data/services/frontend/s3-website.yaml

@@ -1,9 +1,9 @@
-friendlyName: "S3 Static Website Bucket"
-description: |
-  S3 bucket hosting static website assets including HTML, CSS, JavaScript, and images.
-  
-  Configured with website hosting enabled, versioning for rollback capability,
-  and lifecycle policies for cost optimization. Serves as the origin for CloudFront distribution.
-serviceType: S3
-outgoingConnections: []
-
+friendlyName: "S3 Static Website Bucket"
+description: |
+  S3 bucket hosting static website assets including HTML, CSS, JavaScript, and images.
+  
+  Configured with website hosting enabled, versioning for rollback capability,
+  and lifecycle policies for cost optimization. Serves as the origin for CloudFront distribution.
+serviceType: S3
+outgoingConnections: []
+