Readable by people. Inspectable by assistants.
Public draft · Revision DKeep the context.
Make authority explicit.
The vNEXT public draft describes a portable manual workflow and contracts for optional adapters. Publishing a draft does not make it accepted operating law.
The manual baseline
- Name the project and its owners. Declare the purpose, participants, storage and access policy.
- Verify access. Each person checks their own account. Reading a file does not prove permission to write.
- Save a bootstrap. Point to current status, sources, accepted decisions, unresolved questions and the next action.
- Ask the next assistant to check. It should state what it read, what it could not read and which tools it actually has.
- Approve an exact message. Review the content and recipients before any manual copy or supported adapter write.
- Read the result back. Record the outcome. A recipient’s acknowledgment is a separate message.
A few records, with distinct jobs.
| Record | What it establishes |
|---|---|
| Source | The exact saved bytes and their provenance limitations. |
| Status | Where work stands, with references to evidence. |
| Approval | A scoped human decision about exact content and recipients. |
| Receipt | An observed outcome, not delivery or acceptance. |
| Decision | What an authorized person accepted. |
What survives a change?
Keep sources, messages, decisions and recovery instructions outside a single assistant’s private memory. Keep prior versions. Record missing context explicitly. Storage accounts, credentials and runtimes remain dependencies.
An independent backup needs declared coverage and a recovery drill. A Git repository or deployed website does not automatically back up the project’s conversations, decisions or data.
When something goes wrong
A source cannot be opened
Record it as missing. Preserve the access boundary and ask for an authorized alternative. Do not claim it was restored.
A draft changes after approval
Invalidate that approval. Prepare a new action and obtain approval for the new bytes and recipients.
A write times out
Mark the result uncertain. Reconcile using the same action ID. Do not retry blindly or invent a successful receipt.
Two people update the same status
Keep both versions. Use the declared resolver and record a decision before advancing the current pointer.
An adapter is unavailable
Continue permitted local preparation. A human may perform an explicitly approved manual copy followed by readback.
Adoption is an explicit decision.
The exact draft, its scope and effective date must be accepted before an installation adopts it. Preserve earlier artifacts and rehearse recovery. Existing controls remain in force until an approved migration is complete.
Read the authority note →Control is a set of choices.
Choose storage, tools and delegated actions. Keep read access distinct from permission to share with a named recipient for a defined purpose. A person may pre-authorize bounded routine work; that does not mean every click needs a confirmation dialog.
In these examples, delegation permits only local preparation. A simulated send still requires approval bound to exact content and current scope. This does not add a standing-send permission to the reviewed vNEXT-D contract.
Pause automation or revoke future access where the selected system can enforce it. Neither action recalls copies already received. Third-party content rights and service rules still apply.
Read the versioned human-control guide for storage choices, permissions, delegation and compatibility.
Start personally. Collaborate when ready.
Use the readable setup prompt for a personal project, an existing folder or a selected message. The optional personal onboarding-1 packet is an informative file format, separate from these shared vNEXT-D contracts. Its saved/readback observations do not imply a verified backup, shared access or successful handover.
Set up my HAYAT →