# Integrator

Written on `main` for the other sessions to pull. The integrator updates this file by merging a branch. Lanes do not edit it.

The human types `continue`. The process is `docs/radio/README.md`. Read `docs/radio/michael.md` before this file. A line under `## Unread` is an order from Michael and comes first. When that inbox is empty, the current order in this file is `## Now`.

## How to read this

Read `docs/radio/README.md` first. In this file the order is `## Now`, then `## A running game stays up`, then `## The route is the gap`. Every other heading is history. Do not follow it.

When `## Now` names a slice that is already on `origin/main`, skip it and take the next unfinished line `## Now` names. `po.md` Next loses when it names a finished slice, a clear of one field, or a control the API cannot do yet.

grok-dev-1 owns the empire API files named in the radio README. grok-dev-2 owns `play.html` and `play.js`. Do not give both the same file. The integrator does not write the slice text unless Michael asks for an intervention.

A list marked Waiting is not work. Office slices, desk slices, fare cards, and map titles M1 to M32 are Waiting. Do not stop after one slice. Do not write that a heading is clear while `## Now` still names work.

The product brief is `docs/TAXI.md`. Do not invent a second fare table, a second map centre, or a fourth product. Do not edit `docs/TAXI.md`. Do not add `ready`. Leave September 2026 issues 1, 2, 3, 4, and 18 alone. Do not touch API pull request `reeve-branch`. Issues 22 and 29 stay `blocked`. Do not migrate `device_links` and do not write the live database.

Queue depth is in `docs/radio/README.md`. The sixteen slices in front of a dev are behaviours someone can watch, or the seam that makes the next slice smaller. A clear of one field is not one of those slices.

## Now

Master has unpaused the lanes. This section is the order when `docs/radio/michael.md` has no unread line. An unread line there is an order from Michael, including from the laptop, and it comes before the table below. Do not edit `michael.md`. The first line of the next radio note is `Michael <timestamp>: heard`. An older line that says to stop, or to write `morning order not at the front`, is stale. Do not write that phrase.

The only products are the tracker, the booking office, and the empire game in `docs/TAXI.md`. Issues 22 and 29 stay `blocked`. Do not migrate the live database. The open work is the taxi game on `play.html`.

`POST /v1/empire/buy` is deployed. #1178, #1184, #1185, #1186, #1135, #1226, #1227, #1228, #1230, #1235, and #1154 are on API `main` through `088658d`. A second buy does not add T12. A payment under 800000 is not a purchase. A tick does not spend 800000. Do not rebuild them. The bought-car trail, its colour, the latitude-then-longitude order, dropping points older than ten minutes, replacing the trail from each feed, and keeping the chip when the trail is drawn are on site `main`. The depot pin chip is `e025062`. Drawing T11 and not T12 is `ba4147e`. #1197, the 800000 price does not move the ten, is `73fda1e` and is deployed. Do not rebuild them. #1215, the buy control hides once the feed lists T11, is `b89ad62`. #1217, the spent line follows T11, is `09caf50`. #1216, the fare_in line does not show 800000, is `f1ec240`. Do not rebuild them. `cash_pence` is on API `main` as `834d811`, added with ALTER, default 0. Do not rebuild it. `fare_in` stays 0 until a completed job adds a tariff fare, and 800000 is not added to `fare_in`.

Master's review of the pace. Since 05:00 the site has taken hundreds of commits. Most of them are a radio note, or a clear of one field on one event. The live game moved much less than that record. A turn is product on `main` that Master can see on the next refresh, or the seam that makes the next slice smaller. A radio note is at most four lines after that product merge. A second pull request that only notes the slice is not the turn. A clear of one field is not the turn. An order that names a slice already on `main` is stale. Skip it.

Michael 2026-10-24T18:20:00Z is done. The empty-move cap is API `057e70d` and it is deployed. Do not rebuild it. An empty taxi stays within 2 miles of where it already is. A far empty leg with no passenger stops where the car is. A waiting person can still be collected from farther away. The loiter control is site `276f803`. It posts `/v1/empire/loiter` and draws the circle from `feed.loiter`. The office buttons stay. Do not rebuild it. Do not rebase `3b20fdb`. The carrying chip shows `cars[].journey` as site `6c8f42b`. Do not rebuild it. The waiting pin is site `feda805`. `cars[].journey` is API `5841c56`. `people[].journey` is API `919f4bc`. Do not rebuild them. Do not open a pull request until `## Now` names a new slice. Do not wipe. Do not build #1499, #1269, #1270, #1180, #1152, or #1231 to #1234. Do not wipe the database.

| Lane | State | Next slice |
|------|--------|------------|
| Product owner | The carrying chip is site `6c8f42b`. A `po.md` commit is not this turn. | Pull. Do not commit. Do not edit `po.md`. Do not open issues. Do not deploy. |
| grok-dev-1 | `cars[].journey` is API `5841c56`. The person's journey is API `919f4bc`. | Pull. Do not rebuild `5841c56` or `919f4bc`. Do not build #1499, #1269, #1270, #1180, #1152, or #1231 to #1234. Do not edit `play.html` or `play.js`. No radio file. Do not open a pull request until `## Now` names a new API slice. |
| grok-dev-2 | The carrying chip is site `6c8f42b`. The waiting pin is site `feda805`. | Pull. Do not rebuild `6c8f42b` or `feda805`. Do not edit the API. No radio file. Do not open a pull request until `## Now` names a new page slice. |

Do not redo a slice that is already on `main`. Do not start `## Reservoir` until a line from it is in your numbered list. The fullscreen map and the Start error text are already on `main` as `715b7c9`. Do not rebuild them.

## A running game stays up

Master's order. Existing players keep the fleet already stored for their account.

The rows live in SQLite: status, route, `leg_started`, passenger, trail, and `cash_pence`. A deploy must not delete them and must not send a moving car back to the depot. A new column is an ALTER with a default. There is no second account and no re-seed.

`/usr/local/bin/update` recreates the API container only when the pull changed `app/`, `main.py`, `requirements.txt`, `Dockerfile`, or `docker-entrypoint.sh`. A tests-only pull, or a change that is only the site, leaves the container running and prints `api image unchanged; container left running`, so the tick continues. An image change restarts the process for a few seconds and then resumes from the stored leg. An open browser keeps the page it already loaded. A refresh loads the new page.

People and the current job come next. Where a fare appears is the local region, not a ring around the depot. #1331, the place table, is API `6ecd1d3`. Do not rebuild that table. #1332 to #1336 are on main. Do not rebuild them. #1507 is API `9684ee3`. #1490 is API `c3aef25`. A collected person leaves when carrying begins. That is API `90138dc` and it is deployed. Do not rebuild them. #1498 is already on main. The closest person is API `36a8454`. The loiter patch is API `f6a83b6`. Do not rebuild them. The tariff is API `019f461`. Firm bookings are API `10e4e2a`. Do not rebuild them. The loiter control is site `276f803`. Other firms use the same engine and their own draws, and the feed carries their cars. #1325, the arrival runs the passenger trip, is API `5ef8324`. #1324, the stored job, is API `68fe833`. #1323, the empty move, is API `3d45ccf`. #1322, one free taxi, is API `195ad59`. #1320, a person waiting with no taxi, is API `2827e6b` and is deployed. #1321 is tests only, `9c2058d`.

The 1.2 mile pickup and the 3 mile drop on one bearing are not the journey. That ring is finished. Do not call out to the network for each fare. One table in the API names the places. The local hour in `Europe/London` picks the journey. Morning is #1332 `ca1819a`, day is #1333 `c045352`, evening is #1334 `8d74a75`, and night is #1335 `7fa222a`. #1336, the drop on another bearing, is `c782539`. Do not rebuild them. #1507 is API `9684ee3`. #1490 is API `c3aef25`. A collected person leaves when carrying begins. That is API `90138dc` and it is deployed. Do not rebuild them. #1498 is already on main. The closest person is API `36a8454`. The loiter patch is API `f6a83b6`. Do not rebuild them. The tariff is API `019f461`. Firm bookings are API `10e4e2a`. Do not rebuild them. The loiter control is site `276f803`. Other firms use the same engine and their own draws, and the feed carries their cars. #1325, the arrival runs the passenger trip, is API `5ef8324`. #1324, the stored job, is API `68fe833`. #1323, the empty move, is API `3d45ccf`. #1322, one free taxi, is API `195ad59`. #1320, a person waiting with no taxi, is API `2827e6b` and is deployed. #1321 is tests only, `9c2058d`.

Places, each at its real position, inside the circle, and not Berwick. Homes near the depot: Shiremoor, Backworth, Earsdon, West Monkseaton, Forest Hall, Killingworth, Benton. Work and shops: Cobalt, Silverlink, Royal Quays, Regent Centre, Four Lane Ends. Coast: Whitley Bay, Spanish City, Cullercoats, Tynemouth, North Shields. Town: Grey's Monument, Central Station, Haymarket, the Quayside, Osborne Road. Hospitals: North Tyneside General at Rake Lane, the RVI, the Freeman. Newcastle Airport stays a small share at every hour.

Journeys that should come up. Morning, about 07:00 to 09:30: those homes toward Cobalt, Rake Lane, Regent Centre, and town. Day, about 09:30 to 16:30: Silverlink, Royal Quays, the coast, the hospitals, Monument, and Central Station. Evening, about 16:30 to 19:30: Cobalt and town back to the homes and the coast. Night, about 19:30 to 01:00: the Quayside, Osborne Road, Tynemouth, and Whitley Bay back to the homes. The quiet hours make fewer fares. Airport to town or the coast stays uncommon. A drop is the other end of that journey. Two ends do not share one bearing from the depot.

A person appears at the pickup and waits with no taxi allocated. One free taxi is allocated. The person stays on the map until that taxi arrives. The car then does the existing passenger trip. The North Tyneside tariff prices the miles of that journey. It stays the only fare table. 800000 is not a fare. A tick does not add a car because a person appeared. The opening ten stay the opening ten. A car already on a leg is not moved to a new place by this change.

Each taxi has one current job, stored on the car and shown on the chip and in the list: waiting, travelling to a better spot, collecting a passenger, carrying a passenger, or returning to the depot. Collecting is the drive to the person. Carrying is the paid trip. Waiting is the depot hold. Travelling to a better spot is an empty move toward where this hour is busy, with no passenger and no fare, and it does not replace a leg already started. The feed already has `at_depot`, `to_passenger`, `with_passenger`, and `returning`. Keep those rows working. The page draws the person at the feed latitude and longitude.

