The dispatch console didn't pause long enough for the Fabric's PoWR to settle.
It almost never does.
One agent finished a placement cycle and pushed its execution trace into the verification queue. Sensor bundle attached. Motion envelope sealed. Fabric's Proof-of-execution submission landed where it should.
task_dispatch: next_ready
The planner didn’t wait.
Another task execution envelope opened under the same capability filter and the scheduler released it immediately. Same machine identity class. Same task graph branch. Different object ID.
Actuator sequence started again before the first proof cleared verification on Fabric protocol.
I saw it in the queue a second later.
verification_queue_depth: 1
Still pending.
The robot had already moved on.
Second job started while the first execution proof was still waiting for validator replay. One proof aging in the verification queue while fresh actuator telemetry streamed through the task channel.
No alarm.
Just sequencing.
The arm closed around the next payload while the validator mesh was still replaying the previous sensor digest.
I refreshed the verification panel.
Same line.
verification_queue_depth: 1
Proof still pending.
Cursor hovered over the dispatch hold.
Too late.
The second job finished before the first proof hardened.
Two execution traces now sat in the queue.
verification_queue_depth: 2
Actuators already quiet.
Fabric still hadn’t decided if the first movement belonged in ledger history.
Validator replay began attaching stake weight to the earlier proof. Motion checksum verified against sensor frames. Torque profile matched the execution envelope.
Upstream, the scheduler had already moved forward.
Second execution trace referenced the first task’s completion state. Same object chain. Same task graph edge.
That parent edge wasn’t sealed yet.
Second task wasn’t just early.
It was already leaning on a task-bound state transition the Fabric's validator mesh hadn’t confirmed.
If the parent fails, the second move inherits a ghost state.
The robot still moved. The lineage underneath it didn’t.
verification_weight: rising
The validator line ticked upward.
First proof hardened.
execution_certificate: sealed
Ledger-anchored mission history updated on Fabric immediately. The parent edge locked into place and the second trace finally had a confirmed state to inherit.
Two seconds earlier that edge didn’t exist.
Now it did.
That gap was just verification time.
Another actuator trace appeared in the dispatch console.
task_dispatch: released
Third task window opened while the second proof was still entering validator replay.
verification_queue_depth: 2
Second proof replaying.
Next command already running.
Robots continuing their cycles while the @Fabric Foundation verification queue sorted the history behind them.