Everything starts with a vertex.
Node Vertex turns URLs into programmable points for data, forms, apps, analytics, workflows, communication, notifications, secure actions, secrets, files, and live signals.
sales -> form -> array -> listener -> email
Create the endpoint. Attach controls. Notify the right actor. Render secure actions. Let the vertex carry the signal.
Alerts and responses are now part of the vertex fabric.
A Notification Vertex tells someone something happened. An Action Vertex lets someone do something about it.
Notifications can reference actions, but actions remain independent, reusable, securable, auditable vertices. The same approve, reject, acknowledge, retry, rollback, open-artifact, or continue-workflow action can appear in notifications, mobile surfaces, web UI, CLI, agents, and Polygon workflows.
Unread state, severity, source vertex, category filtering, archive, acknowledge, and associated action cards.
/acme/notify/security
Input schema, roles, devices, agents, outcomes, handler target, TTL, single-use, audit, and presentation controls.
/acme/actions/prod/rollback
Your phone is a vertex. Devices can register as notification targets while delivery providers stay pluggable.
/acme/users/u-123/phone
Pause workflows until an action outcome arrives, branch by outcome, or timeout safely.
WAIT_FOR_ACTION
Create the right vertex for the job.
A vertex can be content, a form, a notification, an action, a device, a handoff, a listener, a secret, an array, static HTML, a stream, or an app.