Meet your representative

Cocoon learns before it represents you.

Your personal AI representative begins with a conversation—not a complicated setup process.

You explain who matters, how you want everyday situations handled and where your boundaries sit. Cocoon turns that understanding into a representative designed around your life.

A man speaking naturally to his phone as Cocoon begins forming an understanding of his personal context.

No complicated configuration

Talk about your life in your own words.

When you first meet Cocoon, it asks you to name your representative and begins learning through conversation.

Cocoon asks follow-up questions when something needs clarification. You do not need to translate your life into technical settings or workflows.

01

Who should always be able to reach you?

02

Which calls would you rather not handle?

03

How should appointments be arranged?

04

When are you usually available?

05

Which situations require approval?

06

What should never be shared without asking?

A woman reviewing relationship context connected to family, friends, work and an unknown contact.

Relationships matter

People are not just contact records.

A name and phone number are rarely enough to understand how an interaction should be handled.

The same request may need a different response depending on who is asking, why they are asking and what relationship they have with you.

Close familyFriendsWork contactsHealthcareSchoolsHousehold servicesUnknown callersAlways allowed

How you want things handled

Your preferences become practical rules.

Understanding becomes useful when it changes what happens next.

  • When calls may be screened
  • Which appointments may be moved
  • What information may be confirmed
  • When more detail should be requested
  • What may be handled quietly
  • What must always come directly to you
A man explaining preferences as different handling paths form around his phone.
A woman considering calendar, family and work context connected to her phone.

Your time has context

Free does not always mean available.

A blank space in a calendar does not necessarily mean that someone may book it.

The aim is not simply to find an empty slot. It is to understand which time may appropriately be offered and under what conditions.

Work timeFamily timeTravelRestRoutinesFlexible availabilityProtected timeEmergencies

Understanding is not authority

Permission remains separate from knowledge.

Cocoon may understand that a person is important, that a time is available or that a preference exists. That does not automatically give it permission to disclose information or take action.

KnowWhat context may be remembered
UseWhat context may guide an interaction
ShareWhat may be disclosed and to whom
ActWhich actions may be completed
AskWhen control must return to you
A man reviewing separate layers for what Cocoon understands and what it has permission to use.

No confident guessing

A representative should know when to pause.

Cocoon should ask for clarification where instructions conflict, a relationship is unclear, information appears outdated or an action falls outside existing permission.

01

Clarify

Ask when an instruction is ambiguous.

02

Pause

Stop before acting beyond authority.

03

Return control

Bring meaningful judgement back to you.

Learning through experience

Your representative becomes more useful as your life changes.

Learning should be gradual, visible and correctable. A single choice should not silently become a permanent rule.

Corrections

Changes to inaccurate context.

Permissions

Authority you add, narrow or withdraw.

Approved outcomes

Results you confirm were handled correctly.

New relationships

People whose importance changes.

Changing routines

New patterns in work and family.

Preferences

Instructions you add or remove.

Exceptions

Situations that remain one-off decisions.

A man reviewing personal context connected to family, calendar, notebook, envelope and keys.

Your context remains yours

Understanding should never become a black box.

You should be able to review what Cocoon knows, correct inaccurate information, remove irrelevant context and withdraw permissions that no longer reflect your wishes.

People and relationshipsPreferencesAvailabilityPermissionsRemembered contextCompleted interactionsCorrections and updatesRemoved information

Data minimisation

More information is not always better.

Cocoon should only learn information that has a clear purpose in representing you. It should not collect personal details merely because they might become useful later.

The question is not “How much can Cocoon know?” It is “What does Cocoon need to understand to handle this situation properly?”

The result

A representative built around your life—not a generic assistant.

The purpose of onboarding is not to create a larger profile. It is to provide enough useful context to recognise who matters, apply the right permission, handle routine interactions and return judgement when needed.

Meet your Cocoon representative →
  1. Recognise who matters
  2. Understand what is requested
  3. Apply the right permission
  4. Handle routine interactions
  5. Protect your attention
  6. Return judgement when needed

Common questions

How Cocoon learns about you

How does Cocoon learn about me?

It begins with a guided conversation and learns from corrections and confirmed outcomes over time.

Do I need to configure complicated rules?

No. Cocoon is designed around natural conversation.

Does Cocoon automatically access my contacts or calendar?

No access should be assumed. It only uses information required for enabled features and granted permissions.

Can I correct or remove information?

Yes. Personal context should remain reviewable, correctable and removable.

Does Cocoon learn from every interaction automatically?

No. It should distinguish a one-off choice from a confirmed instruction.

What happens when Cocoon is unsure?

It should pause, ask or return the situation to you.

Start with a conversation

Your representative does not need to know everything before it can help.

Begin with one situation, then add context and permissions naturally over time.