THE THREAD REGISTER — the contract this deck inherits from Wave 13. Wave 13's pages are one continuous 13,720px canvas: the golden thread leaves each page at exactly the y the next page enters. That is what let the film be a camera travelling the thread rather than a sequence of cuts. See videos/smart-safety-thread/METHOD.md §0. V1.2 keeps the contract. Every page below declares `enter -> exit`, and each page's enter MUST equal the previous page's exit. Break a join and the deck still renders — and the film can never be cut from it again. The running band is 404–414: below the body (which ends at 400) and above the gain panel (which starts at 420), so the thread is visible on every page rather than buried behind a card. Re-derived twice on 2026-08-19. The deck went 27 -> 31 -> 32 pages: the site visit came out entirely, the feedback page moved from the front to the back on the owner's ruling that a deck opens on its own thesis, and module seven became three capability pages with the screens they render. The joins below chain exactly; the pages that actually DRAW the thread are the cover, "known, guided and protected", and the close, and none of those moved. 01 cover ->300 17 V job-pack 407->407 02 where we are 300->412 18 V drawing-read 407->406 03 Where the next 412->412 19 No extra proces406->406 04 group briefing 412->411 20 job-aware 406->405 05 known/guided 411->411 21 V point-of-works405->405 06 One fair pictur411->411 22 V vision-test 405->405 07 V safety-cv 411->410 23 What management405->404 08 V mini-module 410->410 24 V agent-queue 404->404 09 Nobody is penal410->409 25 V gang-roster 404->398 10 worker fix 409->409 26 V boundary 398->391 11 V finding-fix 409->409 27 Three more, bui391->385 12 the chain 409->408 28 F competencies 385->379 13 Colin 408->408 29 F handover 379->373 14 V colin-ask 408->408 30 F van brief 373->366 15 V colin-sources408->407 31 what came back 366->360 16 V colin-declines407->407 32 close 360-> Wave 13's cover, continued: the thread lays itself down and the worker ignites at its origin — the first cause in the film. No audience named and no client logo. A bespoke cover reads as a sales artefact to an innovation team, and the product is already sold.
On ALS gangs now, on real jobs. Almost everything in this deck.
In daily use, and being measured.
The bar is to scale: this is mostly a live product, and the proportion is the point. Say the three words out loud — after this, nothing later has to hedge. The direct answer to the health and safety manager who read Wave 13 and could not see the safety. The rail carries a third segment for module seven: three capabilities that are built and rendering and are not yet in use on gangs. The segment is small on purpose and it is the honest proportion — say it out loud rather than letting anyone find it.
Wave 13 opened here and so does this one — the room saw this figure in July. TONE, and it matters: this is NOT a criticism of the toolbox talk. Say out loud that the group briefing works, that it is the floor, and that we sit above it. The argument is additive. A room that hears "your current method is failing" stops listening, and they would be right to.
Wave 13's second page, kept. The three nodes sit ON the thread because they are the three things it carries. Glass-half-full: group safety got us here. We are not saying it failed; we are saying the next gain is somewhere else.
FULL BLEED. videos/ui-safety-cv — 26s. One record, three readers: what the worker sees, what the supervisor sees, what the regulator sees. The line to land is that the lowest band tells a supervisor "read the evidence below before you speak to them" — a prompt to go and talk, not a verdict to deliver.
FULL BLEED. videos/ui-mini-module — 26s. Three phones: it arrives, it runs, the points come back. +6 recovered, and the flat statement that a mini module can only give points back, never take them away. The words are "mini module" throughout, including the status bar. Never assessment, test or quiz. Claim boundary held on screen: "A change in the job's status sends it, on a cadence — no one has to remember to." That is automatic issuance and nothing more. Nothing implies the module was chosen from the worker's own record.
Say "mini module" and never assessment, test or quiz. A surface that reads as a test is the same product with the opposite effect.
FULL BLEED. videos/ui-finding-fix — 26s. Amber, blue, green: the check flags before submit, the crew answer in their own words, the supervisor approves. "Cautious machine. Human decision. Both on the record." This is the deck's real thesis in one screen — the machine is correctly refusing to assume something it was never told, and the human who knows decides. Do not narrate over it.
The finding is right. The crew corrects the work, or the sheet.
The finding is wrong, and obviously so. It closes, and clears the deduction.
Contested, not obvious. It closes nothing and a director rules on it.
Say the backed-the-gang beat out loud: when a supervisor backs their gang, the product shows they tried — whatever the outcome, and no score moves. It is the answer to the surveillance objection, before it is asked. The gang's performance feeding the supervisor's own score is NOT built. Do not claim it. If it comes up, it is direction.
FULL BLEED. videos/ui-colin-ask — 22s, 1920x1080. The render carries its own title: "A question in your own words, answered from the approved source." It is a finished slide. Do not add a headline over it and do not narrate it — the words for this beat are on the next page. HOLD on the cited source opening: UKPN DSR 01 014 · V9.0 — §8.10 Mechanical Excavators. That is the beat nobody expects.
The provenance beat. It answers the question the room asks after the hero slide — "yes, but where does it get that from?" — before anyone has to. The screen carries the figures and the date it was verified. READ THEM OFF THE SCREEN; do not quote a count from memory. This slide's numbers have already moved once inside a week — the previous figure came off a pipeline that was retired on 21 July — and this is the one slide where being wrong about a number costs the whole argument. The point to make out loud is not the size of the corpus. It is that one answer opened: the verbatim clause, the version, the page, and held in the UK.
FULL BLEED. videos/ui-colin-declines — 26s. The credibility beat, and the one the room least expects. The refusal lands at 8s and the three fallback rows get nine seconds — each on its own beat, then a highlight stepping down them so they read as live controls rather than a static list. Let it play. Do not narrate. The half that matters is the second half: it does not just decline, it hands the worker the questions it CAN answer.
FULL BLEED. ui-job-pack-sorted, 24s, 1920x1080. Real job: JOB-4471, 220 documents. The render names the CRM type-id defect on screen — type 1177 filed 195 as drawings, type 933 the same documents one letter apart put 25 in Other.
FULL BLEED. videos/ui-drawing-read — 26s. The sheet is drawn from scratch in SVG and its title block reads SYNTHETIC EXAMPLE SHEET / NOT A REAL SITE. No real as-laid was opened or cropped, which is the only safe way to show this. The argument builds in order: all the text is in the title block, then the 2 lands, then the cable run lights up as read from the drawing. The answer is badged "Read from the drawing, not quoted", carries a stated confidence, and the CAT-and-verify line sits INSIDE the answer at answer size. It closes on the boundary: a drawing can describe a route, never a depth or a position — those are refused outright however clear the sheet looks.
This module answers the objection every crew and every supervisor raises first, and it was missing from the first draft entirely.
The checks fire on WHAT THE CREW DECLARED. PPE is read every time; the rest only when it applies. Two things arm a check, and the order matters. The sheet's own answers arm it — that is live for every gang and it is the left-hand column. The job pack then modulates the ladder check where a VERIFIED depth card exists for that job: past 1.2 m the depth is stated beside the verdict, below it the check quietens with its reason. That read is per tenant and OFF by default, and off means today's behaviour byte for byte — no card, no change. The sentence on this page is the check's own, from its first firing. Read it off the slide; do not paraphrase a depth from memory.
FULL BLEED. videos/ui-point-of-works — 26s. The sheet asks six questions and arms four checks. Excavation Access answered No, so the ladder check reads "not needed" — the job-aware point shown rather than claimed. "Five checks, and a sheet only runs the ones its own answers arm. No extra photographs, no extra steps."
FULL BLEED. videos/ui-vision-test — 19s. The only slide in the deck that shows the AI being MEASURED rather than described. Everything on it is structural and real; there are deliberately no accuracy figures, because the ones we hold were scored against a model that is no longer the primary and a stale number on a slide about measurement is the own goal that undoes the slide. The beat to land is the asymmetry, and the gate's rule is stronger than "weighted differently": claiming a control is there when the photograph shows it is not is TOLERATED: NONE, EVER — and a dangerous verdict is re-run three times in isolation before a release may proceed. The cheap error costs somebody thirty seconds and sits inside a measured band. Also worth saying: four cases exist where the same subject has opposite known answers. A ladder IN the excavation is Present; the same ladder lying on the grass beside it is Absent. A lazy reader says Present to both. To add figures later: run `als powa vision-eval --execute` against the current primary and quote the number WITH its measurement date.
The module Brad asked about by name. It is the one he expects them to like.
A supervisor, at their own gangs. There is no control on this page that sees wider.
Allocated each corrective action to the gang that has to clear it.
Every one carries the day it is due — today, tomorrow, Friday, or already overdue.
This page was a full-bleed render for its whole life and the owner read it as unchanged twice, because everything it said was inside the picture. It is now three facts in type with the screen as evidence. Say the three out loud in order and stop: whose screen it is, what they have done with it, and that every line carries a day. The two windows are the last seven days and everything still open — that distinction is on the card if anyone asks, and it is not worth saying unprompted. The absence still matters and is still worth one sentence: there is no "show everyone" control on this page. Anywhere.
FULL BLEED. videos/ui-gang-roster — 26s. The last of the twelve. One continuous movement, no cut: the row you pick is still the row at the top when the record opens beneath it. That is the argument made structurally — it is the SAME record, read one level up, not a second screen that could disagree. The line to land is on screen: "Every line here is a line the worker can already open on their own phone, with the same evidence behind it. There is no figure on this screen they cannot see." Hierarchy is correct here: the roster shows Operatives and Labourers, and the labourers' readiness reads "builds a record from observations and training, not sheets" — a labourer carries a record without filing a Point of Works. PII: demonstration data, and the card header says so in frame.
FULL BLEED. videos/ui-boundary — 24s. What leaves and what never does, side by side — and the rule that makes it safe: below a minimum number of workers the figure is not released at all, because in a small crew a count is a name.
These are capabilities, not requests, and they are not an appendix — say the module title and go straight into the screens. Each page carries the `next` mark, which this deck defines as built and rendering, not yet in use on gangs. Do not upgrade that to "live" in the room: two of the three are open pull requests tonight, and the third has no human-facing surface at all.
The Point of Works already asks whether you hold the training for the work. Now it answers alongside you: this job is recorded as trial holes, and work like that usually needs deep excavation and cable avoidance — set against the tickets you actually hold, each with the date it runs to.
A worker sees their own record and nobody else’s. Nothing here blocks starting work — it puts the gap in front of the one person who can do something about it.
Demonstration data: a harness persona, not a real worker. Behind a per-tenant flag, off by default, and the table of what a job requires is drafted and not yet signed off.
The frame is an unretouched screenshot from a verification run driving a real
browser against the built branch through a real sign-in. It is the app, not a
mock-up — say so if anyone asks, and say "demonstration data" in the same
breath.
The line NOT to cross: the requirement mapping is a draft. Most of its rows read
"provisional" and only five restate a ticket somebody has already priced.
"Built and rendering" is true. "Agreed", "approved" or "in use with real crews"
is not, and this is the room that would hold us to it.
IF SOMEBODY ASKS WHICH REGULATION SAYS A TRIAL HOLE NEEDS DEEP-EXCAVATION
TRAINING — and in this room somebody might — the answer is "none that we hold".
Say it plainly. The mapping was derived against the 137 approved clauses in our
corpus and the two tickets on this screen do NOT come out the same:
cable avoidance NAMED. HSG47 paras 80-90 — anyone using a locator should
have had thorough training in its use and its limitations.
deep excavation NOT NAMED. SROH requires a designed side-support system in
soft or loose ground and UKPN DSR 01 014 requires a
technically competent person to issue the method statement
that sets the competency. Both govern the WORK. Neither
names the ticket, and the trial-hole link is our
operational reading. It is with Brad for sign-off.
The stronger regulatory story, if you want one, is the substation case rather
than this screen: UKPN's own HSS 40 046 §8.1 admits a person to a substation
operational area only where their competency includes "Enter Substations and
Avoid Danger Inside". That is their document, their words, and their own
example from the site visit — the product reading their rule back to them. It
is a talking point, not what the screenshot shows.A crew leaving a job leaves what the next crew needs — where not to park, the gate code that changed on Tuesday. It opens with the job, and each reader clears it from their own screen when they have taken it in.
The byline carries the gang and the day, never a person’s name. The product gained a direction, not a form: the chain ran up to the office and down to a worker, and a note to the next crew is neither.
Demonstration data: the shipping component rendered from the real stylesheet at phone width, not a capture of the running app. Built, and not yet deployed.
Naming the gang and not the worker is a design decision, not an omission: putting one person's name on "the woman down the road is a nightmare" turns a handover into an attribution nobody asked for. It is written down in ADR-0043. The same ADR is why this is not folded into observations — those are safety evidence in the Ofgem-facing corpus and their reader is the office. A note to the next crew has a different reader, so it got its own instrument.
A job pack ingests. The brief’s facts come off its hand-verified drawing cards and its Construction Phase Plan, a script is built, and a clip is minted and stored durably — proved end to end against a real pack, not a fixture.
The clip on this page is that output, not a mock-up of it — the brief for a real job, in the voice a crew would hear on the way to it. The point is a crew that arrives having heard the brief rather than having meant to read it.
The minting runs behind a per-tenant flag, off by default. The player a crew taps is written and not deployed — there is nothing a crew can tap today.
PLAY IT. This is the one page in the deck with sound, and the clip is the approved take for job 1628945 — verified by size and duration against the approved fingerprint before it was embedded. It does not start on its own: a voice that begins because somebody scrolled is a voice talking over you. Do not name the voice vendor. Two minutes is a long time in a room. Play the opening twenty or thirty seconds, then hold it with the badge and talk over the still — the waveform makes the pause legible, which is why it is drawn rather than left as a black box. What is true if pressed: the pipeline mints this from the pack's own verified drawing cards and its Construction Phase Plan. "IS IT RUNNING ON OUR JOBS TODAY?" — not yet, and say so. The minting is proved on staging against ONE real pack, job 1628945, which is the clip on this page. It has not run against the live pilot's packs. The caption names that job for exactly this reason: it is one pack, and the number is on the slide rather than hidden behind "a real job". Be precise about the flag, because the loose version stops being true next week. The MINTING is tenant-scoped and off by default (ALS_JOBPACK_BRIEFING). The serving route is not flag-gated at all — it simply has nothing to serve outside staging. So the caution to state is not "it is all behind a flag": it is that the crew-facing play control is written, unmerged, and not deployed. Nothing a crew can tap exists.
From the recorded debrief after the visit. These are the workforce’s words, tightened — do not read them as a testimonial and do not attribute them to a named person in the room. This page opened the deck until the owner moved it here, and the ruling is worth keeping in mind if anyone asks to promote it again: a deck opens on its own thesis, not on what somebody thought of it. It earns more at the back anyway — the room has now watched the finding page, the chain, the mini module and module seven, so each sentence lands as a verdict on something seen rather than as a promise about something coming. Land the third one and stop. There is no ask after it; the next page is the close.
The thread completes the run it began on the cover, and rests on a single lit node. Wave 13's close, word for word: the room heard it in July, and it should end the same way having now been SHOWN that each clause is true. No commercial ask. The product is sold — this was an explanation, not a pitch.