One trailer. Three kinds of hands.

• Shared space, separate zones

  Humanoids and people don't work the same square metre. Zone H for humanoids, zone P for people, a lane for the AMRs. A person in zone H pauses every humanoid in it.

• Hazmat goes to people

  A hazmat-labelled carton is never a humanoid's to handle, whatever its size. The task says so as a rule, not a preference.

• Credit where it's due

  A mixed team needs each member's share on the record: for the person's pay, for everyone's reputation, and so a fleet can learn from its own cartons.

• A shortage isn't a failed unload

  If the carrier shipped 310, the crew still unloaded the trailer. The unload is accepted; the shortage is a finding that goes to the carrier claim, with the proof.

• Not a race against robots

  Shares record who did what. They don't rank a person against a humanoid on speed, and the warehouse's mandate can't use them that way.

• The manifest is fixed first

  The count is only as good as what it's counted against. The manifest's hash goes into the task at the start, so nobody can quietly edit it to match.

{
  "schema": "teleport.tap.physical-task",
  "version": "0.2.0",
  "title": "Unload trailer 4471 at dock 6 against manifest",
  "category": "UNLOAD",
  "requester": {
    "requesterType": "DEVICE",
    "principal": { "principalType": "ORGANIZATION" },
    "mandateId": "mdt_harborrow_dock_v3",
    "authentication": { "method": "DEVICE_ATTESTATION" }
  },
  "trigger": { "type": "SENSOR_EVENT", "sourceRef": "dock:6:door_closed_sealed" },
  "fulfillment": {
    "mode": "DIRECT",
    "designatedPerformers": [{ "fleetId": "crew_dock6_mixed", "actorType": "MULTI_ACTOR" }]
  },
  "environment": {
    "siteRef": "site:harbor_row_dc:dock_6",
    "referenceAssets": ["manifest:trl_4471"]
  },
  "actorRequirement": {
    "permittedActorTypes": ["HUMANOID", "HUMAN", "ROBOT"],
    "requiredCapabilities": [
      { "capability": "HANDLE.HAZMAT", "attributes": { "actorType": "HUMAN" } }
    ]
  },
  "completionConditions": [
    { "type": "COUNT", "id": "reconciled", "subjectRef": "manifest:trl_4471",
      "expression": "scanned + damaged == manifest", "verificationMethod": "DETERMINISTIC" },
    { "type": "LOCATION", "id": "pallets_slotted", "subjectRef": "pallet:*",
      "zoneRef": "site:harbor_row_dc:rack_b", "relation": "IN", "verificationMethod": "DETERMINISTIC" },
    { "type": "STATE", "id": "trailer_empty", "subjectRef": "trailer:4471",
      "property": "contents", "expected": "EMPTY", "verificationMethod": "PERCEPTION",
      "minimumEvidenceOrigin": "ATTESTED_DEVICE" }
  ],
  "safety": { "policyId": "dock-zones-h-p-lane-v1" },
  "findings": { "emit": ["SHORTAGE", "DAMAGE"], "affectsAcceptance": false },
  "economics": { "performerPayUsdCents": 0, "settlementAssets": ["FIAT"] },
  "popw": { "required": true, "assurancePolicyId": "VERIFIED", "proofTiming": "WORKFLOW" }
}

Proposed additions this use case surfaced

Team member shares

MULTI_ACTOR performers with each member's share: who did which part, a shareBps for pay, and a per-member commitment in the evidence. v0.2 has the team, not the split.

Separation zones

Zones per actor type in the safety policy, with the pause rule and who may restart. Checked from the robots' own safety logs.

Reference assets

The manifest committed to the task before work starts, so the count is against something that can't move.

Findings that don't block

A shortage or damage finding that goes to an outcome event (the carrier claim) while the unload itself is accepted.

Learning credit

Per-member evidence a robot fleet can pull for training: its own picks, its own misses, under the task's rights policy.

Example economics: no per-task pay in-house; the warehouse pays for verification and the proof. A shortage chargeback to the carrier carries the proof with it. Developer docs