# Oo relationship over time

How evOo should feel after the first run — not just onboarding.

## Principles (Ingo)

| Principle | Product | Anti-pattern |
|-----------|---------|--------------|
| **Always on** | 24/7 presence feeling — help when needed | Fake urgency, guilt trips |
| **Compounding** | Smarter/more practical/more attuned with use | Static bots that forget nothing and learn nothing |
| **Never creepy** | Warm competence; intimacy from consented context | Surveillance vibes, guessing private life |
| **Not yes-men** | Respectful pushback sometimes | Echo chamber, sycophant Wunderwuzzi |

## Implementation notes

| Layer | How |
|-------|-----|
| **Memory** | User `MEMORY.md` seeds `## Oo relationship (product contract)` on first harvest (`user-relationship-contract.ts`) |
| **Compounding** | Existing space/bot memory + threads — deepen with use; onboarding only seeds honest signals |
| **Persona copy** | Voice/stage lines: peer + pushback option, not flattery (`voice-persona-copy.ts`, `bot-persona.ts`) |
| **Group** | Fun friction between Oos models disagreement — not yes-men to each other either (`GROUP-CONVERSATIONS.md`) |
| **Anti-creep** | Harvest only consented/local signals; mark unknowns as unknown; no lifestyle inference |

## Ties to other rules

- **No Wunderwuzzi** — pushback requires a clear lane, not omniscient lecturing
- **Emergent ensemble** — compounding applies to the crew, not one mega-agent
- **Accessibility of ambition** — always-on ≠ always interrupting; quiet-doer mode respected

When adding features that "know the user better": ask *earned or creepy?*

## Future: ambient & video presence

Optional video calls and ambient home presence (alarm/camera metaphors) are **roadmap only** — see `VOICE.md` and `docs/PRODUCT.md`. They must remain user-opt-in with explicit consent UX; never ship as always-on surveillance. Current slice: Stage + sound + onboarding reassurance, no camera without consent flows.