Restaurant cameras that post their own work orders

§ 01

The camera asks. The restaurant answers for it.

Most restaurants already have a camera on the dining room. It already sees the spill before a customer slips on it, and the cooler before it runs out. Teleport gives what it sees somewhere to go.

Who asks: The dining-room camera, under a mandate from the restaurant. The restaurant answers for every task it posts.
Who does it: On-shift staff first. The contracted cleaning company if nobody takes it. The drinks supplier for restocks.
Evidence: The same camera's before and after frames, from the same angle, plus the performer's own photo.
Who pays: The restaurant, from a weekly budget it sets. Staff get a bonus; the supplier gets paid on acceptance.
You get: One receipt for the whole chain: detected, done, checked.

Cameras are good at noticing. Mops are not yet one of their skills.
The short version

Detection is cheap and getting cheaper. The valuable part is what comes after: an accountable task, a checked outcome and a receipt the restaurant, the performer and anyone else can verify.

Bistro 12 is a fictional restaurant. Prices and limits are illustrative.

§ 02

Two jobs the camera already sees.

A dirty floor and a thin cooler. Different people, different money, the same shape: seen, posted, done, checked by the next frame.

Workflow A · Clean

The camera saw the spill. The next frame shows it's gone.

01 Seen for 60 seconds
02 To on-shift staff, 15 min
03 No taker? It goes to the cleaners
04 Same angle, clean floor

Seen. Debris or liquid in zone B for more than 60 seconds. The clip stays off-chain; only its hash is kept.
To staff. Direct to the on-shift floor pool, 15 minutes, $5 bonus. Under the auto-approve line, so no manager tap.
Escalated if nobody takes it. The expired task triggers a second one to the cleaning company, in the same workflow.
Checked. The model is asked one question: is zone B free of spills, debris and standing liquid? A versioned policy turns the answer into a decision.

Workflow B · Restock

It counts empty slots, not bottles. Bottles hide behind each other.

01 Six facings below par
02 Batched into one order at 2 p.m.
03 Over $50, so the GM taps once
04 Counted back to par

Batched. Not one task per empty slot. One restock order when facings drop below par, or at the 2 p.m. cutoff.
Approved. $380 is over the $50 line, so it waits for one tap from the general manager.
Sent. Direct to the named supplier, in the Teleport app or by webhook into their ordering system.
Counted. The cooler frame after the visit shows every facing at or above par. Glare or a blocked view goes to review, not straight to rejection.

§ 03

One spill. One task.

A camera sees the same puddle in every frame. The restaurant should get one task, not a stack of them. The camera is very observant. It is not allowed to be a nag.

Held for a minute
A mop in use or a table being bussed can look like a mess. It has to last.
One open task per zone
Further sightings attach to the open task instead of posting new ones.
A cooldown after
A new spill a minute later is a new task. Not your fault, and not a failed one.

Today a mandate caps volume (tasks per hour, open tasks). Per-condition de-duplication is a proposed TAP addition; see § 08.

§ 04 · The mandate

It can ask for a mop. It can't keep score.

The camera posts only within limits the restaurant sets. A glitch or a flood of detections can't turn into an unlimited bill, and the camera can never be turned on the staff.

Posting mandate · dining-room camerasActive · v1

Can post: Clean, stock, deliver, inspect
Spend: Up to $400 a task, $1,500 a week
Pace: 4 tasks an hour, 3 open at once
Where: This restaurant only
Approval: Automatic under $50; the GM above it
Never: person-tracking
staff-performance
customer-identification

Staff tasks skip approval on purpose. Otherwise every mop would wait for a manager.

The camera asks to post…Clean up a spill · $5 bonusRestock the cooler · $380 orderA fifth task this hourFlag who's been idle

Clean up a spill · $5 bonus

Posted

Under the $50 line, so it goes straight to on-shift staff. Nobody has to approve a mop.

Restock the cooler · $380 order

Waits for the GM

Over $50 and under the $400 cap. One tap from the general manager, then it goes to the supplier.

A fifth task this hour

Held

The mandate allows four an hour and three open at once. A glitchy camera can't run up a bill.

Flag who's been idle

Refused

Person tracking and staff performance are prohibited. The camera watches the floor, not the people on it.

§ 05

Same camera, same angle. A fair before and after.

Every piece of evidence says where it came from. The model estimates; a versioned policy decides.

Evidence	Origin	Used for	Why it's there
Before frame	Attested device	The baseline	Shows the problem was real when the task was posted.
After frame	Attested device	Floor clean, walkway clear	Same camera, same angle, so the comparison is fair. This is the main evidence.
Performer's photo	Teleport capture	Corroboration and disputes	Their own record, in case the camera is blocked or a customer spills again right away.
Robot odometry	Actor telemetry	Coverage of zone B	When a floor robot does the job instead. Same task, different evidence.

Accept
The model is confident zone B is clean and dry, and nothing is left in the walkway.
Review
The camera frame and the performer's photo disagree. A person looks. Nobody is docked by default.
New task
A fresh spill seconds after it was cleaned is a new task, not a failed one.

§ 06

What needs care.

