Technical expertise

AI Systems, Agents & Governance

Production agent orchestration, guardrails, evaluation, and the audit trail behind LLM and OCR document pipelines.

Technology	When	Where it was used	Projects	Connections	Citations
Model Context Protocol Backed by a repository analysed in the corpus.	2025 – presentCurrent(2 yrs)	ITRADE Innovations (2024 – present)	landi-orchestrator, agentable, landi-canvas, landi-orchestration-ui, landing-editor, screenshotmcp, vibed	Zod: the protocol surface in this corpus is consistently a Durable Object with Zod-typed tool schemas Tailwind CSS: both named in 4 repository analyses Cloudflare Durable Objects: the Agents SDK is what turns a Durable Object into an MCP-addressable agent with built-in state AG-UI: both named in 2 repository analyses Cloudflare Workflows: both named in 2 repository analyses CopilotKit: both named in 2 repository analyses AI SDK: both named in the vibed repository analysis Cloudflare Agents SDK Cloudflare Workers Static Assets: both named in the landi-orchestration-ui repository analysis dagre: both named in the landi-orchestration-ui repository analysis Excalidraw: both named in the landi-canvas repository analysis Gemini Live: both named in the agentable repository analysis GitHub Actions: both named in the agentable repository analysis GitHub OAuth: both named in the vibed repository analysis Monaco Editor: both named in the vibed repository analysis Node.js: both named in the screenshotmcp repository analysis OpenNext: both named in the landi-canvas repository analysis Puppeteer: both named in the screenshotmcp repository analysis Radix UI: both named in the agentable repository analysis Sharp: both named in the screenshotmcp repository analysis Vercel AI Gateway: both named in the vibed repository analysis Vercel AI SDK: both named in the landi-orchestrator repository analysis Vercel Sandbox: both named in the vibed repository analysis YAML: both named in the landi-orchestrator repository analysis MCP Servers	7
Cloudflare Workers AI Backed by a repository analysed in the corpus.	2025 – presentCurrent(2 yrs)	ITRADE Innovations (2024 – present)	landi-orchestrator, landi-orchestration-ui, landibuild, landigents, landing-editor, orchestration-stack	Cloudflare Workers Cloudflare AI Gateway Google Gemini: both named in 3 repository analyses Cloudflare Queues: both named in 2 repository analyses Cloudflare Vectorize: Workers AI produces the embeddings a Vectorize index stores and matches Cloudflare Workflows: both named in 2 repository analyses Vitest: both named in 2 repository analyses Cloudflare Agents SDK: both named in the landigents repository analysis Cloudflare Workers for Platforms: both named in the landibuild repository analysis Cloudflare Workers Static Assets: both named in the landi-orchestration-ui repository analysis dagre: both named in the landi-orchestration-ui repository analysis Docker: both named in the orchestration-stack repository analysis Flowise: both named in the orchestration-stack repository analysis Langflow: both named in the orchestration-stack repository analysis n8n: both named in the orchestration-stack repository analysis OpenAI: both named in the landibuild repository analysis pgvector: both named in the landing-editor repository analysis Slack Events API: both named in the landigents repository analysis Storybook: both named in the landing-editor repository analysis Stripe: both named in the landing-editor repository analysis Vercel AI SDK: both named in the landi-orchestrator repository analysis YAML: both named in the landi-orchestrator repository analysis	7
LangGraph Backed by a repository analysed in the corpus.	2025 – presentCurrent(2 yrs)	ITRADE Innovations (2024 – present)	fsm-llm-langgraph, landi-ai-orchestrator, landing-editor, orchestration-stack	LangChain Python Vertex AI: landi-ai-orchestrator's own relations list names both together, and its deep-search state machine runs on LangGraph in front of Vertex AI Cloudflare Queues: both named in 2 repository analyses CopilotKit: both named in 2 repository analyses CrewAI (LangGraph is an alternative to CrewAI): the fsm-llm pair implements the same four-step pipeline twice, once per framework, and the graph runtime is what gives the LangGraph half a native place for its one branch FastAPI: both named in 2 repository analyses Anthropic API: both named in the fsm-llm-langgraph repository analysis Bifrost: both named in the landi-ai-orchestrator repository analysis Gemini: both named in the landi-ai-orchestrator repository analysis Google Cloud Run: both named in the landi-ai-orchestrator repository analysis Google Secret Manager: both named in the landi-ai-orchestrator repository analysis Handlebars: both named in the landi-ai-orchestrator repository analysis OpenAI API: both named in the fsm-llm-langgraph repository analysis pgvector: both named in the landing-editor repository analysis pytest: both named in the fsm-llm-langgraph repository analysis Redis: both named in the landi-ai-orchestrator repository analysis RediSearch: both named in the landi-ai-orchestrator repository analysis Server-Sent Events: both named in the landi-ai-orchestrator repository analysis Storybook: both named in the landing-editor repository analysis Stripe: both named in the landing-editor repository analysis WebSocket: both named in the landi-ai-orchestrator repository analysis LangGraph & LangChain	7
Vertex AI Backed by a repository analysed in the corpus.	2025 – presentCurrent(2 yrs)	ITRADE Innovations (2024 – present)	landi-ai-orchestrator, landi-infra, landing-editor	LangGraph: landi-ai-orchestrator's own relations list names both together, and its deep-search state machine runs on LangGraph in front of Vertex AI Bifrost: both named in 2 repository analyses FastAPI: both named in 2 repository analyses Google Cloud Platform Google Cloud Run: both named in 2 repository analyses Google Secret Manager: both named in 2 repository analyses Redis: both named in 2 repository analyses Gemini: both named in the landi-ai-orchestrator repository analysis Google Artifact Registry: both named in the landi-infra repository analysis Google Cloud CDN: both named in the landi-infra repository analysis Google Cloud DNS: both named in the landi-infra repository analysis Google Cloud Monitoring: both named in the landi-infra repository analysis Google Cloud SQL: both named in the landi-infra repository analysis Google Cloud Storage: both named in the landi-infra repository analysis Google Compute Engine: both named in the landi-infra repository analysis Handlebars: both named in the landi-ai-orchestrator repository analysis LibreChat: both named in the landi-infra repository analysis MongoDB Atlas: both named in the landi-infra repository analysis RediSearch: both named in the landi-ai-orchestrator repository analysis WebSocket: both named in the landi-ai-orchestrator repository analysis AWS Bedrock & Vertex AI	5
Zod Backed by a repository analysed in the corpus.	2025 – presentCurrent(2 yrs)	ITRADE Innovations (2024 – present)	landi-orchestrator, landibuild, landing-editor, agentable, landi-canvas-studio, landi-canvas, vibed	Model Context Protocol: the protocol surface in this corpus is consistently a Durable Object with Zod-typed tool schemas Tailwind CSS: both named in 5 repository analyses Drizzle ORM: the two storage backends Drizzle sits over in this corpus, with Zod validating what goes in AG-UI: both named in 3 repository analyses Cloudflare Pages: both named in 3 repository analyses CopilotKit: both named in 3 repository analyses Gemini Live: both named in 2 repository analyses OpenRouter: both named in 2 repository analyses Playwright: both named in 2 repository analyses Excalidraw: both named in the landi-canvas repository analysis OpenNext: both named in the landi-canvas repository analysis Radix UI: both named in the agentable repository analysis	10
LangChain Backed by a repository analysed in the corpus.	2025 – presentCurrent(2 yrs)	ITRADE Innovations (2024 – present)	orchestration-stack, landing-editor, fsm-llm-crewai, fsm-llm-langgraph	LangGraph Python TypeScript Anthropic API: both named in 2 repository analyses Cloudflare Queues: both named in 2 repository analyses OpenAI API: both named in 2 repository analyses pytest: both named in 2 repository analyses Docker: both named in the orchestration-stack repository analysis Flowise: both named in the orchestration-stack repository analysis Langflow: both named in the orchestration-stack repository analysis n8n: both named in the orchestration-stack repository analysis pgvector: both named in the landing-editor repository analysis Storybook: both named in the landing-editor repository analysis Stripe: both named in the landing-editor repository analysis LangGraph & LangChain	8
Cloudflare Vectorize Backed by a repository analysed in the corpus.	2025 – presentCurrent(2 yrs)	ITRADE Innovations (2024 – present)	orchestration-stack	Cloudflare D1 Cloudflare R2 Cloudflare Workers AI: Workers AI produces the embeddings a Vectorize index stores and matches Docker: both named in the orchestration-stack repository analysis Flowise: both named in the orchestration-stack repository analysis Langflow: both named in the orchestration-stack repository analysis n8n: both named in the orchestration-stack repository analysis	4
CrewAI Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	fsm-llm-crewai	LangGraph (LangGraph is an alternative to CrewAI): the fsm-llm pair implements the same four-step pipeline twice, once per framework, and the graph runtime is what gives the LangGraph half a native place for its one branch Python Anthropic API: both named in the fsm-llm-crewai repository analysis OpenAI API: both named in the fsm-llm-crewai repository analysis pytest: both named in the fsm-llm-crewai repository analysis	6

AWS Bedrock & Vertex AICopilotKit & Generative UI(2 yrs)LangGraph & LangChainAgent Orchestration(2 yrs)AI Governance & GRC(2 yrs)Evaluation & Observability(2 yrs)MCP ServersRAG Pipelines

Platform Engineering & DevOps

CI/CD, GitOps, and infrastructure automation that keeps large engineering organizations shipping with confidence.

Technology	When	Where it was used	Projects	Connections	Citations
Kubernetes Backed by a dated role rather than a repository citation.	2021 – presentCurrent(5 yrs)Spans 2 roles	ITRADE Innovations (2024 – present); Madwire (2021 – 2024)	None cited	GitLab CI Google Cloud Platform Amazon EKS: EKS is the managed Kubernetes control plane used on AWS at Madwire and ITRADE Argo suite Kubernetes & ECS Fargate	5
Argo suite Backed by a dated role rather than a repository citation.	2024 – presentCurrent(2 yrs)	ITRADE Innovations (2024 – present)	None cited	GitLab CI: named together in the same CV highlight, replacing manual deployment steps with GitLab CI and the full Argo suite Kubernetes Argo CD & Kargo	3
GitLab CI Backed by a dated role rather than a repository citation.	2024 – presentCurrent(2 yrs)	ITRADE Innovations (2024 – present)	None cited	Kubernetes Argo suite: named together in the same CV highlight, replacing manual deployment steps with GitLab CI and the full Argo suite GitLab CI & GitHub Actions	2

Technology

When

Where it was used

Projects

Connections

Citations

Kubernetes

Backed by a dated role rather than a repository citation.

2021 – presentCurrent(5 yrs)Spans 2 roles

ITRADE Innovations (2024 – present); Madwire (2021 – 2024)

None cited

GitLab CI
Google Cloud Platform
Amazon EKS: EKS is the managed Kubernetes control plane used on AWS at Madwire and ITRADE
Argo suite
Kubernetes & ECS Fargate

Argo suite

Backed by a dated role rather than a repository citation.

2024 – presentCurrent(2 yrs)

ITRADE Innovations (2024 – present)

None cited

GitLab CI: named together in the same CV highlight, replacing manual deployment steps with GitLab CI and the full Argo suite
Kubernetes
Argo CD & Kargo

GitLab CI

Backed by a dated role rather than a repository citation.

2024 – presentCurrent(2 yrs)

ITRADE Innovations (2024 – present)

None cited

Kubernetes
Argo suite: named together in the same CV highlight, replacing manual deployment steps with GitLab CI and the full Argo suite
GitLab CI & GitHub Actions

GitLab CI & GitHub Actions(2 yrs)Kubernetes & ECS FargateArgo CD & KargoEphemeral Preview Environments(2 yrs)Infrastructure as CodeSite Reliability Engineering(3 yrs)SAST & Feature Flags

Cloud & Infrastructure

Multi-cloud architecture across AWS, GCP, and Cloudflare with modules that onboard new services without bespoke wiring.

