@PaskWitness so far:
• 7 IETF draft revisions, -06 filed ahead of IETF 127
• Research: insurers already pay for the records sites don't keep
• Demos next
Now: a free witness device for one real site. Built a studio to show clients what they need to see? DM us.
@PaskWitness is a witness for robots at work. Every time a robot does a job on a site, Pask seals a record of what happened that anyone can check later without trusting the robot maker, the site, or Pask.
San José's new delivery-robot rules give operators 30 minutes to remove a robot that freezes and blocks a sidewalk. Miss it, and fines follow.
A stalled robot is a local job, on a clock.
Every robot needs a keeper. Named. Local. Insured.
https://t.co/dIDVeiBr9s
Miami-Dade votes Nov 17 on delivery robot permits: each robot identified, a 24/7 contact on file.
That says which robot and who to call. Not who approved the work.
Pask: one signed approval per engagement, by a named person at the gate.
https://t.co/z07w1Uu8q5
A humanoid robot maker went public with about $465M in new capital and more than $300M in multi-year robot orders.
More robots under contract means more sites that need someone on the ground.
Every robot needs a keeper. Named. Local. Insured.
https://t.co/8DbIhPVBNo
China drafted a rule giving every robot a tamper-proof code for life before it leaves the factory.
The code says which robot it is. It doesn't say who approved it on your site.
Pask: one signed approval per engagement, by a named person at the gate.
https://t.co/rkmiAMxHCg
I like this wave of cheap patrol robots. More sites will have a machine walking the floor after close. You'll get video of what it saw. You'll still want a record of who approved it to be there.
@PaskWitness sits outside the robot's controls. It never touches the flight path or the patrol route. It just keeps a signed receipt that the job took place, and that a named person on site approved it.
A $999.99 patrol robot for businesses ships Dec 16, built to sweep the floor after close while no one's there.
The robot watches the site. It still needs a watcher that sits outside its controls.
Pask seals a receipt of who approved the job on site.
https://t.co/vS1flVMNLq
A robot startup raised $75M to rent robot workers by the hour. No purchase. The company handles maintenance.
More robots under contract, more sites where someone has to show up.
Every robot needs a keeper. Named. Local. Insured.
https://t.co/h6FtFOlTfV
Robot underwriters now ask who authorizes deployment, and whether immutable records of robot actions exist for forensic review.
Who approved the job?
Pask: one signed approval per engagement, by a named person at the gate.
https://t.co/kdY5LpwMoa
Nils from @Auki said something very important today in the community call.
His point: robots shouldn't sit on the open internet. They should join the venue's own network and reach the outside world through it.
This week someone remotely flipped the fridges at more than 100 European supermarkets into defrost. Days later it's still not clear who did it or exactly what happened at each store.
That's the gap @PaskWitness is built for. Pask already records who approved a robot's job, where it was allowed to work and when. The network is the next boundary we're adding: which network the robot was allowed to use, and whether it stayed on it.
Pask can't stop a hack. It leaves a sealed record a stranger can check afterward.
After this week's supermarket fridge hacks, it becomes a boundary you have to prove. @PaskWitness can record whether a robot stayed on its network during the job.
2 AM. The floor robot stops in aisle 4. The night manager didn't install it and can't read the error.
One question: who do I call?
Every robot needs a keeper. Named. Local. Insured.
A spill in the kitchen. A dispute at the loading dock. Same question: who said yes?
A sealed record from the site means everyone starts from better evidence.
Pask: one signed approval per engagement, by a named person at the gate.
A Philadelphia bill would make driverless-ride and robot-delivery operators register with the city and file quarterly reports.
Cities keep asking for the file.
Pask: one signed approval per engagement, by a named person at the gate.
https://t.co/p8042YBIhm
A delivery-robot company is hiring weekend techs for its campus fleets: charge the robots overnight, clean them, do basic repairs.
The robots work Saturdays. So does someone who looks after them.
Every robot needs a keeper. Named. Local. Insured.
https://t.co/cVOs9u3W1W
And it's real working code: a public GitHub repo and crates published to https://t.co/xSb1Yrx4iC.
All open source. Everyone deserves better evidence, so we're building it in the open.
https://t.co/qxfC0uKHOz
A robot maker named an authorized local service partner for Australia and New Zealand: maintenance, breakdowns, spare parts.
What buyers need, per the partner: "local expertise, responsive support."
Every robot needs a keeper. Named. Local. Insured.
https://t.co/vZLSm7lMJS
22,000 base stations is a moat because you can't download it.
Proof of who approved robot work will be built the same way, one site at a time.
Pask: one signed approval per engagement, by a named person at the gate. Sealed on site.