Explanation
Explanation
Background on why icuvisor works the way it does — read these to build a mental model, not to complete a task.
A short explanation of Model Context Protocol for icuvisor users.
How the local binary, OS keychain storage, and no-SaaS connector model fit together.
What icuvisor keeps local, what still leaves your machine, and what it does not claim.
Why tool responses stay small unless you ask for full detail.
The reasoning behind safe, full, and none delete/write modes.
How icuvisor targets multiple athletes without making athlete IDs credentials.
Why get_fitness_projection is a deterministic scenario model, not a forecast.
How to read interval data without inventing workout steps that were never planned.
Why there is no add_note tool — notes are NOTE-category calendar events.