Protect the work.
Learn from the data.
Scale with intent.

As the site became more original — especially with Thoughts When Driving — the next question was not another feature. It was how to make the ownership and sharing rules clear without pretending that copyright can lock up ideas themselves.

1. Add a sitewide copyright notice. Public pages now identify © 2026 Rouzbeh Salehinia and link to one consistent content-use policy.
2. Give the blog extra clarity. Thoughts When Driving now explains that original human-authored writing and original photographs may be linked and briefly quoted with attribution while substantial republication requires permission unless the law allows it.
3. Publish a Copyright & Content Use page. The policy separates ordinary sharing from republication and clearly states that facts, general ideas, methods, short phrases, fair use and other legal rights are not being claimed as exclusive property.
4. Document the AI boundary. Because this is an AI-assisted project, the policy limits its claim to human-authored or otherwise protectable elements instead of overstating what belongs to the site.

After the site began appearing prominently for a branded Google search, the next move was intentionally not another public feature. We built measurement so future decisions can be based on real behavior instead of guesses.

1. First-party website activity. Page views, anonymous browser-session counts, page popularity and referral domains are collected through the existing Vercel + Supabase stack.
2. Reza usage signals. The dashboard measures Reza opens, recorded-question IDs, general intent categories, résumé clicks, calendar clicks and unknown-question ticket counts.
3. Blog engagement. Opening a Thoughts When Driving post is measured so future writing can be compared by actual reader interest.
4. Private owner access. Site Insights lives behind the same secure 30-minute owner session used by Reza Command Center.
5. Privacy was designed in. The analytics system does not intentionally store visitor IP addresses or copy freeform Reza question text into the analytics table.

We tested the idea of creating a separate recruiter landing page, but it duplicated information already available throughout the portfolio. The simpler solution was stronger: put the recruiter experience inside Reza and keep one public website experience.

1. Add a Recruiter Overview button. Hiring managers can request a fast two-minute summary directly from Reza.
2. Keep the response focused. Reza summarizes Rouzbeh’s operations background, core leadership strengths, recommendations and interview-answer library.
3. Make the next actions obvious. From the same response, a recruiter can open Career, Recommendations, the résumé or the live booking calendar.
4. Measure usage. Site Insights records the recruiter-overview intent so we can see whether visitors actually use it.

As the site became a real professional platform, the contact identity needed to match the brand. Phase 3 added a website-owned Google Workspace mailbox at rouz@rouzbehsalehinia.com and connected the site’s owner-access flows to it.

1. Create the domain mailbox. Google Workspace was connected to rouzbehsalehinia.com so the site could use a professional address on its own domain.
2. Verify the domain in Vercel. Google’s TXT verification record was added to the domain DNS without disturbing the live website records.
3. Route and authenticate mail. Gmail routing was activated with the required MX record, then SPF and DKIM were added so outgoing mail can be authenticated.
4. Create useful aliases. contact@rouzbehsalehinia.com and reza@rouzbehsalehinia.com were added as aliases feeding the main Rouz mailbox.
5. Route owner permissions to one mailbox. Reza Command Center access links, unknown-question escalation, API billing alerts and Thoughts When Driving author access now route to rouz@rouzbehsalehinia.com.
6. Standardize the public contact address. The website and Reza now use the domain-branded email instead of a personal Gmail or Yahoo address.
7. Update every résumé endpoint. The preferred résumé PDFs use the new professional email while view, download and compatibility filenames remain synchronized.

Late in Phase 3, the homepage went through its most aggressive visual iteration cycle. The goal was not to add decoration for its own sake. It was to make the first screen feel unmistakably connected to operations leadership while still working cleanly on a phone, tablet and desktop.

1. Replace the circular leadership wheel with a moving film reel. Eight real career photos became an equal-size, gold-framed horizontal reel with a duplicated set for a seamless loop. The reel preserved the career-history feeling while using far less vertical space.
2. Test — then remove — the Quote of the Day panel. The quote concept looked good in isolation, but on smaller screens it competed with the hero image and contributed to sizing and overlap problems. The final homepage gave the warehouse hero the full width instead.
3. Stabilize the mobile header. Reza’s AI control stayed in the upper-right area with its own portrait and description, while the navigation was rebuilt as a predictable grid so it would not cover nearby content. The extra How We Built It navigation tab was removed; the yellow page-body button remained.
4. Make the warehouse hero match the reel. The original portrait card was replaced with the warehouse scene and then widened until its outer edges matched the film reel above it. Unique asset filenames were used when browser caching made image replacements appear unchanged.
5. Rebuild the reel gallery interaction. The first version was difficult to tap while it was moving, and the old Previous/Next logic no longer matched the new reel. The gallery was rebuilt so a touch pauses the reel, either copy of the loop can open the viewer, and large overlay arrows plus swipe navigation handle browsing.
6. Experiment with motion — and reject the wrong motion. We tried subtle camera drift, clipped image layers, moving pixel regions and Reza characters traveling across the navigation. Some versions were too subtle to notice; others made Reza’s body appear to break apart or made the interface feel busier than the content.
7. Use one intact video frame sequence for the final hero motion. The current approach moves the warehouse scene as a real looping MP4 instead of independently shifting sliced image regions. That keeps Reza, the forklift and pallet visually intact while preserving the scanner/glow treatment and adding an iPhone/iPad autoplay fallback.

The final Phase 3 decision was operational rather than visual: declare a stable version. The site had reached the point where another large redesign was more likely to introduce regressions than improve the story.

1. Keep the core navigation stable. Home, Career, Recommendations, Thoughts When Driving and LinkedIn remain the main public paths.
2. Keep Reza focused on usefulness. Reza remains the AI website manager for interview answers, recruiter context, résumé/contact access, unknown-question escalation and booking — not a decorative character moving around the page.
3. Protect the working visual hierarchy. Film reel first, warehouse hero second, leadership identity and How We Built It CTA below. Future changes should be isolated rather than rebuilding the whole cover.
4. Shift the work from redesign to reliability. The next improvements should prioritize page speed, mobile behavior, gallery controls, Reza accuracy, analytics and real visitor feedback.