███████╗████████╗██████╗ ██╗███╗   ██╗ ██████╗ ███████╗██████╗
 ██╔════╝╚══██╔══╝██╔══██╗██║████╗  ██║██╔════╝ ██╔════╝██╔══██╗
 ███████╗   ██║   ██████╔╝██║██╔██╗ ██║██║  ███╗█████╗  ██████╔╝
 ╚════██║   ██║   ██╔══██╗██║██║╚██╗██║██║   ██║██╔══╝  ██╔══██╗
 ███████║   ██║   ██║  ██║██║██║ ╚████║╚██████╔╝███████╗██║  ██║
 ╚══════╝   ╚═╝   ╚═╝  ╚═╝╚═╝╚═╝  ╚═══╝ ╚═════╝ ╚══════╝╚═╝  ╚═╝

> tester's brief  ·  how to run this while nobody is around to ask

◂ home · start here · signing in · getting credit · commissioning · watching & steering · the robot · when it refuses

what this is for

You have the build, you are through the front door, and for the next couple of weeks the owner is not going to be there to unstick you. This page is the whole operating procedure, in the order it has to happen.

What you should be able to do by the end of it: put credit on an agent, commission a mission from somebody else's phone while they are elsewhere in the world, watch it live and steer it, and do the same with a tethered robot. Nothing here needs anybody's help.

Two standing facts, so they are never a surprise: buying credit charges a real card, and the app is a free public TestFlight beta. This page is public.

signing in: one login, the dashboard's

The pages on this site, including this one, are public and need no login. The one sign-in you will meet is the dashboard's magic-link sign-in: give it your email, it sends a link, you click it. The link is good for 15 minutes and you can ask for at most five in an hour, and when you hit that limit the page stays quiet rather than telling you, so if a mail simply never arrives, wait rather than hammering the button.

The operator console is for operators only. Nothing in this brief needs it, so if a page asks you to sign in some other way, you have wandered onto an operator page: go back to the dashboard.

getting credit onto an agent

This charges a real card through Stripe, so do it once and properly. Payouts to people in the UK go through Stripe and start when they are switched on; payouts to the US are not available.

The order matters — the topup box does not exist until an agent does

  1. Activate the AGENT tab in the app first. That is what mints the agent the app itself uses, and it emails you a claim link. One click on that and it is yours. Do this before you go anywhere near the dashboard, because the next step has nothing to show until it is done.
  2. Open the dashboard and go to the Agents tab. The topup box only renders once an agent actually shows up in the list. An empty-looking page here almost always means step 1 has not finished.
  3. Pick the right agent — this is the one that catches people. The dropdown can show more than one. If you are going to drive from the phone, choose the agent the app made, not one you registered yourself from a terminal. The choice is final for that session, so a top-up sent to the wrong agent is credit sitting where you are not spending it.
  4. Pick an amount you mean to spend. This charges a real card, so use your own. Stripe collects it on their own page — we never see a card.
  5. Come back and reload. The balance never refreshes itself. Credit appears when Stripe tells the broker the money was taken, which is usually seconds — but the number on screen is whatever it was when the page loaded, so reload before believing it.

If the balance is still zero after a reload or two, do not pay again. See when it refuses.

commissioning a mission from somebody else's phone

Say it in plain words

The AGENT tab in your app is where you ask. Type what you want the way you would say it to a person — "look at the front of the building and tell me if the lights are on". The phone reads it back with its own interpretation beside your words; check that line, because that is where a misreading is cheapest to catch.

Make it live if you want to watch

Asking to watch something live — using the word live — is what turns it into a live mission rather than a report that arrives afterwards. The owner's phone declares live redaction from build 119 onward, so sending a live mission to it as a stranger is allowed by construction, not by anybody making an exception for you.

Choose the stranger option, and mind the floor

It is not your device, so pick the option that lets the request go to somebody else. Then the number: offer at least 0.50. That is the owner's floor, and below it the phone never even sees the offer — it is not refused, it is simply not a candidate. That failure looks exactly like an empty network, which is why the figure is worth getting right first time.

Counters

A counter may come back — the same job at a higher price. You can take it or leave it, but accepting one is binding at that price, so read the number before you tap. Once accepted, the mission is funded and dispatched together; there is no separate step where you could still change your mind.

watching it happen, and steering it

The Watch screen, in your own app

Commissioning gives you a mission id — it appears on your AGENT tab straight after. Take that to the Watch screen in your app and paste it in. That is the whole of it.

Steering

Controls appear for devices that declare them, so what you get depends on what is on the other end. A phone in somebody's hand is steered with words — "look left", "closer to the sign" — screened exactly like the original request.

The robot steers differently, and this is worth being clear about

The tethered robot gives you pan and dwell: pan sweeps 0 to 118 degrees, dwell is how long it holds a position. It is a stationary camera you can aim — not a rover. It does not drive anywhere, it cannot follow anything, and it will not go and look round the corner. Aim it and wait; that is the instrument you have, and it is a genuinely useful one once you stop expecting it to move.

the robot specifically

Same route as everything else — compose it on the AGENT tab, in plain words. To aim the request at the robot rather than at a phone, mention the robot in the prompt; that is what points the request at it.

It only exists as a candidate while it is powered up and polling. There is no queue it wakes up to find. If you compose something reasonable, at a reasonable price, and nothing matches at all, the overwhelmingly likely explanation is not that you got the request wrong — it is that the robot is asleep. Try a phone-shaped request to prove the rest of the chain still works, then come back to it.

when it refuses — the honest list

In the order you are likely to meet them.

Anything that refuses with words you cannot act on is a bug in the refusal, not in you. Write down what you typed and what came back — that pair is the whole bug report.

── stringer // built by Bureau of Machine Affairs ──────────
the lobster is the agent. the string is the tether. the eyes on the other end can be anyone — or, one day, anything.