Master's objective for the page. Master can see where each taxi is travelling. A click on a taxi shows where that taxi is going. The trail on the map is where the car has been. The stored route is where it is going. The page draws the rest of that route ahead of the car, and the chip and the list name the place at the end of the leg. The place name comes from the feed. The player can follow one taxi, and the camera stays on it as it moves. Choosing another taxi follows that one. There is a way to stop following, so the rest of the circle can still be seen. Do not add a place list in `play.js`. A car already on a leg keeps that route. Do not invent a second route.

The page grows controls the player can use. Start, sign out, and buying a car stay. Each new control does one real thing, and the product owner names that thing in its own slice. A control that does nothing is not a slice. Do not put the money column back beside the map.

More fares come from the same place table and the same `Europe/London` hour. A busy hour has more people waiting. A quiet hour stays quieter. The North Tyneside tariff stays the only fare table. 800000 is not a fare. Do not call the network for each fare.

Behaviour gets richer after the empty move. A taxi waits, moves toward where this hour is busy, collects, carries, or returns. It does not replace a leg already started. A new status is added to `STATUSES` in the same change, because an unknown status is put back to `at_depot`. A new fare does not add an eleventh car. The opening ten stay.

Master's order. The taxis hunt independently. The ten cars are created on one depot point, and an idle taxi returns there, so they stack. That stack is not the behaviour. An idle taxi does not sit on the same point as another idle taxi. Each one moves toward where the next fare is likely, from the same place table and the same `Europe/London` hour, and two taxis do not cover the same patch. A car that is collecting, carrying, or returning keeps that leg. A quiet spell has nobody waiting. A busy spell has more people waiting than there are free taxis, and the people who are not allocated stay on the map. Do not add a car because the people outnumber the taxis. Do not offset the markers in `play.js` to hide one shared position. The positions come from the feed.

Master's order. The point of the game is to be where the next fare will be, before the other firms. Success is predicting the gap between the cars on the ground and the people who want a taxi.

Journeys come in more than one kind. A commute, a night out, a hospital run, an airport run, a trip to the coast, and a short local hop are all ordinary. The `Europe/London` hour still picks which kinds are common. The North Tyneside tariff still prices the miles. It stays the only fare table. 800000 is not a fare. Do not call the network for each person.

People appear across the whole 50 mile circle, not only on the first 26 names. They are thicker where people live, around the Tyneside and Wearside towns, and thin in open country. A journey is one a person in this region would actually make. A person does not appear in the sea. The circle stays centred on Grey's Monument. The opening depot stays Shiremoor.

The player can open another depot, and can set a patch where that firm's taxis loiter for fares. Each of those is its own control and its own slice. The product owner names the price in the depot slice. 800000 stays the price of a car. A depot is not a car. The opening ten stay. A new depot does not by itself add a car.

Other taxi companies work the same circle. They take fares the player's cars are not covering. The player can see those cars. They belong to this game. They are not a fourth product. Cash still comes from the fares that account's own cars complete.

Do not put any of that inside #1324, and do not put it inside the click or the camera follow. The product owner numbers it behind those.

Master's order. The simulation is an engine, not a pile of hand-written cases. The tick that already advances the account is that engine. On a tick it draws the next person, the journey, and where an idle taxi goes. The draw uses randomness. The weights are where people live inside the 50 mile circle, the `Europe/London` hour, and the journeys people in this region actually make. A commute, a night out, a hospital run, an airport run, a trip to the coast, and a short hop are examples the draw can produce. They are not six functions, and they are not six new place lists.

Do not add another hour band by naming places. Do not add a slice whose only change is one town or one scripted route. #1332 to #1336 stay as they are. Do not rebuild them, and do not extend them by hand. A new kind of journey is a weight.

Each taxi draws for itself, so the cars do not stack and do not share one scripted path. A car already on a leg keeps that leg. Other firms use the same engine and their own draws. A depot or a loiter patch is an input the player sets, and the engine already knows what to do with it. The opening depot stays Shiremoor. There is no second runtime, no second process, and no new framework. The account rows stay in SQLite. Do not wipe the database. Do not call the network for each draw.

Master's order. One fare belongs to one taxi. That is API `9684ee3`. One taxi claims one person and collects that person from where the taxi already is. The other taxis hunt or take a break. Several people are drawn for a spell. An idle taxi with nobody claimed draws a strategic waiting spot. Sitting at the depot is the break. When carrying begins, that person leaves and the same draw adds another while the spell is short. That is API `90138dc`. The other firms are already on main. The loiter control is site `276f803`. Do not rebuild it.

Master's order. Demand decides the break. When few people are waiting beside the free taxis, an idle taxi is likely to drive back to its own depot and clock off for a few minutes. When the people outnumber the free taxis, that taxi is likely to stay out and hunt. A busy spell can still send one car home. A quiet spell can still leave one car out. The feed job is `on break` while it sits. The even-numbered cars parked until 01:00 are not this rule. A depot wins the ground near it, because the same draw prefers the nearer depot's free car. Shiremoor keeps that advantage to its north. A later depot, including a competitor's depot, wins the ground around itself. There is no second AI and no town list per depot. The player watches cars go home, sit, and come out again, and watches different depots cover different ground.

#1325 is API `5ef8324`. #1507 is API `9684ee3`. #1490 is API `c3aef25`. A collected person leaves when carrying begins, API `90138dc`, deployed. Do not rebuild them. #1498 is already on main. The closest person is API `36a8454`. The loiter patch is API `f6a83b6`. Do not rebuild them. The tariff is API `019f461`. Firm bookings are API `10e4e2a`. Do not rebuild them. The loiter control is site `276f803`. The depot purchase stays parked. Firm bookings are API `10e4e2a`. The loiter control is site `276f803`. Do not number one issue per town. #1508 is site `3923f93`. The job string on the chip is site `be06165`. Do not rebuild it. The firms and the time labels are on `main`. The loiter control is site `276f803`. The click is site `390bee0`.

Master's order. Build for the next change, not only for this one. The rate of what Master can see should speed up. A slice that only clears a field, or only repeats a hand-written case, slows that rate down. A slice either changes the running game on the next refresh, or it adds the seam that makes the following slice smaller. The seam is a seeded draw, one function for a rule, and the feed carrying the choice the page shows. Tests live beside the engine. There is no second app and no dev-only page. A new journey, a new firm, or a new depot is then a weight or an input. If a slice is getting larger than the one before it, the seam is missing. Build the seam. Do not wipe the database to make a test easier.

The product owner numbers those outcomes and puts them at the front in this turn. #1448 is site `db799e4`. The click is site `390bee0`. #1508 is site `3923f93`. The field clears stay parked. #1325 is API `5ef8324`. The engine's draw is API `9684ee3`, in front of #1263 and #1180. #1324 is API `68fe833`. Do not number a hand-written journey for each town. The other firms, the depot, and the loiter patch are inputs and users of that same draw. They stay in front of the field clears. #1323 is API `3d45ccf`. grok-dev-1 does not rebuild #1498. `people[].journey` is API `919f4bc`. grok-dev-2 shows it on the waiting pin. Do not invent a journey. Do not rebuild site `3b7aec6`. A turn of only field clears, or only a radio note, is not this order. Do not add slices this turn. A po.md commit is not this turn.

Do not invent a second fare table or a fourth product. The opening depot stays Shiremoor until the numbered depot slice. Do not show 2860, 1130, or 1240.

## The route is the gap

The route is no longer the gap. The place table is API `6ecd1d3`. Morning is API `ca1819a`, day is `c045352`, evening is `8d74a75`, and night is `7fa222a`. #1336 is API `c782539`. #1325, the arrival runs the passenger trip, is API `5ef8324`. #1507 is API `9684ee3`. #1490 is API `c3aef25`. A collected person leaves when carrying begins. That is API `90138dc` and it is deployed. Do not rebuild them. #1498 is already on main. The closest person is API `36a8454`. The loiter patch is API `f6a83b6`. Do not rebuild them. The tariff is API `019f461`. Firm bookings are API `10e4e2a`. Do not rebuild them. The loiter control is site `276f803`. Other firms use the same engine and their own draws, and the feed carries their cars. #1324 is API `68fe833`. #1323 is API `3d45ccf`. #1508, the camera follow, is site `3923f93`. The click is site `390bee0`. The job string on the chip is site `be06165`. The loiter control is site `276f803`. The demand break is inside `9684ee3`. A collected person leaves in `90138dc`. #1498 is on main. A bought depot stays parked. The loiter control is site `276f803`. Do not rebuild it. #1448 is site `db799e4`. Do not send grok-dev-2 down #1450. Journeys, density, idle taxis, and the other firms come out of that draw. Do not hand-write the next journey. The draw takes a seed so a test can replay who appeared and where an idle taxi went. The live tick still varies. A slice Master cannot see, and that does not make the next slice smaller, is not this order. The camera follow is on main. The waiting-name list is site `3b7aec6`. Do not rebuild it. The page does not invent a journey. Do not redo the click. Do not redo #1323 or #1448. Do not wipe the database.

The integrator deploys this PC when those files change. Lanes do not deploy.

## Public site

`https://hackathon.tyneside.software` is GitHub Pages. `play.html` loads `config.js` before `play.js`. On that host, `config.js` calls `https://keyword-chamber-stands-graphics.trycloudflare.com`, which tunnels to the box API. Do not remove that script tag. Do not point the Pages host at `http://100.65.94.5:8080`. The box and localhost keep that HTTP address.

## Last order before morning

Superseded by `## Now`. Do not stop. Do not write `morning order not at the front`.

This is the last note. The continues already queued are the whole of the work until morning. Do not wait for another integrator note.

By morning, http://100.65.94.5/play.html lets Master watch, then grow the empire.

1. The map is the page. Ten taxis are moving in real seconds. The in-game money is changing. One Start is enough when there is no saved account: `POST /register`, then `POST /login`. The token stays `hackathon-empire-token`.
2. A control spends 800000 pence and one more car joins that account and appears on the map. The opening ten stay. The price stays 800000. No second fare table, fuel rate, or standing charge.
3. `test_ten_car_feed_does_not_grow_an_eleventh_sign` stays true. A tick nobody paid for does not add a car. The purchase is the only way to add one.
4. No phone list, no bus toggle, no Place stops. Do not show 2860, 1130, or 1240.

Product owner: one commit, at the front of both queues, those two outcomes. Park the lock list. grok-dev-1 owns the purchase and the feed. grok-dev-2 owns the watch and the control. Do not give both the same file. Do not edit the dashboard tonight.

Devs: the remaining continues build that front, and nothing else. A lock at the front means stop, not another lock. Output is the product pull request.

The integrator PC deploys when `play.html`, `play.js`, `config.js`, or the API `app/` tree changes. Lanes do not deploy. Merge to `origin/main`.

## This stretch

Master has queued a long run of continues. This order stays until Master gives a different one. Do not wait for a new integrator note between turns. An issue number written here goes stale. The list that matters is `docs/radio/po.md`, minus anything already on `main`.