A camera in a dining room records customers and staff. These rules are part of the design, not the small print.

Clips, not streams
Only event frames, cropped to the marked zone, with faces blurred before anything is stored. Raw video stays off-chain.
Tasks, not people
The camera can ask staff for help. It can't track who is slow, idle or absent. Those tags are prohibited in the mandate.
Fair to whoever did it
The payer's camera is the main evidence, so the performer's photo, review-not-reject and a dispute path keep it even.
A shadow isn't a spill
A condition has to hold for a minute, one task per zone, a cooldown after. Low confidence asks the manager first.
Glass doors only
It counts empty slots, not bottles; bottles hide behind each other. Solid-door fridges and back stock stay manual.
The alert goes out first
A spill during service is a slip hazard. Staff get an instant alert. The task is the paperwork, and it never slows that down.

§ 07

Detected, cleaned, checked. One receipt.

The Proof of Physical Work covers the whole workflow, not just the mop. It names the camera that asked, the mandate it asked under, who did the work, where each piece of evidence came from and which policy accepted it.

Dollars pay for the work. The proof shows it was done. Neither needs $PORT.

PROOF OF PHYSICAL WORKworkflow · example

VERIFIED

Task: Clean dining floor, zone B
Requested by: Camera, under the restaurant's mandate
Performed by: Human · on-shift staff
Evidence: Camera before + after, guided photo
Policy: facility-clean v1.0
Decision: Accepted
Paid: $5.00 bonus · USD
Chain: Seen → cleaned → verified

STATUS: FINAL

Example receipt. Fictional restaurant; amounts illustrative.

§ 08

For builders.

Every party in this story maps onto an existing TAP v0.2 type. The camera is a DEVICE requester, the restaurant is its accountable principal, and the trigger is a SENSOR_EVENT.

PhysicalTaskSpec · floor cleaning, task A1TAP v0.2 · preview, subject to change

{
  "schema": "teleport.tap.physical-task",
  "version": "0.2.0",
  "title": "Clean dining-room floor, zone B",
  "category": "CLEAN",
  "requester": {
    "requesterType": "DEVICE",
    "principal": { "principalType": "ORGANIZATION" },
    "mandateId": "mdt_bistro12_cams_v1",
    "authentication": { "method": "DEVICE_ATTESTATION" }
  },
  "trigger": { "type": "SENSOR_EVENT", "sourceRef": "cam-dining-02" },
  "fulfillment": {
    "mode": "DIRECT",
    "designatedPerformers": [{ "fleetId": "staff_bistro12_floor", "actorType": "HUMAN" }]
  },
  "completionConditions": [
    { "type": "SEMANTIC", "id": "floor_clean",
      "question": "Is the floor in zone B free of spills, debris and standing liquid?",
      "verificationMethod": "JEV", "minimumEvidenceOrigin": "ATTESTED_DEVICE" },
    { "type": "STATE", "id": "zone_unobstructed",
      "subjectRef": "zone:dining_b", "property": "obstructed", "expected": false,
      "verificationMethod": "PERCEPTION" }
  ],
  "evidenceProfiles": [{
    "actorTypes": ["HUMAN"],
    "requiredEvidence": [
      { "id": "before_frame", "type": "IMAGE", "acceptedOrigins": ["ATTESTED_DEVICE"] },
      { "id": "after_frame",  "type": "IMAGE", "acceptedOrigins": ["ATTESTED_DEVICE"] },
      { "id": "after_photo",  "type": "IMAGE", "acceptedOrigins": ["TELEPORT_CAPTURE"] }
    ]
  }],
  "verificationPolicy": { "policyId": "facility-clean-v1", "version": "1.0" },
  "economics": {
    "performerPayUsdCents": 500,
    "requesterPayment": { "method": "MANDATE_BUDGET", "maxSpendUsdCents": 4000 }
  },
  "popw": { "required": true, "assurancePolicyId": "VERIFIED", "proofTiming": "WORKFLOW" },
  "timing": { "expiresInSeconds": 900, "priority": "HIGH" }
}

Proposed additions this use case surfaced

Watch rule: The standing instruction behind the task: this camera, this zone, this condition, this template, this mandate. Its hash goes in the trigger, so the proof shows why the task existed.
De-dup + cooldown: One open task per condition, not per detection, and a quiet period after it's done.
Ambient redaction: Always-on cameras see bystanders. Evidence says what was redacted, and the proof records that it was.
Goods vs. work: The drinks are inventory, not labor. Pass-through goods sit apart from performer pay, so the receipt stays about work.

Small and additive; none of them change the v0.2 core. Developer docs

Restaurants and facilities

Already have cameras? Give them a job.

We're working with design partners who run dining rooms, stores and facilities.

The camera saw it first.

The camera saw the spill. The next frame shows it's gone.

It counts empty slots, not bottles. Bottles hide behind each other.

Held for a minute

One open task per zone

A cooldown after

Clips, not streams

Tasks, not people

Fair to whoever did it

A shadow isn't a spill

Glass doors only

The alert goes out first

Proposed additions this use case surfaced

Already have cameras? Give them a job.