CatC to Meraki Migration AI AssistantPrivate project overview
Pain point → operating model

CatC to Meraki Migration AI Assistant

Engineers face repeated manual work when converting Catalyst Center inventory and configuration intent into a Meraki migration plan.

Use case

Engineers face repeated manual work when converting Catalyst Center inventory and configuration intent into a Meraki migration plan.

How it solves it

A guided browser workflow captures scope, device facts, migration choices, readiness, and verification steps while keeping credentials session-scoped.

Architecture

The design separates inputs, orchestration, AI assistance, and human verification. Secrets and environment-specific identifiers belong in runtime configuration, never in this page or source control.

Pain pointquestion or taskSourcesvalidated inputsAgenticOpsroute · retrieve · observeretry · audit · hand offAI / RAGgrounded assistanceVerified outcomehuman-safe action

Software stack

HTML, CSS, JavaScript, guided workflow state, API integration boundaries, safe input handling.

Source-controlledTestableObservableLeast privilege

AI and AgenticOps

AI can explain migration choices and identify missing prerequisites; AgenticOps can coordinate discovery, mapping, approval, and verification as separate observable actions.

Technical operating model

Ingest
Accept structured inputs and normalize them.
Reason
Retrieve approved context and produce a bounded plan.
Verify
Apply guardrails, human review, and evidence checks.

The assistant is designed to help humans make migration decisions; it does not silently apply changes.