HALOS statics: what a blind second-model polish pass does to Diego's drafts

First fixation: headline   Cold read: A stranger reads a body-worn camera with a panic alert for a lone security officer; the camera image and the lone-worker headline tell the same story, and the subhead closes the loop on what the device does.

• P1 background / logo band: A visible tonal seam runs across the frame at roughly 11 percent of the height, directly under the logo; the top band is a flatter, slightly different dark than the gradient below it and reads as two pasted plates. Fix: Make the ground one continuous dark gradient from top edge to bottom edge with no horizontal step behind the logo.
• P1 product / bottom margin: The camera's base sits inside the bottom 12 percent of the frame with only about 3 percent of clearance to the frame edge; platform chrome will clip the bottom of the device. Fix: Raise and scale the product so its lowest point clears the bottom 12 percent, leaving a clean margin below it.
• P2 product scale: The device fills roughly 60 percent of the frame width and 62 percent of the height, noticeably heavier than the designer sheet's product scale, so it pulls against the headline for first fixation. Fix: Reduce the product to about 45 to 50 percent of the frame width so the headline clearly wins and the composition breathes.
• P2 subhead: The bold white emphasis begins mid-line after 'supervisor', leaving one grey word stranded at the start of line 2 and a ragged weight change. Fix: Rebreak the subhead so the bold phrase starts on its own line or the whole second line carries one weight, without changing any words.
• P2 logo: The top wordmark is small relative to the headline and the oversized product, and it floats in a large empty band. Fix: Scale the wordmark up modestly (about 20 percent) and tighten the space above the headline so the top zone does not read as empty.

Language flags (for a human, never applied):

• Nobody knows until they call. On a cold read 'they' can attach to 'Nobody' as easily as to 'officer', so the line briefly reads as if nobody is the one calling. Alternative: Nobody knows until the officer calls.

First fixation: Product camera with glowing blue LED ring, centered (FAILS, competes with Headline 'People behave differently when the camera is visible.')   Cold read: A stranger reads this as a chest-worn body camera for security and frontline staff whose visible presence deters incidents. Picture and headline agree: four workers wear the device on the chest and the hero product shows what it is. The subhead's 'after one' is the only stumble.

• P1 subhead: Subhead wraps to a two-word orphan 'after one.' on its own line, producing an awkward shape and a stalled read. Fix: Rebreak the subhead so the two lines are near-equal: 'Fewer incidents on the shift,' then 'not just better evidence after one.'
• P1 chips / product: The four white chips sit directly on top of the lower third of the product, covering the bottom panel of the camera; the product is obscured rather than cut off, but the chips and hardware collide. Fix: Scale the product down about 15 percent and raise it so its bottom edge clears the chip block, or drop the chip block below the product with clear air between them (while staying out of the bottom 12 percent).
• P1 chips: Second chip row (Uploads itself, Proof of presence) sits at roughly 85 to 90 percent of frame height, inside the bottom 12 percent that platform chrome covers. Fix: Lift the whole chip block so its lowest edge sits at or above 86 percent of frame height.
• P1 hierarchy: The oversized glowing product and the heavy headline compete for first fixation; the product wins on size and colour, the headline carries the message. Fix: Reduce product scale so its width is about 40 percent of frame width, keep the headline at its current weight and size so it lands first.
• P2 chips: Chip rows are uneven: row 1 is wider than row 2, chips are staggered rather than aligned on a grid, and the four leading icons are four different glyph styles (filled ring, dot, arrow, hollow ring). Fix: Set the four chips in a tidy two-by-two grid with equal chip widths, equal gutters, and one consistent icon style in orange.
• P2 photo panels: The four floating photo panels are asymmetrical in size and angle (top-left much larger than top-right; bottom-left and bottom-right at different heights), which reads as unintended rather than composed. Fix: Mirror the left and right panel pairs so sizes, heights and perspective angles match.
• P2 background: A faint lighter horizontal band runs across the top 4 percent of the frame behind the logo, reading as a banding seam. Fix: Make the background gradient continuous with no visible band at the top edge.

Language flags (for a human, never applied):

• Fewer incidents on the shift, not just better evidence after one. 'after one' forces the reader to back-resolve 'one' to 'incident'; on a cold three-second read it stalls. Alternative: Fewer incidents on the shift, not just better evidence after an incident.
• Proof of presence Slightly abstract next to three concrete feature chips; a reader may not know whose presence or presence where. Alternative: Proof the guard was there

First fixation: headline   Cold read: A camera with a lens and a wearer-focused subhead reads as a body-worn camera; the headline plus the panic and man-down rows make the problem (a worker alone in trouble, help summoned instantly) clear. The subhead's office-versus-wearer contrast is the only line that takes a second read.

• P1 feature rows / product: The feature column's left edge and its divider rules butt directly against the product's right ridged edge; the text and rules appear to touch the chassis with no gutter. Fix: Scale the product down roughly eight percent or shift it left so a clear gutter of at least 40 pixels separates the chassis from the arrows, titles and divider rules.
• P2 feature row bodies: Two descriptions wrap into a single-word or two-word orphan line (alarm; they press it), which makes the row rhythm uneven. Fix: Widen the column slightly or nudge the wrap so each two-line description breaks into two balanced lines.
• P2 lower frame: The feature block ends at roughly 73 percent of frame height and the product base at 84 percent, leaving the bottom fifth as empty floor while the top is dense; the composition reads slightly top-heavy. Fix: Add a little more air between subhead and the product/feature group and let the group sit fractionally lower, keeping everything above the bottom 12 percent.
• P2 product: The blue LED ring is flat and unlit compared with the designer bar, where the ring emits a soft glow and anchors the product. Fix: Add a subtle blue glow around the ring and a faint blue floor reflection under the product.

Language flags (for a human, never applied):

• What the person wearing it gets. Not what the office gets. On a cold read the office-versus-wearer contrast is not immediately clear; a stranger may not know what the office would normally get. Alternative: Protection for the person wearing it, not just a record for the office.

First fixation: headline (FAILS, competes with blue LED ring on the camera)   Cold read: The visible lens and ring read as a body-worn camera, and the body copy bridges to lone-officer response. The headline alone reads as a retention or HR message, so picture and headline tell slightly different stories until the third paragraph resolves it.

• P0 product: The camera is cut off by the bottom frame edge and its left side runs behind the body copy; only the upper two thirds of the device are visible. Fix: Scale the camera so the full chassis sits inside the frame in the lower-right, with clear air between it and the text column.
• P1 body paragraph 2 and 3: Body copy overlaps the product: 'Every camera in range recording.' runs across the lens panel and lens, and 'Nobody writes that on a' crosses the chassis top edge. Grey text over glossy black and reflective pixels loses contrast. Fix: Keep all body lines on the plain dark ground; either narrow the text column to roughly 55 percent of frame width or move the camera down and right so no text touches it.
• P1 logo: The HALOS wordmark sits at roughly 93 percent of frame height, inside the bottom 12 percent that platform chrome covers. Fix: Raise the wordmark so its baseline sits above the 88 percent line, keeping its left alignment with the text column.
• P1 body: Three paragraphs of small grey regular-weight copy at roughly 2 percent of frame height per line will be hard to read at phone size, and the mixed regular plus bold within paragraphs adds visual noise. Fix: Increase body size and line spacing slightly and lighten the grey toward white; keep the two bold sentences bold, everything else regular.
• P2 margins: About 13 percent of dead space above the headline while the lower half is congested; the vertical balance is top-heavy in emptiness and bottom-heavy in content. Fix: Shift the whole text block up so the headline starts near 9 percent from the top, freeing room below for the product.
• P2 hierarchy: The saturated blue ring is large and bright enough to pull first fixation away from the headline. Fix: Reduce the camera so the ring is smaller than the headline block, and keep the headline the brightest white on the frame.

Language flags (for a human, never applied):

• They quit over the night nobody came. On a cold read 'came' has no destination; the reader has to infer 'came to help'. Alternative: They quit over the night nobody came to help.
• People go after the shift where something happened 'Go' as a verb for quitting is ambiguous next to 'shift'; it can read as going to work. Alternative: People leave after the shift where something happened
• That’s the post you don’t have to fill twice. 'Post' can read as a job posting or a guard post; the double meaning slows the payoff. Alternative: That’s the position you don’t have to fill twice.

First fixation: headline   Cold read: A stranger sees a body camera with review software on a monitor, a split between dusty paperwork and a clean footage workflow, and a headline about complaints costing the same whether true or false. Product (body-worn camera plus footage platform) and problem (unverifiable complaints that get settled by process instead of proof) both land. Picture and headline tell the same story.

• P1 left column label: WITHOUT FOOTAGE is mid-grey text laid over the brightest pixels on the left half (white mug, handset, paper). Weak contrast on busy pixels; will not survive phone size. Fix: Render the label in white or a light warm grey at the same weight as WITH HALOS, and add a soft dark scrim or move the desk objects so the label sits on plain dark ground.
• P1 right column label and chip stack: WITH HALOS is drawn across the camera's lower body, and the four blue chips cover the bottom third of the camera. Text overlaps the product and the product is partially hidden. Fix: Scale the camera down roughly ten percent and raise it so its full body is visible with its base just above the WITH HALOS label; the label and chips must clear the hardware entirely. There is roughly eight percent of spare floor above the protected bottom band to absorb the shift.
• P2 headline: The right half of both headline lines crosses the blurred monitor and its bezel; contrast holds but the ground is busier than on the left half. Fix: Darken or blur the monitor region behind the headline slightly so both halves read on a comparable ground.
• P2 bottom band: Around sixteen percent of the frame below the chips is empty floor, more than the protected twelve percent, which makes the middle of the layout feel compressed while the bottom is slack. Fix: Use the slack to give the camera and labels breathing room (see the P1 fix); keep the bottom twelve percent clear.
• P2 product: LED ring reads slightly lighter and more cyan than the deep royal blue of the reference photo. Fix: Match the ring to the reference blue.

Language flags (for a human, never applied):