The morning goal comes first. Master will open http://100.65.94.5/play.html and watch the empire before playing it.

The first feeling is the watch. The map is the page. Ten taxis are already working, moving in real seconds, and the in-game money is changing. One small Start is enough when there is no saved account: create the account, or sign in, with the existing `POST /register` and `POST /login`. Then the map takes over. Do not leave an empty map behind a hidden token. Do not put a wall of lock sentences in front of the taxis. Sentences a test still needs can stay, out of the way of the map.

Then Master can play. A control spends 800000 pence of the in-game money and one more car joins that account's fleet. The starting ten stay. The price stays 800000. Do not invent a second fare table, a second standing charge, or a second fuel rate. The feed the page already polls grows by that car, and the new chip appears on the map. grok-dev-1 owns the purchase and the feed. grok-dev-2 owns the watch and the control. Do not give both the same file.

Finish the slice you are already in. Then these morning slices are the queue. A lock that does not change the moving map or the purchase waits in the reservoir. The product owner writes that order in one `po.md` commit. The devs build it. The integrator does not name the issue titles.

The integrator deploys from this PC with `scripts/deploy-if-product.ps1` when `play.html`, `play.js`, `config.js`, or the API `app/` tree has changed. Lanes do not deploy. Merge to `origin/main`. A radio-only commit still does not deploy. The dashboard waits until the morning page can be watched and a car can be bought.

The circle, the Shiremoor depot, and the rest of the game rules stay as they are. There is no phone list, no bus toggle, and no Place stops.

Output is product code. Since 05:00 on 24 Oct 2026 the site had about 30 commits that changed `play.html`, `play.js`, or `app/`, and about 192 commits that changed only `docs/radio/po.md`. grok-dev-1 had about 20 radio notes and was merging API slices. grok-dev-2 had about 28 radio notes. A turn with more radio commits than product commits has not produced enough software.

Devs: one slice is still one product pull request. After it merges, the radio file gets at most four lines: the issue, the commit, what it did, and the next issue. Then build the next slice. Do not open a second pull request that only points at the next slice. Do not batch two slices into one pull request. If your heading still has unfinished issues, the next action is code.

Product owner: several new slices go in one `po.md` commit. One or two of those commits can fill a turn. Do not merge a commit whose only text is `Record issue N`. The devs read the list. They do not need a commit per line. When both queues have 16 unfinished slices and the reservoir has 24, stop recording and leave the turn for one dashboard change.

Unfinished means the work is not already on `main`. A heading that still shows 16 lines is short if many of those lines are done. Keep 16 unfinished in front of each dev, and 24 in the reservoir. For this stretch the new slices and the reservoir are the taxi game, not the office waiting list, not map titles M1 to M32, and not issues #699 through #786. Those stay paused. When you move a reservoir line into a dev queue, write a new reservoir line so the 24 does not shrink.

If a dev writes `queue empty`, the supply failed. The next product-owner turn starts by refilling that queue. Say that the dev turn stopped early. Leave enough slices for about 30 minutes. A dev who stopped after one or two slices also had a short turn. Say so.

Supply comes before the dashboard. If the refill takes the whole 30 minutes, do the dashboard on the next turn. If the queues are already deep enough, still land one dashboard change in the turn. The devs do not edit `scripts/agents_dashboard.py`.

Dashboard, one change a turn, in this order. Skip a step that is already true:

1. GitHub against the box for the three products. That comparison has started. Keep it true.
2. Show unfinished slices separately from lines already on `main`.
3. Show each lane's last radio time, and whether that turn was about 30 minutes or short.
4. Keep the code line-count graph. Do not add a second graph of the same commits.
5. Then the next gap in the strategy picture. One change. Do not rewrite the whole page in one turn.

Do not commit `agents.html`. Do not put a password in the script. A dashboard commit is not a deploy. These turns do not deploy the box. Merge to `main` only. The integrator deploys when Master is back.

## Game page

Master's order. The product owner designs the slices. The integrator does not.

The taxi game is `play.html`. It is not `app/`. `app/` keeps phones, buses, and waypoints. `play.html` shows the game only: the map, the ten taxis, and the in-game money. No phone list, no bus toggle, no Place stops. Same centre `54.9783, -1.6178`, same 50-mile circle, same Shiremoor depot `55.0367, -1.5075`.

An account still starts the fleet, and the fleet still runs on the box when the browser is closed. `ensure_game` creates T1 to T10 at the depot, not three. T1 stays `#f5b942`, T2 `#38bdf8`, T3 `#4ade80`. The product owner names seven more colours in the slices. Cars are not devices. One real second is one game second. OSRM duration is the journey. If OSRM does not answer, the car moves straight at 30 mph and the page says `OSRM unavailable`.

The page shows in-game money as it changes: fares earned, and the game costs already fixed (driver share, fuel at 20 pence a mile, standing). Integer pence. The North Tyneside tariff already in `docs/TAXI.md` is the fare. Do not invent a second fare table. Do not show the company totals 2860, 1130, or 1240 on `play.html`. Do not show game costs on `office.html`. `game.html` stays the simulated booking desk. Do not turn it into this map.

The product owner writes at least 16 unfinished slices for each dev, and 24 in the reservoir, all for this game page. Name the files. One dev should own `play.html` and its script. The other should own the API fleet of 10 and the money figures on `GET /v1/empire`. Do not give both the same file. Say in the radio that the old `app/` queue is paused. Leave `## Next for me`.

`po.md` is that queue now. Keep writing it. Issues #699 through #786 stay paused. Do not go back to three cars, `app/map.js`, or the office waiting list. When a dev has finished slices, the unfinished count falls. Top it back up to 16, and keep 24 in the reservoir. That topping-up is your work. Do not wait to be asked.

The dashboard is also your work. `scripts/agents_dashboard.py` builds the page Master reads at `http://127.0.0.1:5510/`. Keep improving it every turn: the three products, what is on GitHub against what is on the box, how full the queues are, and graphs of code line counts. One dashboard change, then the radio, then the next, in the same turn as the queues. Do not drop the queues to only edit the dashboard. Do not commit `agents.html`. Do not put a password in the script. The devs do not edit that file. The integrator restarts the local page after the script is on `main`. A dashboard commit is not a deploy.

The empire is a real-time game. One real second is one game second. There is no faster clock. When OSRM returns a duration, that duration is the journey. The car moves along the route as those seconds pass. When OSRM does not answer, the car moves in a straight line at 30 miles per hour, the built-up speed limit, and the page says `OSRM unavailable`. The account fleet does not use the old 20-second offer rule. A car finishes, waits four seconds at the depot, then takes the next fare. Each trip is inside the circle, not Berwick. The checked day stays −1120. The company desk is unchanged.

GitHub Pages publishes https://hackathon.tyneside.software from `main` on every push. The home page and `progress.html` must describe that `main`. The box site last checked was `ff1e142`. `/health` was `0.1.27`. `check.ps1` printed `CHECK-OK`. The board was 50 cards. Map clicks do not add a waypoint unless Place stops is on. This note is orders only. It is not a deploy.

## Account fleet

This is the objective. It replaces the fare-card queue and the map slices M6 to M32. Re-read this section from `origin/main` between slices. Write your own radio after each slice. The product owner opens the issue. The dev builds it. The integrator deploys. Nobody deploys but the integrator.

A person creates a username and password. The fleet then runs on the Linux box all the time, one real second per game second, even when the browser is closed. A1 to A32 started that fleet with three cars. Those slices are done. Do not rebuild them. The next fleet is ten cars on `play.html`. Read `## Game page`. The three-taxi sentences below are the history of A1 to A32, not the next queue. Each account has its own cars, fares, and trails. Game rows are never devices.

Each car follows a route. Every 10 seconds it checks in. The position is calculated from how far it should be along that route. The map draws a fading trail from those check-ins, the same idea as the bus trails, and the car marker glides along the route between check-ins. A fare that is waiting has a marker until that taxi arrives. Hide taxis hides only that account's cars. Phones and buses stay. The sample car stays, and it is not T1.

Play on `http://100.65.94.5/app/`. The HTTPS site cannot call the HTTP API. Password at least 8 characters. Username at least 3. Use the existing `POST /register` and `POST /login`. Do not invent a second user table. Do not wipe SQLite. Do not migrate `device_links`. Issues 22 and 29 stay blocked. Do not add `ready`.

`GET /v1/empire` requires `Authorization: Bearer`. It returns only that account. `server_now` is unix seconds. `check_s` is 10. `trail_s` is 600. Each car has `sign`, `colour`, `status`, `passenger`, `lat`, `lng`, `route` as `[lat, lng]` pairs, `duration_s`, `leg_started`, `osrm`, and `trail` as `[lng, lat, unix]` triples like the buses. `fares` lists waiting pickups only, with `name`, `lat`, `lng`, and `sign`. Colours are T1 `#f5b942`, T2 `#38bdf8`, T3 `#4ade80`. Depot is `55.0367, -1.5075`. Status is `at_depot`, `to_passenger`, `with_passenger`, or `returning`. Four seconds at the depot, then the next fare. OSRM driving, or a straight line at 30 mph when OSRM does not answer, and then `osrm` is false. Names cycle Mina, Owen, Priya, Jack, Helen, Tom. The username shifts the bearing so two accounts do not drive the same streets.

### Product owner titles

One issue, then a radio note, then the next. Body is the matching slice. If the exact title exists, comment and do not open a second. No `ready`.

Titles 1 to 16 and 33 to 48: label `repo:api` only. Titles 20 to 32 and 49 to 64: label `repo:site` only. Skip titles 17, 18, and 19. Those slices are already on `main`: `15d66fb`, `d41eed7`, and `c0c2f02`. Do not open them again. Titles 1 to 64 except those three are already opened. The next slices are yours to write in `docs/radio/po.md`. Do not wait for the integrator to name them.

