What’s new

Now a press on a failed walk opens a small sheet with the whole message and one key the shop PC chose: bring the file in from the X5 again, ask the shop PC again, or walk it again.

The first case is new: a file copied off the X5 while it was still recording has no index, so the engine cannot read it and asking again can never help. The shop PC now says exactly that, and the key opens Walk so the full recording can be brought in from the camera’s card.

Now the copy is final only when the re-read head says so — a sized mdat with the index after it — else it keeps waiting for the camera to close the file (up to its 90 s, then the road after Stop copies it whole). The original is still on his card; the X5 closed it after the copy had already left.

A TEST build, not the update notice: builds/test/b11.apk.

And: the shop PC card said only "1 in line" while the box sat resting after its memory ran out. The box now reports its rest and when it ends in its heartbeat, and the card says "resting after its memory ran out — starts again 8:01 PM", or "starting it now".

A person's own Claude still reads their record through the connector, on their own plan — search, a day with its photographs, a 360 walk frame by frame. tradesman_ask now says so instead of answering. The camera form loses its Scan key; the Wi-Fi name and password are typed.

The code is kept behind one switch (TRADESMAN_APP_MODEL=on, and NEXT_PUBLIC_TRADESMAN_APP_MODEL=on for the Scan key) that turns it back on for everyone at once. Batches already out are still collected; nothing new is sent.

The front: each job is one row with a round picture — its newest walk — and one line under its name (when it was worked, how many walks), then its newest photos as small circles ending in "+N". The job you are standing at leaves the list for its own spot at the top, "You're here", with a bigger ball, a HERE tag and how many walks it has; while its tour is on the way it wears the same four step dots the Walk page shows (the X5, the phone, the shop PC, the tour) and a ring of how far along it is. Held stops show as one amber line. The shop PC is one card at the top when it is busy. New job and Unfiled share the last row.

A job's page now opens on one big round picture of its newest tour, the walk count on it and a "Walk the tour" key under it, then the job's name large and one line. The address, Directions, who is on it and its docs are chips under the name. Each day is one row: its walk's ball (greyed with a ring while the tour is on the way, an empty glass ball on a day with no walk), the date and the walks' times, the step dots while it builds, one line, the day's photos as circles, and Claude at the right.

