Execution and Security Flows

Editor test

Text alternative: the authenticated editor sends a fixture to the session API; BraidRunner creates and executes a run, persists events, then returns the run and browser-sink receipts.

Public webhook

Text alternative: the public endpoint validates a DataBraid token, runs the same server engine, resolves provider secrets internally and returns either JSON or 204, always with a run identifier when created.

Template and Bead lifecycle

A built-in template is copied into a user-owned Braid. Its note remains in the editor but is not executable. At startup, LiteGraph registers node classes; DataBraid combines declarative ports, generated properties and runtime policy into the Bead manifest used by the palette and Inspector.

Secrets are references. A node stores the selected secret name; the authenticated server endpoint resolves the value for the owning user. Raw values must not enter the Braid document, run summaries, fixtures or documentation.