1. `Empire tables are not devices`
2. `Register starts the fleet on the box`
3. `The box ticks every account every second`
4. `A car checks in every ten seconds`
5. `OSRM or a straight line at 30 mph`
6. `Depot pause then the next fare`
7. `Waiting fare has a marker position`
8. `Empire feed is one account`
9. `Two accounts do not share a fleet`
10. `A tick does not write a device`
11. `Trails keep ten minutes`
12. `Health version is 0.1.27`
13. `Accounts drive different streets`
14. `Passenger names cycle`
15. `A car at the depot still checks in`
16. `One car failing does not stop the others`
17. `The map asks for an account first`
18. `Create account and sign in on the map`
19. `The token is kept in the browser`
20. `The map polls the account fleet`
21. `The car glides along the server route`
22. `The taxi trail fades like a bus`
23. `Waiting fares are markers`
24. `Hide taxis leaves phones and buses`
25. `A taxi tooltip does not say device`
26. `A click on a fare does not add a waypoint`
27. `The sample car is not one of the account taxis`
28. `The status says the fleet runs on the box`
29. `A rejected token shows the account form`
30. `The public HTTPS page points at the box`
31. `Panning does not restart the fleet`
32. `Sign out clears the cars`
33. `The three cars leave a few seconds apart`
34. `Trips stay inland of the North Sea`
35. `Pickup and drop-off stay inside the circle`
36. `The clock does not start during tests`
37. `The fleet survives a new session`
38. `An old account starts on the feed`
39. `Car colours are on the feed`
40. `Position is the fraction of the route`
41. `One account has one game row`
42. `A check-in writes one trail point`
43. `Three cars can be on different legs`
44. `The feed names the clock and the trail`
45. `The feed says when OSRM missed`
46. `A leaving leg starts at the depot`
47. `Car status is one of four words`
48. `Empire tests pass before the merge`
49. `Signed in hides the account form`
50. `A failed sign-in shows the error`
51. `The map does not invent cars while it loads`
52. `The trail fades with age`
53. `A car at the depot sits on the depot`
54. `Chip colours come from the feed`
55. `The waiting chip says the name`
56. `A quiet feed keeps the last cars`
57. `Sign out is not hide taxis`
58. `The account form leaves the sample car`
59. `Hide taxis keeps the token`
60. `A late poll does not jump the car back`
61. `The empire block hides both ledgers`
62. `The status says the fleet is loading`
63. `The map files are cache-busted`
64. `Phones and buses stay for a signed-in player`

### grok-dev-1 — API slices A1 to A32

Checkout `C:\Users\MichaelThomson\source\lanes\grok-dev-1\hackathon-api`. Branch `lane/grok-dev-1/<slug>` from `origin/main`. Squash-merge into `Tyneside-Software/hackathon-api`. Do not run `box.ps1`.

You may add `app/empire.py`, `tests/test_empire.py`, `app/routers/empire.py`, and the smallest hooks in `app/models.py`, `app/main.py`, `app/routers/auth.py`, and `app/config.py`. Tables are `empire_games` and `empire_cars` only. No `device_id`. `create_all` only. Do not wipe the live database. Do not change `devices`, `location_pings`, or `device_links`. Do not edit the site map.

A1. Add `empire_games` and `empire_cars`. No `device_id`. A test reads the columns and fails if `device_id` is one of them.
A2. `POST /register` still creates the user. After that row is stored, `ensure_game` creates T1, T2, and T3 at the depot for that username.
A3. A background tick in the API process advances every account once a second. One real second is one game second. It keeps going when no browser is open.
A4. Each car checks in every 10 seconds. The lat and lng come from the route and the leg clock. A test shows no check-in at 9 seconds and a check-in at 10.
A5. A leg asks OSRM. If OSRM does not answer, the car moves in a straight line at 30 mph and `osrm` is false. The test does not call the network.
A6. After the drop-off the car is `returning` until the depot, then `at_depot`. Four seconds later the next fare starts.
A7. While status is `to_passenger`, the feed includes that fare's name and pickup. After arrival the fare is gone.
A8. `GET /v1/empire` with the bearer token returns only that account. `401` with no token.
A9. A test with two usernames shows that one's feed does not contain the other's fare coordinates.
A10. A test runs a tick and shows `devices`, `location_pings`, and `device_links` gained no rows.
A11. Pings older than 600 seconds are dropped. Trail points are `[lng, lat, unix]`.
A12. `VERSION` in `app/config.py` becomes `0.1.27`. `/health` returns that version. Do not change the board.
A13. The bearing is shifted by the username. Two accounts do not get the same pickup point.
A14. Names cycle Mina, Owen, Priya, Jack, Helen, Tom.
A15. A car at the depot still checks in, so it has a position.
A16. If one car raises, the tick logs it and still advances the other accounts. `tests/test_empire.py` passes before the merge.
A17. The three cars do not start the first fare on the same second. Stagger the first departures by about 7 seconds.
A18. Bearings used for a trip stay inside 160 to 300 inclusive, so the trip does not go into the North Sea. A username whose raw bearing falls outside that range is clamped. The test does not call the network.
A19. The pickup is about 1.2 miles from the depot. The drop-off is further along the inland bearing. Both points are inside the 50-mile circle and are not Berwick.
A20. The clock starts in the FastAPI lifespan and stops on shutdown. Importing the app inside `tests/test_empire.py` does not start the clock and does not open the live database file.
A21. Create a game, close that session, open a new session, and T1, T2, and T3 are still there for that username. The rows are in SQLite, so the game survives a process restart. Do not wipe the live database.
A22. `GET /v1/empire` for a user who has no empire row yet calls `ensure_game` and then returns the three cars. No token is still 401.
A23. The feed colours are T1 `#f5b942`, T2 `#38bdf8`, and T3 `#4ade80`.
A24. The position is the fraction of the route by elapsed time over `duration_s`. At 0 the car is on the first point. At `duration_s` it is on the last point. Halfway it is halfway along the points. The test uses a known route and does not call OSRM.
A25. Many ticks still leave one `empire_games` row for that username.
A26. A check-in appends one trail point. A one-second tick that is not a check-in does not append a point. Points stay `[lng, lat, unix]`.
A27. T1, T2, and T3 of one account can be on three different statuses at the same time.
A28. The feed includes `ok`, `username`, `server_now`, `check_s`, `trail_s`, `osrm_unavailable`, `cars`, and `fares`. `check_s` is 10. `trail_s` is 600. `server_now` is the server clock.
A29. `osrm_unavailable` is true when a current leg did not get an OSRM route. It is false when every current leg did.
A30. Each car's `route` is `[lat, lng]` pairs. A leg that leaves the depot starts at `55.0367, -1.5075`.
A31. Status is only `at_depot`, `to_passenger`, `with_passenger`, or `returning`.
A32. `tests/test_empire.py` passes for A1 to A31 before the merge. No network. No live database file.

A1 to A32 are on `main`. Skip them. A1 is `82363dc`. A2 is `64460c3`. A3 to A32 are `1a22a90`. Do not rebuild them. The next API slices are written by the product owner in `docs/radio/po.md`, not here.

### grok-dev-2 — map slices U1 to U32

Checkout `C:\Users\MichaelThomson\source\lanes\grok-dev-2\hackathon-site`. You may edit `app/map.js`, `app/map.css`, and the Empire block in `app/index.html`. Do not edit the API. Do not bring back a browser-only fleet as the source of truth. The sample car button stays.

U1 is on `main` at `15d66fb`. Skip it. The account form is the first empire control, and the page does not start T1, T2, and T3 by itself.
U2 is on `main` at `d41eed7`. Skip it. The form has username, password, Create account, and Sign in. The hint says the password is at least 8 characters.
U3 is on `main` at `c0c2f02`. Skip it. Create account calls `POST /register`, then `POST /login`. The token is stored in `localStorage` under `hackathon-empire-token`.
U4 is on `main` at `8b9910c`. Skip it. Sign in calls `POST /login`. Sign out removes the token and the cars, trails, and fare markers.
U5 is on `main` at `3cbde90`. Skip it. While signed in, `GET /v1/empire` is called with `Authorization: Bearer` about every 2 seconds.
U6. The marker glides with `route`, `leg_started`, `duration_s`, and `server_now`. It does not jump only when a poll arrives.
U7. A fading trail is drawn from `trail` in that car's colour, the same idea as the bus trail. Hide taxis removes it.
U8. Each waiting fare is a marker with the name and the word `waiting`. It leaves when the feed drops it.
U9. The tooltip says collecting, the passenger name while aboard, returning, or `at depot`. It does not say `device`.
U10. Hide taxis removes only this account's chips, trails, and fare markers. Phones and buses stay.
U11. A click on a taxi or a fare marker does not add a waypoint.
U12. The sample car still has its own button. It is not T1.
U13. The status line says the fleet runs on the box. If `osrm_unavailable` is true, it also says `OSRM unavailable`.
U14. A `401` clears the token and shows the form again.
U15. On `https://hackathon.tyneside.software/app/` the empire status tells the person to open `http://100.65.94.5/app/` because that page cannot call the API.
U16. After the player pans or zooms, the map does not jump back.
U17. Once signed in, the form is hidden and the status line shows the username.
U18. A failed create or sign-in shows the error from the API and does not store a token.
U19. Before the first successful poll, the page does not draw stand-in cars.
U20. Each trail point fades with its age and is dropped after `trail_s`.
U21. A car `at_depot` sits on the Shiremoor depot. The tooltip says `at depot`.
U22. The chip colour is the feed colour. T1 is `#f5b942`, T2 is `#38bdf8`, and T3 is `#4ade80`.
U23. A waiting fare uses the lilac chip. The text is the passenger name plus `waiting`.
U24. A poll that fails for a reason other than 401 leaves the last cars on the map. The status says the feed is quiet.
U25. Sign out is a button in the empire block. It is not the Hide taxis button. It removes the token, the cars, the trails, and the fare markers, and shows the form.
U26. The account form does not cover the sample-car button. The sample car stays off until that button is pressed.
U27. Hide taxis does not remove the token. Sign out does not change the Hide taxis control.
U28. The glide uses `server_now` against the browser clock, so a late poll does not jump the car backwards.
U29. The empire block does not show 2860, 1130, 1240, −1120, or 800000.
U30. When the token is present and `cars` has not arrived, the status says the fleet is loading.
U31. The cache query on `map.js` and `map.css` changes with this client, so a refresh loads the new files.
U32. Phones and buses still load for a signed-in player. Do not stop while U6 to U32 remain.

## Product owner

You may commit and squash-merge a branch that changes `docs/radio/po.md`. You may also commit and squash-merge a branch that changes `scripts/agents_dashboard.py`. That script is the dashboard. Keep improving it: the three products, GitHub against the box, queue depth, and code line-count graphs. Do not commit `agents.html`. Do not put a password in the script. The devs do not edit that file. A dashboard commit is not a deploy. Do not edit any other product file.

Done, already on `main`: issues 30, 31, 32, 33, and 34 are open. Issues 23 and 24 are commented. Issues 22, 29, and 34 stay `blocked`. Do not open those titles again.

You own short-term priority. The integrator directs. You design and you communicate, and you should be busy for the whole continue. A turn is about 30 minutes. One issue is not a turn.

On this continue, read `## Game page` and `## Now`. You do not wait for Master. Master talks to the integrator. You own the short-term plan inside that order. The order is still the ten-taxi game on `play.html`, and the dashboard. Issues #699 through #786 stay paused. Do not open more of them.

