green rose systems

“growth, forever”
A Software Studio · Established 2026

substrate-ui

A console for watching, steering, and authoring runs on the Substrate runtime.

01  ·  description

substrate-ui has three capabilities, all on the real runtime.

Observe. A record rail lists runs. Pick one and the run-as-graph lights up: firing-anchored Producer-instance lifespans with spawn-cohort bands showing which Producers started together. A second view shows the static topology structure (the authored Producers, Triggers, Views, Routes, TerminationPolicy). The event stream scrolls alongside. One seq-cursor drives the graph and stream in lock-step. A provenance inspector traces any event back through the chain that produced it. The health verdict reads green FINALISED, red FAILED or NOT-CLEAN, cyan PAUSED, amber INCOMPLETE, or green LIVE. Record diff finds the first divergence by sequence number. An I/O pane shows seed, baseline, and artifacts.

Control. Launch a bundled topology, resume a paused run, or live-attach to follow a run as it writes. Launch and resume only; the UI never mutates run semantics.

Author. The Studio (at /studio.html) offers structured-form and drag-canvas authoring of Producers (deterministic stub or model-backed), Views, Triggers and Predicates, Routes, and composed (any_of / all_of) TerminationPolicies. Changes validate live through the real TopologyBuilder. Build and launch a genuine recorded run from the canvas, then deep-link back into the console to observe it. Model-backed Producers call the runtime’s own Responder.

No framework, no build step, no CDN. Vanilla JS frontend, stdlib Python backend. The UI reads the runtime through its public surfaces only, never kernel internals. That boundary is enforced by an import-boundary test, not just by convention. PolyForm Noncommercial 1.0.0.

02  ·  repository

github.com/laffeyp/substrate-ui

Contact

We’re open to a small number of new engagements. Write with a short note about the work and the timeline.

info@greenrosesystems.com