This condensed edition of Volume 2 brings together the one-page guides for the approved chapters and the final appendix. It includes the Author's Note, Chapters 1 through 11, the epilogue, and the appendix on AGI without the fog. You will move through process redesign around AI, the shift from output to outcome, teams with agents, the one-person company, an affordable AI staff for small and midsize businesses, the agent as customer, children in a world of cheap answers, the new labor economy, the physical rails of AI, four scenarios for 2030, the change compass, the final question of who holds the wheel, and five practical questions to replace fear of AGI.
It sorts email, fills a cart, compares terms, and prepares an action. This is no longer a chat with a model. It is an operating loop.
If the agent cannot find, understand, and verify your offer, you have not lost to a competitor. At this new point of choice, you simply do not exist.
Output first became cheaper at one person's desk. Now it is becoming cheaper across departments and industries, while value shifts toward outcomes and responsibility.
When a machine pays, AI slogans do not matter. Rules do: who assigned the task, who checked it, who signed off, and who is responsible for a mistake.
| Layer | Old foundation | New test |
|---|---|---|
| Storefront | Website, shelf, packaging, recognition | Visibility to the agent: structured data, terms, price, trust |
| Sales | Advertising, impulse, the usual channel | Access to the customer through the system that now filters the choice |
| Expertise | "I know, and you do not" | Basic knowledge gets cheaper. Personalization, responsibility, and liability get more expensive. |
| Trust | A human face and reputation | A process: who checks, who signs off, and who fixes a mistake |
The question is no longer "How can AI make people faster?" It is how to build a team, process, verification system, and clear ownership around people and agents.
Building has become cheaper, but delivering value to the customer has become harder. You need visibility, trust, and access to demand.
Volume 1 asked how a person can remain useful. Volume 2 asks a harder question: what should a business do when an agent increasingly chooses, compares, and pays?
Licenses, assistants, and training may help people work faster without changing the company's cycle time, cost, risk, or financial results.
Electricity paid off only when factories were rebuilt around the new source of power, not when owners simply replaced a motor.
A point solution speeds up one step. An application changes a procedure. A system changes roles, metrics, and the design of work.
The advantage goes to the company that proves the new process economics first, not the one with the loudest model announcement.
| Signal | Cosmetic AI | Redesign |
|---|---|---|
| Work map | An assistant was added to the old path | The sequence of steps was redrawn for AI |
| Roles | People simply use the model | Someone owns the AI process and its outcome |
| Metrics | Documents, emails, and prompts are counted | Speed, quality, risk, and outcomes are measured |
| Control | "Looks fine" and manual trust | Quality checks happen before an expensive mistake |
| Money | Minutes saved disappear at the next handoff | Cycle time, cost, or process margin changes |
No AI, scattered experiments, or personal productivity only. Work feels easier, but the organization still follows the old rules.
A team process, operating model, or AI-native business. Roles, KPIs, controls, and the economics all change.
A company does not lose because it lacks the newest model. It loses when it keeps managing work by the old rules after the cost of doing that work has changed.
Texts, reports, and drafts become nearly free. That does not mean the business has gained value.
An outcome exists when the work reaches a customer, a decision, or the bottom line instead of stalling in artifact production.
Evaluation, flow metrics, and stop rules turn a smooth model response into a working process.
When a mistake is expensive or a decision is ambiguous, the human does not disappear. The human becomes the point of accountability.
| Point | What to examine | What changes |
|---|---|---|
| What you counted | Emails, reports, prompts, generation speed | Decision speed, quality, risk, and value delivered |
| Where it goes wrong | A polished pile of work looks like progress | The value stream may still be blocked before it reaches the customer |
| What to fix | Not the model by itself | The process, verification, metrics, and ownership |
Do not celebrate the number of drafts. Prove that the outcome improved.
Measure the value stream and the point of verification, not team activity.
Buy a shorter path to the customer and revenue, not more generation.
AI produces more. A business wins only when more value reaches the customer.
Work now includes participants that act in steps, call tools, and leave a record.
A defined role, inputs, permissions, checks, escalation path, and owner turn an agent from a toy into part of the process.
Shared memory, rules, a stop rule, and an evidence trail matter more than the number of agents in the system.
Responsibility cannot be delegated to a model. The manager owns the outcome of the whole system.
| Point | What to examine | What changes |
|---|---|---|
| No operating loop | Each agent has its own context, permissions, and guesses | Mistakes multiply while the human loses the full picture |
| With a contract | The agent has a task, boundary, escalation path, and metric | Its permissions and mandatory stop points are clear |
| With shared infrastructure | Common data, an action log, and controls | The team becomes a system that can be audited |
Learn to assign work to an agent and verify the result, not just write prompts.
Define the agent contract before you scale. Otherwise, speed will turn into noise.
Build the shared operating loop first, then add agents.
An agent without a contract is not a team member. It is a source of random motion. The operating loop creates the team.
Stories about the one-person company easily turn into a fantasy of complete autopilot.
One person working with agents can run marketing, analytics, support, or document operations.
Code, media, and agents provide permissionless leverage. You can assemble serious capacity without building a separate department.
The person running the system still carries the operating loop, trust, customer relationships, and risk of burnout.
| Point | What to examine | What changes |
|---|---|---|
| Not autonomous | The whole company, trust, legal responsibility, and customer relationships | These stay with the person and the organization |
| Partly autonomous | A single function with repeatable steps and verification | This is where agents provide real leverage |
| Foundation | A harness, external memory, contracts, and stop rules | Without them, one person becomes the bottleneck |
Build your own operating system and run a function instead of merely working faster.
Give agents functions that have an owner, a metric, and a verification loop.
Buy leverage deliberately. It amplifies your work but does not remove responsibility.
A one-person company works when the function is autonomous and the person still owns the boundaries, the customers, and the purpose.
Do not start with "adopt AI." Start by preventing lost calls, leads, revenue, trust, or owner time.
The idea should move new revenue, costs, or the customer experience. Otherwise, it is busywork with AI.
A subscription gives you a tool. An assistant makes you faster. An autopilot sells a completed function within narrow boundaries.
Platforms provide capacity and charge a take rate. The agent helps, but a person must stop an expensive mistake.
| Point | What to examine | What changes |
|---|---|---|
| Pain point | Where revenue, leads, trust, or time leak today | Start here, not with a tool shortlist |
| Pilot | If touching the core feels risky, start with work you already outsource | A budget already exists and the internal process stays intact |
| Outcome | Easy work goes to the agent. Hard cases reach a person with context. | In retail: faster service, lower operating cost, and a better conversation |
| Rails | Payments, KYC, support, and marketplaces provide a ready-made staff | Do not give one channel control of both the customer and the data |
Think like the owner of a function. What can you run as a team of you plus agents?
Before opening a role, ask whether a supervised agent can do the work and which value lever would move.
Choose one pain point, build the operating loop, and count your own time in the new cost base.
A small business no longer has to be large to have a staff. But a staff of agents is a drill. A person still chooses where the hole should go.
Customers increasingly ask an AI what to buy and arrive with a choice already made.
Ads, storefronts, and impulse have less power. The machine compares the job, price, risk, and evidence.
The loudest brand does not win. The agent must be able to find it, understand it, and recommend it safely.
When an agent buys and pays, authority, limits, identity checks, logs, and accountability all matter.
| Test | What the machine will ask | What to fix first |
|---|---|---|
| Findability | Do AI answers and trusted sources include you for real customer queries? | Profiles, reviews, citations, and a clear description of the job you solve |
| Evaluability | Can the agent understand the price, terms, limits, availability, and evidence? | Remove vague claims, data trapped in images, and "ask a sales representative" |
| Actionability | Can it buy, enroll, or begin without a required conversation? | Provide clear steps, an API or form, payment, confirmation, and a log |
| Moat | What can the machine neither strip of identity nor reduce to a price? | Strengthen relationships, reputation, trust, and the human touch |
Run a real customer query and see whether you appear in the AI answer and how the machine describes you.
Shift marketing from buying attention to providing data, evidence, and trusted sources that agents can read.
Check three things: can agents find you, understand you quickly, and buy from you without a conversation?
You used to persuade a person. Now a machine must choose you first. The door to the customer changes before the customer ever clicks "buy."
AI does not take an entire profession at once. It takes the bottom rung where beginners used to grow beside experienced people.
Mastery needs challenge, difficulty, and connection. A "do it for me" button weakens all of them.
An adult delegates a skill they already have. A child delegates a skill that has not developed yet.
Real projects, a present mentor, evidence of completed work, and the role of agent boss restore a place to grow.
| If AI... | What the child gets | How to turn it into practice |
|---|---|---|
| Writes for them | A quick submission without practice in writing or thinking | Have it check the outline, ask questions, and point out weak spots |
| Solves the problem | An answer without the experience of finding the path | Ask for a hint, the next step, or a check question, but not the solution |
| Builds the project | Polished output with no authorship | The child sets the goal, makes choices, edits the work, and defends it under their own name |
| Always agrees | Easy companionship without the friction of a real relationship | Use AI to rehearse a conversation, not to replace the person beside them |
Look past the job title to the place where growth happens. Where does the child think, choose, make mistakes, and do the work?
If junior tasks disappear, future senior professionals cannot grow. Build learning rungs inside the team.
Demand for workshops, mentorship, projects with real stakes, and "hands plus AI" will grow faster than the school system can adapt.
We cannot choose a profession for our children. We can preserve places where they do the work themselves, ask questions, check quality, and answer for the result.
Work does not vanish, but the lower rungs shrink. Younger workers are filtered out earlier, and fewer entry-level tasks remain.
Engels' pause is a reminder: technology grows productive quickly, while worker pay often catches up later.
It decides whom to show, how to calculate ratings, and which rules will control access to work tomorrow.
Bargaining power grows from outcomes, direct relationships, and a reputation you can take with you.
| Career foundation | Old ladder | New reality |
|---|---|---|
| Right to enter | A degree, internship, or junior role | A portfolio of outcomes and evidence of real work |
| Visibility | A person reads your resume | A filter may stop you before a recruiter sees you |
| Reputation | A reference or a name inside one company | Your rating is often locked inside a platform |
| Rules for growth | Known to everyone and slow to change | The platform owner changes them alone |
Check your dependence on platforms. If access closes tomorrow, what remains besides your resume?
A narrow entry path creates a shortage of midlevel talent later. Build learning rungs inside the team.
Own your channel and your customer trust. A rating in someone else's results is worth less than distribution you control.
Use other people's platforms, but do not confuse access with ownership. A career is more resilient when the outcomes, relationships, and name belong to you.
A model answers in seconds, but value still depends on roads, warehouses, electricity, people, and hardware.
As each request gets cheaper, it makes sense to give AI more tasks. The total compute bill rises.
Data centers need electricians, installers, and technicians. The shortage has moved from intelligence to the physical world.
You do not own the chips, energy, clouds, marketplaces, or APIs. Their owners charge rent for the ride.
| Position | How to recognize it | Move up |
|---|---|---|
| Owns a node | You have customers, data, trust, or expertise that others pay to access. | Deepen the moat through context, accountability, and direct relationships. |
| Builds deliberately | You pay rent but know the amount, keep a backup route, and own an asset of your own. | Move one asset from rented to owned each year. |
| Pays without looking | You do not know how much revenue goes to platforms or what you would do after a price increase. | List every toll and add them into one number. |
Identify the platforms between you and the value. Strengthen what you can carry to any set of rails.
Recalculate the process with compute at three times the price. Keep a second route for models, data, and prompts.
Calculate platform rent as a share of revenue. Do not let one AI provider become the only gateway to your cost base.
Use the large platforms, but keep a map of alternate routes: portable data, several providers, open models, and a value node of your own.
Benefits concentrate, but people still command a price. Customers, work, and audiences arrive through gates owned by others.
Benefits gather at the top while the middle loses value. Career rungs shrink, and the public response becomes the main force.
AI amplifies people. The machine prepares, calculates, and drafts. The person chooses, verifies, and takes responsibility.
An abundance of generated work raises the price of the human touch. Trust, presence, a signature, and care become the product.
| What to watch | What growth looks like | First move |
|---|---|---|
| Platform dependence | The share of sales, hiring, or demand that comes through algorithmic intermediaries | Maintain a direct channel and combine all platform rent into one number. |
| Entry into the profession | Beginners find it harder to get their first real tasks and make useful mistakes | Build practice rungs and a reputation people can carry elsewhere. |
| Human premium | Customers pay more for personal involvement, trust, and a human signature | Strengthen your name, relationships, and willingness to take responsibility. |
Find your place on the indicator panel and build a portfolio of outcomes, customers, reputation, trust, and a backup route.
Your AI metric is a vote for a scenario. Measure the growth in outcome per person, not only the roles removed.
Move at least one asset from rented to owned: a channel, customer list, brand, data, or customer trust.
Betting on one forecast makes you hostage to one scenario. A portfolio of no-regret moves will not pay equally in every world, but you need it in all of them.
Do not automate chaos. Start with work you can describe, repeat, and verify.
Learning belongs next to the operating loop. People learn on real tasks, not in a course taken to check a box.
Record the baseline first. Measure the time, cost, and rework across the full cycle.
Responsibility cannot be delegated. The agent has an owner, boundaries, a log, and an emergency stop.
| Question | A good candidate | When "no" helps |
|---|---|---|
| Does it repeat? | A stream of similar requests, documents, or decisions returns every week. | A rare expert task is better left to a person. |
| Is there enough volume? | There are enough cases to show the savings and keep training grounded in real work. | Low frequency will not pay for the verification loop. |
| Can you verify it? | You know what a correct result looks like and who confirms the quality. | Without verification, the agent will only make the mistake faster. |
| Can you tolerate an error? | You can stop and fix a failure before it reaches the customer without human review. | High risk requires a narrow role and a human decision. |
| Does the context exist? | Instructions, the knowledge base, data, rules, and history are available to the system. | If context lives in people's heads, collect it first. |
The process was chosen for a reason, not because it is fashionable.
A baseline metric exists.
A human owner has been named.
An error is visible and can be stopped.
People learn through live work.
Context is not lost across a zoo of services.
You know what to expand and what to close.
Notice where your work owns the outcome and where the agent only prepares a draft.
Start with one process, one owner, one metric, and one failure you are prepared to accept.
Test the outside loop. Can other people's agents find, understand, and choose your product without a human salesperson?
Half the processes should receive a "no" after scoring. That saves attention, money, and trust.
Production gets cheaper. Writing, calculating, searching, and assembling drafts have become easier and faster.
The harbor does not appear by itself. Even the best engine cannot tell you why the trip is worth taking.
The navigator is not accountable. A model can suggest a turn, but the review will still come back to a person.
Judgment is the final scarce resource. Choice, verification, and the willingness to carry the consequences did not become cheap.
AI can make the draft. Your value lies in knowing which draft is right and what you are willing to stand behind.
A team with agents depends on the person who sees the goal, verifies the outcome, and accepts the review.
A company wins through the machine built around the engine: the process, destination, customer, metric, and control.
A model can suggest a route. But you learn to hold the wheel when letting go feels easiest only by staying in the driver's seat.
Replace a bad question with a workable one. "Can a machine think?" gives way to a testable game.
The fear becomes physical. The machine makes a move that a master would not have found alone.
Defeat does not end growth. Go players began playing stronger and more novel moves alongside a superhuman machine.
This is no longer a board game. Business has messy data, people, a cost of error, and responsibility.
| Dimension | Strong models today | AGI as a hypothesis |
|---|---|---|
| Breadth | Many classes of tasks, with failures and blind spots. | Broad transfer across unfamiliar tasks. |
| Reliability | Superhuman in places, unstable at the edges. | Consistent performance at the level of a strong human across a broad class of tasks. |
| Autonomy | A short horizon under rules and review. | Long chains of action inside broad boundaries. |
| Verification | Without an operating loop, it can make mistakes with confidence. | It still requires authorization, a known cost of error, and accountability. |
Do not ask how smart it is. Ask what it does and where that work sits on your task list.
An email draft and a customer payment belong to different worlds of risk.
Test it on messy data, exceptions, and the details of your work, not only in a demo.
Find the action trail, the stop rule, and the name signed under the result.
A tool can strengthen judgment or weaken the habit of checking long before AGI arrives.
AI is not simply replacing us. Each year, it asks a harder question: what exactly are you useful for?