A book about the consequences of intelligence
The3 Asof AI
Access.Autonomy.Answers.
Who can enter.
What can continue.
What can become known.
Three promises.
Three kinds
of evidence.
Access makes useful capability available to a person. Autonomy carries authorized work toward an outcome. Answers contributes to new knowledge. This book follows the framework from its 2024 origins into the practical questions of learning, agents, research, and human presence.
Open the complete reading panel, use the chapter selector to return to a passage, or take the EPUB with you. The teaching examples are fictional; the source notes distinguish published arguments, research findings, and future scenarios.
Scroll to read. Choose a chapter for a focused view. Exercises open at the end of each chapter.
Opening
Three different promises
A vocabulary for consequences, with a different test for each promise.
Chapter 01 / 18
Three Different Promises
A person sits down after a long day and finally understands something that has defeated her for years. Across town, a small business finishes its day without its owner returning six telephone calls. Somewhere else, a research team tests a material no one on the team would have thought to make.
All three events may involve artificial intelligence. They do not represent the same promise.
The first changes who can reach a capability. The second changes who must carry the work. The third changes what can become known. Confuse those changes and almost any demonstration will seem to prove almost anything. Separate them and you can begin asking useful questions.
I call them the 3 As of AI: Access, Autonomy, Answers.
Access means that help once denied, delayed, or reserved for a few can become available to the person who needs it. Autonomy means that an authorized system can carry work toward an outcome without requiring a person to conduct every step. Answers means that AI contributes to the discovery of knowledge or solutions, extending what we know rather than merely presenting what is already available.
These are purposes, not product categories. One product may participate in all three. A laboratory system might conduct experiments, produce a new result, and make that result available through a teaching interface. Its operations involve Autonomy; its discovery contributes to Answers; its public explanation offers Access. The machine has not changed identity three times. We have examined three consequences of what it does.
Nor are these three levels of intelligence. A modest system that reliably books ordinary appointments may deliver useful Autonomy. A more capable model trapped in a conversation may deliver only Access to advice. An expensive research system can fail to produce an Answer. Capability matters, but capability and delivered consequence are different things.
I first published this framework in November 2024. My later essays explored a future in which Access became the defining human impact of AI, Autonomy became part of the background of everyday work, and Answers became an engine of discovery. Some of those essays deliberately looked backward from an imagined 2030. This book is written in October 2026. A future scene remains a future scene; it does not become a measured result because it is written in the past tense. [S1] [S2]
The distinction matters to the argument. A forecast asks us to imagine and prepare. Evidence asks us to check what happened. We need both, and we need to know which one we are reading.
This book develops the framework as an instrument for ordinary judgment. You do not need to build a model or know the names of its internal components. You need to recognize the promise being made, the conditions required to deliver it, and the evidence that would establish delivery.
For Access, ask: Who can now do something useful that they could not practically do before? For Autonomy, ask: What continues without requiring the person to keep carrying it? For Answers, ask: What has become known, and how was it established?
Notice that none of those questions asks whether a demonstration was impressive. A demonstration can astonish and leave the underlying barrier untouched. A response can sound intelligent and leave the work with you. A proposed discovery can look convincing and fail the first serious test.
Our recurring examples will be deliberately modest. Lena is a fictional adult learner. Palmetto Studio is a fictional appointment business. The materials laboratory is an illustrative research team. They are not case studies of named deployments or disguised claims of measured performance. Their job is to make the distinctions visible.
We will move from the person seeking help, to the work that can continue, to the knowledge that can be discovered. Then we will bring the three together. The larger question runs through every chapter: when intelligence becomes more available, what has to change around it before human life actually improves?
A question to carry · Chapter 01
Name a recent AI experience. Did it make help available, carry work toward completion, or contribute to something newly known? State the consequence and the evidence before assigning it to one of the three As.
Part I · Access
Who can enter?
Useful capability, available at the point of need.
Chapter 02 / 18
The Door That Was Closed
Lena has postponed learning the bookkeeping side of her work for years. She can serve a customer, make the product, and recognize quality. She gets lost when an explanation moves too quickly from an ordinary word to an accounting term. A classroom meets while she is working. A patient tutor is difficult to arrange. At night, the unanswered question is still there.
The barrier is easy to misdescribe. We might say Lena lacks information. But the information already exists. It is in textbooks, lectures, help pages, and other people's heads. Her problem is access to an explanation that can meet her where she is, at a time she can use it, without making her feel foolish for needing it again.
An AI tutor can change the shape of that encounter. Lena asks what cash flow means. She receives an explanation using the workshop she knows. When the example fails, she asks for another. When a term is unfamiliar, the explanation slows down. The conversation can return tomorrow without requiring her to begin at the beginning.
The consequential event is not that a computer can define a term. It is that Lena can stay with the problem long enough to understand it.
This is Access. The machine makes a service available at the point of need. The person still initiates the encounter and participates in it. She has not delegated the learning. Learning is the reason she is there.
My earliest essay described access as denied or deferred. That distinction remains useful. Denied access says the service is beyond your reach. Deferred access says it exists, but not now, not nearby, not in your language, or not in a form you can use. A delay can have the same practical effect as a refusal when the need does not wait. [S1]
Some barriers are material: a device, connectivity, available funds, a place to sit. Others are social: embarrassment, language, unfamiliar conventions, the feeling that a service belongs to people unlike you. Still others are embedded in the service itself. A person may technically have access to a website while being unable to navigate its assumptions.
A service has not become accessible merely because a link can be opened. Access is an encounter that reaches a usable result.
This changes what we should build. If we begin with the machine, we ask which capabilities to display. If we begin with Lena, we ask why previous forms of help failed to meet her. The second question can lead to a very different product: voice instead of typing, a familiar example instead of a technical definition, an explanation in smaller steps, or an easy return to an unfinished lesson.
It also changes what we should measure. Counting accounts tells us who entered the doorway. Counting useful encounters tells us whether the doorway leads anywhere. Did Lena understand the distinction well enough to use it next time? Could she explain it in her own words? Did the help reduce her dependence, or merely produce another answer she copied?
Access is sometimes presented as the least sophisticated A because it often begins with a simple conversation. That judgment mistakes the visible interface for the scale of the consequence. A patient explanation available to a person who has never had one can matter more than a spectacular capability shown to people who already have several ways to get help.
The first question of AI is therefore human and local: Which door is closed, to whom, and what would it mean for that person to walk through it?
A question to carry · Chapter 02
Choose one service you find easy to obtain. Name a person for whom it would be denied or deferred. Describe the barrier without blaming the person. Then ask whether AI removes that barrier or simply puts a new interface in front of it.
Chapter 03 / 18
Availability Is Only the Beginning
Imagine Lena can reach her tutor whenever she wants. The tutor is patient, fluent, and willing to explain everything. We might be tempted to declare the problem solved. Yet an always available source of poor help can make a person more confidently mistaken.
Access has at least three practical tests: availability, usefulness, and fit. Availability means the encounter can happen. Usefulness means the encounter helps with the actual need. Fit means the service makes sense for this person in this situation. These tests are an operating tool for this book, not three additional As.
Lena's tutor may be available while misunderstanding her local business practices. It may provide a useful general explanation while assuming a level of literacy she does not have. It may fit her vocabulary while giving an incorrect account of a rule. Each failure occurs at a different place, and each requires a different repair.
This is why broad claims that AI is a teacher, a lawyer, or a doctor need to be handled precisely. The important ambition in my early writing was to make expertise-like help immediate. A role label is not proof that a system can perform every duty of a profession, accept its obligations, or provide an appropriate service in every case. The encounter has to be judged by what it actually does.
For a learner, explaining an unfamiliar word can be enough. For a person trying to understand a professional conversation, helping prepare questions can be valuable. Neither result requires pretending that the system has assumed the entire professional relationship. A clear service defines its contribution so the person knows what she has received and what remains unresolved.
The same principle applies outside familiar professions. An AI writing partner can make editorial attention available to someone who has never had an editor. Its value may lie in helping the writer see a weak passage, not in claiming that every revision improves the work. A design assistant can widen the set of people who can explore visual possibilities. It still needs to respect the purpose, constraints, and judgment of the person making the thing.
Good Access creates a usable relationship between capability and need. It does not require every encounter to be expansive. Sometimes the most useful response is a short explanation. Sometimes it is a clear statement that the system lacks the information needed to answer. Sometimes it is a well prepared handoff to a person who can do the remaining work.
The handoff itself deserves attention. A service that says seek help and leaves the person at the original closed door has made less progress than it appears. A useful handoff preserves context, names the unresolved question, and explains the next practical route. Whether it can take that route on the person's behalf is a question about Autonomy, which we will reach later.
Consider the difference between a tool that translates a document word by word and one that helps a person understand what they are being asked to do. The first changes the language. The second changes the person's ability to participate. Both may be useful. Their outcomes should not be confused.
Access is complete only relative to a stated purpose. If the purpose is to explain a term, understanding the term is the test. If the purpose is to make a service usable, an explanation alone may be insufficient. The promise determines the boundary of completion.
A practical builder should therefore finish this sentence before choosing features: This service makes it possible for this person, under these conditions, to accomplish this useful thing. A sentence that cannot name the person, conditions, and useful thing is still an aspiration. It may be a worthy aspiration, but it is not yet an offer that can be tested.
A question to carry · Chapter 03
Take an AI service you already use. Write its useful promise in one sentence. Avoid words such as intelligent, seamless, and powerful. Describe what a person can actually accomplish, and how you would know.
Chapter 04 / 18
The Most Human A
When I wrote about AI from the imagined vantage of 2030, I placed Access at the center. The scenario was deliberately large: people who had lacked patient teaching, understandable guidance, and timely support could finally reach them. The numerical scale in that essay was a forecast device. The underlying thesis was about who gets to participate. [S2]
Why give Access this emphasis? Because a capability can advance dramatically while remaining socially narrow. If a breakthrough reaches only the people who already have abundant support, its technical importance can exceed its human reach. If a modest capability reaches people whose need has repeatedly gone unmet, its human consequence can exceed its technical novelty.
These are different axes of progress. We should be able to celebrate a scientific advance and still ask who can use it. We should also be able to recognize a widespread improvement without requiring it to be the frontier of machine intelligence.
Lena does not experience model size. She experiences whether an explanation makes sense. She does not live inside a benchmark. She lives inside a schedule, a language, a household, and an uneven history of confidence. Access becomes real where a capability fits those conditions.
The phrase democratizing intelligence can conceal a great deal. Intelligence might be widely available while the means of acting on it remain concentrated. A person can understand how to apply for a program and still be unable to produce the required document. A small business can know which operational change would help and still lack the authority or resources to make it. Knowledge expands the possible; institutions, tools, and material conditions determine much of what can actually happen.
This is the bridge to my later writing about the environment that carries intention into events. Two people can consult similar intelligence and still live in very different worlds. One must coordinate every handoff. The other has systems and relationships that carry the intention onward. Access to an answer does not erase the difference. [S8]
We should resist describing that difference as personal failure. Sometimes the missing ingredient is persistence. Sometimes it is a credential, a spare hour, a functioning public service, an available human, or a dependable connection between systems. Calling everything an information problem makes the part AI can supply look like the whole solution.
The human importance of Access therefore creates an obligation to examine the last stretch. What happens after the explanation? What becomes easier? What remains closed? Who still cannot enter? These questions protect the promise from becoming a count of people who have encountered a chatbot.
They also create business opportunities that are easy to miss. A builder who understands a neglected barrier can design a more useful service than a builder displaying the same general capability to everyone. The differentiation may be a language, a workflow, a relationship, or a specific moment when help usually disappears.
Access can expand markets, but its meaning is larger than market expansion. A person who can finally ask an unembarrassed question has gained something even before a transaction occurs. A student who can keep learning after a setback has entered a different relationship with possibility. An older adult who can understand a confusing instruction has recovered a piece of practical agency.
That is why Access is the most human A. It asks us to look away from the capability long enough to see the person. What did the person previously have to forgo? What is available now? And does that new availability actually belong in the life they are trying to live?
A question to carry · Chapter 04
List the steps between receiving good advice and benefiting from it. Mark the steps the person still has to coordinate. This remaining sequence is where an Access project may need partners, a different service design, or a carefully defined move into Autonomy.
Part II · Autonomy
What can continue?
Authorized work that survives after the asking ends.
Chapter 05 / 18
From Asking to Assigning
Lena's tutor explains how to arrange a meeting with her mentor. It suggests a message, tells her to compare calendars, and drafts an agenda. The encounter is useful. The meeting does not yet exist.
Now imagine she gives an authorized agent the assignment: arrange a thirty-minute meeting with the mentor next week, within the availability and constraints already known to the system. The agent checks the relevant information, coordinates a suitable time, creates the event, and verifies the invitation. Lena returns to find the meeting in the calendar she already uses.
The shift is from help with the work to responsibility for carrying some of the work. That is the practical threshold of Autonomy.
An agent may begin in a chat window. My October 2026 introduction to agents makes this explicit: software receives a goal, chooses steps, uses tools, and checks what happened. The fact that a person initiated the goal does not make every later action merely conversational. The question is what the system can do after the assignment. [S6]
At the same time, one action does not establish an autonomous operation. An agent might create the event but fail to notice that the invitation was rejected. It might choose the wrong timezone. It might stop when a normal scheduling conflict appears and return the entire problem to the person. The task is defined by the outcome, including the ordinary work implied by it.
We need a vocabulary that does not force every system into a yes-or-no label. A system can perform one action independently and remain dependent for the overall task. It can handle a defined class of routine events under standing authority and escalate exceptions. It can carry a larger goal across several systems. These are different scopes of autonomy.
The scope should be stated in ordinary language. What can it initiate? What can it change? Which decisions belong to it? What conditions cause it to stop? Who receives the unresolved work? What event counts as completion?
Those questions make the capability concrete. They also reveal when the supposed agent is a collection of drafts. A drafted email is a document. A sent email is an event. A suggested appointment is a proposal. A committed appointment is a change in the world. The documents may be necessary intermediate work, but they do not substitute for the promised event.
A common mistake is to make the human responsible for every transition and then credit the system with the whole result. The model drafts; the person copies. The model recommends; the person submits. The model asks; the person finds the missing record. The process may be faster, and that improvement may be valuable. It still leaves a recognizable amount of work with the person.
Autonomy asks us to examine that remaining work without embarrassment. If a required approval is appropriate, keep it and count it. If the system cannot complete the assignment, say so. If it completes only a narrow class of tasks, name the class. A precise small promise is more useful than a large ambiguous one.
The important change is not that asking disappears. It is that the assignment can survive after the asking ends. An intention becomes something the system can carry through steps, ordinary interruptions, checks, and completion, within an authority the person or institution has actually granted.
A question to carry · Chapter 05
Write two versions of one request. In the first, ask for advice. In the second, assign an outcome. Then mark every action that must occur outside the conversation for the second request to be complete.
Chapter 06 / 18
The Business That Keeps Working
Palmetto Studio has a familiar problem. The owner is good at the work customers come for. Every interruption to arrange that work makes her less available to do it.
A prospective customer calls while she is with someone else. A regular needs to change an appointment. A supplier asks whether a delivery time is acceptable. None of these events is extraordinary. Together they become an unpaid second occupation: the owner as the integration between everybody else's needs and the business systems.
In an Access arrangement, an assistant helps her deal with the queue. It summarizes messages, proposes replies, and explains how to reorganize the schedule. She still returns at the end of the day to move the work across the finish line.
In an Autonomy arrangement, the studio defines which ordinary requests its agent can handle. The agent knows the service durations, staff availability, buffers, booking rules, and escalation conditions. When a routine request arrives, it gathers the needed information, checks the current state, acts within the rules, and confirms the result in the studio's existing systems.
This is an illustrative operating design, not a report that every product sold as an agent can do these things. Its value lies in the complete sequence. The request enters where customers already communicate. The commitment appears where the studio already works. The receipt goes where the customer expects to find it.
My essay Talk to My Agent used a hairdresser to make this point. The owner should not need a new portal simply to finish a task the agent supposedly completed. The result belongs in the calendar, customer record, and other systems that already carry the business. [S5]
A new management interface may still be useful for a technician or an owner setting policies. The principle concerns the operating burden. If every ordinary booking requires the owner to visit a separate dashboard, interpret a recommendation, and re-enter a decision, the system has moved the desk rather than removed the job.
Now introduce a complication. Two customers want the same opening. The first has already received a confirmation; the second request arrives before every connected view has updated. A convincing conversation is no help if the underlying commitment is wrong. The agent must respect the authoritative schedule, avoid duplicate commitments, and report what actually happened.
Or consider an unfamiliar request. A customer asks for a service the studio does not offer. The agent should preserve the business's defined offer. Autonomy does not grant it authority to invent a new company in pursuit of a sale. It can explain the boundary and route a genuinely unresolved issue to the responsible person.
The operating achievement is easy to overlook because successful routine work is quiet. The owner experiences an appointment that is correct, a customer who knows where to arrive, and a record that does not need reconstruction. The absence of repeated intervention is part of the product.
But quietness must not mean obscurity. The owner needs a readable account of what was committed, which policy governed it, and what remains unresolved. Good autonomy removes the obligation to conduct every routine step while preserving the ability to inspect and correct the arrangement.
The studio does not need an AI that sounds like an excellent receptionist for five minutes. It needs an operation that remains faithful to its promises throughout the day.
A question to carry · Chapter 06
Choose one recurring business interruption. Follow it from arrival to completed record. Name the authoritative system at every step. Wherever a person must copy, reconcile, or remind, you have found work the autonomy claim still needs to address.
Chapter 07 / 18
Authority Is Part of the Machine
The studio's agent can act only inside an arrangement of authority. It may have the technical ability to cancel every appointment in a calendar. That does not mean the business has authorized it to do so.
We often discuss permission as though it were paperwork added after the useful machine is built. In an autonomous service, authority is part of the operating design. It determines which possible actions can become actual commitments.
An assistant can be trusted with a narrow recurring task before it is trusted with a broad one. Palmetto Studio might authorize ordinary bookings in unreserved openings, permit routine changes under a stated policy, and require the owner for disputes or unusual commitments. The boundary is meaningful because it describes actual decisions the agent will encounter.
A vague instruction to use good judgment is insufficient when two reasonable people would make different choices. The studio needs to say what matters: which calendar wins a conflict, how long a slot can be held, which requests are outside the offer, and who owns an exception. These choices express the business. They are not merely settings for a software technician.
Authority also has a source. A message from a stranger is an input to evaluate, not a new governing instruction. A customer can ask for an appointment. The request does not authorize the agent to reveal another customer's information or rewrite the owner's policies. An external document can supply facts; it does not automatically gain the right to redirect the operation.
That distinction is fundamental wherever agents read the world and then act. The same system may encounter trusted policy, private records, ordinary messages, and misleading instructions inside material it was asked to inspect. A useful design keeps the roles of those inputs separate. The action must remain answerable to the person or institution that granted the authority.
Personalization makes the question more interesting. An agent that knows the owner well can avoid needless questions. It can remember recurring preferences and carry context across a task. But knowing what someone usually prefers does not grant unlimited power to commit them. Familiarity informs decisions within a mandate; it does not create the mandate by itself.
A mature system should therefore support a practical return. The owner can inspect the arrangement, change a policy, narrow authority, or stop the operation. If leaving the service requires abandoning the records of what it did, the autonomy has created a new dependency. The records should belong in a place the business can understand and continue to use.
This is also where a business's defined customer experience matters. The agent should deliver the experience the company has chosen to offer. A customer may fit that offer or choose another business. The machine should not improvise exceptions merely because it can produce agreeable language. A faithful refusal can be better service than an unauthorized promise. [S12]
None of this requires a person to approve every harmless step. The point of an explicit mandate is to make ordinary action possible without repeatedly reconstructing permission. Clear authority can increase useful autonomy because both the system and its owner know where independent action belongs.
Think of the mandate as a working agreement: these events may start this work; these records govern it; these changes are allowed; these conditions return it to a person. Then ask whether the tools can enforce that agreement. An eloquent policy that the system cannot operationalize leaves a gap exactly where action begins.
A question to carry · Chapter 07
Describe one recurring assignment using four sentences: what starts it, what it may do, what it must never decide for itself, and who receives an exception. If the sentences contradict each other, resolve the contradiction before granting more authority.
Chapter 08 / 18
The Receipt and the Reality
The studio's agent says, Your customer is confirmed. The owner asks a better question: Confirmed where?
Perhaps the agent drafted a message but did not send it. Perhaps it sent the message but failed to reserve the opening. Perhaps it reserved the opening in a secondary calendar while the staff works from another one. Perhaps the booking is correct, but nobody told the customer. Each intermediate event can support a confident sentence. None is the complete outcome by itself.
Autonomy needs receipts tied to the world it claims to have changed.
A receipt is more than a cheerful completion notice. It names the action, the affected record, the relevant time, and the remaining condition, if any. The owner should be able to inspect it without having to reconstruct the entire conversation. A calendar event can be opened. A submitted record has an identifier. A changed order has a current state. The proof belongs to the system where the consequence exists.
This is why checking is part of acting. A tool call can return successfully while the intended outcome remains wrong. A service can accept a request and complete it later. A network interruption can make the result uncertain. An agent that treats every ambiguous return as a fresh opportunity to repeat the action may create duplicates.
The ordinary human analogy is useful. If you are unsure whether you reserved a room, making the reservation again can solve the uncertainty by creating a second problem. You first inspect the booking record. The autonomous operation needs the same discipline, expressed in the tools and records it uses.
Receipts should also preserve incompleteness. The studio might be waiting for a customer's reply. The request might be outside the agent's authority. A system outage might prevent confirmation. Those are states of work, not failures of rhetoric. A service becomes more useful when it can say exactly what remains open and who owns the next move.
There is a difference between a record of activity and a record of accomplishment. Ten messages, six checks, and two generated documents can describe a busy process that has not secured an appointment. Counting the process can help diagnose the operation. It should not replace the completion condition.
At the same time, the completion condition must not shrink after the system encounters difficulty. If the assignment was to arrange the appointment, a list of available times does not become success simply because arranging it turned out to be harder. The original promise remains the reference.
The principle extends to every A, though the evidence differs. Access needs evidence that help reached and served a person. Autonomy needs evidence of the completed work and the human involvement still required. Answers needs evidence that a claim survived the tests appropriate to the claim. A single screenshot of fluent output cannot serve all three purposes.
A good receipt is therefore an act of respect. It lets the person stop thinking about ordinary work because the work has a dependable place in the record. It also gives the person a way back when something does go wrong.
The aim is neither constant surveillance nor blind faith. It is justified confidence: enough evidence to rely on the operation, enough clarity to understand its limits, and a practical path to repair.
A question to carry · Chapter 08
Take a recent completion message from any system. Identify the external record that proves it. If the message concerns a multi-step outcome, check whether the record proves the whole outcome or only one intermediate event.
Chapter 09 / 18
Count What Still Requires You
A system can appear autonomous because the demonstration ends before the person starts repairing it.
The agent finds a flight. The traveler enters the passenger details, resolves a baggage problem, approves the booking, and discovers that the chosen connection does not work. The promotional account reports a flight found. The lived account includes the work the traveler still had to do.
My proposed AGI Index begins with that lived account. For a specific delegated task, count the required human actions. A lower count means less human involvement under the stated conditions. Zero is the floor. It is meaningful only alongside full successful completion; a system that fails silently has not earned a zero. [S9]
The proposal is an evaluation instrument, not an established scientific standard, and it does not certify every aspect of intelligence. Here it gives us a useful way to inspect claims of Autonomy.
First define the outcome in the ordinary meaning of the request. Arrange the meeting means more than draft an invitation. Order dinner carries more than submitting a purchase. It carries the practical requirements that connect the assignment to an appropriate meal and the person's hunger being satisfied. A system does not get to discard implied work merely because it is inconvenient to test.
Next define a human action consistently. Supplying information, retrieving a file, approving a step, correcting an error, and taking over part of the task all count when required. A single message can contain several actions. Moving the work to another employee or a hidden human service does not make it disappear.
Then disclose the starting conditions. An agent given complete preferences, prepared accounts, working integrations, and standing permissions has a different start from an agent that requires the person to assemble those things during the assignment. Both may be useful. Comparing them requires an honest account of setup, context, tools, and authority.
Imagine three illustrative appointment runs, all using the same counting convention. In the first, the system completes the full task with no required human contribution after assignment. In the second, the person provides one missing fact and approves one action: two required contributions. In the third, the system never secures the appointment and nobody intervenes. That third run is a failure, not an equal of the first. These are teaching examples, not measured product scores.
Elapsed time belongs in a separate record. A deadline can be part of successful completion, but duration does not add points to this index. A fast system that repeatedly hands the job back remains dependent. A slower system that completes it independently may score better on required human involvement.
A necessary approval still counts. Counting it does not imply that removing it would be wise. The instrument measures dependence within an arrangement. It does not decide the arrangement's purposes or judge every tradeoff for the owner.
Repeated trials matter. One clean demonstration can hide a long tail of exceptions. Publish failures, variation, and the work required to recover. A summary across tasks should disclose the task list, counts, completion results, and combination method. An average cannot carry more authority than the records beneath it.
For a business owner, the practical version is simple. Keep a task log for a week. For each assignment, record the promised outcome, whether it happened, each required human action, and unresolved work. The resulting account will often be less glamorous than the demo. It will also tell you where the actual burden lives.
A question to carry · Chapter 09
Choose a recurring task and agree on the completion condition and counting convention before a trial. Record every required human action, including corrections nobody requested. Report failed runs separately. Repeat under comparable starting conditions.
Chapter 10 / 18
A Day With More Than One Timeline
The deepest promise of Autonomy is not that the person becomes faster at operating software. It is that useful work can continue while the person is present somewhere else.
I use the word Parality for temporal freedom through personalized AI representation and delegated work. Mobility loosened the bond between work and location. Parality loosens the bond between every progressing task and one person's sequential presence. [S7]
The person does not acquire several conscious minds. Lena cannot attend fully to three conversations at once merely because three agents are active. The parallelism belongs to the systems. Her attention remains a human resource, with the ordinary limits and qualities of attention.
Suppose she is having a quiet conversation with her daughter. At the same time, an authorized scheduling agent resolves a routine change, an assistant compiles material for tomorrow's lesson, and a business process reconciles ordinary records. These are hypothetical delegated timelines. The value is not a claim that Lena herself is everywhere. It is that progress elsewhere does not require her to leave the conversation she chose to have.
The distinction becomes clear when all three systems interrupt. One asks for information it already has. Another wants approval for a routine step. A third announces every minor success. Lena has acquired parallel demand rather than temporal freedom. The machines are active, but she remains their common bottleneck.
A good arrangement needs an interruption policy as much as an action policy. Which events genuinely require the person now? Which can wait for a summary? Which should be resolved inside the existing mandate? Which indicate that the mandate itself needs revision?
Silence should follow dependable routine completion. Actionable exceptions should arrive with enough context to decide. Repeated uncertainty should lead to a repaired arrangement rather than an endless stream of individual approvals.
Personal representation adds a further requirement. A useful twin carries more than a generic instruction. It understands relevant preferences, commitments, and context well enough to represent the person faithfully within its authority. Its familiarity should reduce repetition. Its transparency should prevent the representation from turning into impersonation.
There is a commercial temptation to measure the result in work multiplied. More tasks, more output, more active timelines. That may be valuable for a business. It is not the complete human promise. A person can spend every saved minute acquiring a new obligation and finish the experiment with less room to live.
Parality is valuable when it protects the possibility of chosen presence. The choice may be a difficult project, a friend, a long walk, or an hour with no defined purpose. Nothing in the framework requires every freed interval to become productive.
This is why the owner's judgment remains central even when routine actions become independent. The systems can carry work. They cannot determine by activity alone whether the resulting life fits the person. A calendar full of successful commitments can still be a life the person did not want.
A useful test is therefore personal and practical: after the system began carrying these timelines, where did your attention become more available? If the answer is only that you supervise more machines, the promise remains unfinished.
A question to carry · Chapter 10
Name one period of presence you want to protect. Identify the routine work that currently competes with it. Design the delegated timeline and its exception policy around preserving that period, then judge whether the experience actually improves.
Part III · Answers
What can become known?
Discovery, validation, and the knowledge around the model.
Chapter 11 / 18
Answers Means Discovery
Ask a chatbot why a familiar material corrodes, and it may explain the chemistry. Ask a research system to help identify a new material that meets a difficult combination of requirements, and a different enterprise begins.
The first encounter can provide excellent Access to existing knowledge. The second may contribute to Answers in the specific sense of this framework: a discovery or solution that extends what is known.
The word answer causes trouble because it is ordinary. Every response to a question can be called an answer. Some of my broader explanatory reports used it that way. But the original 2024 essay and the September 2025 essay devoted to Answers carried a sharper meaning: AI as a contributor to new knowledge, invention, and discovery. That is the meaning this book preserves. [S1] [S4]
A longer response is not necessarily a deeper Answer. Neither is a document with more citations. A system can summarize a field impressively while adding nothing to it. Summarization may be invaluable to a researcher. Its usefulness does not require us to call it a discovery.
Likewise, novelty alone is insufficient. A system can generate a molecule, design, or explanation that nobody has seen because it is invalid. The fact that an output is new does not establish that it is true, workable, or useful. Answers requires a relationship between a new claim and the tests that can support it.
In the illustrative materials laboratory, the team wants a protective coating that meets several operational constraints. Existing formulations leave an unresolved tradeoff. An AI system helps search a space of candidates, proposes a composition, and predicts how it may behave. At this point, the team has a candidate, not a proven coating.
The laboratory makes and tests it. Perhaps the result fails. Perhaps the candidate performs well on one property and badly on another. Perhaps the measurements reveal an error in the model's assumptions. Each result changes what the research process should do next. The eventual contribution may be a successful material, a narrower claim, or knowledge about why a promising route fails.
This is a different kind of work from producing an agreeable response. The research has to encounter resistance from the world. A scientific claim is valuable because it survives an appropriate attempt to show where it breaks, not because a machine states it confidently.
Answers can include more than laboratory science. A new mathematical proof needs valid reasoning that withstands scrutiny. A design needs to satisfy the constraints claimed for it. An operational optimization needs a defensible objective, accurate inputs, and a demonstrated improvement against a relevant baseline. The tests differ because the claims differ.
The category also does not require a machine to have done every research activity without people. Autonomy asks how independently the work proceeds. Answers asks what knowledge or solution the work contributes. A human-led team using AI can produce an Answer. A highly autonomous research pipeline can run all night and produce none.
That distinction frees us from an unnecessary argument about whether the machine is truly the scientist. We can examine the contribution directly: what was unresolved, what did the system add, what evidence supports the result, and what remains unknown?
A question to carry · Chapter 11
Take a claim of AI discovery and identify four things: the prior unresolved problem, the system's specific contribution, the validation performed, and the remaining uncertainty. If one is missing, name the gap before accepting the headline.
Chapter 12 / 18
From Candidate to Knowledge
A real example helps fix the scale of the Answers promise without turning it into magic.
The 2021 AlphaFold paper reported a major advance in predicting protein structures. The researchers evaluated the system in the CASP14 assessment and described accuracy competitive with experimental structures in a majority of cases. This is an important contribution to a difficult scientific problem. It does not mean that a predicted structure is a proven treatment or that every question in biology has been answered. [E1]
The distinction between a scientific result and its eventual applications is essential. A tool can change what researchers can investigate while leaving substantial experimental and practical work ahead. Its contribution is not diminished by describing that work honestly.
Materials research provides another example. In its November 2023 GNoME announcement, Google DeepMind described 2.2 million predicted crystal structures, with a subset of 380,000 considered the most stable candidates. Those numbers describe computational predictions and screening. They are not a count of finished manufactured products. Experimental synthesis and useful performance are separate questions. [E2]
These examples show why a single word such as discovered can cover several stages. A system may generate a candidate, predict a property, verify something computationally, or contribute to an experimentally established result. Each stage can be valuable. Each supports a different claim.
For the fictional coating laboratory, the first stage is a well specified question. Which properties matter? Under which conditions? Compared with what? The answer changes if the goal shifts from performance on a sample to manufacturability at scale. A system can optimize the wrong thing extremely effectively if the research question is incomplete.
The next stage is candidate generation. The machine may search more possibilities than the team could examine unaided. Its output should still carry a record of assumptions, exclusions, and predicted properties. A candidate with a hidden impossibility is not rescued by the size of the search.
Then comes evaluation. Some claims can be checked by computation. Others require physical tests. Some tests establish only a narrow condition. A coating might perform in a controlled sample and fail under repeated real-world exposure. The experiment has to match the proposition someone intends to make.
Finally, the result needs a durable place in knowledge. Methods, conditions, failures, and limits matter because other people need to inspect or reproduce the contribution. A discovery described only as the model said so cannot do the work that established knowledge is asked to do.
There is no shame in a candidate remaining a candidate. Research advances through partial results, rejected hypotheses, and improved instruments. The problem arises when the communication jumps from an early stage to a later one. Prediction becomes proof; proof under narrow conditions becomes universal applicability; potential becomes a product that supposedly already exists.
The same error appears in business. An optimized schedule in a simulation is not a demonstrated improvement in a working operation. A generated policy is not a measured social outcome. A system's persuasive account of what should happen must still meet what does happen.
Answers is therefore a demanding A. It offers the largest possibility while requiring the greatest care about the status of a claim. The more consequential the proposed discovery, the more useful it becomes to say exactly what has been established and by which method.
A question to carry · Chapter 12
Rewrite a discovery headline as a sequence: proposed, predicted, tested, reproduced, applied. Mark the furthest stage the evidence actually reaches. Keep the earlier stages visible so the contribution can be appreciated without exaggeration.
Chapter 13 / 18
The Knowledge Around the Model
A research engine is not a model sitting alone in an empty room. It operates inside a history of measurements, methods, instruments, terminology, failures, and judgments about what counts as evidence.
In my September 2025 essay on Answers, I emphasized knowledge orchestration. The problem is larger than collecting more data. A useful engine must work with the structure and meaning of what is known, including the limits and conditions attached to it. [S4]
Consider the coating laboratory's records. Two experiments may use the same material name while referring to different preparations. A promising result may depend on a temperature recorded in a separate notebook. A failed trial may have been omitted from a presentation. A supplier's specification may apply to a different grade from the one actually tested.
A system that combines these records without understanding their differences can generate an elegant false pattern. The problem is not solved by making its final explanation more fluent. The work begins earlier, where claims are connected to their provenance and conditions.
Knowledge orchestration includes maintaining those connections. What was measured? By which instrument? Under what conditions? Which version of the method? Was the result an observation, an inference, a simulation, or an expectation? Has a later experiment contradicted it? Is the record authorized for this use?
These questions sound administrative until you imagine trying to reproduce a discovery without their answers. Then they become part of the science itself. A machine cannot compensate reliably for an institution that has discarded the distinctions on which its knowledge depends.
The same principle holds in a business. A customer note may record a preference, an agent's guess, or a contractual commitment. Treating all three as equivalent context creates trouble. A research claim, a customer promise, and a remembered possibility need different kinds of authority in the system.
This is one reason a better model does not automatically produce a dependable answer engine. The surrounding work can be expensive and slow: connecting records, preserving meaning, maintaining permissions, designing tests, and bringing domain judgment to ambiguous cases. The quality of that environment affects what the intelligence can responsibly conclude.
My earlier forecast placed the largest answer engines in institutions because the surrounding requirements were substantial. That remains a useful expectation about some frontier problems, but it should not become a permanent ownership rule. A small team can make a new contribution. Shared instruments, public research, and accessible computation can widen participation. The scale of the unanswered problem and the evidence needed to solve it matter more than the prestige of the organization's name.
There is a second mistake to avoid. Expensive knowledge infrastructure is not necessarily good knowledge infrastructure. An organization can invest heavily and still preserve the wrong assumptions, omit inconvenient failures, or create a polished archive that nobody can question. The test is whether the system supports better inquiry and defensible conclusions.
A useful answer engine should make it easier to discover where a claim came from and what could overturn it. It should help researchers see gaps rather than conceal them behind apparent completeness. Its memory needs room for uncertainty, disagreement, and failed paths.
The model contributes intelligence. The institution contributes a world in which intelligence can encounter reliable evidence. Answers emerges from the quality of that relationship.
A question to carry · Chapter 13
Select one important conclusion in your organization. Trace it backward to the observations that support it. Mark the point where provenance becomes unclear. That gap is a knowledge problem an answer engine will inherit unless someone repairs it.
Chapter 14 / 18
The Three As Work Together
It is tempting to draw the framework as a staircase: Access at the bottom, Autonomy in the middle, Answers at the top. Some of my future-facing writing used a ladder to convey increasing scale. The image can help, but it can also mislead.
A ladder suggests that reaching one level makes the previous level unimportant. In practice, each A can strengthen or limit the others.
Return to the materials laboratory. Its research system proposes and helps validate a better coating. That is a contribution to Answers. An autonomous process might maintain ordinary testing records, schedule equipment, and carry out approved procedures. That is Autonomy around the research. A teaching interface might help a small manufacturer understand the result well enough to use it. That is Access to the resulting knowledge.
The discovery can then improve the next generation of accessible tools. Wider Access can bring new problems and perspectives into the research process. Autonomy can reduce the routine coordination required to test those problems. The relationship is a loop rather than a single climb.
But the loop is not automatic. A laboratory may produce a valuable result that remains inaccessible to those who could benefit. An accessible explanation may never become a practical application because the manufacturing capability is unavailable. An autonomous workflow may run smoothly while optimizing an objective that no longer serves the research.
The framework helps locate the break. Has the knowledge not been established? That is an Answers problem. Is the required action not happening? That is an Autonomy or operating problem. Is the capability failing to reach a person in usable form? That is an Access problem. Some failures involve all three, but naming the parts still helps decide what to repair.
Consider education. A tutor explaining algebra delivers Access. A system arranging lesson reminders and maintaining authorized records can deliver Autonomy. Research that establishes a genuinely better learning method can contribute to Answers. One product may combine them, yet each claim needs its own evidence. A pleasant tutoring conversation does not prove that the research claim is true or that the administrative work has been completed.
Or consider a local service business. Customers can ask understandable questions about an offer. Routine bookings can be committed automatically. Analysis may identify an operational pattern the owner had not recognized. The first two outcomes fit Access and Autonomy readily. The third requires care. A pattern is an insight; calling it an Answer in the stronger sense depends on novelty, validity, and the claim being made. We do not need to inflate the category to recognize useful analysis.
The three-way distinction protects investments. An owner seeking fewer interruptions should not buy a better explanation engine and expect the calls to disappear. A researcher seeking validated discovery should not treat an autonomous document generator as a substitute for experimental capacity. A public institution seeking broader participation should not assume that a frontier model automatically removes language and access barriers.
The As are connected, but they are not interchangeable. When a project says it delivers all three, ask it to show three consequences. Who gained useful access? What work continued independently? What new knowledge was established?
A complete answer to those questions is more impressive than a complete list of features.
A question to carry · Chapter 14
Draw your project as three boxes labeled Access, Autonomy, and Answers. Put only demonstrated consequences inside them. Draw an arrow wherever one depends on another. The empty boxes and unsupported arrows show where the next work belongs.
Part IV · Consequence
What becomes possible?
Environments, practical choices, and a future we can test.
Chapter 15 / 18
The Difference Between a Tool and an Environment
Lena now understands more of her business. Palmetto Studio has delegated ordinary bookings. The laboratory has a more capable research process. We might imagine that all three have finished adopting AI. More likely, they have begun rearranging the environment in which intelligence becomes useful.
A tool offers a capability when summoned. An environment makes appropriate capabilities available within the ordinary course of life and work. The distinction is practical rather than absolute. Tools are part of environments, and a good environment may include many visible tools.
The change comes when the person no longer has to be the permanent connector between them.
Lena's explanation matters more if it connects to the records she actually keeps. The studio's agent matters more if its commitments remain consistent with the working schedule. The laboratory's predictions matter more if they connect to tests, measurements, and a record that the next researcher can inspect.
This is the issue in my essay Where Intention Becomes Real. Access to intelligence can become widespread before the practical means of carrying an intention across boundaries does. The apparent difference between two people's ability to act may partly reflect the environment doing invisible coordination for one of them. [S8]
We should design that coordination carefully. An environment can support a person's intention while also narrowing it around the provider's interests. The easiest appointment may be the one that earns the largest commission. The preferred supplier may be the one with the strongest commercial relationship. The supposedly personalized recommendation may simply be the path the system finds most convenient.
A person needs enough visibility to understand such choices and enough practical agency to refuse them. The system should preserve the purpose, not merely deliver whatever nearby transaction fits its commercial machinery.
Portability matters for the same reason. If the relationship ends, can the person retain an understandable account of their commitments and permitted records? Can a business continue operating? Can a worker retain general methods without carrying away another institution's protected material?
My essay The Clean Carry draws the last boundary carefully. General capability can travel. Confidential work does not become personal property because an assistant helped someone use it. Sometimes the responsible way to preserve a method is to rebuild it from permitted sources in a new setting. [S11]
An environment worth relying on therefore needs both continuity and an exit. Continuity lets the intention survive ordinary changes and interruptions. An exit keeps useful continuity from becoming captivity.
There is also a quieter requirement: an environment should leave room for things that are not assignments. A person should be able to wonder, speculate, change their mind, or say something emotionally without every sentence turning into an executed instruction. Intelligence around us needs to understand the difference between conversation and a mandate.
The point of an enabling environment is not to remove every visible interface. It is to reduce unnecessary translation, repetition, coordination, and repair while preserving meaningful choice. Some interfaces help people understand their agency. Others simply make people do the integration work themselves. The distinction is revealed in use.
The strongest AI environment will not necessarily be the one that performs the most actions. It will be the one in which the right intentions become dependable events, useful help arrives in a usable form, and the person can still recognize the life as their own.
A question to carry · Chapter 15
Follow one intention across the systems required to fulfill it. Record every repetition of context, change of identity, manual transfer, and unresolved handoff. Those seams describe the environment your tools currently ask you to supply.
Chapter 16 / 18
Choosing the Next Useful Project
An organization can spend a long time discussing AI strategy without naming a single barrier it intends to remove. The 3 As help turn that conversation into a choice.
Begin with the need rather than the available demonstration. Who is struggling to reach help? Which recurring work consumes attention? Which unresolved question is important enough to investigate? These are different starting points. Each leads toward a different kind of project.
For an Access project, describe the person and the blocked encounter. An adult learner needs patient help at irregular times. A customer needs a clear explanation in familiar language. A new employee needs to understand a procedure without guessing which colleague is safe to interrupt. Choose a need whose current barrier you can observe.
For an Autonomy project, describe a recurring assignment and its completion condition. The studio needs routine bookings to arrive accurately in its working calendar. A service team needs ordinary requests carried to a resolved record. Choose work with clear authority, inspectable results, and an exception owner who can improve the arrangement.
For an Answers project, describe what is unresolved and how a proposed result could be tested. The laboratory needs to establish whether a new formulation meets its constraints. A technical team needs a verifiable improvement to a method. Choose a question whose answer would change a decision, and identify the evidence required before committing to the engine.
Now examine dependencies. An appointment agent may need better access to authoritative records before it needs a more capable model. A tutor may need a different language or delivery channel before it needs more features. A research project may need consistent experimental records before additional compute can help. The glamorous component is not always the limiting one.
Set a baseline. How does the encounter or task work now? Where does it fail? How much human work does it require? What is presently known? Without a baseline, almost any new output can be described as improvement.
Then set a bounded trial. State who participates, what is included, what authority is granted, what counts as completion, and what will be recorded. The trial should be narrow enough to understand and representative enough to encounter the problem you actually want to solve. A demonstration designed to avoid every ordinary complication teaches little about operations.
Evaluate the result using the promise's own evidence. Access needs usable outcomes for the intended people. Autonomy needs completed work and an honest account of human involvement. Answers needs a new contribution and the validation appropriate to it. Satisfaction is relevant, but it cannot stand in for every other kind of evidence.
Decide what to do with the result. Expand a demonstrated success, repair a known limitation, narrow an overbroad promise, or stop a project whose conditions do not support it. An organization that can stop clearly has learned something. Continuing indefinitely because the technology is important is not a strategy.
This approach does not require three separate departments or one project for each A. It requires clarity about the change you are buying or building. A small project that removes a persistent barrier can create more value than a broad program whose central accomplishment is announcing itself.
The next useful project is usually close to a specific person's repeated frustration, a recurring task nobody wants to carry, or an unresolved question that actually matters. Start there. Let the framework sharpen the choice rather than enlarge the presentation.
A question to carry · Chapter 16
Write a one-page project brief: person or institution served, current barrier, primary A, promised consequence, required conditions, evidence, exception owner, and decision date. If you need several pages to explain the useful consequence, narrow the first trial.
Chapter 17 / 18
Looking Toward 2030 Without Pretending
A future can be described in the past tense to make it easier to imagine. That technique lets us inhabit consequences rather than merely list technologies. It also creates a responsibility: readers should know when they have entered a scenario.
My 2030 essays imagined billions gaining useful support, personal Gatekeepers handling ordinary work, and research engines contributing to problems on a civilizational scale. They also imagined particular hardware forms and deployment patterns. Those details were forecasts, not observations recorded in advance. [S2] [S3]
The enduring framework does not depend on every detail coming true. Access can improve through a phone, a shared device, a voice interface, or a form not yet familiar. Autonomy can operate locally, in the cloud, or across an arrangement of systems. Answers can emerge from a large institution or a smaller team with an unusually good question and access to the right evidence.
The architectural choice matters for privacy, continuity, performance, and control. It should be evaluated on those grounds. A forecast about one architecture should not harden into a definition that excludes every other way to deliver the human consequence.
For 2030, three conditional questions are more useful than a confident inventory of gadgets. What if useful guidance becomes much more available? What if ordinary work can continue with substantially less required human involvement? What if research systems become better at contributing to validated discovery?
Under the first condition, education and service design would have to account for people who can ask more questions and arrive with more context. The opportunity would be broader participation. The unfinished work would include reaching people whose language, circumstances, or infrastructure still prevent useful access.
Under the second, organizations would have to reorganize around outcomes and exceptions rather than assuming a person must conduct every transition. The opportunity would be less routine coordination. The unfinished work would include authority, dependable records, recovery, and the distribution of benefits among owners, workers, and customers.
Under the third, research institutions would have to improve the relationship between computation, evidence, and application. The opportunity would be a wider search for solutions. The unfinished work would include validation, reproducibility, access to instruments, and the practical translation of a result into something people can use.
None of those consequences is guaranteed by better models alone. Adoption can be uneven. Institutions can preserve old bottlenecks. A system can lower the cost of producing claims while raising the burden of checking them. Convenience can deepen dependence when records and choices are trapped inside a service.
These are reasons to build deliberately, not reasons to stop imagining. A forecast becomes useful when it identifies conditions we can work on and signs we can observe. We can ask which barriers have actually fallen, which tasks are actually being completed, and which discoveries have actually survived serious tests.
We can also ask who benefits. A future in which a few people gain dependable coordination while everyone else receives only more advice would represent an uneven realization of the 3 As. Access should keep the human distribution of capability in view even as Autonomy and Answers advance.
I still regard Access as the defining human question. Intelligence matters through what it makes possible. The future worth preparing for is one in which more people can participate, work can proceed without consuming every moment of presence, and new knowledge enlarges the range of things humanity can do.
A question to carry · Chapter 17
Choose one 2030 prediction you find compelling. Separate its proposed human consequence from its assumed device, company, architecture, and deployment count. Identify the conditions that would make the consequence possible and the evidence that would show progress.
Chapter 18 / 18
What Becomes Possible
Return to the three scenes at the beginning.
Lena is still a person learning, with the effort, uncertainty, and satisfaction that learning involves. The achievement is that she can reach a form of help that fits her life. Access has not removed her from the process. It has made her participation more possible.
The owner of Palmetto Studio is still responsible for the business. She defines what it offers and answers for the commitments made in its name. The achievement is that ordinary work can continue without repeatedly requiring her to become the connection between every system. Autonomy has not abolished responsibility. It has changed which work must pass through her hands.
The researchers are still engaged in inquiry. They must define questions, examine evidence, and distinguish a candidate from an established result. The achievement is that AI can contribute to searching, proposing, and establishing things that would otherwise remain beyond reach. Answers has not made truth effortless. It has changed the possibilities of discovery.
These are three expansions of the possible: participation, action, and knowledge.
They are also three invitations to discipline. Make the help usable. Carry the work to the promised outcome. Submit the claim to the right test. The framework becomes stronger when each A is required to deliver the particular thing it promises.
For the person using AI, this provides a way to ask for what you actually need. Sometimes you want to understand. Sometimes you want something done. Sometimes you want to investigate what nobody yet knows. There is no prize for turning every request into the most ambitious category. A good explanation can be exactly right. A completed ordinary task can be enough. A research question deserves the time and evidence it requires.
For the builder, the framework provides a way to resist empty scope. Define the human consequence. Build the conditions that support it. State the limits plainly. Make the evidence inspectable. Let the user judge the benefit in the life or institution where it is supposed to appear.
For the business leader, it distinguishes three kinds of investment. Access expands the reach of useful capability. Autonomy changes the operating burden. Answers expands what the organization can discover or establish. They can reinforce one another, but they do not become substitutes merely because the same model appears in all three proposals.
For educators and public institutions, the framework keeps a larger question visible. Capability that never reaches people is an incomplete social achievement. A system that makes action easier for some while leaving others to coordinate every barrier can widen an old divide in a new form. Broader participation requires attention to the whole route from help to consequence.
And for all of us, there is the question of presence. What do we want to become available for when less routine work requires us? AI can help rearrange the conditions. Activity alone cannot answer what a good life should contain.
The final measure is therefore close to home. Someone can understand what previously defeated them. Someone can stay with a person they love while ordinary work continues. Someone can test an idea that once seemed too difficult to investigate. A larger possibility becomes part of a particular life.
Access asks who can enter. Autonomy asks what can continue. Answers asks what can become known.
Keep the three questions distinct. Build the connections between them. Then look beyond the conversation and see what has actually changed.
A question to carry · Chapter 18
Write three sentences about your own next year: a capability you want to reach, a responsibility you want carried faithfully, and a question you want to investigate. Give each a consequence you could recognize in the world. Those sentences are a beginning.
Appendix A
The working cards
Use these prompts to prepare a project or inspect a promise. They are practical tools developed for this edition, not a claim that one score can measure all three As.
The Access card
Who is the person? What help is denied or deferred? Which barrier will this service remove? Under what conditions will it work? What usable outcome will show that the person benefited? Who is still excluded?
The Autonomy card
What event starts the work? What is the full outcome? Which records govern it? What may the agent change? When must it return to a person? How will completion be verified? What required human work remains, including repairs?
The Answers card
What is unresolved? What knowledge already exists? What contribution is new? What assumptions govern it? Which test could support or overturn it? What has actually been validated? What remains a candidate or a prediction?
The shared record
Record the promise before the trial. Preserve starting conditions, context, tools, authority, baseline, outcomes, failures, and unresolved work. Choose a decision date. Use the evidence to expand, repair, narrow, or stop the project.
The personal test
What has become possible in the person’s actual life? What burden has diminished? What new burden appeared? Where did attention become available? A busy system is not sufficient evidence of a better experience.
Appendix B
A small glossary
Access
Useful help or capability made available to a person whose need was denied, deferred, or poorly served. The test is a usable encounter, not merely an account or an open link.
Autonomy
The ability of an authorized system to carry work toward a defined outcome without a person conducting every step. Always state the task, scope, starting conditions, and exceptions.
Answers
AI’s contribution to new knowledge or a validated solution. In this book the term is more specific than an ordinary conversational response.
Agent
Software that uses AI to choose and carry out steps toward a goal, using tools and checking results. An agent’s actual independence depends on its tools, context, reliability, and authority.
Authority
The mandate that permits a system to act for a person or institution. Technical access and knowledge of someone’s preferences do not by themselves establish authority.
Completion condition
The full consequence that makes an assignment successful, including ordinary implied obligations. An intermediate event does not replace the original promised outcome.
Receipt
An inspectable account of an actual action, its affected record, and what remains unresolved. It should connect the completion claim to the system where the consequence exists.
Human remainder
The work people still must perform for a delegated assignment to succeed, including supplying context, approvals, corrections, and recovery.
AGI Index
John Rector’s proposed task-specific count of required human actions. Lower is less involvement; zero requires full successful completion. Time is recorded separately, and the proposal is not an established universal standard.
Parality
Temporal freedom through personalized AI representation and concurrent delegated timelines. Machines can advance several objectives while the person’s conscious attention remains singular.
Knowledge orchestration
Connecting evidence, meanings, provenance, methods, permissions, and limits so a research process can make defensible use of what is known.
Scenario
An imagined future used to explore consequences and preparation. Even a scenario written in the past tense is not a record of an observed outcome.
Appendix C
Sources & development
This is a newly written synthesis of John Rector’s published framework, researched against the live site on October 29, 2026. Source markers connect chapters to the relevant essays. The original publication dates below come from WordPress; several older posts also show later modification dates.
The adult learner, appointment business, and materials laboratory are fictional teaching examples. Proposed tools and hypothetical trials are labeled as such. The 2030 passages are scenarios, and the AGI Index remains the author’s proposal. Broader 2025 reports were also reviewed; their conversational use of Answers is distinguished from the sharper discovery meaning retained here.
The Three A’s of AI: Access, Autonomy, and Answers
The earliest framework essay found in this research. It distinguishes immediate personal help, independent background action, and the generation of new knowledge. This book develops that distinction as a practical guide to the consequences AI delivers.
Access, Autonomy, and Answers: The Three Pillars of AI in 2030
The Access-centered 2030 scenario. Its future population scale and service descriptions are projections, not established 2026 outcomes.
The Three A’s of Artificial Intelligence in 2030
A future scenario developing Gatekeepers and institutional answer engines. The hardware, architecture, and deployment counts are forecasts; this book preserves the consequences while treating those particulars as contingent.
The 3 A’s of AI: Answers
The key source for Answers as discovery and knowledge orchestration. The economic concentration of frontier research is treated as a forecast tendency rather than a permanent ownership rule.
Talk to My Agent
The operating principle of no new required surface: complete ordinary work in the calendars and business systems people already use. This book distinguishes that principle from a ban on useful management interfaces.
What is an AI Agent
The goal, tools, action, and checking account of an AI agent. An agent may begin in chat; the practical distinction concerns the work carried out after assignment.
What Is Parality? Temporal Freedom Through AI Digital Twins
Parality as temporal freedom through personalized digital representation and delegated timelines. Parallel progress does not require dividing the person’s conscious attention.
Where Intention Becomes Real
The environment that carries an intention across services and into an actual outcome. Access to intelligence can coexist with unequal ability to act on it.
A Timestamp, a Number, a Grade
The task-specific proposed AGI Index. Count all required human actions, preserve implied outcome obligations, disclose setup and counting conventions, keep time outside the index, and report failures separately.
The Manual Remainder | App to Stack
Related reading on the work a person still has to carry after delegating. It complements the task log and completion discussion in Chapters 8 and 9.
The Clean Carry | App to Stack
Portability without extraction: retain general methods, protect institutional work, and rebuild from permitted sources when context cannot travel.
CX: Customer Experience Is Not Negotiable
The company authors a defined customer experience and must deliver it faithfully. This informs the limits of an agent’s authority to make promises in a business’s name.
Highly accurate protein structure prediction with AlphaFold
Primary research anchor for Chapter 12. The paper reports protein structure prediction assessed at CASP14. A predicted structure is not a proven treatment or a solution to every biological question. Journal bibliographic record and the primary PubMed abstract were checked.
Millions of new materials discovered with deep learning
Primary project announcement checked for Chapter 12. Its 2.2 million and 380,000 counts concern computational predictions and a screened candidate subset. The book does not equate those counts with manufactured products or adopt the announcement’s promotional time-equivalence claims.