Technology	When	Where it was used	Projects	Connections	Citations
Cloudflare Workers Backed by a repository analysed in the corpus.	2025 – presentCurrent(2 yrs)	ITRADE Innovations (2024 – present)	landibuild, landi-orchestrator, landigents, orchestrator-dev-sandbox, orchestration-stack, landing-editor, agentable, landi-canvas, landi-orchestration-ui	Cloudflare AI Gateway Cloudflare Workers AI Cloudflare Durable Objects Wrangler Cloudflare Containers and Sandbox SDK Cloudflare R2 OAuth Google Gemini: both named in 4 repository analyses Hono Next.js Cloudflare D1 (Cloudflare D1 depends on Cloudflare Workers): D1 is reached through a Worker binding Cloudflare KV Cloudflare Pages: both named in 3 repository analyses Tailwind CSS: both named in 3 repository analyses AG-UI: both named in 2 repository analyses Cloudflare Queues: both named in 2 repository analyses Cloudflare Sandbox SDK: both named in 2 repository analyses Cloudflare Workflows: both named in 2 repository analyses CopilotKit: both named in 2 repository analyses GitHub Actions: both named in 2 repository analyses OpenRouter: both named in 2 repository analyses Vitest: both named in 2 repository analyses Cloudflare Agents SDK: both named in the landigents repository analysis Cloudflare Workers for Platforms: both named in the landibuild repository analysis Cloudflare Workers Static Assets: both named in the landi-orchestration-ui repository analysis dagre: both named in the landi-orchestration-ui repository analysis Docker: both named in the orchestration-stack repository analysis Excalidraw: both named in the landi-canvas repository analysis FastAPI: both named in the landing-editor repository analysis Flowise: both named in the orchestration-stack repository analysis Gemini Live: both named in the agentable repository analysis GitHub CLI: both named in the orchestrator-dev-sandbox repository analysis Langflow: both named in the orchestration-stack repository analysis n8n: both named in the orchestration-stack repository analysis OpenAI: both named in the landibuild repository analysis OpenCode: both named in the orchestrator-dev-sandbox repository analysis OpenNext: both named in the landi-canvas repository analysis pgvector: both named in the landing-editor repository analysis Radix UI: both named in the agentable repository analysis Slack Events API: both named in the landigents repository analysis Storybook: both named in the landing-editor repository analysis Stripe: both named in the landing-editor repository analysis Vercel AI SDK: both named in the landi-orchestrator repository analysis YAML: both named in the landi-orchestrator repository analysis Cloudflare Workers & Pages	10
Supabase Backed by a repository analysed in the corpus.	2025 – presentCurrent(2 yrs)	ITRADE Innovations (2024 – present)	landing-editor, landibuild, landi-canvas-studio, landi-ui, orchestration-stack, vibed, client-mobile-content-app-study, landi-infra, landi-orchestration-ui	OAuth: the Supabase-backed and MCP-scoped OAuth flows in this corpus both terminate on a Worker Cloudflare Pages: both named in 4 repository analyses Tailwind CSS: both named in 4 repository analyses Google Gemini: both named in 3 repository analyses AG-UI: both named in 2 repository analyses Anthropic Claude: both named in 2 repository analyses Google Cloud Storage: both named in 2 repository analyses Playwright: both named in 2 repository analyses Vitest: both named in 2 repository analyses AI SDK: both named in the vibed repository analysis Banuba SDK: both named in the client-mobile-content-app-study repository analysis Bifrost: both named in the landi-infra repository analysis Cloudflare Workers Static Assets: both named in the landi-orchestration-ui repository analysis dagre: both named in the landi-orchestration-ui repository analysis Gemini: both named in the client-mobile-content-app-study repository analysis Gemini Live: both named in the landi-canvas-studio repository analysis GitHub OAuth: both named in the vibed repository analysis GitHub Packages: both named in the landi-ui repository analysis Google Artifact Registry: both named in the landi-infra repository analysis Google Cloud CDN: both named in the landi-infra repository analysis Google Cloud DNS: both named in the landi-infra repository analysis Google Cloud Monitoring: both named in the landi-infra repository analysis Google Cloud Run: both named in the landi-infra repository analysis Google Cloud SQL: both named in the landi-infra repository analysis Google Compute Engine: both named in the landi-infra repository analysis Google Secret Manager: both named in the landi-infra repository analysis LibreChat: both named in the landi-infra repository analysis Monaco Editor: both named in the vibed repository analysis MongoDB Atlas: both named in the landi-infra repository analysis Multi-agent orchestration: both named in the client-mobile-content-app-study repository analysis Node.js: both named in the client-mobile-content-app-study repository analysis OIDC: both named in the client-mobile-content-app-study repository analysis Okta: both named in the client-mobile-content-app-study repository analysis pnpm: both named in the landi-ui repository analysis PyMuPDF: both named in the client-mobile-content-app-study repository analysis React Native: both named in the client-mobile-content-app-study repository analysis Redis: both named in the landi-infra repository analysis REST API: both named in the client-mobile-content-app-study repository analysis Server-Sent Events: both named in the landi-canvas-studio repository analysis Tesseract OCR: both named in the client-mobile-content-app-study repository analysis Vercel AI Gateway: both named in the vibed repository analysis Vercel Sandbox: both named in the vibed repository analysis YAML workflow configuration: both named in the client-mobile-content-app-study repository analysis PostgreSQL & Redshift	9
Cloudflare Containers and Sandbox SDK Backed by a repository analysed in the corpus.	2025 – presentCurrent(2 yrs)	ITRADE Innovations (2024 – present)	landibuild, landing-editor, orchestration-stack, orchestrator-dev-sandbox, vibed	Cloudflare Workers Cloudflare AI Gateway: both named in 4 repository analyses Cloudflare Durable Objects: a container is bound through a Durable Object Google Gemini: both named in 3 repository analyses Cloudflare Pages: both named in 2 repository analyses Cloudflare Queues: both named in 2 repository analyses Cloudflare Sandbox SDK: both named in 2 repository analyses Docker AI SDK: both named in the vibed repository analysis Anthropic Claude: both named in the landibuild repository analysis Cloudflare Workers for Platforms: both named in the landibuild repository analysis FastAPI: both named in the landing-editor repository analysis Flowise: both named in the orchestration-stack repository analysis GitHub Actions: both named in the orchestrator-dev-sandbox repository analysis GitHub CLI: both named in the orchestrator-dev-sandbox repository analysis GitHub OAuth: both named in the vibed repository analysis Langflow: both named in the orchestration-stack repository analysis Monaco Editor: both named in the vibed repository analysis n8n: both named in the orchestration-stack repository analysis OpenAI: both named in the landibuild repository analysis OpenCode: both named in the orchestrator-dev-sandbox repository analysis OpenRouter: both named in the landibuild repository analysis pgvector: both named in the landing-editor repository analysis Playwright: both named in the landing-editor repository analysis Storybook: both named in the landing-editor repository analysis Stripe: both named in the landing-editor repository analysis Vercel AI Gateway: both named in the vibed repository analysis Vercel Sandbox: both named in the vibed repository analysis	5
AWS Backed by a private artifact rather than a repository.	2009 – presentCurrent(17 yrs)Spans 5 roles	Profile Your City, Inc. (2009 – 2014); ValueCentric (2014 – 2016); Testimonial Tree 2016–2020 (2016 – 2020); Testimonial Tree 2020–2021 (2020 – 2021); Madwire (2021 – 2024); ITRADE Innovations (2024 – present)	madwire-finops	Amazon EC2: EC2 was the compute layer of the AWS work from Profile Your City through ITRADE Amazon Route 53: Route 53 was the DNS layer of the AWS work from Profile Your City through ITRADE Amazon S3: S3 was the object storage layer of the AWS work from Profile Your City through ITRADE Amazon SNS: SNS was the pub-sub layer of the AWS work from Profile Your City through ITRADE Amazon SQS: SQS was the queueing layer of the AWS work from Profile Your City through ITRADE Auto Scaling: Auto Scaling adjusted capacity for the AWS work from Profile Your City through ITRADE Elastic Load Balancing: GCP was paired with AWS at Madwire and Testimonial Tree; EC2, S3, SQS, SNS, Elastic Load Balancing, Auto Scaling, and Route 53 were the AWS services used from Profile Your City through ITRADE Google Cloud Platform: GCP was paired with AWS at Madwire and Testimonial Tree; EC2, S3, SQS, SNS, Elastic Load Balancing, Auto Scaling, and Route 53 were the AWS services used from Profile Your City through ITRADE Amazon ECS: ECS, including Fargate, ran container workloads on AWS at Testimonial Tree and ITRADE Amazon EKS: EKS is the managed Kubernetes control plane used on AWS at Madwire and ITRADE AWS CloudFormation: CloudFormation was the AWS infrastructure-as-code service at Testimonial Tree, Madwire, and ITRADE AWS Step Functions: Step Functions orchestrated AWS workflows at Testimonial Tree and ITRADE AWS (EKS, ECS, Lambda, IAM) AWS Bedrock & Vertex AI	13
Cloudflare Durable Objects Backed by a repository analysed in the corpus.	2025 – presentCurrent(2 yrs)	ITRADE Innovations (2024 – present)	landibuild, landing-editor, landi-orchestrator, landigents, orchestrator-dev-sandbox	Cloudflare Workers Cloudflare AI Gateway: both named in 4 repository analyses Cloudflare Containers and Sandbox SDK: a container is bound through a Durable Object Model Context Protocol: the Agents SDK is what turns a Durable Object into an MCP-addressable agent with built-in state Cloudflare Agents SDK Cloudflare Sandbox SDK: both named in 2 repository analyses Cloudflare Workflows: both named in 2 repository analyses Vitest: both named in 2 repository analyses Anthropic Claude: both named in the landibuild repository analysis Cloudflare Workers for Platforms: both named in the landibuild repository analysis FastAPI: both named in the landing-editor repository analysis GitHub Actions: both named in the orchestrator-dev-sandbox repository analysis GitHub CLI: both named in the orchestrator-dev-sandbox repository analysis OpenAI: both named in the landibuild repository analysis OpenCode: both named in the orchestrator-dev-sandbox repository analysis OpenRouter: both named in the landibuild repository analysis pgvector: both named in the landing-editor repository analysis Slack Events API: both named in the landigents repository analysis Storybook: both named in the landing-editor repository analysis Stripe: both named in the landing-editor repository analysis Vercel AI SDK: both named in the landi-orchestrator repository analysis YAML: both named in the landi-orchestrator repository analysis	7
Wrangler Backed by a repository analysed in the corpus.	2025 – presentCurrent(2 yrs)	ITRADE Innovations (2024 – present)	landi-orchestrator, landibuild, landigents, landing-editor, orchestration-stack, orchestrator-dev-sandbox	Cloudflare Workers Cloudflare AI Gateway: both named in 5 repository analyses Google Gemini: both named in 3 repository analyses Cloudflare Sandbox SDK: both named in 2 repository analyses Cloudflare Workflows: both named in 2 repository analyses Pulumi: orchestration-stack removed a scoped Pulumi package in favor of Wrangler and the dashboard Cloudflare Agents SDK: both named in the landigents repository analysis GitHub CLI: both named in the orchestrator-dev-sandbox repository analysis OpenCode: both named in the orchestrator-dev-sandbox repository analysis Slack Events API: both named in the landigents repository analysis Vercel AI SDK: both named in the landi-orchestrator repository analysis YAML: both named in the landi-orchestrator repository analysis	7
Pulumi Backed by a repository analysed in the corpus.	2025 – presentCurrent(2 yrs)	ITRADE Innovations (2024 – present)	landi-infra, landing-editor	TypeScript: the Pulumi programs here are TypeScript against the GCP provider Google Cloud Platform: the Google Cloud footprint in this corpus is Pulumi-provisioned and fronts a Python service Wrangler: orchestration-stack removed a scoped Pulumi package in favor of Wrangler and the dashboard Bifrost: both named in the landi-infra repository analysis Google Artifact Registry: both named in the landi-infra repository analysis Google Cloud CDN: both named in the landi-infra repository analysis Google Cloud DNS: both named in the landi-infra repository analysis Google Cloud Monitoring: both named in the landi-infra repository analysis Google Cloud Run: both named in the landi-infra repository analysis Google Cloud SQL: both named in the landi-infra repository analysis Google Cloud Storage: both named in the landi-infra repository analysis Google Compute Engine: both named in the landi-infra repository analysis Google Secret Manager: both named in the landi-infra repository analysis LibreChat: both named in the landi-infra repository analysis MongoDB Atlas: both named in the landi-infra repository analysis Redis: both named in the landi-infra repository analysis Terraform: named together in the same CV highlight, reusable infrastructure modules in Pulumi and Terraform Infrastructure as Code Pulumi & Terraform	6
Amazon EC2 Backed by a dated role rather than a repository citation.	2009 – presentCurrent(17 yrs)Spans 5 roles	Profile Your City, Inc. (2009 – 2014); ValueCentric (2014 – 2016); Testimonial Tree 2016–2020 (2016 – 2020); Testimonial Tree 2020–2021 (2020 – 2021); Madwire (2021 – 2024); ITRADE Innovations (2024 – present)	None cited	AWS: EC2 was the compute layer of the AWS work from Profile Your City through ITRADE	7
Amazon Route 53 Backed by a dated role rather than a repository citation.	2009 – presentCurrent(17 yrs)Spans 5 roles	Profile Your City, Inc. (2009 – 2014); ValueCentric (2014 – 2016); Testimonial Tree 2016–2020 (2016 – 2020); Testimonial Tree 2020–2021 (2020 – 2021); Madwire (2021 – 2024); ITRADE Innovations (2024 – present)	None cited	AWS: Route 53 was the DNS layer of the AWS work from Profile Your City through ITRADE	7
Amazon S3 Backed by a dated role rather than a repository citation.	2009 – presentCurrent(17 yrs)Spans 5 roles	Profile Your City, Inc. (2009 – 2014); ValueCentric (2014 – 2016); Testimonial Tree 2016–2020 (2016 – 2020); Testimonial Tree 2020–2021 (2020 – 2021); Madwire (2021 – 2024); ITRADE Innovations (2024 – present)	None cited	AWS: S3 was the object storage layer of the AWS work from Profile Your City through ITRADE	7
Amazon SNS Backed by a dated role rather than a repository citation.	2009 – presentCurrent(17 yrs)Spans 5 roles	Profile Your City, Inc. (2009 – 2014); ValueCentric (2014 – 2016); Testimonial Tree 2016–2020 (2016 – 2020); Testimonial Tree 2020–2021 (2020 – 2021); Madwire (2021 – 2024); ITRADE Innovations (2024 – present)	None cited	AWS: SNS was the pub-sub layer of the AWS work from Profile Your City through ITRADE	7
Amazon SQS Backed by a dated role rather than a repository citation.	2009 – presentCurrent(17 yrs)Spans 5 roles	Profile Your City, Inc. (2009 – 2014); ValueCentric (2014 – 2016); Testimonial Tree 2016–2020 (2016 – 2020); Testimonial Tree 2020–2021 (2020 – 2021); Madwire (2021 – 2024); ITRADE Innovations (2024 – present)	None cited	AWS: SQS was the queueing layer of the AWS work from Profile Your City through ITRADE	7
Auto Scaling Backed by a dated role rather than a repository citation.	2009 – presentCurrent(17 yrs)Spans 5 roles	Profile Your City, Inc. (2009 – 2014); ValueCentric (2014 – 2016); Testimonial Tree 2016–2020 (2016 – 2020); Testimonial Tree 2020–2021 (2020 – 2021); Madwire (2021 – 2024); ITRADE Innovations (2024 – present)	None cited	AWS: Auto Scaling adjusted capacity for the AWS work from Profile Your City through ITRADE	8
Elastic Load Balancing Backed by a dated role rather than a repository citation.	2009 – presentCurrent(17 yrs)Spans 5 roles	Profile Your City, Inc. (2009 – 2014); ValueCentric (2014 – 2016); Testimonial Tree 2016–2020 (2016 – 2020); Testimonial Tree 2020–2021 (2020 – 2021); Madwire (2021 – 2024); ITRADE Innovations (2024 – present)	None cited	AWS: GCP was paired with AWS at Madwire and Testimonial Tree; EC2, S3, SQS, SNS, Elastic Load Balancing, Auto Scaling, and Route 53 were the AWS services used from Profile Your City through ITRADE	7
Google Cloud Platform Backed by a repository analysed in the corpus.	2025 – presentCurrent(2 yrs)	ITRADE Innovations (2024 – present)	landi-ai-orchestrator	AWS: GCP was paired with AWS at Madwire and Testimonial Tree; EC2, S3, SQS, SNS, Elastic Load Balancing, Auto Scaling, and Route 53 were the AWS services used from Profile Your City through ITRADE Python: the Google Cloud footprint in this corpus is Pulumi-provisioned and fronts a Python service Kubernetes Pulumi: the Google Cloud footprint in this corpus is Pulumi-provisioned and fronts a Python service Vertex AI Bifrost: both named in the landi-ai-orchestrator repository analysis Gemini: both named in the landi-ai-orchestrator repository analysis Google Cloud Run: both named in the landi-ai-orchestrator repository analysis Google Secret Manager: both named in the landi-ai-orchestrator repository analysis Handlebars: both named in the landi-ai-orchestrator repository analysis Redis: both named in the landi-ai-orchestrator repository analysis RediSearch: both named in the landi-ai-orchestrator repository analysis Server-Sent Events: both named in the landi-ai-orchestrator repository analysis WebSocket: both named in the landi-ai-orchestrator repository analysis GCP (GKE, Cloud Run, BigQuery)	6
AWS CloudFormation Backed by a dated role rather than a repository citation.	2016 – presentCurrent(10 yrs)Spans 3 roles	Testimonial Tree 2016–2020 (2016 – 2020); Testimonial Tree 2020–2021 (2020 – 2021); Madwire (2021 – 2024); ITRADE Innovations (2024 – present)	None cited	AWS: CloudFormation was the AWS infrastructure-as-code service at Testimonial Tree, Madwire, and ITRADE	5
Amazon ECS Backed by a dated role rather than a repository citation.	2016 – presentCurrent(7 yrs)Spans 2 roles	Testimonial Tree 2016–2020 (2016 – 2020); Testimonial Tree 2020–2021 (2020 – 2021); ITRADE Innovations (2024 – present)	None cited	AWS: ECS, including Fargate, ran container workloads on AWS at Testimonial Tree and ITRADE AWS (EKS, ECS, Lambda, IAM) Kubernetes & ECS Fargate	5
Hono Backed by a repository analysed in the corpus.	2025 – presentCurrent(2 yrs)	ITRADE Innovations (2024 – present)	landibuild, orchestration-stack	Cloudflare Workers Drizzle ORM: Hono fronts the Drizzle-backed D1 layer in landibuild Docker: both named in the orchestration-stack repository analysis Flowise: both named in the orchestration-stack repository analysis Langflow: both named in the orchestration-stack repository analysis n8n: both named in the orchestration-stack repository analysis	5
AWS Step Functions Backed by a dated role rather than a repository citation.	2016 – presentCurrent(7 yrs)Spans 2 roles	Testimonial Tree 2016–2020 (2016 – 2020); Testimonial Tree 2020–2021 (2020 – 2021); ITRADE Innovations (2024 – present)	None cited	AWS: Step Functions orchestrated AWS workflows at Testimonial Tree and ITRADE	4
Amazon EKS Backed by a dated role rather than a repository citation.	2021 – presentCurrent(5 yrs)Spans 2 roles	Madwire (2021 – 2024); ITRADE Innovations (2024 – present)	None cited	AWS: EKS is the managed Kubernetes control plane used on AWS at Madwire and ITRADE Kubernetes: EKS is the managed Kubernetes control plane used on AWS at Madwire and ITRADE AWS (EKS, ECS, Lambda, IAM)	3
Terraform Backed by a dated role rather than a repository citation.	2024 – presentCurrent(2 yrs)	ITRADE Innovations (2024 – present)	None cited	Pulumi: named together in the same CV highlight, reusable infrastructure modules in Pulumi and Terraform Pulumi & Terraform	4

