Noel Q Portfolio

what it proves

Proves that the portfolio itself can be engineered as a trustworthy product: recruiter-first presentation, reviewed evidence, privacy-aware AI, bounded provider routing, fail-closed storage and a secure operational path.

This website is a project in its own right. It combines a server-rendered recruiter journey, project case studies, a public-only knowledge base, a bounded AI assistant and a Google-protected operations foundation. The implementation treats unsupported claims, private source material, provider failure and cost ceilings as product constraints rather than details to hide.

the journey

1. 01 · where it started

   The work began with PortfolioOps: a private, curated view of project evidence and readiness. The first public-site plan was much simpler -- turn that reviewed material into a recruiter-facing portfolio with an optional chat assistant.

2. 02 · the challenge

   A public AI portfolio creates harder problems than rendering project cards. Private career material had to stay out of prompts and bundles, model answers needed to remain factual, free-provider failures and cost limits needed predictable behaviour, and the deployed site needed an accurate privacy notice rather than broad assurances.

3. 03 · what changed

   The site was rebuilt around a public-only evidence boundary, server-owned encrypted chat sessions, a signed privacy acknowledgement, bounded Cloudflare-to-Gemini routing, deterministic project tools, secret scanning and a Netlify deployment. The homepage became recruiter-first, the pixel portrait became the visual identity, and Google OAuth plus privacy-preserving Operations metrics replaced an over-complex self-hosted recovery design without exposing unfinished modules.

4. 04 · where it stands

   v1.0 is live at noel-q.dev with project case studies, the reviewed public knowledge base, the bounded chatbot and the Role Matcher. Automated type, lint, test, build and secret checks pass.

proof points

• ·Public chat grounding includes only committed project evidence and active records explicitly approved for public use
• ·Chat history is server-owned, encrypted before storage and expires after 24 hours; storage failure closes the AI route
• ·Cloudflare is the bounded primary and Gemini is a single pre-output fallback, with no paid-provider escape path
• ·The deployed surface includes a recruiter-first homepage, project case studies, privacy acknowledgement, deterministic secret scanning and an authenticated Operations foundation

evidence

where to see it

Live site: noel-q.dev

The repo is currently private. The evidence on this page comes from the case study; happy to walk through the code in a conversation.