AI + Local Gemma
Use AI as a connected tool without making it the center of every workflow.
HYiYH treats AI as one connected tool among projects, Body, calendar, maps, research and business work. Eligible Expert workflows can connect to a privately configured local Gemma service, while the rest of the operating system continues to function without requiring every record to be sent to an AI provider.
What it does
A focused surface with connected context.
Local Gemma connection
Expert users can connect the website to a separately configured local Gemma service rather than relying exclusively on a remote hosted model.
Provider-aware tools
AI features are treated as explicit provider workflows with membership and configuration checks instead of invisible background processing.
Useful without AI
Projects, maps, calendar, Body, drawing, capture and Local Workspace remain functional tools on their own.
How it fits into a day
Practical workflows, not feature checkboxes.
Ask in context
Use AI where it can reduce synthesis work, then return the result to the project or decision that created the question.
Keep configuration explicit
The local model endpoint is configured by the operator and is not silently enabled for every account.
Avoid fabricated evidence
Performance and Body workflows continue to distinguish real available records from unavailable measurements rather than using AI to fill missing health evidence.
Start from the problem instead
See how this feature fits into a real workflow.
The HYiYH solution guides begin with common friction—digital overload, scattered project context, private Body planning, local-first work, professional operations and cross-device workflows—and show which features work together to reduce it.