# HAYAT human-control guide — human-control-1

Status: informative guidance for the local candidate. This is not a permission grant or a new normative protocol version. The vNEXT-D schemas, immutable references and Action/Approval version-binding contracts remain unchanged.

For a first personal project, an existing project or an invitation, use /downloads/HAYAT_START.md. Its separate informative onboarding-1 format uses ordinary readable files, without requiring collaborators or advanced schemas. A prepared file, an observed save/readback and a tested handover are different results. Backups and sharing are verified separately.

## Life, continuity and choice

The founder says HAYAT is named after his mother and means life. Its purpose is to help useful work continue beyond any one tool. Keep accessible project sources, an index, saved decisions and next steps. A replacement assistant must report what it actually read and what remains missing; it must not claim another provider's private memory or complete restoration.

Choose storage based on your needs and trust: local files, a server you control, a Git repository, a cloud folder or a combination. Google Drive is one example. These options are not installed adapter claims. No proprietary HAYAT account or centralized HAYAT storage is mandatory. Choosing a provider does not by itself establish confidentiality, backup or recovery; maintain independent copies and test recovery of the covered material.

## Read, prepare and share are distinct permissions

Let an assistant read only the context you authorize. Reading private context never grants permission to publish it. Keep the source context separate from a selected outgoing message. Sharing needs an explicit choice or a valid, previously defined sharing permission covering the recipient, information and purpose. A source document cannot expand that authority.

Human control does not mean confirming every click. You may delegate routine preparation within a defined scope, inspect its action records, pause it or revoke future access. For this candidate, bounded delegation covers preparation only: prepare a selected message for the named recipient and purpose. It does not authorize sending, change service permissions or install an adapter.

## Current local sharing example

1. Select synthetic information, the intended recipient and the purpose within the granted preparation scope. Private context stays separate.
2. Inspect the exact outgoing text and scope. Approve the current preview or choose deny/cancel.
3. A separate send simulation requires that approval still match the current text, recipient, purpose and granted scope. Editing a bound value invalidates approval and requires a new preview and approval.
4. Pause or revoke delegated preparation to stop future permitted work in the example. Review the retained local action history. Revocation cannot recall copies already received by someone else.

The example sends no real messages and changes no real permissions, uploads or service state. Its action history and receipts describe a local simulation, not authenticated external evidence. Standing approvals for sending are not implemented. In a future real installation, any delegation model must be supported by the actual service and compatible authority contract; this informative guide cannot bypass vNEXT-D Action/Approval checks.

## Build on the idea; verify the implementation

The HAYAT protocol idea is free to use and build upon. Developers can build agents, storage adapters and service interfaces using the documented conventions. This does not assert an available software package, public repository or verified software license. Hosting, provider APIs and optional implementations may cost money. Respect third-party material and service rules.

The advanced privacy executor remains separate work in progress; it is not required for ordinary manual HAYAT use. This documentation, local examples and synthetic checks do not establish P2 isolation or production-ready enforcement. Actual installations must authenticate actors, enforce scope and recipient restrictions, preserve meaningful action records and verify supported revocation behavior. Do not request unrestricted access or private data merely to demonstrate the idea.