Proofs stacked on Fabric before the registry cleared the front.
queue_depth: 2
Two Proof of Robotic Work bundles sitting in the distributed verification registry. Validators attaching weight. Certificate path moving.
verification_throughput: steady
Then another robot finished.
queue_depth: 3
One more bundle. One more validator pass.
Then Robot A closed its sweep and pushed another proof.
Fourth.
Fifth.
The line didn't clear.
queue_depth: 11
Robot A finished clean. Motion envelope sealed locally. Actuator logs hashed on Fabric agent-native protocol. Bundle submitted.
proof_bundle: pending
validator_weight: delayed
Robot idle.
Proof still fifth.
Before that one moved, Robot B finished.
Another.
The distributed verification registry kept accepting bundles while validators worked the front of the queue one trace at a time. No reject. No dispute.
queue_depth: 12
task_complete: true
reward_release: waiting
Controller closed the cycle. Wallet didn’t.
I cut the batch size on the next run.
Smaller tasks. Shorter traces. Lighter proofs.
Fabric's verification_throughput: unchanged
proof_size: reduced
Proofs got lighter. Queue didn't.
One certificate cleared.
Two more bundles landed.
Front moved once. Back filled twice.
queue_depth: 9
Next task finished. Front still uncleared.
queue_depth: 10