Observe → propose loop
Assistant proactif
What it is
Five bricks shipped: usage journal, nightly habit mining, proposal cards, auto-distillation, feedback loop. The assistant notices, proposes, and learns from what you decline.
The architect's call
The guardrail lives in code, not in the prompt: hard cap of 3 proposals per session, a rejection is final for that (habit, kind) pair, an acceptance buys 30 days of silence, three rejections in a row mute a whole category for 14 days. The model receives the aggregate as informative data — never as a decision. Journal private by default: first 256 characters plus a SHA-256 fingerprint, enough to detect repetition without storing the text.
The code
Private repository — walkthrough over a call
Capabilities engaged
Your data cannot leave the building?
That is precisely the problem I solve. A 30-minute call is enough to scope an audit.