WORK-004 — onroover.com MVP surgical content pass

Status: RETURN — NOT CLEAR TO ROUTE; DO NOT START
Work ID: WORK-004
Prepared: 27 Aug 2026 PT
Decision: ACCEPT / RETURN / HOLD / ESCALATE

First Mate clarity gate: RETURN — NOT CLEAR TO ROUTE on 27 Aug 2026. No allocation, RUNNING state or start receipt exists.

Outcome

Produce one immutable TEST candidate for the smallest credible onroover.com company front door Mike can share with investors, industry partners, family and friends. Preserve the current live page's visual system and interaction design. Make only the exact content, sequence and hero-default changes below so the page reads as one clear narrative rather than a set of disconnected sections. This outcome is a TEST review host, not a publish or live deployment.

Founder review question

Does this file capture the exact MVP Mike intends? If ACCEPT, First Mate may review it for execution ambiguity, return any clarification gap to Founder Operator, then route the unchanged approved handoff. No work starts before Mike's acceptance.

Target and authority

• Current baseline: https://onroover.com/
• Stable Workspace review link: https://roover-work-004-workspace.pages.dev/ (HTTP 200 verified 27 Aug 2026). The accepted handoff and every returned TEST candidate/evidence package must be reviewable from this one Workspace surface.
• Target after Mike accepts this handoff: one new immutable TEST review host. The first return must not replace live https://onroover.com/.
• Mike's acceptance of this handoff authorises First Mate to route production of the review candidate only. It is not publication authority.
• Live https://onroover.com/ remains unchanged until Mike separately accepts the returned TEST candidate.
• After candidate acceptance, publication authority is limited to promoting that exact independently verified candidate build/commit to live. Do not rebuild a different version for production.
• This is not authority to redesign, add sections, alter the contact flow, change DNS, change another domain, or expand the company story.
• roover.com is not a Roover-controlled domain and is out of scope.
• Apex is off for this execution pass: do not publish or deploy to live onroover.com.

Exact approved baseline shots

Screen 1 — current live desktop, 1440 px

SHA-256: e7437b46058b6b131556c8219d88ef762ae8a6cfbddcf5e820936d35fb318927

Screen 2 — current live mobile, 390 px

SHA-256: 5de439c587a1e07ea3e1896b0f02b710650a6f666a3f68ddb655eba52e01e15b

The shots are the visual baseline, not inspiration. Anything not explicitly named as CHANGE or REMOVE must remain materially unchanged.

Exact narrative order after the change

1. Your roof starts here.
2. Homeowners start with a roof problem. Roover turns that problem into a clear job roofers can understand and price.
3. Roofing isn't backwards.
4. A simple centred downward arrow connecting this section to the next.
5. It just starts backwards.
6. When a homeowner's starting point is straight to roofers before the job is clear, what unfolds is repeated visits, measuring, selling and competing interpretations.
7. Roover gets the job clear first.
8. Roover turns a roof problem into a clear job roofers can understand and price.
9. Existing closing section: eyebrow OnRoover, heading Your roof starts here., and CTA Talk to Roover with live href /contact.

Exact implementation delta

1. Hero copy

CHANGE

• Old H1: Runs on Roover.
• New H1: Your roof starts here.
• Old supporting line: Your roof starts here.
• New supporting line: Homeowners start with a roof problem. Roover turns that problem into a clear job roofers can understand and price.

KEEP

• Current hero composition, green field, header, Roover mark, Talk to Roover link, roof visual, controls, type system, spacing system and responsive behaviour.

2. Hero roof default

CHANGE

• The interactive reference roof must load with Standing seam selected by default.

KEEP

• Classic, Standing seam, Light steel and Dark green controls remain available and functional.
• Preserve the current model, camera/orbit behaviour, drag interaction, roof geometry, control styling and accessibility behaviour.

3. Roofing isn't backwards. section

REMOVE FROM THE LIVE MVP

• Orange eyebrow: WHY IT FEELS THAT WAY.

PRESERVE, DO NOT DELETE FROM HISTORY

• Record the removed eyebrow as a candidate for a later iteration. Its absence from the live MVP must not erase it from the current baseline, version history or Workspace evidence.

KEEP

• Heading: Roofing isn't backwards.
• Existing cream section, typography, width, alignment, spacing and responsive behaviour.

MOVE/REPLACE