• One secure link, sent The comma makes the fragment read as a stray edit rather than a completed action on a cold read. Alternative: One secure link sent
• Settled inside the phone call Inside is an unusual preposition here and briefly reads as a technical feature of the call itself. Alternative: Settled on the first phone call

First fixation: headline   Cold read: A body-worn camera is plainly visible and the copy ('guard', 'prove it', 'records and uploads itself', 'invented complaint') tells a stranger this is a body camera for security teams that defends guards against false complaints. Picture and headline tell the same story.

• P1 footer logo: The HALOS wordmark sits at roughly y=1265 of 1350, fully inside the bottom 12 percent that platform chrome covers; the brand mark will be hidden in feed. Fix: Lift the wordmark so its baseline sits at or above the 85 percent line, aligned to the left text margin, or move it to the top left above the headline.
• P1 product: The camera's lower third extends below the 88 percent line and its bottom edge comes within about 60 px of the frame bottom; the lower body and mount get covered by chrome and the product reads as sinking out of frame. Fix: Raise the product so its bottom edge clears the bottom 12 percent with a visible margin, keeping it in the lower right.
• P2 composition: The bottom-left quadrant is an empty near-black dead zone; the layout is top-heavy with text and bottom-right heavy with product, leaving an unbalanced void. Fix: Scale the product up slightly and shift it left toward centre-right so it occupies roughly 50 percent of the frame width, filling the void without touching the text block.
• P2 product: The chassis is underlit; the left ridged flank and lower body merge into the background so the silhouette is lost, unlike the designer sheet where a rim light separates the product. Fix: Add a soft cool rim light along the left and top edges of the camera and a faint blue glow spill from the ring so the silhouette separates from the ground.
• P2 product: The lens on the top panel is rendered as a smeared highlight rather than a clear round glass element with concentric rings as in the reference photo. Fix: Render the lens as a crisp circular glass element with concentric inner rings and a small specular highlight, matching the reference.
• P2 body copy: Three paragraphs of light-grey body copy on near-black at about 30 px cap height will be dense and borderline legible at phone size; the grey is a step darker than needed. Fix: Lift the body grey one step lighter and increase body size by about 10 percent, keeping the same line breaks and emphasis pattern; do not change any words.

Language flags (for a human, never applied):

• Every shift records and uploads itself. On a cold read the subject is odd: a shift does not record; the camera does. A stranger may stumble before understanding it means automatic recording and upload. Alternative: Every shift is recorded and uploaded automatically.

First fixation: headline   Cold read: A stranger reads this as a body-worn camera plus companion cloud/search software for a service business (security, field service) that needs to retrieve and share footage fast; picture and headline tell the same story.

• P1 callout chip 1 / product: The 'Uploads when the shift ends' pill overlaps the ridged right edge of the camera body instead of sitting clear of it. Fix: Shift the pill left or down so there is a visible gap between it and the product, matching the clean separation the other three chips have from the hardware.
• P1 subhead / monitor mockup: The last line of the subhead ('the original.') sits almost flush against the top edge of the monitor bezel behind it, with no breathing room. Fix: Add vertical spacing between the bottom of the subhead block and the top of the monitor, or nudge the monitor down slightly.
• P2 hierarchy / product: The saturated blue LED ring is bright enough to pull a second, competing fixation against the headline on a cold three-second read, even though the headline still wins. Fix: Slightly dial back the ring's bloom/brightness relative to the headline area, or increase headline scale a touch, to widen the margin of victory.
• P2 monitor mockup / left nav: The dashboard's left-nav text is blurred past legibility, and the first two rows appear to show the same label twice (one plain, one highlighted), which reads as a possible duplicated nav item. Fix: Confirm the source UI asset uses distinct nav labels, or intentionally simplify the background chrome so it doesn't imply duplicated content even at a glance.
• P2 logo (top) / brand fidelity: The wordmark's O renders as a single-tone thin orange ring rather than the reference file's three-arc grey / white / red-orange halo motif, so fine brand detail is lost at this scale. Fix: Rebuild the logo O to match the reference file's layered arc treatment rather than a flattened single-color ring.
• P2 product scale: Against the designer sheet's bar, the camera reads slightly smaller and more offset than the confident, larger hero placements used there. Fix: Consider enlarging the product modestly or centering it a touch more within its zone for a stronger anchor.

Language flags (for a human, never applied):

• You keep the original. On a cold read it is not immediately obvious whether 'the original' refers to the raw footage file, ownership rights, or the physical clip, since no prior sentence establishes what is being duplicated or shared. Alternative: You keep the original footage.

First fixation: headline $97,000+   Cold read: The ridged black device with the blue ring and the chips about uploading and logging views read as a body-worn camera with evidence management. The dollar figure ties to liability claims, but a stranger has to work through three sentences to connect a camera to a claim; the picture and headline tell two stories until the last line.

• P0 product: The camera is cut off by a hard vertical edge at roughly 91 percent of the frame width, and a flat dark column runs the full height of the frame to the right of it. Only the left half of the device shows; the badge reads HA and the lens panel is clipped. This looks like a canvas or compositing artifact that shipped in the art. Fix: Remove the dark right-hand column so the background gradient runs edge to edge, and bring the whole camera inside the frame with clear margin on all sides.
• P1 chip bar: The orange bar overlaps the bottom of the product and is a large saturated mass that pulls the eye away from the headline; it is the strongest second fixation on the page. Fix: Sit the bar below the product with a clear gap, reduce its height and width so it reads as a feature strip rather than a button, and keep it above the bottom 12 percent.
• P1 composition: Roughly the middle third of the frame on the left is empty dark background between the subhead and the chip bar, while the product is crammed against the right edge. Balance is far below the designer sheet, where the product is centred and fully visible. Fix: Centre the camera in the band between subhead and chip bar so it fills about 45 percent of the frame width, and let the background gradient and floor reflection sit behind it.
• P1 subhead: Emphasis is inverted: the source attribution sentence is bold white, the two sentences that carry the story are light grey. On a phone the eye reads the disclaimer first. Fix: Set the whole subhead in a single regular weight and one light grey tone so the sentences read in order; if any emphasis is kept, keep it minimal and consistent.
• P2 logo: Wordmark is small and sits with a generous gap above the headline; the designer sheet runs the mark a touch larger with tighter rhythm to the headline. Fix: Scale the wordmark up slightly and close the gap to the headline so the top block reads as one unit.
• P2 subhead: Three lines at this size will be readable on a phone but the line length is long and the paragraph runs close to the headline width; small text is at the edge of comfortable. Fix: Slightly increase the subhead size and tighten the measure so line lengths stay balanced.

Language flags (for a human, never applied):

• Industry data, National Small Business Risk Index, not a HALOS figure. A footnote-style source citation placed mid-paragraph interrupts the argument and, on a cold read, sounds like the brand is distancing itself from its own headline. Alternative: Source: National Small Business Risk Index.
• the first claim they don't lose Losing a claim is ambiguous for a reader who does not think in insurance terms; it is unclear whether the claim is against them or made by them. Alternative: the first claim they beat

First fixation: headline 'Not everyone is as honest as they say they are.'   Cold read: The camera with the blue ring reads as a body-worn camera at a glance, and the body copy makes clear the problem is fabricated complaints against officers. Picture and headline tell the same story, though the headline alone (without body) says nothing about cameras; the reader has to get to paragraph 3 for the product to be named as a mechanism.

• P1 body paragraph 3 / product: The last line 'handled. The invented ones stop working.' runs directly over the top-left corner of the camera; 'working.' overlaps the chassis edge. Fix: Lower the product or tighten the text block so there is a clear gap of at least one line-height between the final body line and the top of the camera.
• P1 footer logo: The HALOS wordmark sits at roughly 94 percent of frame height, inside the bottom 12 percent that platform chrome covers. Fix: Raise the wordmark so its baseline sits above the 88 percent line, or move it to the top-left above the headline where the designer exemplars place it.
• P1 composition: Large dead void in the bottom-left quadrant (below the body copy, left of the camera) while the top half is dense with text; the layout feels top-heavy and unbalanced. Fix: Scale the camera up and shift it left so it anchors the lower half, or shift the whole text block down so text and product share vertical space more evenly.
• P2 product: The camera is underexposed; the matte black chassis nearly merges with the background so only the blue ring and lens read. Ridged sides and silhouette are lost. Fix: Add a soft rim light along the left and top edges of the chassis so its outline separates from the ground, keeping the chassis matte black.
• P2 body: Bold emphasis runs start mid-line ('So you pay for...' and 'The honest complaints...') producing uneven texture; the body block is long for a static ad and the three paragraphs have slightly different measure widths. Fix: Keep the bold runs but align paragraph measures to a single consistent right edge; consider a slightly larger body size with the same line count.
• P2 bottom 12 percent / product: The base of the camera extends into the bottom 12 percent; not critical, but it will be partially covered by platform chrome. Fix: Lift the product so its base clears the 88 percent line.

Language flags (for a human, never applied):

• The invented ones stop working. On a cold read 'stop working' can be parsed as the complaints themselves malfunctioning rather than the tactic ceasing to pay off; the intended sense arrives only after re-reading. Alternative: The invented ones stop paying off.

First fixation: headline   Cold read: The device reads unmistakably as a body-worn camera and the headline names the pain (no footage, doubt falls on your own officer). Picture and words tell the same story.

• P1 product / bottom edge: The base of the camera and its floor reflection extend down to roughly 96 percent of frame height, so the grounding of the product sits inside the bottom 12 percent that platform chrome covers. The device will look chopped at the bottom on feed. Fix: Lift the product so its lowest point and the reflection sit above the 88 percent line, or scale it down about 8 percent while keeping it the dominant element.
• P2 background / logo band: There is a hard horizontal seam at about 10 percent of frame height where the flat near-black logo band meets the gradient below. It reads as a rendering artifact rather than an intentional header bar. Fix: Blend the top band into the body gradient so the ground is one continuous dark-to-blue-grey field behind the logo.
• P2 spacing: A tall empty band sits between the subhead and the top of the camera, larger than the headline-to-subhead gap, so the copy block floats slightly detached from the product. Fix: Tighten the gap so the camera top sits closer beneath the subhead, keeping clear air but making the copy and product read as one stack.
• P2 logo: Logo is small relative to the headline mass; it is legible but slightly timid against the designer sheet bar. Fix: Increase the wordmark by roughly 15 percent, keep it centred in the top band.