You feed grok-dev-1, grok-dev-2, and yourself. Read `## This stretch`. Unfinished means not already on `main`. If either dev is under 16 unfinished slices, or the reservoir is under 24, filling them is the first part of the turn. Design the next `play.html` slices, open the issue, merge the radio, and write the next. If the queues are already deep enough, or once they are, improve `scripts/agents_dashboard.py` once and merge that too. Read the dev radios and the commit times. If a dev stopped after a slice or two, or wrote `queue empty`, say the turn was short and leave enough slices for half an hour. Leave `## Next for me` with at least four jobs, and one of them is the next dashboard improvement. If that heading would be empty, you are finishing early.

Then spend the turn designing the 10-car game on `play.html`. Write `### grok-dev-1`, `### grok-dev-2`, and `## Reservoir` again, all for that game. At least 16 unfinished slices for each dev, and 24 in the reservoir. One dev owns the API fleet of 10 and the money on `GET /v1/empire`. The other owns `play.html` and its script. Name the next slice, the files, and that the turn runs about 30 minutes. Put several new issues in one radio commit. Do not merge once per issue. Do not stop while a dev is under 16 unfinished slices.

Leave yourself work. End the radio with `## Next for me` and at least four jobs you will do on the next continue: check the dev turn lengths, top up whichever queue is short, write the next slices, and tell the devs. If `## Next for me` would be empty, you are finishing early. Write more before you stop.

Titles 1 to 64 are already opened except 17, 18, and 19. Do not reopen them. Do not add `ready`. Do not write `queue low`. Map titles M1 to M32 and slices 115 to 134 wait. Do not open them. The integrator will not write these slices for you. Map clicks on the box do not add a waypoint unless Place stops is on. That shipped in `ff1e142`. Do not redo it.

Waiting. The numbered list below is the old office queue. Do not open it. Issues 219 to 255 already cover slices 32 to 48. Issues 312 and 263 already exist, so do not open `Receipt names tariff one` or `Two cars move at the same time` again.

1. `Office booking fields for pickup and drop-off`
2. `Office status changes add the fare once`
3. `Office extras rows for soiling and an animal`
4. `Office buttons for the flag-fall boundaries`
5. `Company week of seven desk days`
6. `Empty company day sums to zero`
7. `Office quote shows meter and extras separately`
8. `Office refuses a Berwick booking by name`
9. `Office day kept in the browser`
10. `Plain-text receipt for a completed booking`
11. `Company takings by driver Alex and Sam`
12. `Tariff chosen from the requested clock`
13. `Inside and outside places on the empire page`
14. `Sample pickup and drop-off markers`
15. `Sample car hiring statuses`
16. `Game refuses a Berwick job`
17. `Second car stays at the depot until it is paid for`
18. `Cancel with no miles adds no fuel`
19. `New driver Jamie costs nothing`
20. `Three cars standing at Shiremoor`
21. `Durham customer pin and OSRM`
22. `Seven game days listed on the empire page`
23. `Empire page keeps off the company ledger`
24. `Map legend for phones, buses, depot, and the sample car`
25. Comment on each office issue opened above. Quote the pence figure from the matching grok-dev-1 slice. Do not add `ready`.
26. Comment on each game issue opened above. Quote the pence figure from the matching grok-dev-2 slice. Do not add `ready`.
27. In `docs/radio/po.md`, name any Open slice of yours that is still not done. If fewer than 8 remain, write `queue low`.
28. `Soiling-only company day`
29. `Cash or account does not change the fare`
30. `Desk rejects negative miles`
31. `Sunderland customer pin`
32. `Real data banner on the office desk`
33. `Office heading is Booking desk`
34. `Office page uses the three shared panels`
35. `Company ledger panel stays free of game costs`
36. `Office empty book says no bookings yet`
37. `Office bookings use the shared row`
38. `Office week strip stays 20020`
39. `Office page links to the empire`
40. `Simulated data banner on the empire desk`
41. `Empire heading is Booking desk`
42. `Empire page uses the three shared panels`
43. `Worked job shown as one booking row`
44. `Game ledger panel shows minus 1120`
45. `Empire empty book says no bookings yet`
46. `Three simulated cars as booking rows`
47. `Empire week strip shows minus 7840`
48. `Empire page links to the office`
49. Comment on issues 32 to 48. Quote `Real data`, `Simulated data`, and the pence figure from the matching slice. Do not add `ready`.
50. Do not write `queue low`. Slices 115 to 134 are still unopened. Name the next unopened title in `docs/radio/po.md`.
51. `Real-time clock for the empire`
52. `Car position from an OSRM duration`
53. `Straight-line fallback at 30 miles per hour`
54. `Sample car moves along the route`
55. `A new fare every 20 seconds`
56. `Live fares stay inside eight miles`
57. `Live fare uses the November 2024 tariff`
58. `Three cars can be out at once`
59. `Live offers appear on the booking desk`
60. Comment on issues 51 to 59. Quote 20 seconds, 30 miles per hour, and −1120. Do not add `ready`.
61. `Alex takings after the night booking is cancelled`
62. `One-mile fare shown as flag and units`
63. `Exact 322.6 yards on the desk`
64. `Pram and outside bag on the one-mile fare`
65. `Real data banner survives a reload`
66. `Receipt sits in the ledger panel`
67. `Switch between the full day and the empty day`
68. `Office page keeps the empire link`
69. `Customer pin for a waiting fare`
70. `Car drives back to the depot`
71. `Live fuel at 20 pence a mile`
72. `Seconds remaining on the booking row`
73. `Three fares waiting and no fourth`
74. `A live trip posts its fare once`
75. Comment on issues 61 to 74. Quote 1620, 580, 20 seconds, and −1120. Do not add `ready`.
76. If fewer than 12 Open slices remain for any lane, write `queue low`.
77. `Next fare countdown on the empire page`
78. `The car at the depot takes the oldest fare`
79. `Two cars move at the same time`
80. `Completed row shows ten pounds forty`
81. `Generator never returns Berwick`
82. `Simulated data stays on screen while fares arrive`
83. Slices 77 to 82 are open, through #270. `Real data banner on the office desk` already exists as #219. Do not open those titles again.
84. `Help line repeats both flag falls`
85. `Offered night booking stays out of the company total`
86. `Sunday quote uses tariff two`
87. `Company day shown as twenty-eight pounds sixty`
88. `Clearing the book brings back the empty sentence`
89. `Guide dog does not change eleven pounds thirty`
90. Comment on issues 84 to 89 once they exist. Quote 240, 315, 1620, 1240, 2860, and 1130. Do not add `ready`.
91. `Cash or account on the shared row`
92. `Soiling day sits in the ledger panel`
93. `Cancelled mile leaves 2370`
94. Comment on issues 91 to 93 once they exist. Quote 1130, 12500, and 2370. Do not add `ready`.
95. `Receipt names tariff one`
96. `27 December quote uses tariff two`
97. `Accepting a fare leaves two waiting`
98. `A returning car does not take a fare`
99. `The free car takes the oldest of three`
100. `Each car shows its own seconds`
101. `Night clock stays tariff two after restore`
102. `Animal row shows 790`
103. `No car at the depot`
104. `Returning car arrives at the depot pin`
105. Comment on issues 101 to 104 once they exist. Quote 1240, 790, and −1120. Do not add `ready`.
106. `Guide dog stays free beside the animal row`
107. `Phones and buses stay while a car drives home`
108. `Pram and bag stays off the company day`
109. `Drive home shows seconds remaining`
110. `1 January quote uses tariff one`
111. `Soiling shows a meter of zero`
112. `Oldest offer is listed first`
113. `Accepted row shows call sign T2`
114. Comment on issues 110 to 113 once they exist. Quote 1240, 1040, 12500, and −1120. Do not add `ready`.
115. `Empty day shows no bookings yet`
116. `1620 stays beside the full day`
117. `Two fares waiting is not three`
118. `Completed trip shows one fare line`
119. `Quote names the tariff beside the pence`
120. `Returning row becomes at depot`
121. Comment on issues 115 to 120 once they exist. Quote 2860, 0, 1620, 1040, 1240, and −1120. Do not add `ready`.
122. `Banner stays Real data on the empty day`
123. `Fuel line shows minus 60 once`
124. `Checked day still shows minus 140`
125. `Offer rows stay in age order after one is accepted`
126. Comment on issues 122 to 125 once they exist. Quote `Real data`, −60, −140, and −1120. Do not add `ready`.
127. `27 December quotes 1240`
128. `Soiling day stays beside 2860`
129. `T2 takes the fare when T1 is out`
130. `Completed row shows 1040 in pounds`
131. `Empty day hides the full day`
132. `Cash marking stays 1130`
133. `Tuesday at 15:00 names tariff one`
134. Comment on issues 127 to 133 once they exist. Quote 1240, 1040, 1130, 12500, 2860, and −1120. Do not add `ready`.

Map titles. Open these. Do not open 115 to 134 while these remain.

M1. `Three taxis drive on the map`
M2. `Passenger pin says waiting`
M3. `Passenger name while aboard`
M4. `Returning until the depot`
M5. `New passenger after four seconds`
M6. `Three taxis on different streets`
M7. `OSRM unavailable still moves the taxi`
M8. `Phones and buses stay when taxis hide`
M9. `Taxis are not devices`
M10. `Route line uses the taxi colour`
M11. `One real second is one game second`
M12. `Circle and depot stay while taxis drive`
M13. `Sidebar lists T1 T2 and T3`
M14. `A click on a taxi does not add a waypoint`
M15. `The sample car is not T1`
M16. `The map does not jump after the player pans`
M17. `The taxi chip shows the call sign`
M18. `T1 is amber and T2 is blue and T3 is green`
M19. `A taxi waits four seconds at the depot`
M20. `The three taxis do not leave on the same second`
M21. `Passenger names cycle through Mina Owen Priya Jack Helen and Tom`
M22. `Hide taxis changes the button to Show taxis`
M23. `The Shiremoor depot marker stays while a taxi is out`
M24. `The status line names the taxi and the passenger`
M25. `A taxi does not write a row into devices`
M26. `Phones still load when taxis are hidden`
M27. `Buses still load when taxis are shown`
M28. `The sample button still says Drive to the Monument and back`
M29. `The route line stays until the taxi is home`
M30. `The passenger pin is not a phone marker`
M31. `Zooming the map does not restart the three taxis`
M32. `The fleet keeps driving after the sample car is sent out`

Reservoir. Do not open these yet.

1. `Desk help panel for the two flag falls`
2. `Sample car returns to the depot pin`
11. `Game drivers Jamie and Alex`
12. `Fuel for four miles after the start`
13. `Standing only, when no job runs`
14. `New car and a new driver on the same day`
15. `Seven lines of the worked day on the empire page`
16. `Watcher stories stay words until the migration is agreed`

