$ROBO #ROBO @Fabric Foundation
Config hash changed while the arm was still inside the zone.
I didn't notice the vote. I noticed Fabric's compliance trace stop matching itself.
Dispatch read the old parameter set. Same contract. Same robot. Same task ID. Sweep already halfway when the chain ticked and the active config wasn’t what the planner had loaded.
effective: this block
dispatch_config: v1 / active_config: v2
Midpoint crossed.
Zone gate doesn’t care which hash you meant.
Actuator kept moving. Motion continued. Reference moved.
Bind shows up where you can't afford ambiguity:
accepted under old config
sealed under new config
Restricted entry happened under v1. The receipt gets written under v2.
No alarms. No revert. Just a verification path on Fabric Protocol switching the number it was going to certify against while the proof was still forming.
pre-seal
post-vote
mid-motion
I let it finish. Didn't override. Watched the settlement edge. Anyways...
Settlement cleared. Certificate latched onto the new hash... not the one dispatch started with. Compliance trace looked "clean" again, just… for v2.
Next run I froze a compliance snapshot at dispatch. If Fabric's governance flips mid-cycle, the task fails before motion. Hard stop. Early failure beats silent drift.
dispatch now blocks on state_read.
cycle_start slips when the read misses.
supervisor notices the pause.
Seal binds. Dispatch doesn’t.
Next block flips it again. You won’t know until the receipt picks a side.
#ROBO $ROBO