Language flags (for a human, never applied):

• takes your own team out of it On a cold read 'out of it' is loose; it takes a beat to resolve that 'it' means the argument rather than the incident or the team being removed. Alternative: takes your own team out of the argument

First fixation: headline   Cold read: A body-worn camera in front of a desktop review screen; headline names the problem (false complaints) and the subhead names the workflow (search, open, send a link). Picture and headline tell the same story.

• P1 frame: Visible letterbox bands: a flat dark strip runs along the top edge (roughly the first 30 px) and the bottom edge (roughly the last 45 px) where the scene does not fill the 4:5 frame, showing a hard seam Fix: Extend the scene to bleed to all four edges with no bands or seams
• P1 chip row: The second row of chips sits from about y 1145 to 1205 on a 1350 px frame; the bottom 12 percent starts at about y 1188, so the chips will be clipped by platform chrome Fix: Lift the whole 2x2 chip grid so its lowest edge sits above 88 percent of frame height, tightening the gap under the camera
• P1 subhead: Awkward wrap: the emphasised sentence begins with a lone bold 'The' at the end of line one and continues on line two Fix: Break so line one reads 'Search the shift, open the clip, send one link.' and line two reads 'The conversation ends there.'
• P2 chip row: Ragged left edge: row one left chip starts about 40 px further right than row two left chip, while the right column is aligned; the grid reads as two independently centred rows Fix: Set the four chips on a true grid with the left column left-aligned and the right column right-aligned, equal gutters
• P2 chip icons: Four different orange glyphs (dot, filled ring, diamond, concentric ring) with no shared logic Fix: Use one consistent small orange marker style across all four chips
• P2 subhead: The left third of the subhead sits over the brighter monitor thumbnails, reducing contrast versus the right side Fix: Deepen the blur and darken the monitor region directly behind the subhead so the text sits on a uniform dark ground
• P2 background monitor UI: The on-screen software is a dark-theme dashboard with a map; the real desktop software is a light-theme video grid, so the screen is only loosely plausible (mitigated by heavy blur) Fix: Keep it blurred and generic, or nudge it toward a light card grid of video thumbnails
• P2 hierarchy: The saturated blue ring pulls the eye almost as hard as the headline Fix: Slightly soften the ring glow bloom so the headline wins cleanly; do not change ring colour

Language flags (for a human, never applied):

• Proof of presence On a cold read it is unclear whose presence is being proven (the guard, the visitor, the incident) Alternative: Proof the guard was there
• Every view logged Could be read as every camera angle rather than every time someone plays back the footage Alternative: Every playback logged

First fixation: headline   Cold read: A rugged camera with a lens and a badge, plus rows that say 'clip', 'camera', 'audit trail', reads as a body-worn camera for staff. The headline and the 'They were never there' row make the problem clear: false complaints against people on the job. Picture and headline tell the same story.

• P0 product: The camera's left ridged flank runs off the left edge of the frame; the product silhouette is cut by the frame. Fix: Scale the camera down slightly or shift it right so its entire silhouette sits inside the frame with a clear margin from the left edge, keeping its current three-quarter angle and its position relative to the feature column.
• P1 feature rows: Three of the five benefit lines wrap a single word onto a second line ('did', 'it', 'device'), which makes the column ragged and looks like an unfinished layout. Fix: Widen the benefit column slightly or break each line earlier so that any second line carries at least two words; no benefit line should end with a one-word orphan.
• P2 composition: Roughly the bottom fifth of the frame is empty floor and reflection below the camera base, so the layout reads top-heavy against the designer sheet. Fix: Let the camera and feature column sit a little lower as a unit, or shorten the floor plane so the visual mass is closer to the vertical centre, while keeping the bottom 12 percent free of text.
• P2 product: The LED ring is a slightly muted, greyish blue compared with the saturated blue on the reference photo. Fix: Render the ring in the saturated, clean blue of the reference, with a soft glow, no colour shift toward grey or cyan.
• P2 logo: The top wordmark is small relative to the designer sheet, where it holds noticeably more width and anchors the top of the frame. Fix: Increase the wordmark to roughly a quarter of the frame width, centred, with the same clearance above the headline.

Language flags (for a human, never applied):

• "They were never there" doesn't survive it The pronoun 'it' has to be traced back to the row title 'Proof of presence', which a skimming reader may not do; the line reads stilted on its own. Alternative: "They were never there" doesn't survive the timestamp
• The client opens the same file you did On a cold read 'the client' is ambiguous: it could mean the reader's customer or a software client. Alternative: Your client opens the same file you did

First fixation: headline   Cold read: A stranger sees a rugged body-worn camera in front of monitors showing a video library, a dashboard and a map, and reads that the pain is retrieving footage, not capturing it. Picture and headline tell the same story; the subhead explains the mechanism (auto-upload, searchable by shift, location, incident).

• P1 headline: Three-line wrap leaves 'part.' orphaned alone on line 2, so the first sentence reads as a stutter and the block forms a lopsided shape (long, short, medium). Fix: Reflow to two lines with a break at the sentence boundary: line 1 'Recording was never the hard part.' then line 2 'Finding the clip is.' Tighten size slightly if needed so line 1 clears the side margins.
• P1 background screens: Left monitor shows placeholder strings ('MyBestClip', 'File Copy (mp4)') and three identical repeated thumbnails with identical '0:33' timestamps; these are semi-legible through the blur and read as unfinished set dressing. Fix: Keep the screens defocused but replace placeholder labels with illegible, non-repeating UI texture so no readable word survives the blur.
• P2 logo header: The top band behind the wordmark is a distinctly darker flat block with a hard horizontal seam at roughly the 8 percent line, separating it from the gradient below. Fix: Blend the header into the background gradient so there is no visible band edge behind the logo.
• P2 product / background: The centre dashboard monitor peeks out on both sides of the camera, creating busy edges around the product silhouette. Fix: Push the centre monitor further back or darker so the product edge reads clean against a calmer field.
• P2 product placement: The camera base sits at roughly 86 percent of frame height, just above the 12 percent chrome zone, leaving a large empty floor below and little breathing room above the crop line. Fix: Raise the product slightly (base at about 82 percent) and let the floor reflection carry into the safe zone.

Language flags (for a human, never applied):

• Footage uploads itself when the shift ends and lands searchable by shift, location and incident. 'lands searchable' is a slightly unusual construction; on a cold read some readers pause on 'lands'. Alternative: Footage uploads itself when the shift ends and arrives searchable by shift, location and incident.

First fixation: headline   Cold read: A stranger sees a drawer full of old body cameras on the left and one clean HALOS camera with a software screen on the right, and reads that this is a body camera whose footage is stored and findable rather than lost on cards. Picture and headline agree. One quiet contradiction: the right column says 'no dock' while the camera is sitting on a circular puck that reads like a dock.

• P1 right column label: 'THE HALOS VAULT' is placed over the camera body and the chip stack then occludes the bottom third of the product; the hero product is partly hidden by text and chips. Fix: Raise the camera or reduce its scale so its full silhouette clears the label and the first chip; put clear ground between the product's bottom edge and the label.
• P1 left column label: 'SD CARDS AND DRAWERS' is pale grey caps set over busy drawer pixels (cables, camera edges) with almost no contrast; it will not survive a phone screen. Fix: Set it in the same white weight as the right label and darken or blur the photo behind it so it reads instantly.
• P1 bottom band: A hard-edged flat navy strip runs across the bottom 6 percent of the frame, disconnected from the scene; it reads as a compositing artifact. Fix: Let the scene's ground fade smoothly to the bottom edge with no horizontal seam.
• P1 product staging: The camera rests on a circular puck that looks like a charging dock, directly above a chip reading 'Uploads itself, no dock'. Fix: Remove the puck; let the camera stand on the plain surface or float with a soft ground shadow.
• P2 background screen UI: The blurred software screen behind the camera carries fake label strings; it also mixes a map tile and a street photo in a layout unlike the real desktop software. Fix: Keep the screen heavily blurred and label-free, or make its layout resemble the real desktop video library grid.
• P2 spacing: Roughly 16 percent of the frame below the chip stack is empty dark ground while the top zone is comparatively tight; the composition feels bottom-heavy in dead space. Fix: Shift the whole content stack down slightly or enlarge the product so the vertical rhythm is even, keeping everything above the bottom 12 percent.
• P2 left column chips: Left chips are translucent over the drawer photo so cables and camera edges show through behind the text. Fix: Increase chip fill opacity a little so the text sits on a calm ground.

Language flags (for a human, never applied):

• Footage sits where it landed 'Where it landed' is figurative and a cold reader may not connect it to a memory card left in a drawer. Alternative: Footage stays on the card it was shot to

First fixation: Two-line white headline   Cold read: The camera with the blue ring plus the glowing folder and the word 'footage' make it clear this is a body-worn camera with a footage storage and retrieval service; the problem (getting your own footage out when you need it) reads from the headline and the five rows. The subhead 'None of this needs anyone to remember to do it' points forward to a list the reader has not reached yet, so it lands slightly before its referent, but it resolves once the rows are scanned.