AWS (EKS, ECS, Lambda, IAM)(9 yrs)Spans 3 rolesPulumi & TerraformCloudflare Workers & PagesFinOps & Cost Optimization(3 yrs)GCP (GKE, Cloud Run, BigQuery)VPC Networking & DNS

Data & Machine Learning

Applied ML on review text, pharmaceutical supply chain data, and anomaly detection at platform scale.

Technology	When	Where it was used	Projects	Connections	Citations
Cloudflare R2 Backed by a repository analysed in the corpus.	2025 – presentCurrent(2 yrs)	ITRADE Innovations (2024 – present)	landi-orchestrator, landibuild, landing-editor, orchestration-stack	Cloudflare Workers Cloudflare AI Gateway: both named in 4 repository analyses Cloudflare D1 Google Gemini: both named in 3 repository analyses Cloudflare Queues: both named in 2 repository analyses Cloudflare Vectorize Cloudflare Workflows: both named in 2 repository analyses Anthropic Claude: both named in the landibuild repository analysis Cloudflare Sandbox SDK: both named in the landibuild repository analysis Cloudflare Workers for Platforms: both named in the landibuild repository analysis Docker: both named in the orchestration-stack repository analysis FastAPI: both named in the landing-editor repository analysis Flowise: both named in the orchestration-stack repository analysis Langflow: both named in the orchestration-stack repository analysis n8n: both named in the orchestration-stack repository analysis OpenAI: both named in the landibuild repository analysis OpenRouter: both named in the landibuild repository analysis pgvector: both named in the landing-editor repository analysis Storybook: both named in the landing-editor repository analysis Stripe: both named in the landing-editor repository analysis Vercel AI SDK: both named in the landi-orchestrator repository analysis YAML: both named in the landi-orchestrator repository analysis	6
Cloudflare D1 Backed by a repository analysed in the corpus.	2025 – presentCurrent(2 yrs)	ITRADE Innovations (2024 – present)	landibuild, orchestration-stack	Cloudflare R2 Cloudflare Workers (Cloudflare D1 depends on Cloudflare Workers): D1 is reached through a Worker binding Drizzle ORM Cloudflare Vectorize Anthropic Claude: both named in the landibuild repository analysis Cloudflare Sandbox SDK: both named in the landibuild repository analysis Cloudflare Workers for Platforms: both named in the landibuild repository analysis Docker: both named in the orchestration-stack repository analysis Flowise: both named in the orchestration-stack repository analysis Langflow: both named in the orchestration-stack repository analysis n8n: both named in the orchestration-stack repository analysis OpenAI: both named in the landibuild repository analysis OpenRouter: both named in the landibuild repository analysis	5
Cloudflare KV Backed by a repository analysed in the corpus.	2025 – presentCurrent(2 yrs)	ITRADE Innovations (2024 – present)	landibuild, landing-editor	Cloudflare Workers OAuth: landing-editor's KV namespace is where its MCP OAuth state lives Anthropic Claude: both named in the landibuild repository analysis Cloudflare Sandbox SDK: both named in the landibuild repository analysis Cloudflare Workers for Platforms: both named in the landibuild repository analysis FastAPI: both named in the landing-editor repository analysis OpenAI: both named in the landibuild repository analysis OpenRouter: both named in the landibuild repository analysis pgvector: both named in the landing-editor repository analysis Storybook: both named in the landing-editor repository analysis Stripe: both named in the landing-editor repository analysis	8
Drizzle ORM Backed by a repository analysed in the corpus.	2025 – presentCurrent(2 yrs)	ITRADE Innovations (2024 – present)	landibuild, vibed	Zod: the two storage backends Drizzle sits over in this corpus, with Zod validating what goes in Cloudflare D1 Hono: Hono fronts the Drizzle-backed D1 layer in landibuild AI SDK: both named in the vibed repository analysis Cloudflare Workers for Platforms: both named in the landibuild repository analysis GitHub OAuth: both named in the vibed repository analysis Monaco Editor: both named in the vibed repository analysis OpenAI: both named in the landibuild repository analysis Vercel AI Gateway: both named in the vibed repository analysis Vercel Sandbox: both named in the vibed repository analysis	5
Big Data (Hadoop, MapReduce) Backed by a dated role rather than a repository citation.	2014 – 2016(2 yrs)	ValueCentric (2014 – 2016)	None cited	Big Data (Hadoop, MapReduce)	1

Big Data (Hadoop, MapReduce)(2 yrs)Anomaly Detection(3 yrs)Document Intelligence & OCR(2 yrs)PostgreSQL & RedshiftSentiment & Topic Extraction(4 yrs)PrestoSQL & Pinot

Security & Compliance

DevSecOps, regulated environments, and the controls behind production AI and document processing systems.

