What Cocoon may learn
Important people, preferences, routines, availability, repeated instructions and how you like things handled.
Permissions and boundaries
You decide what Cocoon can handle, and what comes back to you.
Cocoon is designed to represent you without taking over. You can decide what your personal representative may remember, who it may respond to, which routine tasks it can handle, and when it must ask before acting.
The problem
Most automation asks for too much trust too soon.
Many tools ask for access first and explain the consequences later. That is not how a personal representative should work. Cocoon should become useful by learning your preferences, respecting your boundaries and acting only where you have allowed it to act.
Useful help should not mean handing everything over. A representative should know the difference between a routine step, a judgement call and something that needs your permission.
The goal is not full automation. The goal is useful help without losing control.
The boundary model
Remember. Handle. Ask. Pause.
Cocoon should know the difference between help, judgement and permission.
What can move forward
Screening calls, confirming simple details, collecting routine information, summarising outcomes and low-risk admin.
What needs you
Sensitive decisions, commitments, unusual requests, approvals, personal judgement calls or anything with consequences.
What should not be guessed
Anything outside your rules, unclear intent, sensitive information requests or situations where checking first is safest.
Permission-led action
Cocoon should know when to act and when to stop.
A useful representative should not ask you about every tiny step. But it also should not improvise when something matters. Cocoon uses your permissions, relationship context and the reason for the request to decide whether to handle, ask or pause.
- Routine requests can usually be handled inside your rules.
- Personal context helps Cocoon respond in the way you prefer.
- Sensitive moments should come back to you before anything happens.
- Unclear situations should pause, ask or escalate rather than guess.
What you control
Your boundaries are the operating rules.
You can define who Cocoon may respond to, what it may say, what it may remember, what it may arrange and when it must ask you first.
Real examples
Useful help still needs clear routes.
The same representative can handle routine steps, pause at sensitive moments and bring decisions back to you.
Appointment confirmation
Cocoon confirms the time and brings back the outcome.
HandleUnknown caller asks for details
Cocoon screens the request but does not share sensitive information.
Pause or askService provider needs approval
Cocoon collects the options and brings the decision back to you.
AskTrusted person needs access
Cocoon applies your straight-through rule or escalates according to your preferences.
Handle or let throughWork request during protected time
Cocoon can hold, summarise or escalate depending on the rule.
Handle, ask or wait
Where judgement stays with you
Some decisions should stay with you.
Cocoon can reduce interruption, but it should not replace your judgement. When a request involves consequences, personal information or uncertainty, the safest action is to bring it back to you.
- Approving a payment or commitment
- Sharing personal information
- Changing an important appointment
- Responding to a sensitive personal matter
- Anything outside Cocoon’s permission rules
Boundaries
Cocoon does not get a blank cheque.
Permission-led representation only works if the limits are clear. Cocoon should be useful inside your rules, cautious at the edges and ready to come back to you when something matters.
- It does not act outside the permissions you set.
- It does not treat uncertainty as permission.
- It does not share personal information just because someone asks.
- It does not make sensitive decisions without approval.
- It does not assume all contacts deserve the same access.
- It does not stop you from overriding or changing a rule.
Related features
Boundaries connect to the rest of Cocoon.
Permissions shape who gets access, what can be handled, when your attention is protected and what Cocoon learns from you.
Permissions and boundaries FAQ
Common questions about control, approval and limits.
Can I choose what Cocoon is allowed to do?
Yes. Cocoon should let you define what it may remember, who it may respond to, what kinds of tasks it may handle and when it must ask first.
Does Cocoon act automatically?
Only inside the boundaries you choose. Routine tasks can move forward, while sensitive or uncertain requests should come back to you.
What does Cocoon ask approval for?
Cocoon should ask before sensitive decisions, commitments, sharing personal information, unusual requests or anything outside the rules you have set.
What happens if Cocoon is unsure?
It should pause, ask or escalate rather than guess. Uncertainty should not be treated as permission.
Can I change permissions later?
Yes. Your boundaries should be adjustable as your life, relationships and preferences change.
Can Cocoon share my personal information?
Only where you have allowed it. Sensitive requests should be treated carefully and brought back to you when needed.
Is this the same as phone app permissions?
No. Phone permissions control what an app can technically access. Cocoon permissions are about how your representative behaves on your behalf.
Can I turn off a type of handling?
Yes. You should be able to restrict or disable specific types of handling and keep Cocoon in a more limited role.
Let Cocoon help without handing over control.
Your representative can handle the routine, pause at the sensitive and ask when something needs you.