• Remove this exact current live supporting paragraph from this section:
  • Homeowners call roofers before the job is clear, creating repeated visits, measuring, selling and competing interpretations.
• Its replacement appears under It just starts backwards. as specified in item 5. Do not leave both paragraphs in the TEST candidate.

4. Narrative connection arrow

ADD

• One simple centred, static downward arrow at the bottom of the Roofing isn't backwards. section.
• Use the existing orange accent and current page design language.
• The arrow communicates “continue to the explanation below.”
• Use an inline text/CSS arrow such as ↓; do not create, import or fetch a new image, SVG, icon, font or other asset.
• The arrow is not interactive. Expose its meaning accessibly as Continue to why it starts backwards; do not add a focus target or keyboard behaviour for a non-action.

MVP LIMIT

• No new illustration, scroll-jacking, parallax, elaborate animation or new transition system.
• No arrow motion or animation. The MVP arrow is static.

5. It starts backwards. section

CHANGE

• Old H2: It starts backwards.
• New H2: It just starts backwards.
• Add this supporting line directly beneath the heading:
  • When a homeowner's starting point is straight to roofers before the job is clear, what unfolds is repeated visits, measuring, selling and competing interpretations.

KEEP

• Existing dark section, grid, typography, positioning, spacing and responsive behaviour, except for the minimum local height/spacing adaptation required to fit the added supporting line cleanly.
• The new supporting line may wrap to the number of lines required at each viewport. Do not truncate, clamp, shrink below the existing readable type treatment, overlap or clip it to preserve the old text slot.

6. Roover announcement section

KEEP

• Orange eyebrow: START WITH THE ROOF.
• Existing green section, type system, layout, spacing and responsive behaviour.

CHANGE

• Old H2: Roover turns a roof problem into a clear job roofers can understand and price.
• New H2: Roover gets the job clear first.
• Old supporting line: Roover fixes the order: first understand the roof and job, then let suitable roofers price the same work.
• New supporting line: Roover turns a roof problem into a clear job roofers can understand and price.

7. Closing and contact

KEEP EXACTLY