Technology	When	Where it was used	Projects	Connections	Citations
OAuth Backed by a repository analysed in the corpus.	2025 – presentCurrent(2 yrs)	ITRADE Innovations (2024 – present)	agentable, landibuild, landi-canvas-studio, landing-editor, vibed, client-mobile-content-app-study	Supabase: the Supabase-backed and MCP-scoped OAuth flows in this corpus both terminate on a Worker Cloudflare Workers Tailwind CSS: both named in 5 repository analyses Cloudflare KV: landing-editor's KV namespace is where its MCP OAuth state lives Cloudflare Pages: both named in 3 repository analyses Google Gemini: both named in 3 repository analyses AG-UI: both named in 2 repository analyses Anthropic Claude: both named in 2 repository analyses CopilotKit: both named in 2 repository analyses Gemini Live: both named in 2 repository analyses Playwright: both named in 2 repository analyses Vitest: both named in 2 repository analyses AI SDK: both named in the vibed repository analysis Banuba SDK: both named in the client-mobile-content-app-study repository analysis Gemini: both named in the client-mobile-content-app-study repository analysis GitHub Actions: both named in the agentable repository analysis GitHub OAuth: both named in the vibed repository analysis Monaco Editor: both named in the vibed repository analysis Multi-agent orchestration: both named in the client-mobile-content-app-study repository analysis Node.js: both named in the client-mobile-content-app-study repository analysis OIDC: both named in the client-mobile-content-app-study repository analysis Okta: both named in the client-mobile-content-app-study repository analysis PyMuPDF: both named in the client-mobile-content-app-study repository analysis Radix UI: both named in the agentable repository analysis React Native: both named in the client-mobile-content-app-study repository analysis REST API: both named in the client-mobile-content-app-study repository analysis Server-Sent Events: both named in the landi-canvas-studio repository analysis Tesseract OCR: both named in the client-mobile-content-app-study repository analysis Vercel AI Gateway: both named in the vibed repository analysis Vercel Sandbox: both named in the vibed repository analysis YAML workflow configuration: both named in the client-mobile-content-app-study repository analysis	8
KeyCloak Backed by a dated role rather than a repository citation.	2021 – 2024(3 yrs)	Madwire (2021 – 2024)	None cited	Go PHP React TypeScript	3
HL7 Backed by a dated role rather than a repository citation.	2016 – 2020(4 yrs)	Testimonial Tree 2016–2020 (2016 – 2020)	None cited	HIPAA & HL7 Processing	1

Technology

When

Where it was used

Projects

Connections

Citations

OAuth

Backed by a repository analysed in the corpus.

2025 – presentCurrent(2 yrs)

ITRADE Innovations (2024 – present)

agentable, landibuild, landi-canvas-studio, landing-editor, vibed, client-mobile-content-app-study

Supabase: the Supabase-backed and MCP-scoped OAuth flows in this corpus both terminate on a Worker
Cloudflare Workers
Tailwind CSS: both named in 5 repository analyses
Cloudflare KV: landing-editor's KV namespace is where its MCP OAuth state lives
Cloudflare Pages: both named in 3 repository analyses
Google Gemini: both named in 3 repository analyses
AG-UI: both named in 2 repository analyses
Anthropic Claude: both named in 2 repository analyses
CopilotKit: both named in 2 repository analyses
Gemini Live: both named in 2 repository analyses
Playwright: both named in 2 repository analyses
Vitest: both named in 2 repository analyses
AI SDK: both named in the vibed repository analysis
Banuba SDK: both named in the client-mobile-content-app-study repository analysis
Gemini: both named in the client-mobile-content-app-study repository analysis
GitHub Actions: both named in the agentable repository analysis
GitHub OAuth: both named in the vibed repository analysis
Monaco Editor: both named in the vibed repository analysis
Multi-agent orchestration: both named in the client-mobile-content-app-study repository analysis
Node.js: both named in the client-mobile-content-app-study repository analysis
OIDC: both named in the client-mobile-content-app-study repository analysis
Okta: both named in the client-mobile-content-app-study repository analysis
PyMuPDF: both named in the client-mobile-content-app-study repository analysis
Radix UI: both named in the agentable repository analysis
React Native: both named in the client-mobile-content-app-study repository analysis
REST API: both named in the client-mobile-content-app-study repository analysis
Server-Sent Events: both named in the landi-canvas-studio repository analysis
Tesseract OCR: both named in the client-mobile-content-app-study repository analysis
Vercel AI Gateway: both named in the vibed repository analysis
Vercel Sandbox: both named in the vibed repository analysis
YAML workflow configuration: both named in the client-mobile-content-app-study repository analysis

KeyCloak

Backed by a dated role rather than a repository citation.

2021 – 2024(3 yrs)

Madwire (2021 – 2024)

None cited

HL7

Backed by a dated role rather than a repository citation.

2016 – 2020(4 yrs)

Testimonial Tree 2016–2020 (2016 – 2020)

None cited

HIPAA & HL7 Processing

HIPAA & HL7 Processing(8 yrs)Spans 2 rolesAudit Trails & Policy Adherence(2 yrs)OIDC & Cross-Account IAMCilium & Hubble Network PolicySecrets ManagementSplunk & MITRE CyberSeal

Engineering Leadership

Hands-on technical leadership from IC through Director and VP, building teams from intern through senior level.

Team Building & Mentorship(4 yrs)Agile DeliveryCross-Functional AlignmentPre-Sales EngineeringSolutions ArchitectureTechnical Strategy

Languages & Runtimes

Technology	When	Where it was used	Projects	Connections	Citations
TypeScript Backed by a repository analysed in the corpus.	2014 – presentCurrent(12 yrs)Spans 4 roles	ValueCentric (2014 – 2016); Testimonial Tree 2016–2020 (2016 – 2020); Testimonial Tree 2020–2021 (2020 – 2021); Madwire (2021 – 2024); ITRADE Innovations (2024 – present)	Agentable, embedacode, resume-tailor-agent-skill, landing-editor, landibuild, landi-orchestrator, landi-infra, client-mobile-content-app-study, landi-canvas-studio, landi-orchestration-ui, landi-ui, landigents, orchestrator-dev-sandbox, vibed	React: Node and TypeScript from the Madwire platform; C# and .NET from Testimonial Tree, where React started in 2019; Next.js from Madwire in 2023; Landi React work at ITRADE Innovations from 2025 Vite Cloudflare AI Gateway: both named in 5 repository analyses Next.js Tailwind CSS: both named in 4 repository analyses Vitest: both named in 4 repository analyses Cloudflare Pages: both named in 3 repository analyses LangChain Playwright: both named in 3 repository analyses Pulumi: the Pulumi programs here are TypeScript against the GCP provider AG-UI: both named in 2 repository analyses Anthropic Claude: both named in 2 repository analyses C#: C#, .NET, Web Forms and Web API were the Testimonial Tree stack from 2016; TypeScript is listed with C# in the Programming Languages skill group Cloudflare Sandbox SDK: both named in 2 repository analyses Cloudflare Workflows: both named in 2 repository analyses GitHub Actions: both named in 2 repository analyses GitHub Packages: both named in 2 repository analyses Google Cloud Storage: both named in 2 repository analyses Node.js: both named in 2 repository analyses OpenCode: both named in 2 repository analyses AI SDK: both named in the vibed repository analysis Banuba SDK: both named in the client-mobile-content-app-study repository analysis Bifrost: both named in the landi-infra repository analysis Claude Code: both named in the resume-tailor-agent-skill repository analysis Cloudflare Agents SDK: both named in the landigents repository analysis Cloudflare Workers Static Assets: both named in the landi-orchestration-ui repository analysis Cursor: both named in the resume-tailor-agent-skill repository analysis dagre: both named in the landi-orchestration-ui repository analysis Gemini: both named in the client-mobile-content-app-study repository analysis GitHub CLI: both named in the orchestrator-dev-sandbox repository analysis GitHub OAuth: both named in the vibed repository analysis GitHub REST API: both named in the embedacode repository analysis Go Google Artifact Registry: both named in the landi-infra repository analysis Google Cloud CDN: both named in the landi-infra repository analysis Google Cloud DNS: both named in the landi-infra repository analysis Google Cloud Monitoring: both named in the landi-infra repository analysis Google Cloud Run: both named in the landi-infra repository analysis Google Cloud SQL: both named in the landi-infra repository analysis Google Compute Engine: both named in the landi-infra repository analysis Google Secret Manager: both named in the landi-infra repository analysis JSON Resume: both named in the resume-tailor-agent-skill repository analysis JSZip: both named in the embedacode repository analysis KeyCloak LibreChat: both named in the landi-infra repository analysis Monaco Editor: both named in the vibed repository analysis MongoDB Atlas: both named in the landi-infra repository analysis Multi-agent orchestration: both named in the client-mobile-content-app-study repository analysis npm: both named in the resume-tailor-agent-skill repository analysis OIDC: both named in the client-mobile-content-app-study repository analysis Okta: both named in the client-mobile-content-app-study repository analysis pdfkit: both named in the resume-tailor-agent-skill repository analysis PHP (PHP gave way to TypeScript): the Madwire platform work moved off PHP, and TypeScript is what it carried on in, at Madwire and then at ITRADE pnpm: both named in the landi-ui repository analysis PrismJS: both named in the embedacode repository analysis Puppeteer: both named in the resume-tailor-agent-skill repository analysis PyMuPDF: both named in the client-mobile-content-app-study repository analysis React Native: both named in the client-mobile-content-app-study repository analysis Redis: both named in the landi-infra repository analysis REST API: both named in the client-mobile-content-app-study repository analysis Server-Sent Events: both named in the landi-canvas-studio repository analysis Shadow DOM: both named in the embedacode repository analysis Slack Events API: both named in the landigents repository analysis Tesseract OCR: both named in the client-mobile-content-app-study repository analysis Vercel AI Gateway: both named in the vibed repository analysis Vercel AI SDK: both named in the landi-orchestrator repository analysis Vercel Sandbox: both named in the vibed repository analysis YAML: both named in the landi-orchestrator repository analysis YAML workflow configuration: both named in the client-mobile-content-app-study repository analysis	15
PHP Backed by a repository analysed in the corpus.	2011 – 2024(6 yrs)Spans 2 roles	Profile Your City, Inc. (2009 – 2014); Madwire (2021 – 2024)	Live Editor, GS Blog, SEO Manager, MetaRobots, front-end-user-login, Multi-User, Default Content, Extend downloader, Simplicity, Items Manager, FAQ Manager, Random Content, Random Ads, default-content, extend-downloader, faq-manager, getsimple-blog, items-manager, live-editor, seo-manager	GetSimple CMS: every listed plugin and the Simplicity theme is PHP on GetSimple CKEditor: both named in 6 repository analyses jQuery: both named in 5 repository analyses XML: both named in 2 repository analyses CodeMirror: both named in the getsimple-blog repository analysis Disqus: both named in the getsimple-blog repository analysis jQuery UI: both named in the items-manager repository analysis KeyCloak MagpieRSS: both named in the getsimple-blog repository analysis Markdown: both named in the extend-downloader repository analysis MySQL: both named in the front-end-user-login repository analysis ShareThis: both named in the getsimple-blog repository analysis TypeScript (PHP gave way to TypeScript): the Madwire platform work moved off PHP, and TypeScript is what it carried on in, at Madwire and then at ITRADE	21
GetSimple CMS Backed by a repository analysed in the corpus.	2011 – 2014(3 yrs)	Profile Your City, Inc. (2009 – 2014)	Live Editor, GS Blog, SEO Manager, MetaRobots, front-end-user-login, Multi-User, Default Content, Extend downloader, Simplicity, Items Manager, FAQ Manager, Random Content, Random Ads, default-content, extend-downloader, faq-manager, getsimple-blog, items-manager, live-editor, seo-manager	PHP: every listed plugin and the Simplicity theme is PHP on GetSimple CKEditor: both named in 6 repository analyses jQuery: both named in 5 repository analyses XML: both named in 2 repository analyses CodeMirror: both named in the getsimple-blog repository analysis Disqus: both named in the getsimple-blog repository analysis jQuery UI: both named in the items-manager repository analysis MagpieRSS: both named in the getsimple-blog repository analysis Markdown: both named in the extend-downloader repository analysis MySQL: both named in the front-end-user-login repository analysis ShareThis: both named in the getsimple-blog repository analysis	18
Python Backed by a repository analysed in the corpus.	2014 – presentCurrent(4 yrs)Spans 2 roles	ValueCentric (2014 – 2016); ITRADE Innovations (2024 – present)	fsm-llm-langgraph, fsm-llm-crewai, landi-ai-orchestrator, landing-editor, landi-orchestrator	LangChain LangGraph FastAPI Google Cloud Platform: the Google Cloud footprint in this corpus is Pulumi-provisioned and fronts a Python service Anthropic API: both named in 2 repository analyses Cloudflare Workflows: both named in 2 repository analyses ColdFusion (ColdFusion gave way to Python): both were in use at ValueCentric, with REST APIs built in each, and Python is the one the work carried on in CopilotKit: both named in 2 repository analyses CrewAI OpenAI API: both named in 2 repository analyses pytest: both named in 2 repository analyses Bifrost: both named in the landi-ai-orchestrator repository analysis Gemini: both named in the landi-ai-orchestrator repository analysis Google Cloud Run: both named in the landi-ai-orchestrator repository analysis Google Secret Manager: both named in the landi-ai-orchestrator repository analysis Handlebars: both named in the landi-ai-orchestrator repository analysis Redis: both named in the landi-ai-orchestrator repository analysis RediSearch: both named in the landi-ai-orchestrator repository analysis Server-Sent Events: both named in the landi-ai-orchestrator repository analysis Vercel AI SDK: both named in the landi-orchestrator repository analysis WebSocket: both named in the landi-ai-orchestrator repository analysis YAML: both named in the landi-orchestrator repository analysis	8
C# Backed by a dated role rather than a repository citation.	2016 – 2020(4 yrs)	Testimonial Tree 2016–2020 (2016 – 2020)	None cited	React: Node and TypeScript from the Madwire platform; C# and .NET from Testimonial Tree, where React started in 2019; Next.js from Madwire in 2023; Landi React work at ITRADE Innovations from 2025 .NET: the Testimonial Tree platform was .NET, written in C#, with Web Forms and Web API ASP.NET Web API: Web API was the Testimonial Tree HTTP API stack from 2016, on .NET and C# ASP.NET Web Forms: Web Forms was the Testimonial Tree UI stack from 2016, on .NET and C# TypeScript: C#, .NET, Web Forms and Web API were the Testimonial Tree stack from 2016; TypeScript is listed with C# in the Programming Languages skill group	3
.NET Backed by a dated role rather than a repository citation.	2016 – 2020(4 yrs)	Testimonial Tree 2016–2020 (2016 – 2020)	None cited	React: Node and TypeScript from the Madwire platform; C# and .NET from Testimonial Tree, where React started in 2019; Next.js from Madwire in 2023; Landi React work at ITRADE Innovations from 2025 C#: the Testimonial Tree platform was .NET, written in C#, with Web Forms and Web API ASP.NET Web API: the Testimonial Tree platform was .NET, written in C#, with Web Forms and Web API ASP.NET Web Forms: the Testimonial Tree platform was .NET, written in C#, with Web Forms and Web API	2
ASP.NET Web API Backed by a dated role rather than a repository citation.	2016 – 2020(4 yrs)	Testimonial Tree 2016–2020 (2016 – 2020)	None cited	C#: Web API was the Testimonial Tree HTTP API stack from 2016, on .NET and C# .NET: the Testimonial Tree platform was .NET, written in C#, with Web Forms and Web API ASP.NET Web Forms	2
Go Backed by a dated role rather than a repository citation.	2021 – 2024(3 yrs)	Madwire (2021 – 2024)	None cited	KeyCloak TypeScript	3
ColdFusion Backed by a dated role rather than a repository citation.	2014 – 2016(2 yrs)	ValueCentric (2014 – 2016)	None cited	Python (ColdFusion gave way to Python): both were in use at ValueCentric, with REST APIs built in each, and Python is the one the work carried on in	2

