# System Landscape Simulator An interactive, frontend-only architecture map for modelling systems and simulated data journeys. It uses a classic ComfyUI-style LiteGraph canvas, but does not fork or modify ComfyUI and performs no live integrations. ## Run locally ```bash npm install npm run dev ``` The initial landscape contains Website, API, ERP, CRM and Email Platform plus two demo journeys: - **Place order:** Website → API → ERP, followed by parallel CRM and Email Platform updates. - **Register customer:** Website → API → CRM → Email Platform. - **Monday demo journeys:** Contact enquiry, Sample request, Commercial order, and Order retry and recovery. ## Features - Drag and rearrange systems on the dark LiteGraph canvas. - Edit or add systems, connections, scenario steps and parallel branches. - Group systems in explicit nested environment containers such as Azure → Subscription → Resource Group. Containers can be resized, moved with their contents, collapsed to summary nodes, and persisted independently of provider metadata. - Drill into logical system environments such as Dev, QA, UAT and Prod. Environments have editable components, instances, safe example configuration placeholders and internal topology; Sitecore Prod is included as a fictional CM/CD/MSSQL/Solr example. - Classify systems with Application, SaaS Service, Cloud Service, Development Tool and Data Store categories, plus independent tags such as Production, Test and Customer Data. - Use typed Data Flow, Deployment, Dependency and Source Repository relationships. Development playback includes the simulated Bitbucket commit → Azure DevOps build → website deployment journey. - Place reusable Website, CRM, ERP, Email Platform, Analytics and API presets, selecting only the capabilities needed for each instance. - Inspect labelled capability ports and fictional action payloads, expand node actions, and save customised systems as private browser-local presets. - Build reusable custom systems with form-based action, output and endpoint definitions. Actions support button, incoming request/event and simulated schedule triggers; outputs can run in parallel, and endpoints support multiple delayed example responses that may trigger actions. - Model direct request/response exchanges separately from onward event transfers. Request and response payloads are both recorded in the data inspector, with compatibility warnings shown without blocking unusual integrations. - Run, pause, advance and reset scenarios with animated packets and event log output. - Adjust playback speed and inspect the active payload. - Persist the complete landscape, including node positions, in browser local storage. - Export and import the landscape as JSON. Invalid imports and deleted connection references are rejected with actionable errors. - Use the Monday Demo guide at the bottom of the app to walk through playback, data inspection and failure recovery. ```bash npm test npm run build ``` ## Limitations This is intentionally a local simulation prototype. It has no authentication, collaboration, server persistence, external API calls, real payload delivery, or production-grade graph editing. Custom definitions and placed instances are stored in browser local storage; playback state is transient and is not included in saved JSON. LiteGraph supplies canvas rendering and cable interaction; scenario semantics are managed by the Vue application. The minimap is diagnostic rather than a full viewport navigator, and transformation highlighting currently compares top-level JSON fields.