Add custom system builder and simulated endpoints

This commit is contained in:
2026-11-05 22:42:27 +00:00
parent 36111a3166
commit e056837232
5 changed files with 54 additions and 10 deletions
+3 -1
View File
@@ -21,6 +21,8 @@ The initial landscape contains Website, API, ERP, CRM and Email Platform plus tw
- Edit or add systems, connections, scenario steps and parallel branches.
- 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.
@@ -34,4 +36,4 @@ 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. 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.
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.