Frontend & UI

Technology	When	Where it was used	Projects	Connections	Citations
React Backed by a repository analysed in the corpus.	2019 – presentCurrent(6 yrs)Spans 3 roles	Testimonial Tree 2016–2020 (2016 – 2020); Madwire (2021 – 2024); ITRADE Innovations (2024 – present)	Agentable, landing-editor, landibuild, landi-canvas, landi-orchestration-ui, landi-canvas-studio, orchestration-stack, vibed	TypeScript: Node and TypeScript from the Madwire platform; C# and .NET from Testimonial Tree, where React started in 2019; Next.js from Madwire in 2023; Landi React work at ITRADE Innovations from 2025 Next.js: Node and TypeScript from the Madwire platform; C# and .NET from Testimonial Tree, where React started in 2019; Next.js from Madwire in 2023; Landi React work at ITRADE Innovations from 2025 Vite: Vite builds both the Lit component packages and the React apps in this corpus Cloudflare AI Gateway: both named in 4 repository analyses Tailwind CSS: both named in 4 repository analyses .NET: Node and TypeScript from the Madwire platform; C# and .NET from Testimonial Tree, where React started in 2019; Next.js from Madwire in 2023; Landi React work at ITRADE Innovations from 2025 AG-UI: both named in 3 repository analyses C#: Node and TypeScript from the Madwire platform; C# and .NET from Testimonial Tree, where React started in 2019; Next.js from Madwire in 2023; Landi React work at ITRADE Innovations from 2025 Cloudflare Pages: both named in 3 repository analyses CopilotKit: both named in 3 repository analyses Google Gemini: both named in 3 repository analyses Cloudflare Queues: both named in 2 repository analyses OpenRouter: both named in 2 repository analyses Playwright: both named in 2 repository analyses tldraw Vitest: both named in 2 repository analyses Zustand: both repositories pair a canvas engine with a React state approach, and they resolve it differently AI SDK: both named in the vibed repository analysis Cloudflare Workers Static Assets: both named in the landi-orchestration-ui repository analysis dagre: both named in the landi-orchestration-ui repository analysis Excalidraw: both named in the landi-canvas repository analysis Gemini Live: both named in the landi-canvas-studio repository analysis GitHub OAuth: both named in the vibed repository analysis KeyCloak Monaco Editor: both named in the vibed repository analysis OpenNext: both named in the landi-canvas repository analysis Server-Sent Events: both named in the landi-canvas-studio repository analysis Vercel AI Gateway: both named in the vibed repository analysis Vercel Sandbox: both named in the vibed repository analysis	11
Next.js Backed by a repository analysed in the corpus.	2023 – presentCurrent(4 yrs)Spans 2 roles	Madwire (2021 – 2024); ITRADE Innovations (2024 – present)	landing-editor, client-mobile-content-app-study, landi-canvas, orchestration-stack, vibed	React: Node and TypeScript from the Madwire platform; C# and .NET from Testimonial Tree, where React started in 2019; Next.js from Madwire in 2023; Landi React work at ITRADE Innovations from 2025 Cloudflare Workers Tailwind CSS: both named in 4 repository analyses TypeScript AG-UI: both named in 2 repository analyses Cloudflare Queues: both named in 2 repository analyses CopilotKit: both named in 2 repository analyses AI SDK: both named in the vibed repository analysis Banuba SDK: both named in the client-mobile-content-app-study repository analysis Excalidraw: both named in the landi-canvas repository analysis Gemini: both named in the client-mobile-content-app-study repository analysis GitHub OAuth: both named in the vibed repository analysis Monaco Editor: both named in the vibed repository analysis Multi-agent orchestration: both named in the client-mobile-content-app-study repository analysis Node.js: both named in the client-mobile-content-app-study repository analysis OIDC: both named in the client-mobile-content-app-study repository analysis Okta: both named in the client-mobile-content-app-study repository analysis OpenNext: both named in the landi-canvas repository analysis PyMuPDF: both named in the client-mobile-content-app-study repository analysis React Native: both named in the client-mobile-content-app-study repository analysis REST API: both named in the client-mobile-content-app-study repository analysis Tesseract OCR: both named in the client-mobile-content-app-study repository analysis Vercel AI Gateway: both named in the vibed repository analysis Vercel Sandbox: both named in the vibed repository analysis YAML workflow configuration: both named in the client-mobile-content-app-study repository analysis	7
Vite Backed by a repository analysed in the corpus.	2025 – presentCurrent(2 yrs)	ITRADE Innovations (2024 – present)	agentable, embedacode, landi-canvas-studio, landi-orchestration-ui, landi-ui, landibuild	TypeScript React: Vite builds both the Lit component packages and the React apps in this corpus Lit Web Components Cloudflare Pages: both named in 3 repository analyses tldraw Gemini Live: both named in 2 repository analyses GitHub Packages: both named in 2 repository analyses Playwright: both named in 2 repository analyses Cloudflare Workers Static Assets: both named in the landi-orchestration-ui repository analysis dagre: both named in the landi-orchestration-ui repository analysis GitHub Actions: both named in the agentable repository analysis GitHub REST API: both named in the embedacode repository analysis Google Cloud Storage: both named in the landi-ui repository analysis JSZip: both named in the embedacode repository analysis pnpm: both named in the landi-ui repository analysis PrismJS: both named in the embedacode repository analysis Radix UI: both named in the agentable repository analysis Shadow DOM: both named in the embedacode repository analysis	8
Lit Web Components Backed by a repository analysed in the corpus.	2025 – presentCurrent(2 yrs)	ITRADE Innovations (2024 – present)	Agentable, embedacode, landi-ui, landing-editor	Vite Shadow DOM GitHub Packages: both named in 2 repository analyses Playwright: both named in 2 repository analyses Vitest: both named in 2 repository analyses GitHub REST API: both named in the embedacode repository analysis Google Cloud Storage: both named in the landi-ui repository analysis JSZip: both named in the embedacode repository analysis pnpm: both named in the landi-ui repository analysis PrismJS: both named in the embedacode repository analysis	8
tldraw Backed by a repository analysed in the corpus.	2025 – presentCurrent(2 yrs)	ITRADE Innovations (2024 – present)	agentable, landi-canvas-studio	Vite Zustand: both repositories pair a canvas engine with a React state approach, and they resolve it differently Gemini Live: both named in 2 repository analyses React GitHub Actions: both named in the agentable repository analysis Radix UI: both named in the agentable repository analysis Server-Sent Events: both named in the landi-canvas-studio repository analysis	4
Zustand Backed by a repository analysed in the corpus.	2025 – presentCurrent(2 yrs)	ITRADE Innovations (2024 – present)	agentable	tldraw: both repositories pair a canvas engine with a React state approach, and they resolve it differently React: both repositories pair a canvas engine with a React state approach, and they resolve it differently Radix UI: both named in the agentable repository analysis	5
ASP.NET Web Forms Backed by a dated role rather than a repository citation.	2016 – 2020(4 yrs)	Testimonial Tree 2016–2020 (2016 – 2020)	None cited	C#: Web Forms was the Testimonial Tree UI stack from 2016, on .NET and C# .NET: the Testimonial Tree platform was .NET, written in C#, with Web Forms and Web API ASP.NET Web API	2

Career

ITRADE Innovations

Lead DevOps Engineer - AI Governance & Security

2024 – presentCurrentMiami, Florida

Lead AI governance and security for production LLM and OCR pipelines, agent-native systems, and regulated customer environments.

Lead AI governance and security: agent orchestration patterns, guardrails, policy adherence, evaluation, and audit trails behind production LLM and OCR document pipelines.
Build agent-native systems for enterprise customers with AG-UI, A2UI, and generative UI.
Replaced manual deployment steps with automated CI/CD using GitLab CI, Argo CD, Argo Workflows, Argo Rollouts, Argo Events, and Kargo.
Run ECS Fargate services with ephemeral per-branch preview environments for code review.
Build reusable infrastructure modules in Pulumi and Terraform.

Madwire

Sr. Technical Product Manager, Platform Engineering

2021 – 2024Fort Collins, Colorado (Remote)

Led platform engineering teams and products across identity management, infrastructure, and CI/CD at over half a billion requests a month.

