Asynchronous Agency and Attention-Following Work

1. Attention follows the person

AIOS is designed around a simple experience: the person continues at the speed of meaningful attention while longer work proceeds at the speed its judgment requires.

A useful foreground movement returns at conversational scale. Deeper research, composition, editing, workflow execution, or review can continue after authorization against the object that gave it purpose. The person remains free to think in another file, inspect a return, make a local change, or move to a different project without waiting for one long model response to release the interface.

This changes the relationship between human attention and machine latency. The person does not become the attendant of an AI queue. The system carries admitted work while human attention continues to lead.

2. Authorized work retains its own continuity

Asynchronous agency begins with an admitted operation. Operational admission records an authorized movement as bounded work: its object, grant, scope, allowed continuation, yield behavior, return, and landing are established before execution. Chapter 13 uses admission for reusable library resources; here the term governs one executable movement.

The grant defines what may continue, which stages or downstream movements are included, when the work yields, what it returns, and where it lands.

Within that grant, work can advance, publish progress, pause at a declared boundary, resume from durable state, return a bounded unknown, or invoke an explicitly included downstream movement. New semantic work requires a new act of authorization or a grant that already names it.

The distinction makes continuing work genuinely agentic without turning passive observation into permission. Motion follows established purpose and authority.

3. Four rules coordinate attention and operation

Current input follows current attention. The active file, object, or surface determines where the person's next direction is addressed.

Admitted work retains its original address. A later change of focus neither retargets nor silently enlarges an operation already in flight.

A return belongs to its origin. Progress, completion, failure, and needs-attention states land at the file or project that commissioned the work.

Conflict remains local. Revision drift or collision at one artifact is resolved at that artifact's boundary while unrelated work remains available.

Together these rules create a stable relationship: human focus remains fluid, while every operation preserves a fixed semantic and operational address.

4. Attention is local even when work is distributed

The active object is the present center of interaction. It is not a global runtime mode. At the same moment, several operations can remain bound to different files, pending work can wait for admission, completed returns can await review at their origins, and parked branches can preserve their re-entry conditions.

Durable state keeps the field intelligible. When the person opens an object, the system reconstructs its live situation: active and returned work, current revisions, unresolved decisions, and available continuations. The interface reveals the state relevant to attention rather than forcing every operation into a central cockpit.

5. The asynchronous lifecycle remains visible

After admission, binding fixes the operation's object, revision, scope, authority, and return. Development proceeds until the operation can continue under its grant, needs a person, has produced a useful return, or can honestly establish only failure or a bounded unknown.

Return is not integration. The originating situation still requires judgment about what the product changes and what should happen next.

The diagram states the core semantic lifecycle. Interface states refine it for suspension, conflict, and termination: yielded marks a declared pause, stale marks lost revision fit, and canceled marks an authorized stop. Integrated belongs to the originating situation after the separate integration judgment.

6. Files preserve agency beyond the process

An asynchronous line remains reconstructable through the canonical artifact, companion memory, project bearing, workflow and stage records, assignment and grant, source snapshot, receipts, progress, return records, and explicitly pending work.

The durable field carries the position. If an ephemeral model process disappears, the system can resume from known ground, retry within the original grant, or report precisely what failed. Long-running agency therefore depends less on keeping one agent alive than on preserving the purpose, address, state, and evidence needed for the next movement.

7. Foreground, asynchronous, and anticipatory work serve different roles

Foreground work directly serves present attention. It returns a useful human-scale movement and keeps navigation and further input available.

Authorized asynchronous work carries a bounded charge beyond the immediate exchange. It continues only within its source grant, returns at declared points, and remains attached to its origin.

Anticipatory preparation lets sub-agents assemble likely context and surface possible actions before the person asks for each one explicitly. The prepared material remains attached to its originating work and becomes available when the person reaches the relevant point.

Its trigger is an active, authorized event: the person focuses an object, a movement completes, or an admitted workflow establishes a known upcoming need. The trigger supplies the purpose; preparation reduces the latency of a later option whose relevance is judged again before use.

The roles cooperate as part of one attention-following environment. Preparation reduces latency, asynchronous execution extends duration, and foreground interaction keeps the person in an active relationship with the work.

8. Binding makes motion safe

Every in-flight operation preserves its origin identity, source revision or snapshot, admitted command, capability owner, exact mutation ceiling, allowed continuation, expected product, return surface, and behavior under conflict or failure.

These bindings make attention mobility possible. The operation's meaning comes from the object and grant that launched it, not from whichever file happens to be active when it completes.

For consequential changes, receipts make the lifecycle inspectable: what was authorized, which ground was used, where progress stopped, what was changed or returned, and which integration judgment remains outstanding.

