HAYAT

HAYAT means life.

Your digital life.
Under your
control.

Choose where your knowledge lives, which tools you trust, and what your agents are allowed to do. Keep your work portable. Share on your terms.

Set up my HAYAT Explore the protocol

A free, open protocol idea. No mandatory HAYAT account.

You choose the storage, the tools and the sharing.A person is central. They choose where context lives, grant limited access to an assistant and separately select a recipient and purpose for sharing. There is no central HAYAT cloud.YOUR CHOICES. YOUR BOUNDARIES.01 / CHOOSE A HOMESaved contextFiles · server · Git · cloudA choice based on trust02 / GRANT A SCOPETools & agentsRead, prepare, actWithin your scopeYOUAt the center.03 / CHOOSE WHAT LEAVESSelected recipientChosen data. Defined purpose.
YouAt the center
  1. Choose where context livesLocal files, your server, Git or a cloud folder.
  2. Grant tools a limited scopeReading, preparing and sharing are distinct permissions.
  3. Choose what leavesSelected information, recipient and purpose.
Access is a choice.
Sharing is a separate choice.FIG. 01 / HUMAN CONTROL
01 Choose your storage and tools
02 Define what agents may do
03 Decide what you share

The work is part of your life

Change your tools.
Keep your progress.

Your projects carry knowledge, decisions, relationships and unfinished ideas. Give that context a home you can access, so the next tool can work from what you have saved.

YOUR CONTEXT

A history you can inspect.

Keep sources, accepted decisions, meaningful action records and next steps in accessible files. Say clearly what is missing.

YOUR AUTHORITY

Help, within boundaries.

Delegate routine work within an agreed scope. Inspect outcomes, pause automation and revoke future access where enforcement supports it.

YOUR CHOICE

Share deliberately.

Choose the information, recipient and purpose. Permission to read private context is not permission to send it elsewhere.

Choose a home you trust

Your storage.
Your decision.

Use one place or a combination. HAYAT defines conventions for context and permissions; it does not require a central HAYAT cloud.

Local files

A folder you can inspect and copy. You manage access and backup.

Your server

A system you operate. Access controls and upkeep remain your responsibility.

A Git repository

Versioned text and history. Review visibility, collaborators and what is committed.

A cloud folder

A provider you choose to trust. Check sharing settings and keep independent copies.

Storage examples, not automatic connections. None guarantees confidentiality, backup or recovery. Google Drive is one possible cloud folder, not a requirement.

Simple enough to begin with files

Save the thread.
Leave a next step.

A project index, saved decisions and clear permissions are a practical starting point. Add agents and adapters when they serve your needs.

Set up my HAYAT
  1. Give the work a home.

    Choose storage and verify who can read, write and accept decisions.

  2. Make the next step visible.

    Save sources, decisions and missing context in a portable project packet.

  3. Keep a tested way back.

    Make independent copies and rehearse recovery. A saved file is only useful if you can open it again.

One idea. Three useful starting points.

Keep going.
Work together.
Build on your terms.

Start manually, then add supported tools. These examples show the conventions; they do not claim installed production integrations.

01 /

Continue a project.

A new assistant reads the context you saved, checks what is missing and helps with the next authorized step.

Follow the handover ↗
Your files
Your chosen assistant
02 /

Share selected work.

Keep private context separate. Review a bounded message for a chosen recipient and purpose; pause or cancel when you need to.

Try the control example ↗
Private context
Your choice
Selected message
03 /

Work with a service.

Let an assistant prepare a permitted action. The service still enforces authentication, eligibility and its own rules.

Explore the service example ↗
Your scope
Service validation

A name with a personal beginning

HAYAT.
Life, carried forward.

HAYAT is named after the founder’s mother. He explains her name as “life.” That meaning guides the project: the knowledge and work we build with AI should be able to continue beyond any one tool.

A practical reason for continuity

The founder reports losing access to an Anthropic account while independently saved project material remained available. Another assistant could read selected saved materials and continue work.

That is continuity from saved material, not a claim of complete restoration or shared memory between providers. Accessible formats, independent copies and recovery checks make that ambition practical.

Free to use. Open to build upon.

Build something that
keeps people in control.

HAYAT is a free, open protocol idea: conventions for people, context and scoped actions. Developers can build agents, storage adapters and service interfaces on this foundation.

The draft and examples are available here. A public source repository and software license are not yet verified. Hosting, provider APIs and optional implementations may have their own costs and terms.

Explore the developer entry ↗Read and build on the draft →