The dock is one big red key for a 360 walk, with Photo beside it and Upload (on the front) or Note (on a job's page). The word under the red key — "Walk Redland", "Walk it again" — names where the walk goes; pressing that word opens every way to capture and the job and day picker, so nothing the old key did is gone.

Not done: nothing here has met his phone. The front's here-spot shows the step dots only for walks on the shop PC (a walk on his own computer has no dots yet). The tour viewer's mock is another build.

What stays is one upload size limit, the same for every account: a photo 4.4 MB, a clip 300 MB, a PDF 25 MB, a 360 walk 6 GB. The shop PC builds walks in the order it always did, nobody first.

The engine, shop-tour, is public the same night as a clean single-commit export; its old history stays private.

The landing promised a floor plan, a dollhouse and a tour. The plan and the dollhouse have been off the glass since Oct 28 until they are good enough, so the sentence now says what you get today: a tour of the whole job.

The demo tour asked storage for a photo list it does not have on every open, and that showed as an error in the browser on the front page. A tour with no photos pinned to it now answers that question itself — nothing goes out, nothing fails.

The shop PC page named the engine by our private build name and had no way back. It now says in plain words what that computer does — builds every 360 tour, faces, plates and printed names blurred first — with a way home.

Four were the app. A job with days and no job doc yet had no way to keep its first doc — the day's + that held it left on 10-30 and the Docs section draws nothing until there is one — so the job's ⋯ says Add a job doc again until the first is kept. On the front, holding a photo to pick it slid the whole day up the page by the job list's height, because the list stepped aside; now it stays where it was, dimmed and out of reach, while he picks. A shared day's groups sat 6 px in from the loose photos beside them. And the words Walked twice on an opened day were a 20 px press beside the 96 px ball — words now; the ball and the time pills are the presses.

The nightly sweep shares the night fairly: the owner's owed photos first, every one, then at most 60 of each other account's. The X5 screen reader used to call Claude for anyone who asked; it needs a sign-in now.

Uploads know their size for everyone but the owner: a phone clip up to 300 MB, a 360 walk up to 6 GB (the one-piece link, the multipart parts and the finished object are each checked; an object over the cap is taken back). Photos (4.4 MB) and PDFs (25 MB) were capped for everyone already. Nothing the owner does changes.

Now each asks the shop PC's key or his own session, and a walk is read only by the people on its job. The shop PC signs its calls and never follows a redirect with its key. Nothing changes on his phone. What was left as a judgement call is written down in docs/release/SECURITY_REVIEW.md.

Now it sends the way the relay does: on validated internet (the shop Wi-Fi beside the camera's, or real cellular), then the cellular handle, then the default route, trying again with a pause between. When it cannot, the Walk page writes down why ("upload off: …") in its ledger row, and a row lands the moment the first part is up.

Build 9 threw the whole upload away at Stop because the X5 writes the file's first bytes last. Build 10 sends part 1 again with the real head and keeps everything else that already went up.

This is a TEST build, not the update notice: builds/test/b10.apk. A fast 8K walk writes about 15 MB a second, more than any phone uploads, so at Stop part of it is still going — the head start is the point.

Under it, each of your walks is its round picture with a ring for how far along it is, the time, and four dots: the X5, the phone, the shop PC and the tour. Done dots are dark, the one happening now is blue, the ones to come are grey. One short line says the rest: Copying 37%, In line, Building the tour 8 min, 2 stops need your eye (press it to review), or Tour ready with an Open key that opens the tour right there.

Recording is the clock, a red Recording, the stop key and one card saying how much of the walk is already saved to your phone. After Stop, a big green card says X5 can go off only when that is true: the file is whole on the phone or off the card. Until then an amber card says Keep the X5 on, with the copy percent. Then Record another.

Everything under it works as before: the copy still starts the moment you stop, the tail still writes down what it did, review and Import are the same. The long shop PC line is gone from this page; each walk's dots carry it, and only an off shop PC gets one small grey line.

Now every change in what the phone does with the camera file while he records is one ledger row (x5.cardTail) with its reason, and a walk saved with no word from it at all is one too. The next walk tells us which side failed.

While a tour loads, the glass shows the tour's own picture (the small cut the Record already holds paints at once, a sharper one over it) under "Loading the tour…" — never black. A tour that will not load shows its picture dimmed behind the words, with Try again first and Open in your browser beside it.

Smaller things on the daily path: the tour's header says "22 spots · 2 floors" and stands whole (on a small phone Share is its mark alone); an opened day walked twice says "Walked twice", never "2 360 walks"; a day's line says "1 photo · 1 walk"; on the Walk page "on" and the day wrap together, and "Saved to <job>" comes before the copy's progress.

How it works still described the September app: a Jobs tab, Note, Voice and Link on the shutter, a Tools key and 3D drawings that are no longer on the glass. It is rewritten for the app as it is — the 360 walk first, then photos, your jobs as days with their tours, sharing a tour, Claude, your crew, and that the record is yours — and it names only keys you can see.

The front door had no way to How it works or Privacy; both now sit on the engine line, so the page still fits one screen. Sign in and sign up spoke of photos and notes only; they now say what the app makes — the tour — and keep every photo.

A shared tour of a walk with no name read "360 tour" over "Vitronic · 360 tour": the job is its title now, said once. Its foot held a link inside the phone's bottom strip; the mark at the top is the way to Tradesman. The tour frames lost a duplicate fullscreen attribute every browser warned about, and Privacy no longer names a picture-of-tasks reader that was taken out with the tasks.

A tap on the small map opens the same map over the whole glass, every stop numbered, the ones he can walk to from here brighter, the view cone where he looks; a tap on a stop glides there. A Play key walks the tour by itself, stop by stop, turning to face the way it goes; any touch stops it.

Found on the way: a page or a tour.json re-served into a live tour's folder was not reaching the app for an hour or more, because the storage kept the old copy under its bare name. The app now asks for the page with a mark that changes every minute, and the viewer's own reads of tour.json carry the same mark, so a re-served tour lands within a minute.

Never a gate: no sign-in, no internet, a part the storage refuses, and the upload ends quietly (the multipart aborted) while the road after Stop copies and sends the file as before. The Walk page says it as it goes: "412 MB of it is already on the phone · 260 MB sent", "Sending the walk · 3,710 of 3,930 MB — the X5 can go off", "The whole walk is sent — the X5 can go off". Unproven on a real X5 until the next walk.

Now the engine takes the walk the moment its file is on the box. The watchable 360 and the frame shelf run after the tour, on their own thread, once no tour is queued or building. And the file comes down over six connections at once, one stream when the storage refuses ranges. The walk’s row says the shop PC’s own step throughout.

Three fixes. The copier (the app’s build 6) throws a refused resume away and copies the file again from the start, and the background copier checks the copy against the card’s own listed size before it files anything. The server checks the uploaded object’s size against the card’s and refuses a short one in words. And a walk whose camera file failed on the shop PC is no longer "in the Record" on the card sheet: its file is offered again, and the record takes it again.

Now every stop of an .insv walk is levelled by the camera’s own gyroscope and accelerometer: gravity read over a stride either side of the stop, each sample turned by the gyroscope into the stop’s own instant, through the sensor’s fixed mounting in the camera. Measured against the vertical edges on 25 stops of three walks (median 3 degrees apart) and proved on a stop he carried at 59 degrees, which came out level. A video with no sensor still levels itself from its pictures, vertical edges first and the skyline only where there is no vertical to vote with.

A stop the map could not place now takes its place from the walk’s own motion track, so the far side of the street is in the 11:34 tour (15 of 15 stops where 8 were). The rings step no longer refuses such a stop.

The people blur covered whole bodies and a lot of what the viewer wanted to see. By default people now stay in the picture as shot; faces, plates and printed names are blurred as before.

The per-day + is gone from the Record’s and a job’s day rows. The capture stack’s line, "Files to <job> · <day>", is a key: open, it lists his jobs nearest first — the one he stands at is marked and chosen by itself when nothing else is, so a photo on site never lands in Unfiled — the day an Upload lands on, and New job.

Said plainly: whether the X5 serves a file it is still writing is measured tonight on his phone, not before. If it refuses, the tail ends quietly and the copy after Stop runs as it did. Build 5 (1.4) carries it, as a test copy under its own address; the app everyone installs is unchanged until one real walk has gone through it.

Now the page hands the copy road the walks it shows waiting for the camera's file, and every card file the record matches to one of his streamed walks by when it began is brought in, the walk just saved first, then the ones on the page, then the newest. The phone's own memory of a walk matches by the file's name as well as its path. Connect means it, on any phone, after any reload.

Then, the same hour, his read of the first run: the copy's words sat at the foot of the page while the walk's own row still said press Connect, and the shop PC's line told him to press Connect with the X5 already connected. Now the copy and the send are said on the walk's own row with a bar, the walk after it says it is next, the Done lands on the row, and the line stops telling him to press a key he has pressed. Measured off the ledger: the 656 MB walk copied off the X5 in 23 seconds and took 148 seconds to send over cellular, because the camera holds the phone's Wi-Fi while it is connected. The send is the wait, and it is the next thing to take off his hands.

The landing's frame now takes the height left between the sentence and the foot — portrait on a phone, wide on a desktop — with everything still on one screen, and the page's own word over the viewer is gone. The Help pictures were refused by the page's policy twice over: the prelude that sends a tour's relative pictures to its storage folder was inserted before the page's first script, and the help markup comes before that script; and the shop PC never uploaded the guide/ pictures with a tour at all. The prelude now goes at the head of the page, the pictures ship with every tour, and the four live tours were re-served with both fixes.

The engine's viewer gained a Motion key on touch screens: the view turns with the phone the way a street view does. Off until pressed (iOS asks its permission inside the press), a drag still turns the view, no jump when it comes on, and "No sensor" when the phone has none. Every frame the app puts a tour in now hands the frame the motion sensors (gyroscope, accelerometer, magnetometer) beside fullscreen. Nothing here has met a real phone's sensors yet; the first turn of his Razr is the proof.

Said plainly for the record (CLAUDE.md, STOP IS THE LAST PRESS): the Android build 4 that copies and sends a walk in the background with the screen off is built and committed but not published — it goes out after one real run with his X5 — and whether Cloudflare R2 still refuses an upload was not measured tonight.

Now the copy of the walk just saved starts the moment the camera's last seconds have drained — no idle wait — and it goes before any older walk. The screen is held on from Stop to the last byte of the send, and asked for again whenever the page comes back. If the camera handed back no file name at Stop (it stopped on its own — a full card, a flat battery), the record's match by when the walk began still finds its file on the card.

If the X5 goes off or out of reach part way through, the walk is not failed: it waits, says so ("nothing is lost — the copy picks up by itself the next time the X5 is on and connected"), and is tried again on its own — in thirty seconds, at once when the page comes back to the glass, or whenever the camera is next connected here or on /x5. No press.

The words say what is happening and what he can do: "Saved. Copying the full-quality file off the X5 · 43% · about 2 min — keep the X5 on until this says done. You can put the phone away." The moment the file is off the card it says the X5 can go off, even while the upload runs over cellular; when it is in, "Done — the X5 can go off. The shop PC is building the tour." Not yet met on his Razr; the native foreground service that keeps the copy going with the app in the background is a separate build.

One line in lib/capture-model.ts carries it now, and tests/tour-model.spec.ts pins it: a queued walk stamped waitsFor reads "Waiting for the camera's full-quality file — open Walk with the X5 on and press Connect" on the Record, a job's page and the orb's toast, shop PC up or down. The walk itself needs the same press it needed before: Connect on the Walk page with the X5 on.

Opened, a day on a job’s page and on the Record now leads with ONE 96 px orb — the day’s newest walk in a thin halo ring, its count on the ball — and beside it the day’s walks as time pills, oldest first, the newest in ink; a press on a pill walks that one. Under the pills one line says where the tour stands and what goes with it (“Walk the tour › · 9 photos · 1 clip with it”), and the day’s grid follows. The small orb and the strip of squares step aside while the day is open (the grid is the photos) and come back when its line folds it.

Both pages draw the same block (DayRow.tsx OpenWalkOrb). The pills are 44 px — law 1 caught the first cut at 30. Pinned by tests/job-walks.spec.ts (a day walked twice) and tests/days-closed.spec.ts.

Now the line is the date and the street, and one soft line under the orb and the squares says what the day holds — “walked 2 times · 9 photos · 1 clip” — with anything still on its way beside it. The same block on the Record and on a job’s page.

The + on a day is a menu now: add photos, write a note onto that day, add a link, and on a job's page add a job doc — the four ways that used to live at the foot of the job. The address, Directions and who is on the job moved to the top of the page, and the people show on the front's rows and the Record's days too.

In the People sheet, 'How Sergio sees it' draws the job as that member sees it — nothing to rename, move or delete. The profile opens on his work: tours as orbs, jobs as rows, the crew as faces, then the photos.

Behind the glass: the full production build runs on the shop PC again and is the gate before every push — it catches what the nine failed deploys since October 14 died of. Vercel's deployment retention is a day for anything but production, a week for production.

While it waits the app says so in one sentence everywhere the walk shows — the Record's row, the Walk page, the shop PC's status line: the camera's full-quality file is still on the X5, open Walk with the X5 on and press Connect. The file then comes in by itself and the shop PC builds the tour from it.

The Walk page is simpler. The shop PC's own line is the first thing under the title — what it is building, the step, the minutes left, who is in line — with only the walks still on their way under it. The list of finished tours is gone from this page; a tour is the walk's orb on the Record and on its job. Where a walk files now has a day as well as a job: a recording or an import made today of Tuesday's walk goes on Tuesday.

The capture key now wears its destination over it, 'Vitronic · today', changing as you move through the app, so nothing goes in on faith. (Second deploy: the first build failed on Vercel.)

The stacked orbs and the chapters from earlier tonight are gone. The owner: "a walk should be a static thing for a day, but there can just be different times."

Opened, the day reads as chapters: each walk a wide card that opens its tour, with the photos taken during that walk under it. What was taken outside any walk comes last. The photos feed the walk; the walk is the frame.

The owner asked for it after a photo added at 8:05 PM went to the wrong day.

The capture key says where it files before the press: the job, and today. The adding toast says the day too.