• Closing eyebrow: OnRoover.
• Closing heading: Your roof starts here.
• CTA anchor text: Talk to Roover.
• Exact current live CTA href: /contact (resolves to https://onroover.com/contact on the live host).
• Footer and the existing header/footer contact href /contact.
• Do not add About, investor, homeowner, roofer or partner sections in this MVP.

MUST NOT MOVE

• Do not redesign or reinterpret the page.
• Do not add downstream benefit claims, feature explanations or an “as a result” section.
• Do not change the brand mark, header, navigation, contact destination, footer, palette, typography system, roof model, geometry, visualiser controls or overall section architecture.
• Do not turn the page into a generic SaaS homepage, technical product page or industry-disruption pitch.
• Do not blame roofers, call roofing backward, say the industry is broken, or claim Roover fixes the industry.
• Do not import or merge the older WORK-004 film, three-spine library, V7 page or another candidate into the live page.
• Do not touch RoofHero or WORK-049.
• Do not alter any other live host, domain, DNS record or production surface.

Source and truth boundary

• Founder direction in the current Founder Operator session: FOUNDER-APPROVED WORKING INTENT, pending Mike's acceptance of this written interpretation.
• Roover_Messaging_Foundation_CANONICAL_LOCKED_2026-08-13 2.docx: source claims CEO lock on 13 Aug 2026. Used for Your roof starts here, Roover gets the job clear first, and the fuller explanation. It remains a source document; this handoff does not promote or relocate it.
• Roover_V4_Narrative_Source_Doc_2026-08-09.docx: explicitly SOURCE / REFERENCE, not an implementation brief. Used for the shortest-summary line and narrative guardrails.
• Current live HTML SHA-256 at preparation: 9de63d4a6ca5b785a680c31f1dfd858acf740f989156ae54729f4a325c55fb07.
• First Mate clarity-return screenshot: /var/folders/hv/04s62snd1bz47q1w0nv1n6bw0000gn/T/TemporaryItems/NSIRD_screencaptureui_zTs6FN/Screenshot 2026-08-27 at 2.09.40 PM.png; SHA-256 0dc60075973860cbbcad8bee864a6748052e95969f96cc59ec92bac55892de4d.
• Owning repository, branch and deploy mechanism: UNKNOWN — FIRST MATE MUST RECOVER BEFORE ALLOCATION; DO NOT GUESS.

Exact local source pointers

• /Users/mikebullot/Downloads/Roover_Messaging_Foundation_CANONICAL_LOCKED_2026-08-13 2.docx
• SHA-256: e16403b50bfcbb59d43e7065bcc9915031159d9f33bbf3eeae68ebf13d2884ce
• /Users/mikebullot/Downloads/Roover_V4_Narrative_Source_Doc_2026-08-09.docx
• SHA-256: bfef7a3740807ddaea2c12c883a548971abca863f721378694192e098464b457

Definition of done

The routed implementation is review-ready only when all checks below have evidence:

1. Exact copy matches this handoff character-for-character, including punctuation.
2. Section order matches the nine-step narrative order.
3. Standing seam is visibly selected on initial page load; all roof controls still work.
4. A static orange inline/CSS downward arrow clearly links Roofing isn't backwards. to It just starts backwards. on desktop and mobile; it uses no new asset, adds no focus target, and introduces no scroll-jacking or motion.
5. The removed orange eyebrow and exact old live paragraph are absent from the TEST candidate but preserved in version/Workspace evidence.
6. Header, contact route, roof interaction, closing section and all MUST NOT MOVE elements remain materially unchanged.
7. No horizontal overflow, clipped copy, overlapping text, broken roof controls or layout regression at 390 px mobile and 1440 px desktop.
8. Accessibility smoke check passes: heading order, existing keyboard access and focus visibility, accessible arrow meaning, readable wrapped copy and reduced-motion behaviour elsewhere on the page.
9. Before/after screenshots are returned side by side for desktop and mobile.
10. The implementation is independently checked against this handoff.
11. The first return is deployed to one new immutable TEST review host, with live https://onroover.com/ unchanged.
12. The Workspace places the returned result and evidence immediately above the exact handoff it answered.
13. Every version Mike actually reviews remains addressable by its own immutable URL and is not pruned or overwritten.

Separate candidate acceptance and live promotion

When the TEST candidate is review-ready, Mike decides ACCEPT / RETURN / HOLD / ESCALATE on that candidate—not on a rebuilt approximation.

• RETURN: preserve the reviewed TEST URL, attach Mike's feedback to WORK-004, and create the next iteration at a new immutable TEST URL.
• ACCEPT: promote the exact accepted, independently verified candidate build/commit to live https://onroover.com/; then return the live deployment receipt and body/browser verification.
• Do not treat acceptance of this written handoff as acceptance of the future candidate.

First Mate clarity-gate status and exact review

Current gate result: RETURN — NOT CLEAR TO ROUTE.

• The return identified three formerly inventable live fields and two reusable specification gaps; this revision quotes and resolves them.
• There is no worker allocation, RUNNING state, start receipt, TEST candidate or deployment receipt yet.
• First Mate must re-check this revised handoff before any allocation.

Before allocation, First Mate must return one of:

• CLEAR TO ROUTE with recovered owner/repository/branch/deploy path and start receipt requirements; or
• RETURN with the exact ambiguous or missing field.

First Mate must not reinterpret design intent, choose different copy, add scope or file this on top of the stale 25 Aug four-piece-film handoff. This handoff replaces that execution instruction for the current MVP while preserving the old package as history.

First Mate does not author this handoff and does not sit inside the Mike-and-Head/Founder-Operator working conversation. It gates the send: clarity review, return of exact ambiguity where needed, allocation, start receipt, tracking and governed return.

Worker return format

• Work ID: WORK-004
• Owner and start receipt
• Repository, branch/worktree and commit SHA
• Immutable TEST review URL and deployment receipt; live onroover.com must still be unchanged
• Requirement-by-requirement PASS/RETURN table
• Desktop before/after screenshots
• Mobile before/after screenshots
• Automated test/build result
• Accessibility/browser smoke result
• Exact remaining uncertainty or NONE
• Exact restart point

Exact restart

Mike reviews this file and says either:

ACCEPT WORK-004 MVP handoff and send it to First Mate for clarity review and routing.

or gives natural-language corrections. Founder Operator applies only the necessary correction and returns the same handoff for review.

After ACCEPT, First Mate performs one final clarity check and routes a TEST candidate. Mike will receive the candidate at the same stable Workspace link and separately decide whether it may replace live onroover.com.