Led platform engineering teams and products across identity management, infrastructure, and CI/CD, handling over half a billion requests a month across hundreds of Kubernetes deployments.
Implemented CI/CD and high-availability systems with virtually no downtime.
Ran cloud cost reduction across GCP and AWS through storage lifecycle policies, right-sizing, and committed-use discounts against measured usage.
Orchestrated machine learning efforts including network anomaly detection, website scrapers, spam detectors, and customer KPI anomaly detection.

Testimonial Tree 2020–2021

VP of Products

2020 – 2021Fort Myers, Florida

Led the product team and helped the company reach profitability following a significant investment round.

Increased enterprise customer retention from 75% to over 90%, with over 100% year-over-year growth.
Took the SaaS platform from serving small and mid-size businesses to serving enterprises in regulated industries including real estate, mortgage lending, and healthcare.
Ensured regular compliance audits and maintained HIPAA compliance standards.

TypeScript AWS Amazon EC2 Amazon Route 53 Amazon S3 Amazon SNS Amazon SQS Auto Scaling Elastic Load Balancing AWS CloudFormation Amazon ECS AWS Step Functions HIPAA & HL7 Processing

Testimonial Tree 2016–2020

Staff Software Engineer to Director of Engineering

2016 – 2020Fort Myers, Florida

Joined as Staff Software Engineer and moved into Director of Engineering, leading engineers, designers, testers, and systems engineers.

Used machine learning to extract sentiment, topics, and false positives from customer reviews, turning review text into structured, validated signal.
Introduced CI/CD and gitflow protocols where releases had been manual.
Implemented auto-scaling AWS infrastructure with GCP redundancy for disaster recovery.
Implemented and managed HIPAA-compliant servers and processing of HL7 feeds and data drops.

ValueCentric

Lead Software Engineer

2014 – 2016Orchard Park, New York

Worked with the largest pharmaceutical companies in the world, using machine learning and big data analysis on supply chain data at billions of records.

Ran machine learning and big data analysis over pharmaceutical supply chain data consisting of billions of records, using Hadoop and MapReduce.
Built REST APIs in Python and ColdFusion and cross-platform native applications for pharmaceutical and supply chain companies.
Implemented and managed a HIPAA-compliant data center and the blinding of incoming data from specialty pharmaceutical and medical device companies.

TypeScript AWS Python Amazon EC2 Amazon Route 53 Amazon S3 Amazon SNS Amazon SQS Auto Scaling Elastic Load Balancing Big Data (Hadoop, MapReduce)ColdFusion HIPAA & HL7 Processing Big Data (Hadoop, MapReduce)

Profile Your City, Inc.

Lead Architect & Sales Engineer

2009 – 2014Buffalo, New York

Built and managed over 300 real estate broker portals in a multi-server SaaS environment supporting tens of thousands of agents.

Built versioned component distribution across hundreds of live sites, with automatic revert and reporting when a distribution step or unit test failed.
Built Multiple Listing Service (MLS) managers to synchronize and normalize data across dozens of MLS feeds over RETS.
Built an analytical service and API for market and property analysis, applying AI playbooks to trend and property value estimation.

PHP GetSimple CMS AWS Amazon EC2 Amazon Route 53 Amazon S3 Amazon SNS Amazon SQS Auto Scaling Elastic Load Balancing

Cited from repositories

