$ Pulse · AI Notes
How AI was used to build this piece, then an honest account of how AI is — and isn’t yet — used inside it.
## BUILD_PROCESS
Pulse was built with Claude Code pairing throughout — scaffolding the Azure Functions app structure, the Cosmos DB container and partition-key design, and the seed-data generation scripts, then iterating on the trend-chart and coaching-tip UI against real responses from the running Function App rather than static mockups.
## COACHING_TIPS_ARE_CURRENTLY_MOCKED
Coaching-tip generation is currently mocked, not live AI. generateCoachingTip(techStats)returns a canned or randomized tip from a small local array of examples rather than a real Azure OpenAI call, pending model deployment quota. This page states that plainly rather than implying the tip generation is live AI today — the same honesty standard this site already holds itself to elsewhere (Bug List, Testing & Verification) when there’s genuinely nothing more to report yet.
What’s real is the architecture around the mock: tip generation is isolated behind that single function boundary specifically so swapping in a real model call is a contained, one-file change later, not a rewrite. See Design Notes for why that isolation was designed in up front.