9. Parallel attention does not make every mutation parallel

Operations on separate objects can often proceed independently. Work against the same artifact requires serialization or explicit reconciliation when mutations overlap, one result becomes another's dependency, the revision changes, structure shifts underneath a local edit, or related changes require whole-document review.

Revision binding turns collision into a local, intelligible state rather than silent corruption. An operation can yield as stale, request re-grounding, or return a proposal against the earlier snapshot. Unrelated objects remain usable while that conflict is resolved.

10. Progress should be calm and truthful

The interface exposes the semantic lifecycle through related display states: pending, active, yielded, needs attention, returned, failed, bounded unknown, stale, and canceled. Integration appears on the originating situation after return. Partial work appears as partial. A completed return lands quietly at its origin. Progress is available when the person asks for it, and reopening the file restores the current situation.

The system protects attention from two opposite failures: hidden work that cannot be understood and constant status interruption that makes the person monitor the machine. Visibility follows relevance.

11. Latency has an attention cost

Long responses break cognitive continuity even before their financial cost matters. Waiting weakens the person's hold on the question, discourages deep work, triggers context switches outside the system, and turns the interaction channel into a scarce queue.

Attention-following work changes the experience from request-and-wait to authorize-continue-receive. Its success is measured through time to a useful foreground movement, interruption frequency, resumption effort, attention disruption, and total supervision burden alongside total completion time.

The architecture does not pretend that deep work becomes instantaneous. It prevents the duration of one operation from monopolizing the person's relationship with the whole system.

12. Natural direction becomes more powerful

Because the active file, recent movement, project structure, role, workflow, source standing, operation contract, and return surface already establish the situation, the person can direct work in ordinary speech instead of encoding system mechanics.

This creates a path toward voice-first interaction. Voice quality remains an empirical product question involving transcription, latency, interruption, privacy, accessibility, and correction. The architectural contribution is a context rich enough to situate natural direction against an exact object and authority boundary.

13. Several lines can remain coherent at once

A person authorizes a source comparison for a research file, then moves to a draft and completes a local edit. They open the project plan, record a dependency revealed by that edit, and continue elsewhere. The comparison later returns to its research origin with findings, limitations, and a proposed bearing on the project.

The lines share durable project purpose, but they retain separate addresses and grants. The research return does not overwrite the draft or seize the foreground. When the person reopens the research file, the system reconstructs the return and the exact integration judgment it requires.

14. AIOS can connect local work with external agent systems

AIOS is designed to operate as local workflow middleware between a person's durable reasoning environment and external agent systems. It can commission work by packaging the parent purpose, exact charge, relevant context, source standing, approvals, expected return, latest useful return, receiving object, and stopping condition.

External-agent integration will be defined case by case because agent capabilities, interfaces, and operating practices continue to develop. AIOS's structured communication, workflow context, approvals, durable files, and origin-bound returns provide the interoperable local environment through which those systems can participate. Possible uses include research, specialist analysis, artifact development, workflow-stage work, comparison, and other commissioned contributions that return to the work that requested them.

An inbound result returns with provenance, assumptions, limitations, and its proposed bearing on local work. The local system then integrates it through the same files, workflows, and approval structures used for other contributions. This makes external capacity available without relocating the person's durable knowledge system into the external agent.

Boundary: asynchronous agency continues granted purpose

The architecture supports continuing motion, not self-originating work from passive state. Focus changes do not retarget operations. Completion does not force attention. A return does not integrate itself. These boundaries let the system carry more work without transferring control of purpose or consequence away from the person.

15. Failure conditions and evaluation

The principal failure conditions are distinct:

• Passive initiation: observation originates semantic work without an authorized event or admitted purpose.
• Operation retargeting: a change in foreground attention moves an in-flight operation to another object.
• Global locking: one long operation makes unrelated objects or interaction unavailable.
• Focus-stealing return: completion seizes attention instead of landing quietly at its origin.
• Hidden in-memory queue: continuing work cannot be reconstructed from durable state after process loss.
• Uncontrolled overlap: concurrent mutations touch the same artifact without revision binding or reconciliation.
• Charge expansion: an operation enlarges its purpose, scope, or consequence beyond the admitted grant.

Evaluation tests foreground response time, useful work completed while deeper operations continue, scope and retargeting errors, same-file conflict handling, restart reconstruction, disruption caused by returns, clarity of operation state, supervision burden, quality differences between synchronous and asynchronous routes, and fidelity of external-agent returns.

Attention-following agency makes duration compatible with human continuity. Work can remain active without requiring the person to wait beside it or surrender the direction of the larger intelligence system.