Help hiring teams assess Jay for senior software engineering, enterprise AI integration and forward deployed engineering (FDE) work. The intended takeaway is that Jay can understand business workflows, connect software and AI, and contribute throughout delivery. FDE is a direction of interest, not a previous job title. No statement of immediate availability is made.
The primary path is homepage positioning → four engineering cases → professional experience → email / LinkedIn / existing CV. The complete 30-project inventory moves to /projects/ and /zh/projects/. The homepage is for assessing fit; the archive is for exploring breadth. Both languages must preserve facts, stages, attribution and actions.
- Owner's supplied review: https://chatgpt.com/share/6ac9fd69-805c-83ec-a9ea-33b0b300afd2. Adopt the recruiting focus, concise case selection, delivery evidence, CV access and metadata correction.
- Owner explicitly requires the Transformer animation to remain unchanged. Preserve its source and all existing
.transformer-field, panel and responsive styling. - Owner confirms FNZ work is delivery-focused and confidential. Use only general responsibilities already in the existing public CV, corroborated by FNZ's official Analyst Developer role description: https://fnz.wd3.myworkdayjobs.com/en-US/fnz_careers/job/Analyst-Developer_REQ-16441-1. This is a general role description from another office, not evidence of Jay's specific assignments. Do not infer trading, payments, migrations, scale or proprietary architecture.
- Existing public CV reviewed in full for the career summary; retain original PDF bytes and URL. Link as CV (PDF), without claiming it is a newly tailored application document. Do not repeat its employer email or internal assignment name in new web copy.
- CRM: existing reviewed portfolio, application source and owner commit history support application/API/CLI implementation, revision history and controlled writes. Use an anonymous title and an empty-data preview. Describe internal operational use without customer names, counts, endpoints, records or commercial impact claims.
- NZ Accounting Assistant: https://github.com/maxazure/new-zealand-accounting-assistant, README and scripts. Original evidence, structured JSON records, unresolved matches, deterministic tooling and Xero CSV / review-pack delivery support the case. Describe software behaviour; give no tax advice, claimed accuracy rate or automated-filing claim.
- HiLily: https://www.hilily.ai/, team and project-stage sections. Attribute volunteer technical guidance in AI architecture, memory and audio processing. Product is a functional MVP preparing for pilots. Team owns overall product delivery; do not claim sole authorship or validated health outcomes.
- CodexView: https://github.com/codexview/codexview, README, package boundaries and owner commit history. Shared transcript events, adapters, React viewer and Markdown CLI support the case. Public source is evidence of implementation, not adoption.
- Video Editing Skill: https://github.com/maxazure/video-editing-skill. Link directly as further public work. Avoid an undated star/fork counter or implied active usage.
| Change | Hypothesis / scope | Primary outcome | Guardrails | Baseline / period | Release evidence | Observation window | Segments | Result source | Decision | Owner |
|---|---|---|---|---|---|---|---|---|---|---|
| recruiting-2026-10 | Clear fit + attributable cases help relevant hiring teams start a conversation; both homepages and project indexes | Relevant recruitment conversations where the sender mentions the portfolio | Confidentiality; accurate role/stage; working CV/contact links; mobile readability; unchanged animation | No existing conversion analytics or comparable count; old homepage gives 30 equal-weight cards | Published source 8520c86; Pages run 38041508348 | First 28 full days after publication; no calendar reminder created | Recruitment source and role interest, manually recorded only if volunteered | Owner's manual count; no new tracking or data collection | observing; no result claimed | Jay |
Keep the graphite/paper/orange palette, fonts, fern, animation and small-image privacy constraints. Show four text-led cases with problem, role, engineering decision and honest current evidence. Keep links to public source/demos beside each relevant case. Expand FNZ into general delivery responsibilities; put tools after capabilities. Add direct CV and LinkedIn actions above the fold and retain contact email.
Update homepage descriptions to distinguish employment from independent AI projects. Preserve established homepage title, schema identity, all old homepage anchors, CV bytes and existing public assets. Add reciprocal project routes, complete initial HTML, sitemap entries, route-specific metadata and same-page locale switching.
Validate typecheck/build, generated HTML contracts, SEO comparison, local links, byte-identical animation/CV/assets, and rendered desktop/mobile paths in both languages. Browser checks include 320px, keyboard navigation, no-JavaScript and reduced motion. No claim about ranking, hiring conversion or field Core Web Vitals follows from these checks.
The installed website skill's optional Impeccable package is unavailable after searching local skill directories. Use the available frontend-design guidance and a direct rendered repair pass; do not claim an Impeccable run. No redesign, new media generation, business CRM operation or analytics setup is in scope.
pnpm check: 24 files, zero errors/warnings/hints.pnpm buildand the seven-page HTML verifier pass.- SEO baseline: deployed
525d9eb, successful Pages run38034557385, matching live/home build bytes. Comparison has zero audit errors, zero critical findings and four intentional warnings (two description changes, two routes added). - Internal link graph: all six indexable pages reachable; no orphan, dead-end, generic-anchor or broken internal URL findings. Existing homepage/group anchors remain available. CV SHA-256 is unchanged.
- Browser: Ego/Chromium at 1440×900, 820×900, 390×844 and 320×844; both homepages and both project indexes. No page-level horizontal overflow. Portrait below the first screen, 94×94px desktop / 76×76px phone, rounded square with a face-centred CSS crop at the owner’s request. Featured claims and archive counts match across languages. Generated previews retain low resolution and show illustration labels.
- Interactions: project language switch preserves page; archive menu returns to the correct homepage section; mobile menu closes and focuses Contact; Escape returns focus to the menu button. CV/email/LinkedIn targets verified without sending a message or changing external profiles.
- Off-happy states: no-JavaScript navigation and all four cases available; text-spacing changes preserve 320px reflow; reduced-motion preference reaches the original static canvas mode; forced colours preserve contact information and controls. The decorative canvas remains blank without JavaScript, matching the preserved original component.
- Preservation: Transformer component SHA-256
adcc96f6413e0ff67a29fd0dd94ec7e7c3848d31f22d07538f10318c7765450f; original CSS bytes remain an exact prefix of the updated stylesheet. All thirty project image files and the existing public CV are byte-identical to baseline. New styles do not target the Transformer or its panel. - Static resource audit: zero critical findings/warnings; project-specific byte ceilings pass. Homepages are approximately 154KB including the 57,785-byte CSS fern. JS 5,714 bytes, CSS 31,512 bytes, fonts 14,432 bytes. These are uncompressed source/resource counts, not measured load times or field Core Web Vitals.
- Visual and text review: desktop and narrow screenshots for the complete visitor path, portrait, selected cases, career and contact are stored temporarily outside Git. Copy heuristic flags the descriptive “from business problems to working systems” and the existing architecture-to-delivery label; both are retained because they describe the actual workflow. No invented metrics, altered testimonial or confidential project details were added.
- Limitations: branded Safari, screen-reader certification, field CWV, hiring outcomes and Search Console indexing have not been measured. No Lighthouse binary was available, so no new Lighthouse score is claimed. The existing documentation files do not match the newly installed skill’s template schemas; those format checks remain reported separately from passing implementation checks.
Portrait follow-up: the owner requested a square or circular frame. Applied a 10px rounded square using CSS object-fit cover at center 40%; 94px desktop, 76px phone, 60px print. Build and HTML verification pass. The subsequent browser capture was stopped because the browser task space was under user control; no new crop screenshot is claimed.
Name follow-up: display “刘杰” in the Chinese hero name and retain “Jay Liu” in English. This is an intentional Chinese H1 wording change; canonical identity and metadata remain bilingual.
Publication: the owner explicitly authorised push and deployment. Commit 8520c86 was fast-forwarded to master and Pages run 38041508348 succeeded. All 57 live release files matched the local build; seven-page contracts, HTTP-to-HTTPS/www redirects and custom 404 passed. The subsequent six-language work is recorded in localisation.md.
The owner requested replacing the internal-style PDF and adding clear CRM evidence. The earlier preserve-CV-bytes rule is superseded; the stable download URL remains. A fictional browser-only walkthrough and internal workflow story are now implemented in all six locales. See current recruiting evidence. The owner subsequently supplied publishable FNZ and HiLily examples, incorporated in the follow-up below.
The owner describes the CRM focus as integrating AI workflows and customising them around each business's service problems, including reminders, analysis/decisions and human review before final execution. Public copy expresses the business-problem-to-action workflow and distinguishes the implemented shared records, follow-up reminders and controlled API/CLI writes from broader AI analysis/decision extensions. Reminder behaviour is corroborated by the application follow-up scheduling and dashboard logic. No autonomous AI decision engine or configurable approval product is claimed to be shipped.
FNZ: the owner states his main work is analysing and resolving complex problems and ensuring high software reliability. The career copy and CV now lead with this responsibility while preserving the Analyst Developer title and confidentiality.
HiLily: the owner identifies hardware development and hardware/software/system extension as central difficulties, with single/dual microphone echo cancellation, recognition in noisy environments, fast response and audio-input/audio-output language models. Copy attributes guidance and contribution to the volunteer AI Coach role, and keeps hardware/product delivery with the team. No measured latency, recognition score or algorithm invention is claimed.
This is first-party career/project evidence supplied in the conversation, not an independently measured outcome. The six language dictionaries, project summaries, internal usage story and two-page CV are updated together. The underlying demonstration remains an explicitly fictional browser simulation of write safety, not a demonstration of autonomous AI analysis.