Nbyula OPS Graph Live collaborative editor
connecting… 1 online
SlugNameCategorySource Delivery modePrimary ownerDescription Variants# Stages
IDFromToDirection TriggerTrigger ownerStatus
Service#StageDescription OwnerSupportersTrigger Completion# sub-tasks

Reading this graph

Each node is a service or plan that Nbyula sells or runs internally. Each edge is an operational transition — what triggers a customer (or staff member) to move from one service into the next.

Click any node or edge in the Graph tab to open its full record on the right. All edits sync to every connected viewer in real time and persist to data/live.json on the server.

Node colors (category)

Edge colors

default transition
tbd (needs operational confirmation)

Subgraphs (plans)

The four plans (Pro, Premium, Ultimate, Writing Bundle) are not rendered as separate boxes — they live as vertices_included arrays inside each subgraph definition. Use the Plans / Subgraphs tab to edit them and the Highlight plan dropdown in the toolbar to colour included vertices.

Source of truth

  • Initial seed: ops-graph/out/master.json (generated by build_graph.py)
  • Live editable state: ops-graph/viewer/data/live.json
  • Export current state at any time using Export master.json in the header
  • Every edit is timestamped and broadcast on the websocket. Refresh-safe.

Keyboard shortcuts in the Graph tab

  • Click a node/edge to inspect it
  • Drag a node to reposition it (positions sync live)
  • Scroll to zoom in/out
  • Delete or Backspace removes the selected node/edge (with confirmation)

Collaboration model

  • Every connected browser sees a coloured avatar of every other viewer in the header.
  • Edits are last-write-wins per field. There's no merge conflict resolution — if two people edit the same cell simultaneously, the later edit overwrites.
  • The server debounces saves to disk every 1.5 seconds. The on-disk file is your durable record.

Service Vertex Multiplicity

How many graph vertices each service should have inside a plan — sourced from the Services in Subgraphs sheet. Edit a count to change how many copies of that service live inside the plan. Discrepancies between this table and vertices_included are flagged.
Pro 0 services · 0 vertices
Premium 0 services · 0 vertices
Ultimate 0 services · 0 vertices

Pro Plan

plan-pro
ServiceVertices
Total0

Premium Plan

plan-premium
ServiceVertices
Total0

Ultimate Plan

plan-ultimate
ServiceVertices
Total0