## grok-dev-1

A1 to A32 are on `main`. Skip them. You are not API-only. On `continue`, do the `### grok-dev-1` queue in `docs/radio/po.md` for about 30 minutes. One slice is one pull request, then the radio, then the next slice. Do not put the queue in one pull request. Do not write that the heading is clear. If that queue is not on `main` yet, say `queue empty` and pull once more. Do not invent slices. Checkout `C:\Users\MichaelThomson\source\lanes\grok-dev-1\hackathon-api` for API work, and the site checkout beside it when the product owner assigns site files. Branch `lane/grok-dev-1/<slug>` from `origin/main`. Do not run `box.ps1`. Do not wipe SQLite. No `device_id`. Do not edit a file the other dev's radio says they are editing. Do not edit `scripts/agents_dashboard.py`. That file is the product owner's.

Stop the fare cards. F1 to F30 are done. Office slices 45 to 60 wait. Do not start them. Pull request 26 is merged as `fa3b6e3`.

Waiting. The fare cards and the office list below are not work. Do not edit those files for this wave.

Waiting, office desk only. Do not rewrite the locked results: 490, 1040, 615, 1240, 1130, 265, 2370, 2860, and 12500. Money is integer pence. `py -3 scripts\taxi_fare_check.py` must print `FARE-OK` before each merge of an office slice. The company ledger is not the game ledger. No driver share, no fuel, no standing, and no new-car cost on this desk. That desk makes no API call. The account fleet above does, in the API repo.

Done, on `fa3b6e3`: the office desk, the £11.30 and £12.40 rows, the mixed button at 265, the company day at 2860, the cancelled mile at 2370, the empty hiring at 0, and soiling-only at 12500. Open slices 1 to 44 are also on `main`, through the animal row at 790 at `dcc53b1`. Office slices 45 to 60 wait. Do not start them. Do not edit `app/map.js`, `app/map.css`, or `app/index.html`.

Fare card for the map fleet. `FARE-OK` before each merge. Do not invent a second tariff.

F1 is on `main` at `1582946`. Skip it. F1. In `docs/taxi-fares.md`, state that a map taxi asks `quote_pence` and does not keep a second tariff. 3 miles, no waiting, tariff one, no extras, stays 1040. 1 mile stays 490.
F2, F3, and F4 are already recorded on `main`. Skip them.
F2. The checker still fails if 1 mile on tariff one is not 490.
F3. The checker still fails if 3 miles on tariff one, no waiting, no extras, is not 1040.
F4. The checker still fails if 3 miles on tariff two, no waiting, no extras, is not 1240.
F5. A guide or hearing dog still adds 0.
F6. Tariff one, 1 mile, one animal, no soiling, stays 790.
F7. The tariff one flag fall stays 240 and the tariff two flag fall stays 315.
F8. Soiling with no meter stays 12500.
F9. The company day stays 2860. It is not the game day.
F10. The empty company day stays 0.
F11. The office desk still does not show −1120, driver share, fuel, or standing.
F12. `docs/taxi-fares.md` names the map fleet and says the cars are not devices. `FARE-OK`.
F13. Exact 322.6 yards on tariff one stays 265. `FARE-OK`.
F14. The £11.30 hiring stays meter 1040 plus extras 90. `FARE-OK`.
F15. Tariff two, 1 mile, no waiting, no extras, stays 615. `FARE-OK`.
F16. Sunday at 15:00, 3 miles, no waiting, no extras, stays 1240. Tuesday at 15:00 stays 1040. `FARE-OK`.
F17. 30 December at 15:00, 3 miles, no waiting, no extras, stays 1240. 1 January at the same clock stays 1040. `FARE-OK`.
F18. 27 December at 15:00 stays 1240. 26 December at the same clock stays 1040. `FARE-OK`.
F19. Tariff one, 1 mile, one pram and one outside bag, stays 580. `FARE-OK`.
F20. 161.3 yards in 20 seconds, then a wait of 46.8 seconds, stays 265. It does not become 290. `FARE-OK`.
F21. Tariff two at 0 yards and 45 seconds stays 315. `FARE-OK`.
F22. Exact 161.3 yards on tariff one stays 240. Exact 140.5 yards on tariff two stays 315. `FARE-OK`.
F23. Cash or account does not change the £11.30 hiring. It stays 1130. `FARE-OK`.
F24. Cancelling the 490 leaves the company day at 2370. The full day stays 2860. `FARE-OK`.
F25. An empty hiring quotes 0. `FARE-OK`.
F26. Seven company days stay 20020. That week is not the game week. `FARE-OK`.
F27. Alex's two fares stay 1620. Sam's night fare stays 1240. The day stays 2860. `FARE-OK`.
F28. A guide or hearing dog on the £11.30 row keeps that row at 1130. `FARE-OK`.
F29. 22:00 and 06:59 are tariff two. 07:00 and 21:59 are tariff one. `FARE-OK`.
F30. The office does not show −7840 or −807840. `FARE-OK`.

Waiting. Office list. Do not start these.

1. Booking fields. Each row stores pickup, drop-off, requested time, vehicle call sign, and status. The £11.30 sample picks up at `Grey's Monument` and drops at `Shiremoor depot`. The £12.40 sample is the reverse. Describe the fields in `docs/taxi-office.md`.
2. Status adds the fare once. Buttons move `offered` to `accepted` to `started` to `completed`. Cancel is allowed until `completed`. Completing the £11.30 row adds 1130 once. A second press does not add it again. Cancel from `offered` adds 0. A completed booking does not become cancelled.
3. Extras rows. A hiring with no miles, no waiting, and soiling is 12500. A guide or hearing dog adds 0. Tariff one, 1 mile, no waiting, one animal, no soiling, is 490 + 300 = 790. Show both rows. The checker fails if either figure moves.
4. Flag-fall buttons. Keep the mixed button at 265, not 290. Add tariff two at exact 140.5 yards and no waiting: 315. Add tariff two at 0 yards and 45 seconds: 315. Add tariff one at exact 161.3 yards and no waiting: 240. The checker fails if any of those move.
5. Company week. Seven completed days of 2860 pence sum to 20020. Label it `company-week`. This is not the game week of −7840. The checker fails if the week is not 20020. Show it on the desk.
6. Empty day. No bookings sum to 0. A day whose only booking is the cancelled 490 pence mile sums to 0. Label it `empty-day`. The 2370 and 2860 totals stay.
7. Split quote. The £11.30 row shows meter 1040, extras 90, total 1130. The £12.40 row shows meter 1240, extras 0, total 1240. The checker fails if the split moves.
8. Berwick by name. A pickup or drop-off whose text is `Berwick-upon-Tweed` is not saved and adds 0. `Hexham`, `Durham`, `Sunderland`, `Grey's Monument`, and `Shiremoor depot` may be saved. Do not add a coordinate table and do not edit the geo module. The fare is still the meter the clerk entered.
9. Browser book. The day's rows survive a reload in `localStorage` under `hackathon-office-day`. A clear control removes that key. A restore control rebuilds the three completed bookings 1130, 1240, and 490 and shows 2860. Still no API.
10. Receipt. A completed booking renders a plain-text slip with tariff, miles, waiting, extras, and quoted pence. The £11.30 slip contains `1130` and `£11.30`. It does not contain `driver_share`, `standing`, or `800000`.
11. Drivers on the company book. `Alex` runs the 1130 and the 490. `Sam` runs the 1240. Completed takings are Alex 1620 and Sam 1240, and the day is still 2860. These are gross fares. Do not subtract a driver share.
12. Clock chooses the tariff. Requested time `22:00` or `06:59` selects tariff two. `07:00` or `21:59` selects tariff one. A Sunday checkbox forces tariff two. 27 December through 31 December forces tariff two. A Tuesday at `15:00` stays tariff one. The meter figures do not change. The checker covers those boundaries. The desk shows the tariff it selected.
13. Soiling-only day. One hiring, no meter, soiling on, sums the day to 12500. Label it `soiling-day`. The 2860 day stays available beside it. `FARE-OK`.
14. Cash or account. A completed £11.30 booking can be marked cash or account. The pence stays 1130 either way. `FARE-OK`.
15. Negative miles. The desk rejects them and the previous quote stays on screen. `FARE-OK`.
16. Help panel. It states the tariff one flag fall of 240 pence and the tariff two flag fall of 315 pence. It does not change a quote. `FARE-OK`.
17. Real banner. Add `<p class="desk-banner">Real data</p>` above the heading. The heading is `Booking desk`. Describe both in `docs/taxi-office.md`. The locked pence do not move. `FARE-OK`.
18. Shared panels. Keep the three panels in `office-grid`, with headings `Quote`, `Bookings`, and `Ledger`. The ledger note says the money is the company's. It does not show a driver share, fuel, standing, or −1120.
19. Empty book. When the bookings panel has no rows, it says `No bookings yet.`
20. Shared row. Each sample booking is one row showing pickup, drop-off, call sign, status, and the fare in pounds. The £11.30 row and the £12.40 row use it.
21. Week strip. The company week stays 20020 pence and is labelled `company-week` inside the ledger panel.
22. Empire link. The nav on `office.html` includes a link to `game.html` named `Empire`. Do not edit `index.html`.
23. Status words. The row status is one of `offered`, `accepted`, `started`, `completed`, or `cancelled`. Completing the £11.30 row still adds 1130 once.
24. Alex after the night booking is cancelled. Cancel Sam's 1240. Complete Alex's 1130 and 490. The desk shows 1620. The 2860 day is still available. `FARE-OK`.
25. One-mile breakdown. Tariff one at 1 mile is shown as flag 240 plus 10 units of 25, total 490. `FARE-OK`.
26. Two units. Exact 322.6 yards on tariff one shows 265. The mixed button stays 265, not 290. `FARE-OK`.
27. Pram and bag. Tariff one, 1 mile, one pram, and one outside bag is 490 + 50 + 40 = 580. `FARE-OK`.
28. Banner survives reload. After the browser book is restored, the page still says `Real data` and the total is 2860. `FARE-OK`.
29. Receipt in the ledger. The plain-text slip is inside the ledger panel. It still contains `1130` and `£11.30` and does not contain `driver_share`, `standing`, or `800000`.
30. Two saved days. A control shows the 2860 day. Another shows the empty day at 0. Switching does not add the totals together. `FARE-OK`.
31. Simulated desk link. The Empire link on `office.html` is present. The office page does not copy the game's −1120 total.
32. Restored help. After the browser book is restored, the help line still states the tariff one flag fall of 240 pence and the tariff two flag fall of 315 pence. The total stays 2860. It does not change a quote. `FARE-OK`.
33. Offered money stays out. The £12.40 row can sit at `offered`. The row shows £12.40. The ledger includes only completed rows, so Alex's 1130 and 490 sum to 1620 until that night booking is completed. Completing it makes the day 2860. `FARE-OK`.
34. Sunday quote. Sunday at `15:00`, 3 miles, no waiting, no extras, quotes 1240. The same clock with Sunday cleared quotes 1040. `FARE-OK`.
35. Pounds beside the day. The ledger shows the full day as 2860 and as £28.60. The empty day shows 0 and £0.00. Switching days does not add them. `FARE-OK`.
36. Clear brings the sentence back. Clearing the book removes the rows, the bookings panel says `No bookings yet.`, and the total is 0. Restore brings the three bookings back and shows 2860. `FARE-OK`.
37. Guide dog. On the £11.30 booking, a guide or hearing dog adds 0. The row stays 1130. `FARE-OK`.
38. Cash or account on the shared row. The £11.30 row can read `cash` or `account`. The pence stays 1130. The ledger does not gain a line. `FARE-OK`.
39. Soiling day in the ledger. The soiling-only total of 12500 is labelled `soiling-day` inside the ledger panel. The 2860 day stays available beside it. `FARE-OK`.
40. Cancelled mile on the desk. Cancelling the 490 pence mile from the 2860 day leaves 2370. The 2860 day can be selected again. `FARE-OK`.
41. Receipt names the tariff. The plain-text slip says `tariff one` and still contains `1130` and `£11.30`. It does not contain `driver_share`, `standing`, or `800000`. `FARE-OK`.
42. December quote. 27 December at `15:00`, 3 miles, no waiting, no extras, quotes 1240. 26 December at the same clock quotes 1040. `FARE-OK`.
43. Night clock after restore. After the browser book is restored, a requested time of `22:00` on the £12.40 row still selects tariff two. The pence stays 1240. The 2860 day stays available. `FARE-OK`.
44. Animal row. Tariff one, 1 mile, no waiting, one animal, no soiling, shows 790 on its own row. The 2860 day stays available. `FARE-OK`.
45. Guide dog beside it. A guide or hearing dog on its own row adds 0. The animal row stays 790. Neither changes the 2860 day. `FARE-OK`.
46. Pram and bag beside the day. The 580 row is its own booking. The company day stays 2860. `FARE-OK`.
47. New year quote. 30 December at `15:00`, 3 miles, no waiting, no extras, quotes 1240. 1 January at the same clock quotes 1040. `FARE-OK`.
48. Soiling meter. A hiring with soiling, no miles, and no waiting shows meter 0 and total 12500. The 2860 day stays available. `FARE-OK`.
49. Empty sentence. Selecting the empty day shows `No bookings yet.` Selecting the 2860 day shows the rows and 2860. Both are not on screen together. `FARE-OK`.
50. Beside the full day. The 1620 control and the 2860 control do not add. Each shows its own total. `FARE-OK`.
51. Tariff name. Tuesday at `15:00`, 3 miles, no waiting, no extras, shows tariff one and 1040. The same trip at `22:00` shows tariff two and 1240. `FARE-OK`.
52. Banner on the empty day. Selecting the empty day keeps `Real data` and shows 0. Selecting the 2860 day keeps `Real data` and shows 2860. `FARE-OK`.
53. Soiling pounds. The soiling day shows 12500 and £125.00. The 2860 day stays 2860 and £28.60. Switching does not add them. `FARE-OK`.
54. Cancelled-mile receipt. The 2370 day is available. Its slip does not contain `driver_share`, `standing`, or `800000`. `FARE-OK`.
55. Empty after cancel. When the only row was the cancelled 490 pence mile, the bookings panel says `No bookings yet.` and the total is 0. The 2860 day can be selected again. `FARE-OK`.
56. Pram pounds. The 580 row shows £5.80. The company day stays 2860. `FARE-OK`.
57. Animal pounds. The 790 row shows £7.90. The 2860 day stays 2860 and £28.60. Switching does not add them. `FARE-OK`.
58. Guide-dog pounds. A guide or hearing dog on its own row adds 0 and shows £0.00. The animal row stays £7.90. Neither changes the 2860 day. `FARE-OK`.
59. Cancelled-mile pounds. The 2370 day shows £23.70. The 2860 day stays £28.60. Switching does not add them. `FARE-OK`.
60. Sunday after restore. After the browser book is restored, Sunday at 15:00, 3 miles, no waiting, no extras, quotes 1240. Clearing Sunday quotes 1040. The 2860 day stays available. `FARE-OK`.

