Fabric didn't reject the command.
It outlived the credential.
Session opened clean. Identity proof matched the registry. Same machine. Same stake.
Then I hit the wrong pane and didn’t notice. Two seconds. Maybe three. The trace kept scrolling like it always does.
Task initiation cleared inside the session window.
Authorization accepted the payload.
Submission went upstream.
The actuator moved.
A small, calibrated shift. Local checkpoint logged. Onchain kernel recorded the task-bound transition. I saw the line and stopped reading.
Then the credential window crossed.
Fabric protocol Session still open.
Command still mid-flight.
Credential no longer valid.
The ledger snapshot updated first.
EXPIRED.
Same receipt ID. Same run. Different identity state.
The registry marked the credential expired at the block boundary. The actuator was still finishing its motion curve. Doesn’t matter. The receipt references the registry snapshot at commit, not what was true when I clicked submit.
I scroll back.
Wrong filter. Of course.
Identity-scoped execution only. There it is: valid at submission nonce. Expired at commit boundary.
Proof-of-execution confirmation on Fabric sits behind the registry update. No loud failure. Just one thin line in the verification logs: identity invalid at finalization.
The actuator doesn’t reverse because a ledger bit flipped.
Session timeout hadn’t triggered. But credential expiry is a different boundary. It closes and you find out after.
Dispute surface lights up.
Validators pull the receipt, pull the registry snapshot at commit, compare. Clean. The receipt points to a credential that’s already dead.
Half the quorum had already extended confidence on the state transition before the invalidation flag finished propagating. So now it’s neither clean nor rejected.
Acted enough to move metal. Disputed enough to stall. Or whatever.
Verification confidence sits under hardening.
Threshold is 0.67. It’s sitting at 0.64 and not moving.
Actuator finished.
State committed locally.
Ledger… hesitating.
I look for a villain. Attestation delay. Propagation. Anything.
It’s alignment.
Identity registry load spiked earlier.... a batch of credential staking updates landed right before mine expired. My expiration event got packed into the same block as my commit.
Bad timing. Same rules.
The receipt has proof.
The Fabric agent-native infrastructure registry says I shouldn’t.
No slashing. No malicious misbehavior. Just boundary mismatch. And it blocks the practical part: reward routing won’t clear until hardening, and I can’t reuse this action as a verified input.
Reward state stays pending. $ROBO doesn’t release.
I throttle the next command. Pause before submission. Check the expiry window manually.
It doesn’t extend because I’m watching it.
A new registry snapshot arrives. I didn’t ask. Same expired flag. Same receipt ID.
The task is still stuck in that bottleneck window... valid motion, expired identity, quorum not aligned.
Cursor already on submit.
My other hand is still on refresh.