Forty-two gauges, three times a shift.
Most rounds find nothing, which is the point of walking them. The robot walks every one. People walk out at 2 a.m. only for the reading that matters.
- Who asks
- The plant operator, through a standing schedule: route R1 at 02:00, 10:00 and 18:00, 42 checkpoints each time.
- Who does it
- A four-legged inspection robot walks the rounds. A licensed technician on call goes out only when the robot finds something.
- Who asks next
- The robot. The moment it finds a real anomaly, it posts the inspection task itself, under the plant's mandate.
- Evidence
- The robot's own gauge reads, thermal images and sound, checked against the plant's own sensors on the same lines.
- Who pays
- The plant: a flat fee per proven round, and the technician's call-out at the usual rate. No pay changes with what's found.
- You get
- A proof for every round, a proof for every anomaly from found to fixed, and a weekly record for your compliance file.
The robot does the walking. It hands over the moment a person is actually needed.
In one task the robot is the performer. A minute later, at pump P-7, it's the requester. The protocol doesn't need a special case for that.
Unit 2 and its plant are fictional. Prices are illustrative.
Two readings. If they differ, one is wrong.
Many gauges have a digital sensor on the same line. The robot's read has to agree with it. When it doesn't, that's a finding: something has drifted. And when a bearing runs hot, the robot stops being the one doing the work and becomes the one asking for it.
Findings are recorded in the proof, but they don't decide whether the round was done. A round with two findings is still a complete round.
From the 02:00 slot to a technician on call, in six steps.
The schedule asks. The robot walks, reads and compares. Only an anomaly brings a person in.
- 01
Schedule
A standing order posts route R1 three times a day. 42 checkpoints, in order, every time.
- 02
Walk
The robot walks the route on its own, and logs where it stood at every checkpoint.
- 03
Read
It reads each analogue gauge by camera, takes a thermal image of every motor, and listens near the flanges.
- 04
Cross-check
Where a gauge has a digital sensor on the same line, the two must agree. If they don't, that's a finding.
- 05
Call a person
Pump P-7's bearing is 22 °C above its baseline. The robot posts an inspection task to the on-call technician.
- 06
Prove
Each round gets one proof. Each anomaly gets its own: found, inspected, resolved.
Was the round walked? Five rules and one read.
These checks decide whether the round happened, in full and on time. Reading a needle is the only part that needs a model, and a plant sensor checks it wherever there is one.
| Check | How | By | Result |
|---|---|---|---|
| Every checkpoint | All 42 visited. A skipped checkpoint means an incomplete round, not a quiet pass. | Rule | Passed |
| In order | Visited in the route's sequence, so a short-cut round can't look like a full one. | Rule | Passed |
| At each spot | The robot's position is inside each checkpoint's zone while it reads. | Rule | Passed |
| On schedule | Started within 15 minutes of the slot, by trusted time. | Rule | Passed |
| Readable capture | Each gauge image is sharp, lit and face-on enough to read. If not, the checkpoint is re-read. | Rule | Passed |
| Gauge read right | The needle read by vision, and checked against the plant's sensor wherever there is one. | Model | Passed |
A blurred gauge isn't guessed at. The robot re-reads it before leaving the checkpoint, and if it still can't, the checkpoint is flagged for a person.
§ 05 · Scope and hazardous areas
Robot-performed. It says so on the proof.
A proof of a robot round is exactly that. Whether it can stand in for a round a permit says a person must walk is the plant's call, not Teleport's. And the robot only goes where it's certified to go.
- Performed by
- Robot, quadruped, on its own
- Proves
- All 42 checkpoints read, in order, on time
- Doesn't prove
- A statutory operator round, unless your permit allows it
- Zones
- Zone 2 certified. Zone 1 walked by people.
- Findings
- Recorded. They never change acceptance.
- Call-outs
- On-call licensed staff only. Never the marketplace.
Its hash goes into every round's proof, and the proof page shows it word for word.
What needs care.
A robot in a plant full of pressure and heat, standing in for people who used to walk the floor. The limits matter as much as the readings.
Not a legal round by default
Some permits and jurisdictions require a person to walk the round. The proof says “robot-performed inspection”, and the plant decides what that counts for.
Certified for the zone
Hazardous-area certification is a capability the robot has to hold for each zone, not an assumption. Where it isn't certified, the route goes round and people cover it.
A mismatch is a finding
When the gauge and the sensor disagree, one of them has drifted. That's useful, and it's recorded. It doesn't fail the round.
Findings don't change pay
A round is paid for being complete, not for being quiet. If “all clear” paid more, rounds would come back all clear.
Licensed people only
Anomaly tasks go straight to the plant's own on-call technicians, with a checked licence. Never to the open marketplace.
One alarm, not ten
A hot bearing stays hot for every round until it's fixed. One open task per asset, with each new reading added to it.
One round, proven. One finding, handed on.
The round's receipt says it was walked, in full, on time, by a robot, and what it found. The P-7 inspection gets its own receipt when the technician closes it.
The plant pays in dollars, per proven round. Nobody needs $PORT to schedule a round or to answer a call-out.
- Task
- Round R1 · 02:00 · 42 checkpoints
- Requested by
- Rounds schedule, for the plant operator
- Performed by
- Robot · quadruped, on its own
- Evidence
- Robot telemetry + plant sensors
- Checkpoints
- 42 of 42, in order
- Findings
- 2 · G-21 drift, P-7 bearing hot
- Scope
- Robot-performed inspection
- Decision
- Accepted
- Follow-up
- P-7 inspection task posted by the robot
STATUS: FINAL
Gauge images, thermal frames and audio stay in the plant. The proof holds their hashes.
For builders.
A SCHEDULE trigger, an INSPECT task with DIRECT fulfillment to the plant's own robots, and a SEQUENCE over every checkpoint. The anomaly task is a separate task, posted by the robot.
PhysicalTaskSpec · one roundTAP v0.2 + v0.3 draft · preview, subject to change
{
"schema": "teleport.tap.physical-task",
"version": "0.2.0",
"title": "Inspection round R1 — Unit 2 pump alley (02:00)",
"category": "INSPECT",
"requester": {
"requesterType": "ORGANIZATION",
"principal": { "principalType": "ORGANIZATION" },
"mandateId": "mdt_plant_rounds_unit2_v1"
},
"trigger": { "type": "SCHEDULE", "sourceRef": "campaign:unit2_rounds_r1" },
"fulfillment": {
"mode": "DIRECT",
"designatedPerformers": [{ "fleetId": "fleet_unit2_quadrupeds", "actorType": "ROBOT" }]
},
"actorRequirement": {
"permittedActorTypes": ["ROBOT"],
"requiredCapabilities": [
{ "capability": "INSPECT.GAUGE_READ" },
{ "capability": "CERT.HAZLOC", "attributes": { "zone": "2", "verified": true } }
]
},
"completionConditions": [
{ "type": "SEQUENCE", "id": "all_checkpoints", "steps": "route:r1:checkpoints[42]",
"verificationMethod": "DETERMINISTIC" },
{ "type": "LOCATION", "id": "at_each", "subjectRef": "robot", "zoneRef": "route:r1:checkpoint_zones",
"relation": "IN", "verificationMethod": "DETERMINISTIC" },
{ "type": "MEASUREMENT", "id": "capture_quality", "metric": "gauge_legibility",
"min": 0.9, "verificationMethod": "DETERMINISTIC" }
],
"findings": { "record": ["READING", "OUT_OF_RANGE", "SENSOR_DISAGREEMENT"], "affectsAcceptance": false },
"rightsPolicy": { "policyId": "plant-internal-only-v1" },
"economics": {
"buyerPriceUsdCents": 400,
"settlementAssets": ["FIAT"],
"requesterPayment": { "method": "INVOICE" }
},
"popw": { "required": true, "assurancePolicyId": "VERIFIED", "proofTiming": "BATCH" },
"metadata": { "verificationScope": "ROBOT_PERFORMED_INSPECTION" }
}Proposed additions this use case surfaced
- Findings beside acceptance
- Readings, out-of-range values and gauge/sensor disagreements recorded in the proof without deciding whether the round was done. The round and the finding are different questions.
- Performer turns requester
- A robot's own small mandate to post follow-up tasks from inside a task it's doing: which kinds, to whom, and up to what cost.
- Paired readings
- A condition that compares two readings of the same thing (vision and sensor) within a tolerance, and records a disagreement as a finding, not a fail.
- Rollups at volume
- 126 rounds a week per route. One rollup proof over all of them, so a compliance officer checks one root, not 126 receipts.
- Verification scope
- Required for every inspection task: “robot-performed inspection” on the proof, word for word, so nobody mistakes it for a statutory human round.
Example economics: $4 per proven round, invoiced monthly. The robot is the plant's own, so there's no performer pay. Call-outs are paid at the contractor's usual rate, on accept. Developer docs
Plant operators
Still walking every round at 2 a.m.?
Tell us your routes and your permits. We're looking for design partners with inspection robots on site.