feat: let a run exist to be compared rather than executed

day01 commented

2026-08-13 09:40:31 +00:00

Owner

First half of roadmap step 5. Before this control plane is trusted with the work, it has to be run beside the one that already does it. A shadow run is how: the same event produces the same run here — opened, numbered, compiled, expanded by matrix and written down like any other — and the single thing it never does is reach a node.

The mode belongs to the run, not to the process that opened it. A control plane that had to remember which mode it was started in would hand yesterday’s shadow runs to a node the first time it came up live, so the queue simply never holds one and the store gives it back as what it was. There is a test for exactly that, over a real database.

A run now also names the workflow file it was compiled from. Two workflows in one commit answer the same event, so without the file there is nothing to line either of them up against on the forge — which is the whole reason a shadow run exists. Origin carries it; the wire message is unchanged, because the node has no use for it yet.

Shadow is stated with --shadow or SYNCODE_SHADOW and never inferred.

The comparison itself — reading what the forge made of the same event and reporting where the two disagree — is the second half and comes next.

First half of roadmap step 5. Before this control plane is trusted with the work, it has to be run beside the one that already does it. A shadow run is how: the same event produces the same run here — opened, numbered, compiled, expanded by matrix and written down like any other — and the single thing it never does is reach a node. The mode belongs to the run, not to the process that opened it. A control plane that had to remember which mode it was started in would hand yesterday’s shadow runs to a node the first time it came up live, so the queue simply never holds one and the store gives it back as what it was. There is a test for exactly that, over a real database. A run now also names the workflow file it was compiled from. Two workflows in one commit answer the same event, so without the file there is nothing to line either of them up against on the forge — which is the whole reason a shadow run exists. `Origin` carries it; the wire message is unchanged, because the node has no use for it yet. Shadow is stated with `--shadow` or `SYNCODE_SHADOW` and never inferred. The comparison itself — reading what the forge made of the same event and reporting where the two disagree — is the second half and comes next.

day01 added 1 commit 2026-08-13 09:40:32 +00:00

feat: let a run exist to be compared rather than executed

		Before this control plane is trusted with the work, it has to be run beside
the one that already does it. A shadow run is how: the same event produces the
same run here, opened and numbered and compiled and written down like any
other, and the single thing it never does is reach a node.

The mode belongs to the run, not to the process that opened it. A control
plane that had to remember which mode it was started in would hand yesterday's
shadow runs to a node the first time it came up live, so the queue simply
never holds one and the store gives it back as what it was.

A run now also names the workflow file it was compiled from. Two workflows in
one commit answer the same event, so without the file there is nothing to line
either of them up against on the forge, which is the whole reason a shadow run
exists.

Shadow is stated with --shadow or SYNCODE_SHADOW and never inferred.

day01 referenced this pull request

2026-08-13 11:17:32 +00:00

feat: measure what this control plane would have run #18

day01 closed this pull request

2026-08-13 11:17:34 +00:00

Pull request closed

This pull request cannot be reopened because the branch was deleted.

feat: let a run exist to be compared rather than executed #17

Pull request closed