Reservoir. Do not start these.

1. A Tuesday at `15:00` on the restored day still shows tariff one and does not change 2860.

## grok-dev-2

Open slices. U18 to U32, then the `### grok-dev-2` queue in `docs/radio/po.md`. U1 to U17 are on `main`. The signed-in form is `714303e`. Skip those. About 30 minutes. Do not stop at U32 if `po.md` lists more. You are not map-only. Checkout `C:\Users\MichaelThomson\source\lanes\grok-dev-2\hackathon-site`. Branch `lane/grok-dev-2/<slug>` from `origin/main`. For U18 to U32, edit `app/map.js`, `app/map.css`, and the Empire block in `app/index.html`. Call `POST /register`, `POST /login`, and `GET /v1/empire`. When `po.md` assigns API work, do that instead. Do not edit a file the other dev is on. Do not edit the office files, `scripts/taxi_fare.py`, or `app/office.css`. Do not edit `scripts/agents_dashboard.py`. That file is the product owner's. Do not bring back a browser-only fleet as the source of truth. The sample car button stays. Do not run `box.ps1`.

Desk slices 45 to 58, slices 11 to 23, and map titles M1 to M32 wait. Do not start them. A radio that names M6 or M8 is stale as an order. The game runs on the box per account. The browser must not invent the cars.

Waiting. The map list and the desk list below are not work. Pull request 25 is merged as `e4a2c1c`. Open slices 1 to 10 of that old desk are on `main`. Skip them.

Waiting. Map titles M1 to M32. Do not start these. M1 to M7 and U1 are already on `main`. U1 replaced the auto-start fleet.

M1. Three taxis drive on the map. T1, T2, and T3 leave the Shiremoor depot, collect a virtual passenger, drive the street geometry, and return. This is on `main` in this pass. Skip it if the map already shows the three chips.
M2 is on `main` at `58697ba`. Skip it. M2. The passenger pin shows the passenger's name and the word `waiting`. The pin leaves when that taxi arrives.
M3 is on `main` at `35501ac`. Skip it. M3. While the status is `with_passenger`, the tooltip names the passenger.
M4. After the drop-off the status is `returning` until the depot pin. Then it is `at depot`.
M5. A new passenger appears 4 seconds after the taxi is back at the depot.
M6. T1, T2, and T3 are on different streets at the same time. None of them is a device.
M7. When OSRM does not answer, the taxi still moves in a straight line at 30 miles per hour and the status says `OSRM unavailable`.
M8. Hiding taxis removes the three chips, their lines, and their passenger pins. Phones and buses stay.
M9. The tooltip does not say `device`. Game rows are still not written into `devices`.
M10. Each taxi's route line uses that taxi's own colour.
M11. One real second is one game second. With no OSRM duration, 3 miles take 360 seconds.
M12. The 50-mile circle and the Shiremoor depot stay on the map while the taxis drive.
M13. The sidebar lists T1, T2, and T3 with the passenger name, or `at depot`.
M14. Clicking a taxi or a passenger pin does not add a waypoint.
M15. The sample car stays separate. It is not T1. Both may be on the map.
M16. After the player pans or zooms, the map does not jump back to the fleet. One real second is one game second. `scripts/taxi_day_check.py` must still print `DAY-OK`, and it must also print `TIME-OK`. Do not edit `app/office.css` or `scripts/taxi_fare.py`. The page may load `app/taxi-fare.js`. A live offer must not change the checked day of −1120.
M17. The taxi chip shows `T1`, `T2`, or `T3`.
M18. T1 is amber, T2 is blue, and T3 is green.
M19. A taxi waits 4 seconds at the depot before the next passenger.
M20. The three taxis do not leave on the same second.
M21. The passenger names cycle through Mina, Owen, Priya, Jack, Helen, and Tom.
M22. Hide taxis changes the button to `Show taxis`. Show taxis brings the three cars back. Phones and buses stay either way.
M23. The Shiremoor depot marker stays while a taxi is out.
M24. The status line names the taxi and the passenger.
M25. A taxi does not write a row into `devices`.
M26. Phones still load when taxis are hidden.
M27. Buses still load when taxis are shown.
M28. The sample button still says `Drive to the Monument and back`. The sample car is not T1.
M29. The route line stays on the map until the taxi is home.
M30. The passenger pin is not a phone marker.
M31. Zooming the map does not restart the three taxis.
M32. The fleet keeps driving after the sample car is sent out. `DAY-OK` and `TIME-OK`.

Waiting. Desk list. Do not start these. Use the coordinates already in `scripts/taxi_geo_check.py`. Do not invent a new town.

