Nodeshiftflow
≡

Custom view

Automation Control Layer

A reference architecture we iterate with clients—trigger model, approval states, notification routing—so executives see the same vocabulary engineers use.

Trigger model

Events enter through adapters (webhooks, buses, flat files). Each trigger carries a schema version, tenant marker, and replay token so operators know whether a send was simulated or live.

Trigger model diagram Source bus Schema gate Quiet arcs Router Simulation sandbox · publish window · reviewer hash

Approval states

States are sparse on purpose: Draft, In review, Waiting externally, Released, and Archived with legal hold. Each transition stores actor, rationale, and optional attachment hash—nothing relies on tooltip memory.

  • • Dual control enforced before Released when policy requires.
  • • Waiting externally shows partner SLA clocks when data exists.
  • • Archived retains read-only reviewer threads.

Notification routing

Routing trees evaluate severity, region holidays, on-call calendars, and digest preferences. When a branch fails open, operators see why—carrier proof optional, never silent drops.

  • • Executive war rooms can opt into richer detail for 48 hours.
  • • Marketing namespaces are blocked from incident paths.
  • • Replay timelines are privacy gated by default.