Current launch state
This public V1 is static and route-led. There is no live Ask Navid memory, no generated answer system, and no visitor profile feature.
Privacy
Static first. Public sources only.
The launch version keeps the public content layer separate from future Ask behavior. Vercel Web Analytics can measure aggregate page traffic once enabled in Vercel; no public LLM calls, backend signup flow, or durable visitor storage are part of V1. Email delivery is prepared as a future route, but not connected.
Analytics
Vercel Web Analytics is prepared for aggregate page-traffic measurement after the production deployment and Vercel project-level Analytics toggle are active. No Google Analytics, Tag Manager, custom visitor profiling, or Speed Insights are part of this pass.
Letters
The RSS feed is public and does not store subscriber information. Letters by email is prepared as a future route, but no signup backend or provider webhook is connected in this public V1.
Email signup
There is no live signup form or subscriber storage in this pass. Visitors can use navid@navidbr.me for a manual update request. The site should not claim a provider, audience, cadence, or stored list until that setup is actually live.
Domain
The public site is prepared for navidbr.me. Preview deployments remain review surfaces only; production copy should be verified on the custom domain after each launch.
Private systems
Ask Navid does not connect to non-public notes, accounts, messaging apps, local files, restricted source material, or personal operating context.
Future Ask Navid
If Ask Navid becomes live later, it should answer from approved public content only, show boundaries and gaps, avoid unsupported claims, and require clear consent for any feature that stores visitor-provided information.
Deletion or withdrawal
If a future feature stores consented information, requests for deletion or correction can be sent to navid@navidbr.me.
Boundary
Any future live Ask release needs an explicit release decision, approved public sources, refusal behavior, rate limits, review paths, and a separate launch review before it is presented as live.
Contact
Send the working context.
Send the business pressure, workflow, source boundary, or proof question. Best fit: hiring, AI roadmap, product-system work, and collaboration where evidence matters before claims.
Navid