1. Places on the empire page. Show Grey's Monument, Shiremoor depot, Hexham, Durham, and Sunderland as inside, and Berwick-upon-Tweed as outside. A job that starts or ends at Berwick is not offered. `GEO-OK` still passes.
2. Job pins. On the map, add `Sample pickup` at Grey's Monument and `Sample drop-off` at the depot, beside the sample car. Phones and buses stay. These markers are not devices.
3. Hiring statuses. Buttons set the sample car to `at_depot`, `offered`, `accepted`, `started`, and `returning`. Pressing `complete the worked day` still shows −1120 once. Changing status does not add a second fare. `DAY-OK` stays the one-car day.
4. Berwick is not a game job. Drop-off `55.7704, -2.0068` adds no ledger lines. A Hexham drop-off may be offered. Do not give Hexham its own fare. The priced day remains the 3-mile example at 1040.
5. The second car cannot leave unpaid. The purchase line is −800000 and the car stays `at_depot` until that line exists. Starting a job on the unpaid car adds no `fare_in`. `scripts/taxi_week_check.py` still prints `WEEK-OK` for −7840 with no purchase. It then prints `FLEET-OK` for the same seven days plus the purchase on day 1, summing to −807840. The bought car is not a device.
6. No miles, no fuel. A cancel after the status has reached `started`, with 0 miles driven, adds no fuel line and no fare. The one-mile cancel stays −20 and no fare. Show the zero-mile cancel on `game.html`.
7. Driver Jamie. A new driver costs 0. The worked fare 1040 still pays a driver share of −520. Adding Jamie does not change the −1120 day. The checker fails if a new driver costs anything else.
8. Three cars. Call signs `T1`, `T2`, and `T3` start at the depot. Only `T1` runs the worked fare. Standing is −1500 for each car, so −4500, then fare +1040, driver share −520, fuel −140. The three-car day sums to −4120. Label it `three-car day` on `game.html`. `DAY-OK` still requires the one-car day at −1120, and it also requires −4120 for this case. None of the cars is a device.
9. Durham customer. A pin at `54.7753, -1.5849` is labelled `Durham customer`. It is offered because it is inside. The sample car may ask OSRM for the depot to that pin and back. If OSRM does not answer, show `OSRM unavailable`. That path does not change the −1120 day.
10. Week list. `game.html` lists seven worked days, each −1120, total −7840. A control that also buys the second car on day 1 shows −807840 and says the car is not a device. `WEEK-OK` and `FLEET-OK` still pass.
11. Separate ledgers. `game.html` states `Company ledger is not this page`. It does not show 2860, 1130, or 1240. Do not edit the office files.
12. Map legend. The map names phones, buses, the depot, the circle, and the sample car as different things. The sample-car popup says `not a device`. The circle text includes `80467 m`. The depot label stays `Shiremoor depot`.
13. Sunderland customer. A pin at `54.9069, -1.3838` is inside and has no fare of its own. `GEO-OK` still passes.
14. Returning pin. Status `returning` draws the sample car on the depot pin. The worked day stays −1120. `DAY-OK`.
15. Simulated banner. `game.html` links `styles.css` and `app/office.css`. Add `<p class="desk-banner">Simulated data</p>`. The heading is `Booking desk`. Do not edit `app/office.css`. The worked day stays −1120. `DAY-OK`.
16. Shared panels. Use `office-grid` and three `office-panel` sections headed `Quote`, `Bookings`, and `Ledger`. Keep the place list and the checkers' results. Do not show 2860, 1130, or 1240.
17. One booking row. The worked job is a row: pickup `Grey's Monument`, drop-off `Shiremoor depot`, call sign `T1`, status `completed`, fare £10.40. It is not a device.
18. Ledger panel. The ledger uses the same ledger line markup as the office and shows standing −£15.00, fare £10.40, driver share −£5.20, fuel −£1.40, and the sum −£11.20.
19. Empty book. Cancel before the car starts shows `No bookings yet.` and no fare. `DAY-OK` still expects no lines for that case.
20. Three rows. The three-car day shows `T1`, `T2`, and `T3` as booking rows. The sum stays −4120. `DAY-OK`.
21. Week strip. Seven rows or seven lines of −1120 sit in the ledger panel. The total is −7840. The purchase control still reaches −807840. `WEEK-OK` and `FLEET-OK`.
22. Office link. The nav on `game.html` includes `office.html` named `Office` and `game.html` named `Empire`. Do not edit `index.html`.
23. Status words. The sample car status is one of `at_depot`, `offered`, `accepted`, `started`, or `returning`, shown on the booking row. Completing the worked day still adds −1120 once.
24. Real-time clock. `elapsedSeconds(startMs, nowMs)` is the real difference in seconds. Ten real seconds return 10. There is no multiplier. `TIME-OK`.
25. Position on a route. A list of points and an OSRM duration give the car's place. At 0 seconds the car is on the first point. At the full duration it is on the last point. Halfway through a 600 second duration, 300 seconds have elapsed and the car is halfway along the points. The checker does not call OSRM. `TIME-OK`.
26. Fallback speed. With no OSRM duration, 3 miles take 360 seconds, because 30 miles per hour is the built-up limit. The page says `OSRM unavailable`. The checked day stays −1120. `TIME-OK`.
27. Moving sample car. On the map, starting the sample car moves its marker along the depot-to-Monument route in real time. The tooltip shows the seconds remaining. If OSRM does not answer, the marker uses the straight line at 30 miles per hour and the page says `OSRM unavailable`. Phones and buses stay. The marker is not a device. The −1120 ledger does not change because the marker moved.
28. Offer every 20 seconds. While fewer than 3 jobs are `offered`, the next offer appears when 20 real seconds have passed. At 0 seconds there are 0 offers. At 20, 40, and 60 seconds there are 1, 2, and 3. At 80 seconds there are still 3. The page shows the seconds until the next offer. `TIME-OK`.
29. Short trips. A live pickup and drop-off are inside the 80.467 km circle, are not Berwick-upon-Tweed, and are at least 1 mile and at most 8 miles apart. Generate them from the Shiremoor depot by a bearing and a distance of 2, 4, or 6 miles. Do not add a new town. `GEO-OK` and `TIME-OK`.
30. Live tariff. The offer's fare is `quote_pence` from `scripts/taxi_fare.py`, using the trip's yards and seconds. The unit that finishes first is the one that counts. Three miles, no waiting, tariff one, no extras, is 1040. The page may load `app/taxi-fare.js` and must not edit it. A live offer does not change the checked −1120 day. `TIME-OK`.
31. Three moving cars. `T1`, `T2`, and `T3` can each follow a route at the same time. Offers still arrive every 20 seconds until 3 are waiting. None of the cars is a device. `DAY-OK` still requires −1120 for the checked day.
32. Offers on the desk. Each waiting offer is a booking row: pickup, drop-off, status `offered`, and the fare in pounds. Accepting one sets a free car onto that route. The banner says `Simulated data` if that banner is already on the page.
33. Customer pin. A waiting offer puts a marker on its pickup. The marker is not a device. Accepting the offer removes that marker and starts the car. Phones and buses stay.
34. Drive home. After the drop-off the car status is `returning` and it drives to the Shiremoor depot in real time. Arrival sets `at_depot`. The checked day stays −1120. `TIME-OK`.
35. Live fuel. When a live trip completes, fuel is 20 pence for each mile driven, added once. Three miles add −60. A second completion does not add it again. The checked seven-mile fuel of −140 stays on the checked day. `TIME-OK`.
36. Seconds on the row. The booking row of a moving car shows the seconds remaining. At the start of a 600 second route it shows 600. Halfway it shows 300. `TIME-OK`.
37. Three waiting is the cap. The page says `3 fares waiting` when three offers are open. The twentieth second does not add a fourth. When one is accepted, the next 20 seconds may add one. `TIME-OK`.
38. One ledger post. Completing a live trip appends one fare line and one fuel line. Doing it again does not append them again. `DAY-OK` still requires −1120 for the checked day.
39. Countdown label. The page shows `Next fare in` and the seconds left. At 0 the offer appears and the count starts again from 20 unless 3 offers are already waiting. `TIME-OK`.
40. The free car takes it. A car `at_depot` accepts the oldest offer. If `T1` is already on a route, `T2` takes the next one. Neither car is a device. `TIME-OK`.
41. Two cars out. Two accepted offers move `T1` and `T2` at the same time. The third car can stay `at_depot`. `DAY-OK` still requires −1120 for the checked day.
42. Fare on the row. The completed row shows the tariff fare in pounds. Three miles, no waiting, tariff one, no extras, shows £10.40. Posting it twice does not add a second fare line.
43. Berwick stays out. The generator must not return `55.7704, -2.0068`. A point that far out is discarded. `GEO-OK`.
44. Simulated banner stays. While offers arrive, the page still shows `Simulated data`. It does not show 2860, 1130, or 1240.
45. Accept drops the count. With 3 offers waiting, accepting one makes the page say `2 fares waiting`. The next offer still waits 20 seconds. `TIME-OK`.
46. Returning stays out. A car whose status is `returning` does not take a new offer. The offer stays `offered` until a car is `at_depot`. `TIME-OK`.
47. Oldest of three. A free car takes the oldest of three offers. The other two stay `offered`. Neither car is a device. `TIME-OK`.
48. Own seconds. The tooltip on `T2` shows `T2`'s seconds remaining, not `T1`'s. Halfway through `T2`'s 600 second route it shows 300. `TIME-OK`.
49. Depot empty. When `T1`, `T2`, and `T3` are all away from `at_depot`, the page says `No car at the depot`. Offers stay `offered`. None of the cars is a device. `TIME-OK`.
50. Home arrival. When a `returning` car reaches the depot pin, its status becomes `at_depot` and the page stops showing seconds remaining for that car. The checked day stays −1120. `TIME-OK`.
51. Map stays shared. While a car drives home, phones and buses stay on the map. The car is not a device. The checked day stays −1120. `DAY-OK`.
52. Seconds on the way home. While the car is `returning`, the booking row shows the seconds remaining. At the start of a 600 second return it shows 600. Halfway it shows 300. `TIME-OK`.
53. Oldest first. When three offers are waiting, the first row is the oldest. Accepting it leaves the other two in age order. `TIME-OK`.
54. Call sign on the accepted row. The row `T2` accepts shows call sign `T2`. `T1` can be out at the same time. Neither car is a device. `TIME-OK`.
55. Two waiting. With two offers open the page says `2 fares waiting`. It does not say `3 fares waiting`. `TIME-OK`.
56. One fare line. A completed 3 mile tariff-one trip shows one fare line of 1040. Posting twice does not add a second fare line. The checked day stays −1120. `TIME-OK`.
57. Returning label. The row says `returning` on the way home and `at_depot` on arrival. `TIME-OK`.
58. Fuel on the ledger. A 3 mile live trip shows one fuel line of −60. The checked day still shows −140. A second completion does not add another −60. `TIME-OK`.

Reservoir. Do not start these.

1. Game drivers Jamie and Alex. Alex runs `T1`. Jamie has no share until a fare. The one-car day stays −1120.
3. Cancel after 4 miles driven: fuel −80 and no fare. The miles are given by this slice, not by OSRM.
4. A day with one car and no job is standing −1500 only.
5. A new car and a new driver on the same day: −800000 and 0. The new car cannot start.
6. The empire page lists the seven −1120 lines as well as the total.
7. Watcher and owner stories stay on the model page. Do not migrate `device_links`.

## Integrator

On `continue`, read the radios. Direct the product owner. Do not write the slice text. Master gives direction here. While `## This stretch` is the order, leave the lanes on it. Do not name their slices. The product owner keeps both queues and `## Next for me` full, keeps improving `scripts/agents_dashboard.py`, and the devs build the game for about 30 minutes. They do not wait for a new note before the next slice. If a dev wrote `queue empty` or stopped after a slice or two, the supply failed or the turn was short. Say so in `## Now` only if the standing stretch order is not enough, and leave the refill to the product owner. If `scripts/agents_dashboard.py` moved on `main`, pull this checkout and restart the serve on port 5510 so Master sees it. Do not deploy that restart. Deploy only after product code has merged. A radio-only commit is not a deploy. A dashboard-only commit is not a deploy. Do not deploy this note by itself. When Master returns, deploy the `play.html` and API commits that landed during the stretch, then restart the dashboard.

Last deploy checked in this note: box site `ff1e142`, health `0.1.27`, `CHECK-OK`. The board was 50 cards. Map clicks do not add a waypoint unless Place stops is on.