Culture Nodes
One ticket is waiting on a person
Each ticket below is where the engine stopped and asked for a human verdict. Nothing here is real data: the demo carries fixture rows so every surface can be exercised.
SCRUM-42
Now Review — waiting on a person: 1 decision and 2 runs of claims to review.
Open SCRUM-42
Inbox
Human tasks awaiting a decision, across every ticket.
Decisions
Proposed claims and pending approvals. The tab strip below is the shared segmented toggle that replaced the unstyled buttons.
Design
Every published workflow, readable as a graph — no run required. Select a version to see it drawn with the same node the Mesh and the run pages use.
Palette
Drag a kind onto the canvas, or tap it to add.
Drag from a node's right port to another node to connect.
Properties
Select a node to edit it.
Source · your YAML, comments kept
Runs
One page, three projections of the same rows.
| Run | Workflow | State | Actor | Updated |
|---|
| Run | Node | Actor / runner | State | Outcome | Usage |
|---|
Mesh
The org as it is right now: machines, the control plane, bridges, published workflows and active runs, joined only by relationships the records hold. Nothing replays on arrival.
machinecontrol plane / bridgehumanworkflow (by key)active run
edges: blue = runs on machine · yellow = actor is used by workflow · amber = run attribution
Fleet divergence visible: thor declares 6 actor keys, orin declares 4 on the same namespace. Which worker wins the poll decides whether company/notify-discord authenticates.
Committed history: 1,284 events. Replayed on this load: 0. The stream connected tail-only at snapshot marker 01J9…SNAP.
Ledger & plan
The confirmed plan for this lift, with real dependency edges. Every row is a task the operator confirmed.
| Task | Wave | Status | Depends on | Evidence |
|---|
Statistics
Usage over the listed window, from attempt rows.
Tokens in / out
412k / 96k
Cost
11.40 USD
median 0.28 per attempt
Runs by actor
- codex-thor
- 14
- codex-orin
- 11
- culture-claude
- 9
- human
- 3