• P1 feature_rows_4_and_5 / product: The last two feature rows collide with the camera. 'Every view, share and download logged' crosses the top edge of the chassis and 'Hours of disclosure work, done before lunch' runs straight over the lens and glossy top panel. Text over busy pixels and elements overlapping the product. Fix: Either raise the feature block into the empty band under the subhead and scale the camera and folder cluster down so the top of the camera sits clearly below the last divider rule, or move rows 4 and 5 so the whole list clears the product with a visible gap. No text may touch the hardware.
• P2 spacing: Uneven vertical rhythm: roughly 90 px of dead space between the subhead and the first feature row, while the rows themselves are packed tightly and then crash into the product. Leading between rows 4 and 5 is consumed by the camera. Fix: Close the gap under the subhead to match the row spacing, and use the recovered height to lift the list off the product.
• P2 background / logo band: A visible horizontal tonal seam runs across the frame just under the wordmark (around 7 percent from the top), making the logo look like it sits in a separate strip rather than on the same ground. Fix: Blend the top band into the background so the ground is one continuous gradient behind the wordmark.
• P2 composition: The right half of the frame between the subhead and the folder is empty while the left is dense with text, so the frame feels weighted to the lower-left and upper-left. Fix: Slightly enlarge the folder and camera cluster once it has been cleared of text, or narrow the list column so the layout balances.
• P2 divider rules: Hairline dividers run to about 94 percent of frame width while the text column sits at 6 percent from the left, so rules extend far past the longest line and past the point where the product starts. Fix: Shorten the rules to end at the text column's right edge, or at least stop them before the product's silhouette.

Language flags (for a human, never applied):

• Intelligence redaction On a cold read this parses as 'redaction of intelligence' rather than a smart or automated redaction feature; the noun-noun stack is ambiguous where the other four row titles are plain. Alternative: Intelligent redaction
• None of this needs anyone to remember to do it. 'This' has no referent yet because the list it describes comes after it; the sentence reads as a fragment until the rows are scanned. Alternative: Nothing below needs anyone to remember to do it.

First fixation: Hero number 35,000   Cold read: A stranger reads: a big volume of footage gets uploaded, secured and searchable, in a dark control-room setting with a surveillance dashboard. They will guess 'video evidence software' or 'CCTV platform'. They will not see that this is a body-worn camera: the device on the desk is roughly 6 percent of frame width, sits in shadow beside the mouse, and its badge and ring are unreadable. Picture says 'operations desk', headline says 'upload volume'; those agree, but the hardware is missing from the story.

• P0 product: The camera on the desk shows a pale grey-white ring around its badge, not the blue LED ring of the reference. The badge is too small to read as HALOS. Fix: Render the camera with a clearly blue LED ring and a legible centred HALOS badge, matching the product photo.
• P1 product: Product is a speck: about 6 percent of frame width, in shadow, half-hidden by the keyboard and mouse. On the designer sheet the camera is never smaller than roughly a third of the frame width. A cold viewer cannot identify a body-worn camera. Fix: Enlarge the camera to roughly 18 to 22 percent of frame width, standing upright on the desk in front of the monitor, lit by the screen glow so the ridged sides, lens and blue ring read at phone size.
• P1 subhead: 'Uploads a day.' is the unit of the hero number and is set in the dimmest tone on the ad, while the secondary clause is bold white. The meaning of 35,000 is subordinated to its own explanation. Fix: Set 'Uploads a day.' in the same bright white weight as the bold clause so number and unit read as one statement; leave line 2 in the lighter grey.
• P2 proof bar: Saturated orange block with heavy dark caps is visually heavier than the subhead and pulls the eye down before the scene and product are read. Fix: Keep the bar and its colour; reduce the label weight one step or slightly lower the bar's saturation so the hero number, subhead, then scene, then bar is the reading order.
• P2 logo: Wordmark is about 17 percent of frame width; designer exemplars run it near 27 percent. It reads as an afterthought above the giant number. Fix: Scale the wordmark up to roughly 24 to 27 percent of frame width, keep it top-centre with the same clearance.
• P2 scene: Second monitor on the right is a blank dark slab with its top edge cut by the subhead zone; the on-screen dashboard on the main monitor is pseudo-text. Fix: Give the second monitor a dim, subdued version of the same dashboard or keep it off but fully inside the frame; keep on-screen labels tiny enough that they never read as words.
• P2 spacing: Gap from subhead baseline to monitor top is about 35px while headline-to-subhead is generous; the monitor crowds the copy block. Bottom 15 percent of the frame is empty floor. Fix: Drop the desk scene about 20px so the monitor clears the subhead, keeping the proof bar above the bottom 12 percent.

Language flags (for a human, never applied):

• 250,000+ / SHARED IN CASE FILES No unit and no timeframe: 250,000 what, and over what period? Beside '1,000+ livestreams a day' the reader assumes a daily figure, which may not be intended. Alternative: 250,000+ / CLIPS SHARED IN CASE FILES
• ISO 27001:2022 / AES-256 ENCRYPTED Two separate proofs stacked in one cell read as a single compound claim ('ISO 27001:2022 AES-256 encrypted'). Alternative: ISO 27001:2022 CERTIFIED / AES-256 ENCRYPTED

First fixation: blue LED ring on the product (FAILS, competes with headline)   Cold read: The device is clearly a rugged camera; the lens and badge sell it. The headline signals contract bidding and proof, and the subhead names RFP accountability, so a stranger gets 'camera that helps you win bids by proving accountability'. The link from picture to headline needs one inference step and the second subhead line ('scores it like staffing ratios') is the weakest bridge.

• P0 product: The camera's bottom edge runs into the frame edge; the chassis is clipped at the bottom with no floor or margin visible beneath it (see bottom-left and bottom-right quadrants). Fix: Scale the product down and lift it so the full bottom edge is visible with clear ground beneath it.
• P1 subhead: Both subhead lines sit on top of the product: line 1 crosses the camera's top edge and the glossy lens panel, line 2 sits entirely on the lens panel. Text over busy, reflective pixels; grey line 1 loses contrast where it crosses the chassis edge. Fix: Move the product down so its top edge sits clearly below the subhead with a visible gap; keep all copy on the plain dark ground.
• P1 headline / product: The descenders of 'prove it.' nearly touch the camera's top edge. Fix: Same as above: create a clear band of dark ground between the last text line and the product.
• P1 hierarchy: The blue ring is the largest, most saturated element and takes first fixation ahead of the headline; the product fills roughly 70 percent of the frame width and 75 percent of the height, well beyond the product scale in the designer sheet. Fix: Reduce the product to about 55 to 60 percent of the frame width and tone the ring glow so the white headline reads first.
• P2 subhead: Line 1 is light grey regular, line 2 is white bold; the mixed weight and colour make the two lines read as two unrelated elements rather than one subhead. Fix: Set both lines in the same size and leading as one block; if emphasis is wanted, keep it to colour only, not a weight jump.
• P2 logo: Wordmark at the top is small relative to the headline and to logo scale in the designer sheet. Fix: Increase the wordmark by roughly 20 percent while keeping it centred.

Language flags (for a human, never applied):

• Procurement scores it like staffing ratios. On a cold read 'it' has no clear antecedent and 'staffing ratios' is procurement jargon that a general reader will not map to accountability; the line is meant to say accountability is now a scored criterion. Alternative: Procurement now scores accountability the way it scores staffing.
• One of them can prove it. 'it' is ambiguous: prove they are identical, or prove the claims in the bid. The intended meaning (prove what happened on shift) only arrives after reading the subhead. Alternative: One of them can prove what happened.

First fixation: headline (FAILS, competes with camera blue LED ring and glow, left third of frame)   Cold read: The camera is unmistakably a body-worn device and the feature rows (audit trail, role-based access, case files, ISO, storage) make it read as camera plus evidence platform sold to organisations answering bids. The headline and the picture tell the same story, but 'either' points to a comparison that is not on the image, so a stranger has a half-second of 'either what?'.

• P0 product: The camera is cut off by the left frame edge: roughly a third of the left side of the chassis (ridged flank and left edge of the lens panel) falls outside the frame. Fix: Pull the camera fully inside the frame with a clear margin of at least 4 percent of frame width on its left, scaling it down slightly if needed so the ring badge stays large.
• P1 composition: Bottom quarter of the frame is empty dark floor: feature rows end at about 75 percent of frame height and the camera base sits at about 73 percent, leaving a top-heavy layout with a dead band before the 12 percent chrome zone. Fix: Redistribute vertically so the camera and feature column both end at about 86 percent of frame height, with the camera ring badge and feature block sharing the middle band.
• P1 subhead vs product: The subhead is centred across the whole width and its left end sits directly on top of the camera's top edge with only a few pixels of gap, so the text and the hardware appear to touch. Fix: Keep the headline and subhead centred but drop the top of the camera so there is at least one subhead line-height of clear ground between the subhead baseline and the top of the chassis.
• P1 feature_row_3_body: Single-word orphan 'over' on its own line breaks the rhythm of the column. Fix: Set the feature column a little wider or the body size a touch smaller so each body line breaks as two balanced lines, no single-word last lines.
• P2 margins: Right-hand margin of the feature column (about 6 percent) is generous while the product has zero left margin; the frame reads lopsided. Fix: Match left and right side margins at about 5 to 6 percent once the camera is inside the frame.
• P2 feature column type: Body lines are set in light grey at a size that will read small on a phone; row titles and bodies are close in size, so the title-to-body step is soft. Fix: Raise body text one step in size and lift its grey toward near-white; keep titles bold so the step is decisive.
• P2 background: The cool grey wash behind the camera brightens the ground just where the camera's right edge meets the feature column and slightly dilutes the blue ring's contrast. Fix: Keep the gradient but hold the ground behind the ring and behind the feature column darker and more even.

Language flags (for a human, never applied):

• Procurement doesn't take your word for it either. 'either' implies a prior party or comparison that is not on the image, so a cold reader stalls on what it refers to. Alternative: Procurement doesn't take your word for it.
• Storage with no tiers 'tiers' is a pricing-page term; a cold reader may not immediately connect it to cost until the body line explains it. Alternative: Storage with no tiers or overages

First fixation: White testimonial card (FAILS, competes with Camera with blue LED ring and reflection)   Cold read: A stranger sees a body camera in front of management software and a security-company quote, so the product category lands. The benefit is only 'sets us apart from competition', which is a differentiation claim without a stated problem; the picture (software, vault screens) and the quote (competitive edge) are not in conflict but neither names what the camera solves.

