The assessment stays inside the existing Services page.
V3 / Website build plan
Make the changes visible before we make them final.
This is the visual companion to the 150-step website audit. It shows what the visitor should experience, how the assessment is built, what the live release proves and what still needs a human decision.
Hurdle, preferred path and readiness lead to one useful next step.
No payment, booking, account, receiver or automatic quote is added.
The visitor reviews a draft addressed to Matthew before sending it.
What the visitor sees
A loose idea becomes a concrete starting point.
The page is deliberately short. It helps a business owner name the problem, choose the kind of help they want and say how ready they are to talk.
- 01
Name the hurdle
Client communication, team information, digital presence or AI literacy.
- 02
Choose the path
Coaching, a custom build or a group session.
- 03
State readiness
Ready to scope, or still exploring and learning.
- 04
See the fit
A pathway recommendation appears. There is no score.
- 05
Review the email
A mailto draft carries the selected context to Matthew.
How it should be made
Simple on the surface. Deliberate underneath.
The supplied project prompt is being applied proportionally. This feature needs proof, not infrastructure theatre.
Start with a real task.
The recommendation points toward work a person can actually do, not a generic AI score.
Agree before paid work.
Scope, format, timing and price are discussed before anything is booked or built.
Keep the boundary clear.
The website prepares a draft. It does not silently collect answers, take payment or claim an email was sent.
The 150-step plan
Every module has a job and a gate.
Use the filters to separate what has evidence, what still needs proof and what requires an owner decision.
Module 00Evidence collected
Control, custody and baseline
One V3 website boundary, one preserved release path, one live route and one audit record.
Gate: Baseline custody and public state agree.
Module 01Owner decision
Requirements and discovery
The requirements matrix, user stories, flow, non-functional record, risks and scope waivers are written.
Gate: Requirements and scope waivers receive owner acknowledgement.
Module 02Evidence collected
Architecture and technology selection
The existing family build, local component state, direct email handoff and route boundary are documented.
Gate: The architecture review and v1 interaction contract are accepted.
Module 03Evidence collected
Data layer design
The assessment keeps choices in component memory and sends no answer to a website receiver.
Gate: Positive and negative data-boundary proof is paired with the privacy decision.
Module 04Evidence collected
Backend implementation
There is no assessment API, auth flow, background job or mail receiver. Build and typecheck are proven.
Gate: Inapplicable backend requirements close as N/A WITH PROOF.
Module 05Proof still needed
Frontend implementation
The live interaction, focus behavior and enlarged feature viewport pass; full-site measurement and lint quality remain open.
Gate: Accessibility, performance and UI quality evidence is complete.
Module 06Owner decision
Security, privacy and compliance
No new secrets or runtime dependencies were introduced. TLS, HSTS and dependency checks are read back.
Gate: The privacy boundary and security-header treatment are accepted.
Module 07Evidence collected
Release path and observability
Candidate, staging, selector promotion, public readback and retained rollback records are mapped.
Gate: The release path and runbooks are reproducible and handed off.
Module 08Proof still needed
Performance, resilience and hardening
Supported feature widths pass; native zoom, broader performance, resilience and monitoring remain.
Gate: Applicable performance, graceful-degradation and monitoring evidence is complete.
Module 09Owner decision
Launch and handoff
The Canada release is live and the previous release is retained. Final UAT, rollback and handoff still need closure.
Gate: Go/no-go, 48-hour monitoring and operational handoff are recorded.
Showing 10 of 10 modules. The authoritative record remains the full prompt audit document.
Read the state honestly
Proof is different from intention.
The live release has strong feature evidence. The remaining work is visible instead of being hidden behind a green checklist.
Proven in the current release
- All 24 hurdle, path and readiness combinations.
- Exact direct-email wording to Matthew.
- Keyboard order, focus, responsive layout and effective enlarged viewport.
- No assessment form or new answer-bearing network request.
Still needs closure
- Owner UAT, privacy acknowledgement and scope waivers.
- Native zoom and full-site performance/accessibility measurement.
- Security-header decision, rollback exercise and 48-hour monitoring.
- Final go/no-go and operational handoff.
Rules for every next change
The plan stays true by design.
These are the working rules that keep the page, source, release and documentation aligned.
One home
Keep the source in the existing Webgate family path and the plan in the one V3 phase document.
Plan before code
Define the change, its boundary, its acceptance criteria and its rollback path first.
Positive plus negative
Prove the feature works and prove the unwanted route, receiver or persistence path refuses.
Preserve the working release
Stage and read back a candidate before promotion; retain the previous release.
Record the truth
Append failures, decisions and evidence to the phase plan and the single shared daily.
Next practical step
Use the assessment. Then decide what deserves to be built.
The page stays reviewable and direct: start with a real task, prepare the conversation and agree the work before it begins.
This is a reader-facing map, not a second source of truth. The full plan remains PH-WEBSITE-FULL-PROMPT-AUDIT.md.