A protocol you can walk through
Synthetic examples · No external writesSee the boundaries.
Try the handover.
Three fictional examples. The interactive steps run only in this browser; they never send a message, contact a service or create an official score.
01 / Continuity
A new assistant.
The same garden project.
Alex has planned a neighborhood garden. A new assistant can read the saved packet instead of trying to reconstruct an inaccessible conversation.
Create this kind of packet →The next assistant’s check-in
Here is where we are.
- Available: the project purpose and initial plan.
- Still missing: a site survey and confirmed storage access.
- No accepted decisions yet: the project remains a draft.
- Next step: Alex chooses shared storage and checks access with Sam.
This is a fictional reading example, not a claim that any external account was restored.
02 / Collaboration & bounded delegation
Your context stays private.
You choose what leaves.
Alex can let an assistant prepare routine garden updates from selected information. That permission is limited to Sam, garden planning and the two fields below. It does not authorize sending.
The neighborhood garden
Progress: The layout is ready for review.
Next step: Choose plants for two shaded beds.
Private note: Alex wants time to think before inviting more volunteers. This note is excluded from the selectable sharing fields.
Delegation can reduce repetitive confirmations within a defined scope. This demo delegates preparation; every simulated outgoing message still needs approval for its exact current content.
Pause or revoke future activity. Revocation cannot erase copies someone has already received. This example creates no real permissions or external messages.
Define the scope first
Example grant: prepare garden-planning drafts for Sam using project progress and next step. No private notes. No automatic sending.
No scope granted. Reading is not sharing permission.
Change the selected fields to edit this message. Free-form private notes cannot enter this bounded example.
Private draft. Nothing has been approved.
Action history in this tab
History and receipts disappear on reload or reset. Demo — no message sent. A local receipt is not proof of delivery or acceptance.
03 / Service interface
You prepare a score.
The service owns the rules.
Imagine a community design jury. Your assistant can help draft scores against published criteria; an actual service still controls authentication, eligibility, deadlines and revisions.
Local demonstration — not an official score. No service adapter is connected.
Read the authority boundary →Fictional entry / The rain garden
Prepare an illustrative score
Each criterion is an integer from 1 to 5. All three are required. These are illustrative criteria, not official jury rules.
Private score draft. No official result.
Developer example: a fictional shared-project packet
This optional vNEXT-D example uses two fictional participants. Personal setup needs only you.
Your example project
Use fictional labels only. Nothing entered here is sent or saved by this site.
Review before downloading
Prepared in this browser. Nothing has been sent. Setup is incomplete.
Your storage is configurable.
Local files, your server, a Git repository or a cloud folder are choices based on trust and practical needs. No proprietary HAYAT account or central storage is required.
These are storage examples; connectors are not installed here. Keep independent copies and test recovery. Storage choice alone is no guarantee of confidentiality or backup.