• P0 testimonial card: The line 'ATTRIBUTION TO CONFIRM BEFORE THIS RUNS' is an internal production note rendered in brand orange inside the card, styled like a live subline. Fix: Remove the line entirely; keep the attribution line 'HALOS customer, private security' as the last line of the card and re-centre the card's inner vertical padding.
• P1 background, just below the logo: A hard horizontal seam runs the full width at roughly 6 percent from the top where a darker header band meets the lighter gradient; it reads as a compositing artefact. Fix: Blend the header band into the gradient so there is a single continuous dark ground behind the logo and card.
• P1 hierarchy: The bright white card and the glowing product are both first-fixation candidates; the card wins on contrast but the product's blue ring and reflection pull the eye equally hard, so the message does not clearly own the first look. Fix: Slightly reduce the ring glow and reflection intensity, and pull the card and product closer together vertically so the card leads and the product supports.
• P2 card margins: Card runs from about 105 px to 1012 px on a 1080 px frame: 105 px left margin versus 68 px right. The orange chip at 70 px masks it, but the card itself sits off-centre. Fix: Centre the card with equal outer margins, keeping the orange quote chip overlapping the top-left corner.
• P2 vertical rhythm: Large dead band between logo and card, a second gap between card and product, and a wide empty floor below the product; composition feels top-loaded with unused depth at the bottom. Fix: Tighten the logo-to-card gap and card-to-product gap; let the product sit slightly lower so the floor reflection fills the lower area, while keeping all critical elements above the bottom 12 percent.
• P2 background UI panels: The three floating software panels have no bezels and are blurred to illegibility; they read as set dressing rather than the real product software. Fix: Keep them as defocused desktop dashboard panels but give them a faint consistent frame and a slightly crisper card structure so they read as one software system.

Language flags (for a human, never applied):

• HALOS customer, private security Anonymous attribution weakens a testimonial on a cold read; the reader cannot tell who is speaking or why they are credible. Alternative: Add a role and company type once confirmed, for example 'Operations Director, private security firm'.

First fixation: headline   Cold read: Body camera plus a review dashboard is clear from the picture; the notebook versus screen split sells 'written account versus recorded proof' well. The only wobble is pronoun logic: the headline says YOU describe and THEY show, but both column labels say YOU, so a stranger has to re-read to work out who 'they' is.

• P1 right column label: 'WHAT YOU SHOW' is set directly over the camera's lower face and the bottom arc of the blue ring; text over the product and over busy pixels. Fix: Reduce the camera so its whole body sits above the label, and give the label its own clear strip of background with a subtle dark scrim; nothing touches the ring.
• P1 product: The first blue chip covers the bottom of the camera; the device continues behind the chip block, so the product reads as chopped off by the UI. Fix: Scale the camera down roughly 15 percent and raise it so its base clears the top of the first chip by a clear gap.
• P1 left column label: 'WHAT YOU DESCRIBE' is light grey on the mid-grey notebook; weak contrast, will wash out on a phone in daylight. Fix: Set the label in white at the same weight as 'WHAT YOU SHOW' and darken the notebook behind it slightly.
• P1 footer / ground: A flat navy band with a hard horizontal edge sits across the bottom of the frame, disconnected from the desk and the reflection above it. Fix: Remove the band; continue the dark desk surface and its soft blue reflection all the way to the bottom edge.
• P2 divider: The glowing vertical seam runs the full height, passing behind the wordmark and between the headline words, and slightly fights the logo. Fix: Fade the seam out above the headline so it lives only in the picture zone.
• P2 on-screen UI: Tablet dashboard is dark-themed and rendered as blurred pseudo-text; the real software is a light interface. Plausible as a tablet, but any sharpening would expose garbled letters. Fix: Keep the screen soft and out of focus with no readable characters; a lighter panel tone would sit closer to the real product.
• P2 chips: Right chips are a very saturated flat blue and, as a block, weigh nearly as much as the headline. Fix: Keep the colour but pull saturation back a touch and keep the current row spacing; the four-over-four alignment is already tight.

Language flags (for a human, never applied):

• WHAT YOU DESCRIBE / WHAT YOU SHOW Both labels address YOU, while the headline splits the two sides between YOU and THEY, so the contrast the headline sets up is not carried into the columns. Alternative: WHAT YOU DESCRIBE / WHAT THEY SHOW
• Every view of it logged 'View' is ambiguous on a cold read; it could mean camera angle rather than playback access. Alternative: Every time it is opened, logged

First fixation: headline   Cold read: A stranger gets it: a body-worn camera for field crews that produces timestamped, located proof that a job happened, aimed at the 'nobody showed up' dispute. The dusk storefront and service van back the field-service story, and the tablet gallery signals reviewable footage. Picture and headline agree.

• P0 tablet UI: The software screen carries garbled pseudo-text throughout: 'Data Captured', 'Data Uploaded', 'Camenc', 'Ceptowe By', 'Durstien', 'Caoners', 'Cevreard By', 'Upliced Date', plus mangled name and ID values and truncated chips 'Rsr' and 'Got'. At phone size it reads as texture, but any zoom or a client review at full size exposes it. Fix: Re-render the tablet screen to match the reference software screenshot with correctly spelled labels (Date Captured, Date Uploaded, Camera, Captured By, Capture Date, Upload Date, Duration, Site) and clean, consistent values; let the chip row run off the right edge naturally instead of ending in a half-word.
• P1 product and tablet placement: The camera's lower third and the tablet's bottom edge sit inside the bottom 12 percent of the frame, where platform chrome will cover them; the tablet also bleeds off both the right and bottom edges, so the composition reads as cropped rather than placed. Fix: Lift the camera and tablet group so the camera base clears the 88 percent line, and let the tablet bleed off the right edge only, with its bottom edge visible or tucked behind the camera.
• P1 body copy: Seventeen lines of grey body across three paragraphs plus a closer; the set size is marginal at phone scale and the block competes with the product for attention on a second look. Fix: Increase body size roughly 10 percent, tighten paragraph gaps slightly, and keep the column's right edge clear of the tablet; no words change.
• P2 logo: The wordmark's O ring is grey and white only; the red-orange arc of the reference wordmark is missing or too faint to register. Fix: Reproduce the wordmark exactly from the reference, including the red-orange segment of the O.
• P2 headline contrast: The second headline line crosses the brightest part of the blurred storefront and sky, softening edge contrast on 'otherwise.' Fix: Deepen the background gradient behind the headline zone so the white type sits on a uniformly dark ground.
• P2 product rendering: The lens is drawn as a glossy dome with a bright reflective ring rather than the recessed, bevelled lens in the reference photo; the ridged side panels are slightly softer than the reference. Fix: Match the lens and side ridges to the reference photo; keep the blue ring, badge and matte finish as drawn.
• P2 balance: The bottom-left quarter under 'Thirty seconds, settled.' is an empty void while the right side is dense with camera and tablet; the weight tips to the lower right. Fix: Lifting the product group (per the P1 fix) and enlarging the body slightly will close most of the gap; keep the closer as the last element in the column.

Language flags (for a human, never applied):

• When your crew wears a HALOS camera. Proof of work uploads itself the moment the job ends The full stop after 'camera' strands the opening clause as a fragment and breaks the cause-and-effect the sentence is building; a cold reader stalls on it. Alternative: When your crew wears a HALOS camera, proof of work uploads itself the moment the job ends

First fixation: Headline 'The free re-do ends when the footage starts.'   Cold read: A stranger reads: body-worn camera plus desktop software, used by a service tech, replaces paper route sheets and ends unpaid return visits. Picture and headline agree. The only wobble is that 'free re-do' and 'Second visit, free' can be misread as offers on the first pass until the × marks register.

• P1 chip rows: Both bottom chips ('Paperwork, not proof' and 'Thirty seconds, settled') sit at roughly 93 to 97 percent of frame height, fully inside the bottom 12 percent that platform chrome covers; the third row straddles the 88 percent line. Bottom margin is about 3 percent. Fix: Lift both chip stacks so the last row bottoms out at or above 86 percent of frame height; tighten the row gap slightly and pull the product and monitor cluster up to make room.
• P1 on-screen UI: The software on the monitor is built from pseudo-text: filter chips, toolbar buttons and card field labels are garbled non-words (Doratlom, Uplired Date, Aewordld Svece). Reads as fake at any magnification and fails a client glance. Fix: Render the monitor content as a faithful reproduction of the desktop software reference: real labels (Videos, Dashboard, Search, Advanced Search, Bulk, Add To Case File, Evidential Flag, Actions, Duration, Site, Camera, Captured By, Capture Date, Upload Date) with values taken from the reference.
• P1 prop: route sheet: Route sheet rows and column headers are pseudo-text at high magnification (Job Ulitso, Desbon, Dxcon vletaco). Fix: Keep 'Route Sheet', 'Name', 'Date' as the only readable words; render the rows as soft out-of-focus printed entries that never resolve into letters.
• P1 hero camera / monitor: The hero camera sits directly in front of the monitor and overlaps the screen's left edge and the bottom of the tech's clipboard; the monitor itself runs off the right edge of the frame. Fix: Separate the camera from the monitor with a clear gap so neither touches the other, keep the monitor fully inside the frame with a margin, and keep the monitor's top edge clear of the tech's hands and clipboard.
• P2 headline / divider: The glowing blue divider line runs straight behind 're-do' and 'footage', a bright stroke crossing white letterforms. Fix: Dim the divider to near-invisible where it passes behind the headline block, at full glow only below the headline.
• P2 prop: wall plaque: Garbled pseudo-text on the door plaque beside the tech. Fix: Leave the plaque blank or as an unreadable blurred surface.
• P2 chip rows: Outer margins are uneven: left stack starts at about 8 percent, right stack ends at about 96 percent, so the right column feels tighter to the edge. Chip widths vary row to row producing a stair-step silhouette on both stacks. Fix: Equalise outer margins at about 6 percent each side; keep chips hugging their text but with identical heights, identical vertical gaps and identical corner radius.
• P2 on-screen UI: Second video card and its ID are clipped by the frame edge; card thumbnail text is garbled. Fix: Show a complete first card and let the second card end cleanly inside the monitor bezel.

