Fabric hadn't finished confirming the robot’s identity when the task started moving.
Authorization showed pending.
Not rejected. Not sealed.
I already sent the task assignment contract.
Robot accepted.
I scrolled the trace. Task request first. Execution authorization second. Ping into the robot identity registry. Hardware signature attached. Wallet visible.
Still hashing.
The actuator log flickered on the side panel. First motion cycle had already started. Not the full task. More like the machine leaning into it. I stared at the authorization status longer than I should have.
Still waiting on hardware-bound identity verification on Fabric agent-native protocol.
Motion telemetry kept scrolling.
For a second I convinced myself I was looking at the wrong robot. Same operator account. Two agents live. Similar task IDs.
I checked the signer hash again.
Same robot.
I clicked into the machine identity record.
Same hardware fingerprint.
Same agent wallet.
Back out.
Still pending.
Another motion packet landed. The execution trace started writing the first task lines while the registry entry stayed yellow.
Not red.
Just unresolved.
I refreshed the registry query.
Nothing.
Hardware verification hash still calculating.
The task lifecycle had already moved to active. Execution trace writing. Registry still verifying.
The actuator tone rose as the first action cycle finished. I didn’t notice it at first. Then I did... I couldn’t stop hearing it.
Still pending.
I checked the task assignment contract again. Timestamp clean. Ordering clean. Capability registry had already cleared eligibility earlier.
Green there.
Yellow here.
The execution trace kept growing.
Another line. Another. The robot was already past the first checkpoint and Fabric had begun writing the execution evidence buffer before identity had fully settled. Verification nodes would see the trace either way.
I moved the cursor toward pause.
Not because the movement looked wrong. It didn’t. Task instructions were executing exactly the way they were supposed to.
That was the problem.
The registry flickered.
One block deeper in the Fabric verification pipeline.
Not done.
I scrolled back.
Wrong filter.
Back again.
Same result. Identity still verifying. Task still active. Robot already halfway into the next movement step.
@Fabric Foundationregistry hash moved one node further across the identity registry.
Execution trace kept appending lines.
The machine identity entry looked almost confirmed now... propagation halfway across the registry nodes. Close enough that I waited another second.
The robot didn’t.
Another telemetry packet arrived. Another trace line appended.
Somewhere in the middle of that I stopped watching the robot and started watching the registry instead. By then the machine had already finished another action cycle.
I checked the identity record again.
Still verifying.
Checked the task lifecycle state again.
Still active.
The registry still deciding.
The trace already recording.
I moved the cursor toward the pause control again.
Didn’t click.
Fabric's Registry hash advanced one more block.
The robot started the next movement step before it turned green.
Registry still verifying.
Execution trace still growing.