The problem
A prospective client needs to understand what help is available and whether the work supports the claim. A hiring manager needs the career record and a clear account of the person’s contribution. Both need to find the relevant example without reading an entire portfolio.
My role
I set the audience, service range and rules for using professional evidence. I directed the structure, content and review of the site. AI agents implement and check the pages under those requirements.
What was built
The site connects services to a filterable work library, career history and a downloadable public resume. Each work entry distinguishes my contribution, the deliverable, evidence of use and any measured outcome. Private employer material stays outside the site.
Content checks tie numerical statements to claim records and require released claims for public release. Media requires provenance. Browser checks cover page navigation, forms, narrow screens and accessibility. The static site and its media production tools have separate dependencies.
Evidence
The source is available for review. The resume has a reviewed text projection and matching export hashes. Build and browser receipts are engineering evidence; the site has no published visitor or sales results.
What this does not show
This is the current website project. The mailbox works, as confirmed by Gage. Public launch and a completed inquiry-to-CRM test remain open. A disabled preview form is not evidence of a working inquiry service.
Relevant next action
For a business website, the first scope identifies the visitor, the decision the page should support, the content needed and the handoff after an inquiry. Website and service work.