Language flags (for a human, never applied):

• The free re-do ends when the footage starts. 'Free re-do' can be read on a cold first pass as a customer benefit (you get a free re-do) rather than the callback the contractor eats unpaid; the meaning only lands once the × chips are read. Alternative: The unpaid re-do ends when the footage starts.
• Second visit, free × Same ambiguity as the headline; 'free' reads as a positive until the × registers, and it sits in the column meant to be pain. Alternative: Second visit, unpaid ×
• One link, sent Cryptic without context; a stranger does not know what the link contains or who receives it. Alternative: One footage link, sent

First fixation: headline 'Every visit, on the record.'   Cold read: The device reads as a body camera and the four photo tiles (gate, lawn, van, warehouse) plus 'every stop your crew makes' make it clear this is about proving field crews were where they said they were. Picture and headline agree; the only gap is that nobody is shown wearing the device, so a stranger may not immediately register it as body-worn.

• P1 bottom chips vs product: 'Found in seconds' chip runs across the product's bottom-left corner and 'One secure link' chip butts against the product's lower-right edge; both chips collide with the hardware silhouette. Fix: Nudge the bottom chip row down about 3 percent of frame height and pull each chip outward so a clear gap of at least one chip-height separates chip from product; alternatively shrink the product 5 percent.
• P1 photo tiles: Pseudo-text lettering on the polo shirts in the lawn and warehouse tiles: garbled letterforms that read as nonsense at magnification. Fix: Render the uniforms as plain unbranded polos with no chest lettering.
• P2 bottom of frame: Roughly the bottom 15 percent is empty gradient and reflection; the composition is top-loaded and the product floats with a large void below it. Fix: Tighten the vertical spacing of headline, subhead and chip rows so the whole stack sits about 4 percent lower, or shorten the reflection so the void feels intentional; keep the bottom 12 percent free of text regardless.
• P2 chip alignment: The bottom-left chip starts further left than the top-left chip and the left photo tiles, and the bottom-right chip ends further right than the top-right chip, so the four chips do not sit on a consistent outer edge. Fix: Align the outer edges of the chips to the outer edges of the photo tiles on each side so both columns share one vertical margin.
• P2 photo tiles vs product: The lower-left and lower-right tiles tuck behind the product edge with only a hairline of separation, so the layering reads as accidental rather than deliberate. Fix: Either overlap the tiles clearly behind the product by about 5 percent of tile width, or leave a visible gap; avoid the near-touch.

Language flags (for a human, never applied):

• Found in seconds The subject is missing; on a cold read it is not obvious what is found (the footage, the visit, the crew). Alternative: Footage found in seconds
• One secure link Ambiguous what the link is to or for; it could read as a network link rather than a shareable footage link. Alternative: Share with one secure link

First fixation: headline (Press record. HALOS handles the rest.)   Cold read: A stranger sees a rugged body camera floating in front of desktop management screens (video library, map) and reads it as a body-worn camera with software behind it. The headline implies HALOS automates what happens after recording, but 'the rest' is never specified; the screens carry the hint (upload, library, location) but the problem being solved is inferred, not stated. Picture and headline tell the same story.

• P0 ui panels: The three software screens are filled with garbled pseudo-text (Bpaalty, Comgaavatio, Mentc Gogtured, Diy OT Wastle, Sxledvool Fing, Dets Exposred, Asoel.hies, MatiwerXseaidd, Jss Gliuge). The larger filter chips and user name are readable at phone size and read as broken. Fix: Keep only the labels that match the real desktop software (Videos, Dashboard, Search, Filters, Download, Map Trail, Duration, Site, Captured By, Capture Date, Upload Date, Actions, Sort) and render all other interface content as soft, unresolvable micro-detail with no legible letters.
• P1 ui panel right, map: A third-party map brand mark is visible at the bottom of the map panel. Fix: Remove the map attribution mark; render the map as an unbranded street map.
• P1 product: Blue LED glow floods the whole left ridged flank of the camera so the chassis reads as blue-lit plastic rather than matte black, and the ring brightness pulls fixation against the headline. Fix: Tighten the ring glow falloff to a soft halo within roughly one ring width; the ridged sides stay matte black with only a faint blue rim light.
• P2 ui panel centre: The middle screen is almost entirely hidden behind the camera; the two slivers that show on either side add visual noise without information. Fix: Drop the centre screen or slide it up so its header reads as a deliberate third layer; the two flanking screens do the work.
• P2 frame edges: Both flanking screens run off the left and right frame edges with their glass borders cut mid-panel, which reads as accidental rather than a deliberate bleed. Fix: Pull both screens inward so their outer glass edges sit inside a consistent margin, or bleed them decisively with the border fully outside the frame.
• P2 composition: Camera, three screens and reflection crowd the central 55 percent; the camera's tilt drifts its lower-left corner off the vertical axis of the headline and logo. Fix: Reduce the screens by about 10 percent and centre the camera's ring on the vertical axis of the wordmark.

Language flags (for a human, never applied):

• HALOS handles the rest. On a cold read 'the rest' is undefined; the viewer must infer from the screens what HALOS does after recording. Alternative: HALOS handles everything after.

First fixation: Headline 'Stop chasing footage. Find any clip in seconds.'   Cold read: A stranger sees a body-worn camera plus a video library on a tablet, contrasted with a drawer full of old cameras and loose memory cards. Product is a camera with searchable cloud video storage; problem is footage that is stored but cannot be found. Picture and headline tell the same story.

• P0 on-image UI (tablet): Nearly every string on the software screen is pseudo-text: filter chips, toolbar buttons, card IDs, card metadata and the user name are scrambled glyphs. Visible as wrong in the top-right quadrant and at tablet scale. Fix: Rebuild the tablet screen from the desktop software reference so every label is a real, correctly spelled word; keep the same light UI, orange accent buttons and video-card grid.
• P1 bottom chip rows: The fourth chip row ('You chase the file' / 'You keep the original') sits in the bottom 12 percent of the frame and will be covered by platform chrome; the third row grazes it. Fix: Tighten the empty desk space under the camera and lift both chip columns so the last row's bottom edge clears the bottom 12 percent of the frame.
• P1 on-image UI (tablet): Even where the UI text is real, the card metadata is far too small to survive a phone screen and reads as noise. Fix: Reduce the number of visible video cards (two rows of four is enough) and scale the screen contents up so card IDs and the toolbar are legible at phone size.
• P2 divider / logo / headline: The glowing vertical split line runs straight up through the headline (between 'chasing' and 'footage') and behind the wordmark, adding a bright streak across the two most important elements. Fix: Fade the divider glow to nothing above the headline baseline, or stop the line at the top of the headline block, so logo and headline sit on a clean ground.
• P2 product: The camera is smaller than the designer bar; it occupies roughly a fifth of the frame width and is partly lost against the busy tablet screen behind it. Fix: Scale the camera up so it fills roughly 30 percent of the frame width, and dim or blur the region of the screen directly behind it so the blue ring reads cleanly.
• P2 left chip column: Grey pills on a grey-blue drawer photograph: contrast is adequate but the pills feel heavier than the right column because the left photo is busier behind them. Fix: Darken the photo band behind the left chips slightly so both columns read with equal weight.

Language flags (for a human, never applied):

• No tiers, no limits Cold read: tiers of what? It only resolves once the reader cross-references 'Tiered storage bills' in the opposite column. Alternative: No storage tiers, no limits
• You keep the original Original what? The noun is missing, so a first-time reader has to guess (file, footage, camera). Alternative: You keep the original file

First fixation: glowing blue LED ring on the product (FAILS, competes with headline)   Cold read: The lens, rugged chassis and rows like Search by shift and Full audit trail make it read as a body-worn camera with a footage system. The problem (footage that is hard to upload, find and control) comes through from the rows rather than the headline; the headline on its own is generic. The subhead promises three jobs and the eye then counts five rows, which creates a small stumble.

• P1 feature row 5: The last row (Intelligence → Answers, not archives) sits at roughly 92 percent of frame height, inside the bottom 12 percent that platform chrome covers. Fix: Shift the whole feature block up so the final row baseline clears 88 percent of frame height; tighten row spacing slightly if needed.
• P1 feature rows: Labels are left-aligned, arrows sit in a fixed column, but benefits are right-aligned to the frame edge, so the gap between arrow and benefit varies from tight (No dock, no download) to very wide (Found in seconds). The row rhythm reads ragged. Fix: Left-align every benefit string at one fixed x position immediately after the arrow column so arrow-to-text spacing is identical on all five rows.
• P2 product: The camera fills only about 28 percent of frame width; against the designer sheet, where the hero device fills closer to 40 percent, it feels small for the amount of empty ground around it. Fix: Scale the camera up to fill roughly 40 percent of frame width, keeping the same three-quarter angle and floating position.
• P2 product: The LED ring renders as a hazy cyan glow rather than the saturated blue of the reference photo. Fix: Render the ring a deeper, cleaner blue with a crisper edge and a tighter bloom.
• P2 feature row 1: The blue floor reflection bleeds up behind the right side of the first row band, slightly muddying the ground under Automatic upload and No dock, no download. Fix: Fade the reflection out before the first divider line so all five rows sit on the same flat dark ground.

Language flags (for a human, never applied):

• One system, three jobs. The reader is told three jobs and then sees five feature rows; the three (capture, keep, use) are never mapped to the rows, so the count contradicts what the eye sees. Alternative: One system does all three.
• Intelligence As a bare noun it is the one label that does not name a concrete capability, so the row lands weaker than the other four. Alternative: Built-in intelligence

First fixation: headline 'Capture it. Keep it. Use it.'   Cold read: A stranger sees a rugged body-worn camera in front of a video library and a route map, reads three verbs and a five-row feature-to-benefit list, and leaves knowing this is a camera plus a management platform that uploads, searches, audits and shares footage. Picture and headline agree. The specific pain is stated only implicitly (no dock, no download) rather than in the headline.

