Private family context
One family, one context
Marlow should operate inside a specific family context with clear isolation and no casual bleed between households.
Trust & privacy
Marlow should feel like help, not a risk.
Families only trust a product like this if it is clear, careful, and bounded. Marlow needs to earn that trust through behavior, not slogans.
Design principle
Trust beats aggressive automation.
When something is obvious, Marlow can help quietly. When something is unclear, it should ask. Confidence-aware follow-through matters more than showing off.
Clear source awareness
Actions should be explainable
If Marlow changes the calendar or creates a reminder, it should be able to say what message or source triggered that action.
Curated memory
Remember what matters, not everything
Family memory should stay useful and bounded — preferences, context, and important decisions, not endless transcript hoarding.
What trust means here
The product has to be careful in very specific ways.
Marlow is not just answering questions. It may update calendars, create reminders, interpret school messages, and filter household information. That means it has to be trustworthy in ways a generic chatbot does not.
Families should be able to understand what Marlow changed, what it chose to ignore, what it is unsure about, and what it remembers.
Confirmation when uncertain
A clear reschedule can become an update. An ambiguous message should become a question, not a silent guess.
Parent control over safety
Child-facing behavior, restrictions, and escalation boundaries should be parent-led and easy to inspect.
Preference visibility
If Marlow learns a household preference like “ignore sports emails,” that rule should be visible and editable.
Low-drama summaries
Trust is also tonal. Briefings should be calm, clear, and practical — not alarmist or noisy.
A good trust model
Explain what changed, what matters, and what still needs your decision.
The best version of Marlow doesn’t just act. It keeps the family confident about what it did and why.
- Source-linked actions
- Visible preferences and rules
- Bounded child-safe mode
- Clear review paths for uncertain changes
Example
Why Marlow asked first
- The email mentioned a changed pickup location
- The time was clear, but the pickup details were ambiguous
- Marlow updated the event time and asked for pickup confirmation
- The family stayed informed instead of surprised