Technology	When	Where it was used	Projects	Connections	Citations
Cloudflare AI Gateway Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	landi-ai-orchestrator, landi-orchestration-ui, landi-orchestrator, landibuild, landing-editor, orchestration-stack, orchestrator-dev-sandbox	Cloudflare Workers Cloudflare Workers AI TypeScript: both named in 5 repository analyses Wrangler: both named in 5 repository analyses Cloudflare Containers and Sandbox SDK: both named in 4 repository analyses Cloudflare Durable Objects: both named in 4 repository analyses Cloudflare R2: both named in 4 repository analyses React: both named in 4 repository analyses	7
Tailwind CSS Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	agentable, client-mobile-content-app-study, landi-canvas, landi-canvas-studio, landing-editor, vibed	OAuth: both named in 5 repository analyses Zod: both named in 5 repository analyses Model Context Protocol: both named in 4 repository analyses Next.js: both named in 4 repository analyses React: both named in 4 repository analyses Supabase: both named in 4 repository analyses TypeScript: both named in 4 repository analyses Cloudflare Workers: both named in 3 repository analyses	6
CKEditor Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	default-content, faq-manager, front-end-user-login, getsimple-blog, items-manager, multi-user, seo-manager, simplicity	GetSimple CMS: both named in 6 repository analyses PHP: both named in 6 repository analyses	8
Cloudflare Pages Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	agentable, landi-canvas-studio, landi-ui, landing-editor, orchestration-stack	Supabase: both named in 4 repository analyses Cloudflare Workers: both named in 3 repository analyses OAuth: both named in 3 repository analyses React: both named in 3 repository analyses TypeScript: both named in 3 repository analyses Vite: both named in 3 repository analyses Zod: both named in 3 repository analyses Cloudflare Containers and Sandbox SDK: both named in 2 repository analyses	5
CopilotKit Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	landi-ai-orchestrator, landi-canvas, landi-canvas-studio, landing-editor	React: both named in 3 repository analyses Zod: both named in 3 repository analyses Cloudflare Workers: both named in 2 repository analyses LangGraph: both named in 2 repository analyses Model Context Protocol: both named in 2 repository analyses Next.js: both named in 2 repository analyses OAuth: both named in 2 repository analyses Python: both named in 2 repository analyses CopilotKit & Generative UI	4
Google Gemini Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	agentable, landibuild, landing-editor, orchestration-stack	Cloudflare Workers: both named in 4 repository analyses Cloudflare Containers and Sandbox SDK: both named in 3 repository analyses Cloudflare R2: both named in 3 repository analyses Cloudflare Workers AI: both named in 3 repository analyses OAuth: both named in 3 repository analyses React: both named in 3 repository analyses Supabase: both named in 3 repository analyses Wrangler: both named in 3 repository analyses	4
Vitest Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	embedacode, landi-canvas-studio, landigents, landing-editor	TypeScript: both named in 4 repository analyses Cloudflare Durable Objects: both named in 2 repository analyses Cloudflare Workers: both named in 2 repository analyses Cloudflare Workers AI: both named in 2 repository analyses Lit Web Components: both named in 2 repository analyses OAuth: both named in 2 repository analyses React: both named in 2 repository analyses Supabase: both named in 2 repository analyses	4
GitHub Actions Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	agentable, orchestrator-dev-sandbox, resume-tailor-agent-skill	Cloudflare Workers: both named in 2 repository analyses TypeScript: both named in 2 repository analyses Cloudflare Containers and Sandbox SDK: both named in the orchestrator-dev-sandbox repository analysis Cloudflare Durable Objects: both named in the orchestrator-dev-sandbox repository analysis Model Context Protocol: both named in the agentable repository analysis OAuth: both named in the agentable repository analysis tldraw: both named in the agentable repository analysis Vite: both named in the agentable repository analysis GitLab CI & GitHub Actions	3
AG-UI Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	landi-canvas, landi-canvas-studio, landing-editor	React: both named in 3 repository analyses Zod: both named in 3 repository analyses Cloudflare Workers: both named in 2 repository analyses Model Context Protocol: both named in 2 repository analyses Next.js: both named in 2 repository analyses OAuth: both named in 2 repository analyses Supabase: both named in 2 repository analyses TypeScript: both named in 2 repository analyses	3
jQuery Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	default-content, front-end-user-login, getsimple-blog, items-manager, multi-user, seo-manager	GetSimple CMS: both named in 5 repository analyses PHP: both named in 5 repository analyses	6
Playwright Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	embedacode, landi-canvas-studio, landing-editor	TypeScript: both named in 3 repository analyses Lit Web Components: both named in 2 repository analyses OAuth: both named in 2 repository analyses React: both named in 2 repository analyses Supabase: both named in 2 repository analyses Vite: both named in 2 repository analyses Zod: both named in 2 repository analyses Cloudflare Containers and Sandbox SDK: both named in the landing-editor repository analysis	3
OpenCode Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	agent-builder, opencode-architect-knowledge, orchestrator-dev-sandbox, resume-tailor-agent-skill	TypeScript: both named in 2 repository analyses Cloudflare Containers and Sandbox SDK: both named in the orchestrator-dev-sandbox repository analysis Cloudflare Durable Objects: both named in the orchestrator-dev-sandbox repository analysis Cloudflare Workers: both named in the orchestrator-dev-sandbox repository analysis Wrangler: both named in the orchestrator-dev-sandbox repository analysis	4
Anthropic Claude Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	client-mobile-content-app-study, landibuild	OAuth: both named in 2 repository analyses Supabase: both named in 2 repository analyses TypeScript: both named in 2 repository analyses Cloudflare Containers and Sandbox SDK: both named in the landibuild repository analysis Cloudflare D1: both named in the landibuild repository analysis Cloudflare Durable Objects: both named in the landibuild repository analysis Cloudflare KV: both named in the landibuild repository analysis Cloudflare R2: both named in the landibuild repository analysis	2
Cloudflare Queues Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	landing-editor, orchestration-stack	Cloudflare Containers and Sandbox SDK: both named in 2 repository analyses Cloudflare R2: both named in 2 repository analyses Cloudflare Workers: both named in 2 repository analyses Cloudflare Workers AI: both named in 2 repository analyses LangChain: both named in 2 repository analyses LangGraph: both named in 2 repository analyses Next.js: both named in 2 repository analyses React: both named in 2 repository analyses	2
Cloudflare Sandbox SDK Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	landibuild, orchestrator-dev-sandbox	Cloudflare Containers and Sandbox SDK: both named in 2 repository analyses Cloudflare Durable Objects: both named in 2 repository analyses Cloudflare Workers: both named in 2 repository analyses TypeScript: both named in 2 repository analyses Wrangler: both named in 2 repository analyses Cloudflare D1: both named in the landibuild repository analysis Cloudflare KV: both named in the landibuild repository analysis Cloudflare R2: both named in the landibuild repository analysis	2
Cloudflare Workflows Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	landi-orchestrator, landing-editor	Cloudflare Durable Objects: both named in 2 repository analyses Cloudflare R2: both named in 2 repository analyses Cloudflare Workers: both named in 2 repository analyses Cloudflare Workers AI: both named in 2 repository analyses Model Context Protocol: both named in 2 repository analyses Python: both named in 2 repository analyses TypeScript: both named in 2 repository analyses Wrangler: both named in 2 repository analyses	2
FastAPI Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	landi-ai-orchestrator, landing-editor	Python LangGraph: both named in 2 repository analyses Vertex AI: both named in 2 repository analyses Cloudflare Containers and Sandbox SDK: both named in the landing-editor repository analysis Cloudflare Durable Objects: both named in the landing-editor repository analysis Cloudflare KV: both named in the landing-editor repository analysis Cloudflare R2: both named in the landing-editor repository analysis Cloudflare Workers: both named in the landing-editor repository analysis	2
Gemini Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	client-mobile-content-app-study, landi-ai-orchestrator	Google Cloud Platform: both named in the landi-ai-orchestrator repository analysis LangGraph: both named in the landi-ai-orchestrator repository analysis Next.js: both named in the client-mobile-content-app-study repository analysis OAuth: both named in the client-mobile-content-app-study repository analysis Python: both named in the landi-ai-orchestrator repository analysis Supabase: both named in the client-mobile-content-app-study repository analysis TypeScript: both named in the client-mobile-content-app-study repository analysis Vertex AI: both named in the landi-ai-orchestrator repository analysis	2
Gemini Live Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	agentable, landi-canvas-studio	OAuth: both named in 2 repository analyses tldraw: both named in 2 repository analyses Vite: both named in 2 repository analyses Zod: both named in 2 repository analyses Cloudflare Workers: both named in the agentable repository analysis Model Context Protocol: both named in the agentable repository analysis React: both named in the landi-canvas-studio repository analysis Supabase: both named in the landi-canvas-studio repository analysis	2
OpenRouter Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	landi-canvas, landibuild	Cloudflare Workers: both named in 2 repository analyses React: both named in 2 repository analyses Zod: both named in 2 repository analyses Cloudflare Containers and Sandbox SDK: both named in the landibuild repository analysis Cloudflare D1: both named in the landibuild repository analysis Cloudflare Durable Objects: both named in the landibuild repository analysis Cloudflare KV: both named in the landibuild repository analysis Cloudflare R2: both named in the landibuild repository analysis	2
Server-Sent Events Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	landi-ai-orchestrator, landi-canvas-studio	Google Cloud Platform: both named in the landi-ai-orchestrator repository analysis LangGraph: both named in the landi-ai-orchestrator repository analysis OAuth: both named in the landi-canvas-studio repository analysis Python: both named in the landi-ai-orchestrator repository analysis React: both named in the landi-canvas-studio repository analysis Supabase: both named in the landi-canvas-studio repository analysis tldraw: both named in the landi-canvas-studio repository analysis TypeScript: both named in the landi-canvas-studio repository analysis	2
Bifrost Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	landi-ai-orchestrator, landi-infra	Vertex AI: both named in 2 repository analyses Google Cloud Platform: both named in the landi-ai-orchestrator repository analysis LangGraph: both named in the landi-ai-orchestrator repository analysis Pulumi: both named in the landi-infra repository analysis Python: both named in the landi-ai-orchestrator repository analysis Supabase: both named in the landi-infra repository analysis TypeScript: both named in the landi-infra repository analysis	2
Google Cloud Run Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	landi-ai-orchestrator, landi-infra	Vertex AI: both named in 2 repository analyses Google Cloud Platform: both named in the landi-ai-orchestrator repository analysis LangGraph: both named in the landi-ai-orchestrator repository analysis Pulumi: both named in the landi-infra repository analysis Python: both named in the landi-ai-orchestrator repository analysis Supabase: both named in the landi-infra repository analysis TypeScript: both named in the landi-infra repository analysis	2
Google Secret Manager Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	landi-ai-orchestrator, landi-infra	Vertex AI: both named in 2 repository analyses Google Cloud Platform: both named in the landi-ai-orchestrator repository analysis LangGraph: both named in the landi-ai-orchestrator repository analysis Pulumi: both named in the landi-infra repository analysis Python: both named in the landi-ai-orchestrator repository analysis Supabase: both named in the landi-infra repository analysis TypeScript: both named in the landi-infra repository analysis	2
Node.js Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	client-mobile-content-app-study, resume-tailor-agent-skill, screenshotmcp	TypeScript: both named in 2 repository analyses Model Context Protocol: both named in the screenshotmcp repository analysis Next.js: both named in the client-mobile-content-app-study repository analysis OAuth: both named in the client-mobile-content-app-study repository analysis Supabase: both named in the client-mobile-content-app-study repository analysis	3
Redis Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	landi-ai-orchestrator, landi-infra	Vertex AI: both named in 2 repository analyses Google Cloud Platform: both named in the landi-ai-orchestrator repository analysis LangGraph: both named in the landi-ai-orchestrator repository analysis Pulumi: both named in the landi-infra repository analysis Python: both named in the landi-ai-orchestrator repository analysis Supabase: both named in the landi-infra repository analysis TypeScript: both named in the landi-infra repository analysis	2
AI SDK Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	vibed	Cloudflare Containers and Sandbox SDK: both named in the vibed repository analysis Drizzle ORM: both named in the vibed repository analysis Model Context Protocol: both named in the vibed repository analysis Next.js: both named in the vibed repository analysis OAuth: both named in the vibed repository analysis React: both named in the vibed repository analysis Supabase: both named in the vibed repository analysis TypeScript: both named in the vibed repository analysis	1
Cloudflare Workers for Platforms Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	landibuild	Cloudflare Containers and Sandbox SDK: both named in the landibuild repository analysis Cloudflare D1: both named in the landibuild repository analysis Cloudflare Durable Objects: both named in the landibuild repository analysis Cloudflare KV: both named in the landibuild repository analysis Cloudflare R2: both named in the landibuild repository analysis Cloudflare Workers: both named in the landibuild repository analysis Cloudflare Workers AI: both named in the landibuild repository analysis Drizzle ORM: both named in the landibuild repository analysis	1
Docker Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	orchestration-stack	Cloudflare Containers and Sandbox SDK Cloudflare D1: both named in the orchestration-stack repository analysis Cloudflare R2: both named in the orchestration-stack repository analysis Cloudflare Vectorize: both named in the orchestration-stack repository analysis Cloudflare Workers: both named in the orchestration-stack repository analysis Cloudflare Workers AI: both named in the orchestration-stack repository analysis Hono: both named in the orchestration-stack repository analysis LangChain: both named in the orchestration-stack repository analysis	1
Flowise Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	orchestration-stack	Cloudflare Containers and Sandbox SDK: both named in the orchestration-stack repository analysis Cloudflare D1: both named in the orchestration-stack repository analysis Cloudflare R2: both named in the orchestration-stack repository analysis Cloudflare Vectorize: both named in the orchestration-stack repository analysis Cloudflare Workers: both named in the orchestration-stack repository analysis Cloudflare Workers AI: both named in the orchestration-stack repository analysis Hono: both named in the orchestration-stack repository analysis LangChain: both named in the orchestration-stack repository analysis	1
GitHub OAuth Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	vibed	Cloudflare Containers and Sandbox SDK: both named in the vibed repository analysis Drizzle ORM: both named in the vibed repository analysis Model Context Protocol: both named in the vibed repository analysis Next.js: both named in the vibed repository analysis OAuth: both named in the vibed repository analysis React: both named in the vibed repository analysis Supabase: both named in the vibed repository analysis TypeScript: both named in the vibed repository analysis	1
Google Cloud Storage Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	landi-infra, landi-ui	Supabase: both named in 2 repository analyses TypeScript: both named in 2 repository analyses Lit Web Components: both named in the landi-ui repository analysis Pulumi: both named in the landi-infra repository analysis Vertex AI: both named in the landi-infra repository analysis Vite: both named in the landi-ui repository analysis	2
Langflow Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	orchestration-stack	Cloudflare Containers and Sandbox SDK: both named in the orchestration-stack repository analysis Cloudflare D1: both named in the orchestration-stack repository analysis Cloudflare R2: both named in the orchestration-stack repository analysis Cloudflare Vectorize: both named in the orchestration-stack repository analysis Cloudflare Workers: both named in the orchestration-stack repository analysis Cloudflare Workers AI: both named in the orchestration-stack repository analysis Hono: both named in the orchestration-stack repository analysis LangChain: both named in the orchestration-stack repository analysis	1
Monaco Editor Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	vibed	Cloudflare Containers and Sandbox SDK: both named in the vibed repository analysis Drizzle ORM: both named in the vibed repository analysis Model Context Protocol: both named in the vibed repository analysis Next.js: both named in the vibed repository analysis OAuth: both named in the vibed repository analysis React: both named in the vibed repository analysis Supabase: both named in the vibed repository analysis TypeScript: both named in the vibed repository analysis	1
n8n Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	orchestration-stack	Cloudflare Containers and Sandbox SDK: both named in the orchestration-stack repository analysis Cloudflare D1: both named in the orchestration-stack repository analysis Cloudflare R2: both named in the orchestration-stack repository analysis Cloudflare Vectorize: both named in the orchestration-stack repository analysis Cloudflare Workers: both named in the orchestration-stack repository analysis Cloudflare Workers AI: both named in the orchestration-stack repository analysis Hono: both named in the orchestration-stack repository analysis LangChain: both named in the orchestration-stack repository analysis	1
OpenAI Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	landibuild	Cloudflare Containers and Sandbox SDK: both named in the landibuild repository analysis Cloudflare D1: both named in the landibuild repository analysis Cloudflare Durable Objects: both named in the landibuild repository analysis Cloudflare KV: both named in the landibuild repository analysis Cloudflare R2: both named in the landibuild repository analysis Cloudflare Workers: both named in the landibuild repository analysis Cloudflare Workers AI: both named in the landibuild repository analysis Drizzle ORM: both named in the landibuild repository analysis	1
pgvector Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	landing-editor	Cloudflare Containers and Sandbox SDK: both named in the landing-editor repository analysis Cloudflare Durable Objects: both named in the landing-editor repository analysis Cloudflare KV: both named in the landing-editor repository analysis Cloudflare R2: both named in the landing-editor repository analysis Cloudflare Workers: both named in the landing-editor repository analysis Cloudflare Workers AI: both named in the landing-editor repository analysis LangChain: both named in the landing-editor repository analysis LangGraph: both named in the landing-editor repository analysis	1
Storybook Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	landing-editor	Cloudflare Containers and Sandbox SDK: both named in the landing-editor repository analysis Cloudflare Durable Objects: both named in the landing-editor repository analysis Cloudflare KV: both named in the landing-editor repository analysis Cloudflare R2: both named in the landing-editor repository analysis Cloudflare Workers: both named in the landing-editor repository analysis Cloudflare Workers AI: both named in the landing-editor repository analysis LangChain: both named in the landing-editor repository analysis LangGraph: both named in the landing-editor repository analysis	1
Stripe Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	landing-editor	Cloudflare Containers and Sandbox SDK: both named in the landing-editor repository analysis Cloudflare Durable Objects: both named in the landing-editor repository analysis Cloudflare KV: both named in the landing-editor repository analysis Cloudflare R2: both named in the landing-editor repository analysis Cloudflare Workers: both named in the landing-editor repository analysis Cloudflare Workers AI: both named in the landing-editor repository analysis LangChain: both named in the landing-editor repository analysis LangGraph: both named in the landing-editor repository analysis	1
Vercel AI Gateway Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	vibed	Cloudflare Containers and Sandbox SDK: both named in the vibed repository analysis Drizzle ORM: both named in the vibed repository analysis Model Context Protocol: both named in the vibed repository analysis Next.js: both named in the vibed repository analysis OAuth: both named in the vibed repository analysis React: both named in the vibed repository analysis Supabase: both named in the vibed repository analysis TypeScript: both named in the vibed repository analysis	1
Vercel AI SDK Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	landi-orchestrator	Cloudflare Durable Objects: both named in the landi-orchestrator repository analysis Cloudflare R2: both named in the landi-orchestrator repository analysis Cloudflare Workers: both named in the landi-orchestrator repository analysis Cloudflare Workers AI: both named in the landi-orchestrator repository analysis Model Context Protocol: both named in the landi-orchestrator repository analysis Python: both named in the landi-orchestrator repository analysis TypeScript: both named in the landi-orchestrator repository analysis Wrangler: both named in the landi-orchestrator repository analysis	1
Vercel Sandbox Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	vibed	Cloudflare Containers and Sandbox SDK: both named in the vibed repository analysis Drizzle ORM: both named in the vibed repository analysis Model Context Protocol: both named in the vibed repository analysis Next.js: both named in the vibed repository analysis OAuth: both named in the vibed repository analysis React: both named in the vibed repository analysis Supabase: both named in the vibed repository analysis TypeScript: both named in the vibed repository analysis	1
YAML Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	landi-orchestrator	Cloudflare Durable Objects: both named in the landi-orchestrator repository analysis Cloudflare R2: both named in the landi-orchestrator repository analysis Cloudflare Workers: both named in the landi-orchestrator repository analysis Cloudflare Workers AI: both named in the landi-orchestrator repository analysis Model Context Protocol: both named in the landi-orchestrator repository analysis Python: both named in the landi-orchestrator repository analysis TypeScript: both named in the landi-orchestrator repository analysis Wrangler: both named in the landi-orchestrator repository analysis	1
Cloudflare Workers Static Assets Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	landi-orchestration-ui	Cloudflare Workers: both named in the landi-orchestration-ui repository analysis Cloudflare Workers AI: both named in the landi-orchestration-ui repository analysis Model Context Protocol: both named in the landi-orchestration-ui repository analysis React: both named in the landi-orchestration-ui repository analysis Supabase: both named in the landi-orchestration-ui repository analysis TypeScript: both named in the landi-orchestration-ui repository analysis Vite: both named in the landi-orchestration-ui repository analysis	1
dagre Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	landi-orchestration-ui	Cloudflare Workers: both named in the landi-orchestration-ui repository analysis Cloudflare Workers AI: both named in the landi-orchestration-ui repository analysis Model Context Protocol: both named in the landi-orchestration-ui repository analysis React: both named in the landi-orchestration-ui repository analysis Supabase: both named in the landi-orchestration-ui repository analysis TypeScript: both named in the landi-orchestration-ui repository analysis Vite: both named in the landi-orchestration-ui repository analysis	1
GitHub CLI Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	opencode-architect-knowledge, orchestrator-dev-sandbox	Cloudflare Containers and Sandbox SDK: both named in the orchestrator-dev-sandbox repository analysis Cloudflare Durable Objects: both named in the orchestrator-dev-sandbox repository analysis Cloudflare Workers: both named in the orchestrator-dev-sandbox repository analysis TypeScript: both named in the orchestrator-dev-sandbox repository analysis Wrangler: both named in the orchestrator-dev-sandbox repository analysis	2
Radix UI Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	agentable	Cloudflare Workers: both named in the agentable repository analysis Model Context Protocol: both named in the agentable repository analysis OAuth: both named in the agentable repository analysis tldraw: both named in the agentable repository analysis Vite: both named in the agentable repository analysis Zod: both named in the agentable repository analysis Zustand: both named in the agentable repository analysis	1
Anthropic API Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	fsm-llm-crewai, fsm-llm-langgraph	LangChain: both named in 2 repository analyses Python: both named in 2 repository analyses CrewAI: both named in the fsm-llm-crewai repository analysis LangGraph: both named in the fsm-llm-langgraph repository analysis	2
Cloudflare Agents SDK Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	landigents	Cloudflare Durable Objects Cloudflare Workers: both named in the landigents repository analysis Cloudflare Workers AI: both named in the landigents repository analysis Model Context Protocol TypeScript: both named in the landigents repository analysis Wrangler: both named in the landigents repository analysis	1
GitHub Packages Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	embedacode, landi-ui	Lit Web Components: both named in 2 repository analyses TypeScript: both named in 2 repository analyses Vite: both named in 2 repository analyses Supabase: both named in the landi-ui repository analysis	2
Markdown Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	agent-builder, extend-downloader, opencode-architect-knowledge	GetSimple CMS: both named in the extend-downloader repository analysis PHP: both named in the extend-downloader repository analysis	3
OpenAI API Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	fsm-llm-crewai, fsm-llm-langgraph	LangChain: both named in 2 repository analyses Python: both named in 2 repository analyses CrewAI: both named in the fsm-llm-crewai repository analysis LangGraph: both named in the fsm-llm-langgraph repository analysis	2
pytest Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	fsm-llm-crewai, fsm-llm-langgraph	LangChain: both named in 2 repository analyses Python: both named in 2 repository analyses CrewAI: both named in the fsm-llm-crewai repository analysis LangGraph: both named in the fsm-llm-langgraph repository analysis	2
Excalidraw Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	landi-canvas	Cloudflare Workers: both named in the landi-canvas repository analysis Model Context Protocol: both named in the landi-canvas repository analysis Next.js: both named in the landi-canvas repository analysis React: both named in the landi-canvas repository analysis Zod: both named in the landi-canvas repository analysis	1
OIDC Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	client-mobile-content-app-study	Next.js: both named in the client-mobile-content-app-study repository analysis OAuth: both named in the client-mobile-content-app-study repository analysis Supabase: both named in the client-mobile-content-app-study repository analysis TypeScript: both named in the client-mobile-content-app-study repository analysis OIDC & Cross-Account IAM	1
OpenNext Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	landi-canvas	Cloudflare Workers: both named in the landi-canvas repository analysis Model Context Protocol: both named in the landi-canvas repository analysis Next.js: both named in the landi-canvas repository analysis React: both named in the landi-canvas repository analysis Zod: both named in the landi-canvas repository analysis	1
Slack Events API Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	landigents	Cloudflare Durable Objects: both named in the landigents repository analysis Cloudflare Workers: both named in the landigents repository analysis Cloudflare Workers AI: both named in the landigents repository analysis TypeScript: both named in the landigents repository analysis Wrangler: both named in the landigents repository analysis	1
Banuba SDK Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	client-mobile-content-app-study	Next.js: both named in the client-mobile-content-app-study repository analysis OAuth: both named in the client-mobile-content-app-study repository analysis Supabase: both named in the client-mobile-content-app-study repository analysis TypeScript: both named in the client-mobile-content-app-study repository analysis	1
Google Artifact Registry Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	landi-infra	Pulumi: both named in the landi-infra repository analysis Supabase: both named in the landi-infra repository analysis TypeScript: both named in the landi-infra repository analysis Vertex AI: both named in the landi-infra repository analysis	1
Google Cloud CDN Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	landi-infra	Pulumi: both named in the landi-infra repository analysis Supabase: both named in the landi-infra repository analysis TypeScript: both named in the landi-infra repository analysis Vertex AI: both named in the landi-infra repository analysis	1
Google Cloud DNS Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	landi-infra	Pulumi: both named in the landi-infra repository analysis Supabase: both named in the landi-infra repository analysis TypeScript: both named in the landi-infra repository analysis Vertex AI: both named in the landi-infra repository analysis	1
Google Cloud Monitoring Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	landi-infra	Pulumi: both named in the landi-infra repository analysis Supabase: both named in the landi-infra repository analysis TypeScript: both named in the landi-infra repository analysis Vertex AI: both named in the landi-infra repository analysis	1
Google Cloud SQL Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	landi-infra	Pulumi: both named in the landi-infra repository analysis Supabase: both named in the landi-infra repository analysis TypeScript: both named in the landi-infra repository analysis Vertex AI: both named in the landi-infra repository analysis	1
Google Compute Engine Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	landi-infra	Pulumi: both named in the landi-infra repository analysis Supabase: both named in the landi-infra repository analysis TypeScript: both named in the landi-infra repository analysis Vertex AI: both named in the landi-infra repository analysis	1
Handlebars Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	landi-ai-orchestrator	Google Cloud Platform: both named in the landi-ai-orchestrator repository analysis LangGraph: both named in the landi-ai-orchestrator repository analysis Python: both named in the landi-ai-orchestrator repository analysis Vertex AI: both named in the landi-ai-orchestrator repository analysis	1
LibreChat Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	landi-infra	Pulumi: both named in the landi-infra repository analysis Supabase: both named in the landi-infra repository analysis TypeScript: both named in the landi-infra repository analysis Vertex AI: both named in the landi-infra repository analysis	1
MongoDB Atlas Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	landi-infra	Pulumi: both named in the landi-infra repository analysis Supabase: both named in the landi-infra repository analysis TypeScript: both named in the landi-infra repository analysis Vertex AI: both named in the landi-infra repository analysis	1
Multi-agent orchestration Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	client-mobile-content-app-study	Next.js: both named in the client-mobile-content-app-study repository analysis OAuth: both named in the client-mobile-content-app-study repository analysis Supabase: both named in the client-mobile-content-app-study repository analysis TypeScript: both named in the client-mobile-content-app-study repository analysis	1
Okta Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	client-mobile-content-app-study	Next.js: both named in the client-mobile-content-app-study repository analysis OAuth: both named in the client-mobile-content-app-study repository analysis Supabase: both named in the client-mobile-content-app-study repository analysis TypeScript: both named in the client-mobile-content-app-study repository analysis	1
pnpm Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	landi-ui	Lit Web Components: both named in the landi-ui repository analysis Supabase: both named in the landi-ui repository analysis TypeScript: both named in the landi-ui repository analysis Vite: both named in the landi-ui repository analysis	1
Puppeteer Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	resume-tailor-agent-skill, screenshotmcp	Model Context Protocol: both named in the screenshotmcp repository analysis TypeScript: both named in the resume-tailor-agent-skill repository analysis	2
PyMuPDF Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	client-mobile-content-app-study	Next.js: both named in the client-mobile-content-app-study repository analysis OAuth: both named in the client-mobile-content-app-study repository analysis Supabase: both named in the client-mobile-content-app-study repository analysis TypeScript: both named in the client-mobile-content-app-study repository analysis	1
React Native Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	client-mobile-content-app-study	Next.js: both named in the client-mobile-content-app-study repository analysis OAuth: both named in the client-mobile-content-app-study repository analysis Supabase: both named in the client-mobile-content-app-study repository analysis TypeScript: both named in the client-mobile-content-app-study repository analysis	1
RediSearch Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	landi-ai-orchestrator	Google Cloud Platform: both named in the landi-ai-orchestrator repository analysis LangGraph: both named in the landi-ai-orchestrator repository analysis Python: both named in the landi-ai-orchestrator repository analysis Vertex AI: both named in the landi-ai-orchestrator repository analysis	1
REST API Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	client-mobile-content-app-study	Next.js: both named in the client-mobile-content-app-study repository analysis OAuth: both named in the client-mobile-content-app-study repository analysis Supabase: both named in the client-mobile-content-app-study repository analysis TypeScript: both named in the client-mobile-content-app-study repository analysis	1
Tesseract OCR Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	client-mobile-content-app-study	Next.js: both named in the client-mobile-content-app-study repository analysis OAuth: both named in the client-mobile-content-app-study repository analysis Supabase: both named in the client-mobile-content-app-study repository analysis TypeScript: both named in the client-mobile-content-app-study repository analysis	1
WebSocket Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	landi-ai-orchestrator	Google Cloud Platform: both named in the landi-ai-orchestrator repository analysis LangGraph: both named in the landi-ai-orchestrator repository analysis Python: both named in the landi-ai-orchestrator repository analysis Vertex AI: both named in the landi-ai-orchestrator repository analysis	1
XML Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	faq-manager, seo-manager	GetSimple CMS: both named in 2 repository analyses PHP: both named in 2 repository analyses	2
YAML workflow configuration Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	client-mobile-content-app-study	Next.js: both named in the client-mobile-content-app-study repository analysis OAuth: both named in the client-mobile-content-app-study repository analysis Supabase: both named in the client-mobile-content-app-study repository analysis TypeScript: both named in the client-mobile-content-app-study repository analysis	1
GitHub REST API Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	embedacode	Lit Web Components: both named in the embedacode repository analysis TypeScript: both named in the embedacode repository analysis Vite: both named in the embedacode repository analysis	1
JSZip Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	embedacode	Lit Web Components: both named in the embedacode repository analysis TypeScript: both named in the embedacode repository analysis Vite: both named in the embedacode repository analysis	1
npm Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	opencode-architect-knowledge, resume-tailor-agent-skill	TypeScript: both named in the resume-tailor-agent-skill repository analysis	2
PrismJS Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	embedacode	Lit Web Components: both named in the embedacode repository analysis TypeScript: both named in the embedacode repository analysis Vite: both named in the embedacode repository analysis	1
Shadow DOM Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	embedacode	Lit Web Components TypeScript: both named in the embedacode repository analysis Vite: both named in the embedacode repository analysis	1
CodeMirror Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	getsimple-blog	GetSimple CMS: both named in the getsimple-blog repository analysis PHP: both named in the getsimple-blog repository analysis	1
Disqus Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	getsimple-blog	GetSimple CMS: both named in the getsimple-blog repository analysis PHP: both named in the getsimple-blog repository analysis	1
jQuery UI Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	items-manager	GetSimple CMS: both named in the items-manager repository analysis PHP: both named in the items-manager repository analysis	1
MagpieRSS Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	getsimple-blog	GetSimple CMS: both named in the getsimple-blog repository analysis PHP: both named in the getsimple-blog repository analysis	1
MySQL Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	front-end-user-login	GetSimple CMS: both named in the front-end-user-login repository analysis PHP: both named in the front-end-user-login repository analysis	1
ShareThis Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	getsimple-blog	GetSimple CMS: both named in the getsimple-blog repository analysis PHP: both named in the getsimple-blog repository analysis	1
YAML frontmatter Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	agent-builder, opencode-architect-knowledge	None cited	2
Claude Code Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	resume-tailor-agent-skill	TypeScript: both named in the resume-tailor-agent-skill repository analysis	1
Cursor Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	resume-tailor-agent-skill	TypeScript: both named in the resume-tailor-agent-skill repository analysis	1
JSON Resume Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	resume-tailor-agent-skill	TypeScript: both named in the resume-tailor-agent-skill repository analysis	1
pdfkit Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	resume-tailor-agent-skill	TypeScript: both named in the resume-tailor-agent-skill repository analysis	1
Sharp Backed by a repository analysed in the corpus.	Undated	Personal and open-source work	screenshotmcp	Model Context Protocol: both named in the screenshotmcp repository analysis	1

Every row above comes from a source-cited entry in the same knowledge base the assistant answers from. Where a claim has no source, it says so rather than guessing.

hold ctrl to zoom

Click a node to see its era, where it was used, how it connects, and the evidence behind it.

Named thing: a specific technology, or a role held

Practice area: a capability, not a single named tool

Evidence: node size scales with how much backs it

Recency: brighter marks are more recent work

Selecting a node states in words what backs it.