• P0 left and right screen UI: Both screens are filled with garbled pseudo-text: filter chips read 'Data Cnpared', 'Ratiol Tppe', 'Moral Sepand'; the orange primary button reads 'Raicen te socticn'; the user reads 'Jee Gloges'; the Filters button reads 'Fihws'; card metadata values are letter-salad. The screens occupy roughly 60 percent of the frame width at a size where the chips and buttons are readable, so the garbling reads as broken software. Fix: Rebuild both screens from the reference desktop UI with real, correctly spelled labels (Videos, Dashboard, Search, Filters, Download, Advanced Search, Site, Date Captured, Date Uploaded, Asset Type, Joe Bloggs, Manager) and render the card metadata and list values small and soft enough that they read as texture, not words.
• P1 feature row 5: The 'Intelligence -> Answers, not archives' row sits inside the bottom 12 percent of the frame where platform chrome covers it; row 4 is at the boundary. Fix: Compress the table vertically (tighter row pitch, slightly smaller type) and lift the whole table so the last baseline sits above the 88 percent line.
• P1 feature table: The table's bold white label column is set nearly as heavy and large as a secondary headline, and five rows of it occupy about a third of the frame, so the table competes with the headline for weight rather than reading as a support layer. The three columns also have uneven gutters: a wide gap before the arrows, a narrow gap after them, and the benefit column is ragged against a mostly empty right margin. Fix: Reduce label size by roughly 20 percent and use a semibold rather than bold weight; set the arrows in a fixed narrow column with equal gutters on both sides; align the benefit column to a single left edge so the table reads as a tidy two-column ledger under the hero.
• P1 camera and screens: The camera is placed directly on top of the two screens and covers roughly a third of each, hiding the UI and making the three objects read as one clump; the camera also hangs in the air with its base below the screens' bottom edge and a reflection that does not match its position. Fix: Pull the screens outward a little and scale the camera so it overlaps the inner edges only, then seat the camera and its reflection on the same ground plane as the screens.
• P2 camera lower flank: A faint embossed 'HALOS' mark on the lower side of the chassis that is not on the reference product. Fix: Remove the extra mark; the only brand mark on the hardware is the centered badge inside the blue ring.
• P2 subhead: Subhead is a mid-grey light-weight grotesque that drops contrast noticeably against the headline; fine on desktop, soft on a phone. Fix: Lift it one step lighter in tone or one step heavier in weight so it survives a small screen.
• P2 top margin: The logo sits with generous air above it while the headline crowds closer to it than to the subhead, so the top stack feels slightly top-loaded. Fix: Equalise spacing so logo to headline and headline to subhead are in a consistent ratio.

Language flags (for a human, never applied):

• Intelligence As a bare feature label it is ambiguous on a cold read: it could mean an AI feature, security intel, or a general quality of the product, so the reader has to lean on the benefit column to decode it. Alternative: Built-in intelligence
• One system, three jobs. Reads as a claim about the reader's workload rather than the product's three functions; a stranger may briefly wonder whose three jobs. Alternative: One system that does all three.

First fixation: headline   Cold read: The lens, rugged chassis and rows about patrols, shifts and audit trails read as a security body camera; the headline and RFP subhead make clear the problem is winning procurement contracts. A stranger could briefly mistake the device for a smart speaker or doorbell before the feature rows anchor it.

• P1 feature_row_6: The last feature row (One monthly fee, No per-feature pricing) sits at roughly 87 to 90 percent of frame height, inside the bottom 12 percent that platform chrome covers. Fix: Lift the entire six-row column so the last benefit line ends above the 88 percent mark; tighten row spacing slightly if needed.
• P1 feature_rows: The six rows do not share one left edge; each successive title and arrow drifts a few pixels to the right, so the column reads as slightly tilted rather than deliberately ragged. Fix: Snap every title and every arrow to a single vertical axis, with the benefit line indented by one consistent amount below its title.
• P2 product: The LED ring renders as a light cyan glow rather than the saturated royal blue in the product photo, and the bloom softens the edge of the ring. Fix: Deepen the ring to the reference blue with a crisp ring edge and a restrained glow.
• P2 product: The side controls (rectangular button, grille slots, power key) appear on the left flank; in the reference photo the same controls sit on the right flank, which suggests the model was mirrored. Fix: Match control placement, lens position and proportions to the product photo while keeping the three-quarter angle and scale.
• P2 product: The camera base sits about 8 percent from the bottom edge while the logo sits 6 percent from the top; the product also extends into the bottom 12 percent zone, so its base will be partly covered by chrome. Fix: Raise the camera slightly so its base clears the 88 percent line, keeping it the same size.

Language flags (for a human, never applied):

• A full shift As a feature title it names a duration rather than a capability, so on a cold read it does not say what the feature is until the benefit line is read. Alternative: Full-shift battery
• → Patrols, verified The comma construction is terse enough to be ambiguous about who or what is verified. Alternative: Every patrol verified

First fixation: White quote text block on the dark navy card   Cold read: The words body cams plus the small blue-ringed camera on the right guard's chest make the category clear; the problem read is accountability and differentiation for a private security operator. Picture and copy tell the same story. The product itself is tiny (about 2 percent of frame width), so the device is understood from the copy, not the image.

• P1 quote card / subjects: The right edge of the dark quote card runs within about 1 percent of the left guard's shoulder and sleeve, creating a tangent that reads as a collision at feed size. Fix: Narrow the card or shift it left so there is a clear 3 to 4 percent gap between the card edge and the nearest figure; keep the same line breaks.
• P2 composition: The bottom fifth of the frame is empty polished floor; the card ends at about 80 percent and the figures' feet at about 86 percent, so the layout floats high and feels top-heavy. Fix: Tighten the crop or drop the scene so the floor band is shorter, while keeping all text above the bottom 12 percent.
• P2 product: The camera on the guard's chest is very small; the blue ring is visible but the badge and chassis detail are not legible, so the product carries almost no visual weight. Fix: Crop closer on the two figures so the chest-worn camera is 2 to 3 times larger and clearly shows the blue LED ring and black chassis.
• P2 logo: Wordmark is set in black on a bright wall panel rather than the reference white treatment; it reads as signage in the scene and is slightly lighter in visual weight than the quote card. Fix: Keep placement, but render the wordmark exactly to the reference letterforms with the grey and red-orange ring O and the registered mark; white-on-dark or black-on-light are both acceptable as long as letterforms match.
• P2 attribution: Grey attribution line is roughly one line-height of small text at mid contrast; it survives phone size but only just. Fix: Raise it one step lighter in grey or one step larger; keep the wording.

Language flags (for a human, never applied):

• Using body cams set us apart from the competition and meets our promise to stay 100% accountable to our clients. Subject-verb agreement is inconsistent (set versus meets); on a cold read it stumbles mid-sentence. Alternative: Using body cams sets us apart from the competition and keeps our promise to stay 100% accountable to our clients.
• HALOS customer · Private security Anonymous attribution weakens the proof; a stranger cannot tell who is speaking or at what level. Alternative: Operations director, private security firm · HALOS customer

First fixation: headline 'Three ways to buy a body camera.'   Cold read: A stranger sees three body cameras in a presentation box and reads that there are three ways to buy one, so the category is clear. No problem or stake is stated on this card; the subhead lists options in an order (Enterprise, Budget, connected vault) that does not match the box (Enterprise, HALOS HORIZON, Budget) and calls the centre option 'connected vault camera system' while the box calls it 'HALOS HORIZON', so the reader has to work to connect the words to the picture.

• P1 product box / margins: The box's left corner sits about 3 percent from the left frame edge while the right corner has roughly 5 percent; the composition reads as cramped and slightly off-centre, and the left corner is close to being clipped. Fix: Scale the box down a few percent and centre it so both left and right corners clear the frame by at least 6 percent.
• P1 compartment labels: ENTERPRISE, HALOS HORIZON and BUDGET are small, perspective-warped and set in mid-grey on dark grey; at phone size they drop below comfortable legibility, and they are the only thing tying the subhead to the three cameras. Fix: Enlarge the three labels by roughly 30 percent, set them in near-white, reduce the perspective distortion so they read as flat printed labels on the box surfaces.
• P2 HALOS camera chassis: The blue glow tints the whole centre camera navy-blue; the reference chassis is matte black with the blue confined to the LED ring. Fix: Keep the chassis matte black, limit the blue to the ring and a soft halo on the tray immediately around it.
• P2 HALOS camera proportions: The centre camera is squarer and its lens smaller and more recessed than the reference, whose lens is a large circular element in a black top panel over a taller body. Fix: Match the reference: taller body, vertical ridged sides, a large round lens in the black top panel above the ring.
• P2 composition: The box's flat front face is a large empty dark plane occupying the lower quarter of the frame and running into the bottom 12 percent, leaving the lower right dead. Fix: Raise the box slightly and reduce the visible height of its front face so the lower band stays clear and the three cameras sit nearer the vertical centre.

Language flags (for a human, never applied):

• Budget SD cards. Reads as though the budget option is buying SD cards, while the box shows a budget camera; a cold reader stalls on it. Alternative: Budget SD-card cameras.
• Or the connected vault camera system. The subhead names the third option one way and the box labels it HALOS HORIZON, so nothing on the card tells the reader these are the same thing; the subhead order also differs from the box order. Alternative: Or HALOS HORIZON, the connected vault camera system.

First fixation: The lens of the large grey camera at centre, lit by the background glow (FAILS, competes with Headline 'Enterprise camera systems', Rusty padlock at lower right of the cable tangle)   Cold read: A stranger reads this as a critique of enterprise body-camera systems: cable tangle, rusty padlock and four crossed-out drawbacks say lock-in and cost. But there is no brand, no product and no alternative on the frame, so they leave with a complaint and no idea who is making it or what is being offered. Picture and headline agree with each other; the ad simply has no sender.

• P1 logo: No HALOS wordmark on the frame. Every ad on the designer sheet anchors with the wordmark at top centre; this card has no sender at all. Fix: Human decision: place the wordmark small at top centre above the headline (light version, coloured O intact) or accept as an unbranded carousel card that relies on its neighbours. Not added in the regen prompt because it would be a new text string.
• P1 feature_rows: The fourth chip 'Procurement project' sits at roughly 90 to 94 percent of frame height, inside the bottom 12 percent that platform chrome covers; the third chip's lower edge grazes the same zone. Fix: Shift the whole four-chip stack up so its bottom edge lands at about 86 percent of frame height; tighten the gap between the cable tangle and the first chip to make room.
• P1 hierarchy: The large centred lens wins first fixation over the headline; the headline and the padlock then compete for second. The element that carries the message (headline plus X-list) is not what the eye lands on. Fix: Reduce the camera-and-cable cluster to about 40 percent of frame width and bring the headline weight and size up marginally so the headline reads first, the object second, the chips third.
• P2 feature_rows: Chips are wide grey pills with the X badge hard left and the label optically centred in the remaining space, so the labels do not share a left edge; 'Built for police' and 'Procurement project' start at different x positions. Fix: Left-align all four labels to one x position a fixed gap after the X badge, keep pill widths equal.
• P2 product: The rusty brass padlock and cable partly obscure the lower third of the camera body; the padlock reads brown-orange and is the warmest object in an otherwise cold frame, pulling the eye to the lower right. Fix: Keep the concept but cool the padlock toward a dull gunmetal or weathered grey so it does not out-compete the headline.
• P2 background: The rear glow is centred behind the lens and fades to near black at the headline, so the headline sits on the darkest band while the object sits on the brightest; it inverts the intended reading order. Fix: Lift the glow slightly so it also underlights the headline, or flatten it so the object is not the only lit element.

Language flags (for a human, never applied):

• Built for police Presented as a drawback with an X, but on a cold read most people see 'built for police' as a credential, not a flaw; the intended meaning (over-built for a commercial buyer) is not carried by the words. Alternative: Built for police, not you
• Procurement project A noun phrase without a verb reads as a label rather than a complaint; a stranger cannot tell whether it means the purchase takes a formal procurement process (bad) or that the product is a procurement tool. Alternative: Needs a procurement project

First fixation: headline 'Budget SD-card cameras.'   Cold read: A stranger reads this as a takedown of cheap SD-card body cameras: cards get swapped, break, nothing is searchable, no chain of custody, the program fades. Picture and headline agree. What they cannot tell is who is talking or what the alternative is, because there is no brand mark anywhere; the olive device shares the reference camera's silhouette (top lens panel, central disc, ridged side) so a reader could take it for the advertiser's own product.

• P1 chip row: The fourth chip 'Program dies quietly' sits entirely inside the bottom 12 percent of the frame and the third chip's lower half does too; platform chrome will cover the closing argument. Fix: Shift the whole composition up: pull the headline toward the top, raise the camera, and end the chip stack above the 88 percent line.
• P1 chip row: The four pills are not aligned: left edges step progressively leftward in a diagonal cascade and widths vary, which reads as drift rather than a deliberate stagger. Fix: Set the four pills as one column with a common left edge and equal height, either equal width or centered as a block, with even vertical gaps.
• P1 product and brand: No wordmark or brand mark appears anywhere, and the depicted olive camera borrows the reference product's form factor minus ring and badge; on a cold read the advertiser is unknown and the negative claims could attach to the wrong device. Fix: Human decision, outside the regeneration scope: confirm the olive device is meant as a generic competitor stand-in and decide whether the brand wordmark belongs on this card as it does on every designer exemplar. Regeneration keeps the device as drawn and adds nothing.
• P2 vertical balance: Roughly 12 percent of dead space above the headline while the bottom is crowded; the frame is bottom heavy. Fix: Reduce the top margin to around 7 percent and redistribute the gain to the gap between the SD cards and the first chip.
• P2 type: Chip text uses the same heavy condensed weight as the headline, so the two tiers fight for the same visual register; the designer sheet uses a lighter regular grotesque for chip rows. Fix: Keep the headline heavy condensed; set the chip copy in a clean regular-weight grotesque at a clearly smaller size.
• P2 chip icons: The cross-in-circle icon and its gap to the text vary slightly chip to chip. Fix: Identical icon diameter and identical icon-to-text gap on all four chips.

Language flags (for a human, never applied):

• Card in, card out On a cold read this describes a routine rather than a failure; the reader has to infer the pain (manual swapping, cards walking away). Alternative: Cards swapped by hand

First fixation: Camera with glowing blue LED ring (FAILS, competes with Bright white monitor screen, Headline)   Cold read: A stranger sees a rugged body camera paired with desktop evidence software and reads a pitch about simple all-inclusive pricing and automatic upload. Picture and headline agree. The word 'Vault' inside the headline is a slight stumble on a cold read (is Vault a product, a place, or an adjective?), and the chips do not explain it.

• P0 ui on monitor: Almost every string on the software screen is garbled pseudo-text: filter chips ('Cait Sgllenlatl', 'Cay of Binth'), toolbar buttons ('Ecandoed Deepot', 'Gdil to Cons File', 'Ecarteaad Frey'), field labels ('Sgomose', 'Explosrd Dite'), card IDs with letters mixed into numbers, and dates like 32/10/2029. The toolbar row is large enough to be read in the full frame. Fix: Re-render the screen so every visible label is a real word matching the reference desktop software: Search, Videos, Filters, Download, filter chips Site / Date Captured / Date Uploaded / Asset Type / Quality / Compression / Month Captured / Year Captured / Day Of Month, toolbar Advanced Search / Bulk / Add To Case File / Evidential Flag / Actions / Sort, card fields Duration / Site / Camera / Captured By / Capture Date / Upload Date, with plausible numeric IDs and dates. Any text too small to render cleanly should be reduced to neutral grey placeholder bars rather than letter-like noise.
• P1 feature chips: The bottom chip 'Full audit trail' sits inside the bottom 12 percent of the frame (roughly the last 275 px of a 2304 px frame) and will be covered by platform chrome. Fix: Shift the whole chip stack upward so the lowest chip's bottom edge clears the bottom 12 percent, tightening the gap between the camera base and the first chip.
• P1 hierarchy: The large, near-white monitor screen is the brightest area in the frame and competes with the blue-ring camera for first fixation; the headline reads third. Fix: Drop the screen brightness by roughly a third (soft light-grey UI ground instead of pure white) and keep the camera and its blue ring as the brightest object, so the eye goes camera, then headline, then screen.
• P1 feature chips: The four orange pills are staggered in a zig-zag with different left and right edges, which reads as accidental rather than designed and leaves the stack visually unstable against the centred headline and logo. Fix: Align the four pills on a single centre axis with equal vertical spacing, check icons vertically centred to the text, consistent horizontal padding on each pill.
• P2 background: A stray blue glow spills on the floor behind and left of the chip stack, unrelated to the LED ring, and looks like a compositing artefact. Fix: Remove the detached blue glow under the chips; keep only the ring's natural spill on the desk and the monitor's soft backlight.
• P2 product and monitor: The camera occludes the first column of video cards on the screen, so the leftmost cards read as cut in half; the overlap also crowds the monitor bezel. Fix: Nudge the monitor slightly right or scale it down a touch so the camera overlaps only the bezel and the first card column is either fully hidden or fully visible.

Language flags (for a human, never applied):

• The Connected Vault Camera Platform On a cold read 'Vault' interrupts the phrase and is ambiguous: it could be a product name, a storage place, or a descriptor of the camera. The rest of the ad never explains it. Alternative: The Connected Camera Platform, with Vault
• Uploads itself The subject is unstated; a stranger has to infer that footage, not the camera, uploads automatically. Alternative: Footage uploads itself

First fixation: Headline: Documentation is the tiebreaker.   Cold read: A stranger sees a body-worn camera, its video library on a tablet, and a checked RFP requirement, and reads that documentation now decides contract awards. Picture and headline tell the same story. Readers outside procurement may not know RFP, but the checked form plus VERIFIED stamp carries the idea visually.

• P0 document body: The RFP paper is covered in pseudo-English that is legible enough at phone size to be read as gibberish (taiandi, proveisbly, undenisam). Fix: Render the paragraph areas as soft-focus grey text lines with no resolvable letterforms; keep only RFP, the checklist row, and the VERIFIED stamp as readable text.
• P1 tablet UI: Chip labels, toolbar buttons, the account name, and every card value are garbled pseudo-text; Advanced Search is misspelled and the lower right cards decay into stray strings (SIGM, 8600) and empty folder icons. Fix: Reproduce the software layout from the reference with only the short labels spelled correctly; render IDs, dates, names, and other values as neutral grey placeholder bars, and fill every card slot with a proper thumbnail so no cards dissolve.
• P1 left edge / tablet: The tablet runs to the left frame edge with no margin and its left corner is clipped. Fix: Pull the tablet inward so its full outline sits inside the frame with a margin roughly equal to the headline side margins.
• P1 bottom of frame: The VERIFIED stamp sits at roughly 83 to 87 percent of frame height, right at the edge of the zone platform chrome covers, and the paper text runs through the bottom 12 percent. Fix: Raise the checklist row and stamp so they sit fully above the bottom 12 percent; leave only the blank paper and desk in that band.
• P2 product: The LED ring reads as a lighter cyan-blue glow rather than the saturated blue of the reference photo. Fix: Deepen the ring to the saturated blue of the reference while keeping the soft glow on the paper.
• P2 composition: The gap between subhead and product is slightly generous and the right side of the paper is denser than the left, pulling weight to the lower right. Fix: Tighten the vertical gap slightly and balance the document so its readable row sits closer to centre under the camera.

Language flags (for a human, never applied):

• RFPs now score documentation the way they score staffing ratios. Relies on the reader knowing the acronym RFP and the convention that staffing ratios are a scored criterion; a cold reader outside procurement gets the shape but not the specifics. Alternative: Contract bids now score your documentation the way they score your staffing.