@ma_zhenyuan: https://x.com/ma_zhenyuan/status/2069049367747797275

X AI KOLs Timeline News

Summary

This article explores the ultimate form of AI organizations, arguing that the core is not simply cost reduction and efficiency improvement, but rather to precipitate the implicit judgments of bosses and employees into a recordable and calibratable system, thereby achieving the retention and transfer of organizational judgment. The article introduces the concepts of OpenTSC and TSC, proposes a thin-shell company model, and suggests that future organizations will be more like guilds.

https://t.co/m548UfJ3Uk
Original Article
View Cached Full Text

Cached at: 06/22/26, 03:47 PM

The Final Form of AI Organizations

Zhang Xuefeng’s passing made many bosses realize: if the most valuable judgment in a business resides in one person, when that person falls, the company is gone.

Zhang Xuefeng never just sold school information;

What parents truly bought was his judgment combining their child’s scores, personality, family conditions, and risk tolerance.

Today’s final form of AI organizations can solve this problem.

The False Core of AI Organizations: Cost Reduction & Efficiency Gains

I’ve been meeting with bosses offline recently. When I mention AI organizations, their first thought is always cost reduction and efficiency gains.

That’s normal. Labor costs keep rising, customers become harder to please, the market is fiercely competitive, and AI suddenly can write copy, handle customer service, generate weekly reports, draft sales follow-ups, and write code. Naturally, bosses wonder: can the work of 10 people be done by 3? Can something that took half a day now have a first draft in ten minutes?

A company must survive first before it can talk about organizational ideals. Cost reduction and efficiency gains are the entry point—we shouldn’t mock them.

But it’s a false core.

I call it false because it only scratches the surface. If AI just makes old processes run faster, the company still gets the same old company.

Where humans used to fill in the gaps with intuition, AI continues to guess; Where bosses used to make the final call, AI still doesn’t know the standards; Where seasoned employees used to backstop, AI can only read the context once and give a plausible answer.

What AI organizations truly need to solve is that the valuable experience and judgment within a company can no longer be tied to individuals. Hiring fewer people is merely a byproduct.

The Real Core: Judgment Retention

When an employee leaves, the biggest headache isn’t just an empty position.

Handover documents can pass along accounts, customer lists, project statuses, and to-do items. But the truly valuable things often can’t be handed over:

When an operations lead leaves, they take their sense of campaign pacing, channel feel, content judgment, and understanding of platform nuances. When a sales manager leaves, they take their customer segmentation, pricing boundaries, payment risk, and the sense of when to push forward and when to shut up. When a project manager leaves, they take their feel for people and timelines: knowing when someone says “almost done” really means almost done, and when someone says “close enough” means two more days.

These things are gritty and detailed, but a company relies on them every day.

A position can be filled. A process can be patched. But if the invisible system within a person isn’t preserved, the new hire will just have to stumble through the same pitfalls.

That’s why many bosses fear losing people. They say it’s about business continuity, but essentially, they fear that a part of the company’s world model has collapsed. Customers, projects, and systems may still exist, but the “how to judge” framework is gone.

Simply deploying Agents into roles is meaningless for an AI organization. Agents can write daily reports, reply to customers, and crunch data, but they don’t know where the predecessor’s judgment came from or which conclusions have already been proven wrong by reality.

Experience must be retained, and it must become a chain of events, evidence, judgment, and outcomes.

The Boss Is the Company’s Biggest Single Point of Failure

When employees leave, they take experience. When the boss steps back, they take direction.

In many companies, true direction doesn’t live in strategy PPTs or org charts. It lives in the boss’s seemingly casual daily judgments.

A product manager brings a proposal; the boss glances at it and says, “This won’t work.” A salesperson wants to take on a client; the boss listens and says, “This client will cause trouble later.” An operations team wants to launch a campaign; the boss holds back, saying, “Let’s stabilize cash flow first.” Outsiders might think it’s arbitrary, but insiders know the boss is often right.

The problem is that the boss themselves often can’t explain why.

They just have a hunch. The client feels off. The project seems like it will drag on. The employee isn’t a good fit for that role.

It sounds like intuition, but it usually comes from compressed experience: similar clients caused problems before, similar projects dragged the team down, similar employees faltered at critical moments, similar cash flow pressures nearly sank the company. These events were never systematically recorded, so they all get compressed into an “I think so.”

Small companies survive on the boss’s “I think so,” and that’s normal. When the boss is present, judgment can be passed down directly. But as the company grows, this structure breaks down. The boss can’t oversee every step, so subordinates have to guess the boss’s standards. Some guess their preferences, some act according to their own understanding, and some stop and wait for the boss whenever a key decision is needed.

On the surface, the company has departments, positions, and processes. In reality, it’s like many limbs connected to one brain.

If the boss steps back, the brain is gone, but the limbs keep moving, and the company’s direction quickly distorts.

The starting point for an AI organization is here: extract the judgments from the boss’s mind so the company no longer relies on any single person being present.

OpenTSC: Turning Impressions into Events

What’s interesting about OpenTSC is that it doesn’t frame an AI organization as simply “adding more Agents.”

It deals with deep organizational issues: how to turn implicit human judgments about people, projects, and opportunities into a structure that can be recorded, queried, audited, and calibrated.

It’s not a CRM. A CRM records who the customer is, what stage the follow-up is at, and the deal amount. OpenTSC cares about how the judgment was formed.

You can’t just write “Zhang San is reliable.” You need to record what Zhang San did, when, what evidence exists (meeting minutes or chat logs), how credible it is, which project it relates to, and what the outcome was.

This is crucial.

The most easily distorted thing in a company is impression. If someone recently helped you, you forget they dropped the ball before. If a client recently paid promptly, you overlook their consistent price-haggling. If a project’s recent data looks good, you temporarily ignore delivery pressure.

The human brain automatically retouches the picture. An event stream keeps the original.

OpenTSC includes an event graph, a judgment engine, a judgment codex, and prediction calibration. Events enter the system first, then judgments are derived based on the codex; emotions can’t directly masquerade as conclusions. It also adds credibility, source, and decay to attributes, so a good impression from long ago doesn’t permanently hog the spotlight.

More importantly is calibration.

After you make a judgment, it can’t just stay as “it seemed right at the time.” It needs an expiration date, a review of the outcome, and a determination of whether it was right, wrong, or only half-right.

This might not be comfortable for bosses. Many are used to making decisions unilaterally, not having their judgments audited by a system.

But without this step, an AI organization can easily become an amplifier of the boss’s emotions. If the boss likes someone, the system finds evidence for them. If the boss wants to pursue a certain direction, the system makes it sound more reasonable. If the boss doesn’t want to face a risk, the system packages it in prettier language.

That’s not an organizational brain.

That’s just a better-talking sycophant system.

TSC’s Thin-Shell Company: What Exactly Is Thin

TSC sits above OpenTSC; it’s more like a set of organizational principles.

It splits a company into two parts: the soul and the shell.

The soul is the company’s laws, judgments, and memory. What counts as good, who is trustworthy, what is worth pursuing, what has happened before, which judgments were validated by reality, which ones later proved wrong—all of these belong to the soul.

The shell is what runs this soul today: software, Agents, teams, models, processes, skills. All of these are the shell.

The “thin” in a thin-shell company doesn’t mean making the company smaller or laying everyone off. It means the shell should be light, replaceable, and transferable; the soul should be thick, preserved, and usable by future shells.

Traditional companies are often the opposite.

The shell is thick: many departments, layers, meetings, approvals, and job descriptions full of content. But the soul is thin: judgment is in the boss’s head, experience is with senior employees, retrospectives stay in meeting rooms, and the actually effective criteria never enter the system.

So the company appears large, but is actually fragile.

TSC’s judgment is straightforward: AI will make execution layers increasingly cheap. What’s truly scarce is intent, judgment, and calibration ability. It’s not hard for one person to lead a group of Agents. The hard part is: what standards do those Agents follow? Who decides when conflicts arise? How to correct errors in judgment? How to learn for next time?

A company can reduce headcount, change tools, upgrade models, or rewrite software. As long as the soul remains, it’s still the same organization. If the soul dissipates, even the most beautiful shell is just an empty framework.

The Zhang Xuefeng Case: Leave Behind a Judgment Ledger

Applying this framework back to a business like Zhang Xuefeng’s makes it easy to understand.

The shallowest approach is to build an “AI Zhang Xuefeng”—mimicking his tone, organizing his opinions, answering parent questions, even acting convincingly.

This can handle some consulting demand, but it doesn’t preserve the most valuable asset.

What needs to be preserved is the judgment ledger.

Every consultation is an event: the child’s score, province, family conditions, whether their personality is conservative or aggressive, whether parents can accept relocation, and the hard constraints on major selection.

Every recommendation is a prediction: the risks of this choice, how things might change in the coming years, the probability of admission, the potential employment outcomes.

Every admission result, university experience, employment feedback, and family satisfaction must feed back into the calibration system.

If a major was consistently recommended but later has poor employment outcomes, we need to know what went wrong. Was it a policy change? Sample bias? Industry cycle shift? Or was the weight given to the child’s personality initially incorrect?

If certain types of families always regret their choices, we need to know why. Was it insufficient information? Was risk preference not clearly communicated? Or did parents say they’d respect the child’s choice but then acted on their own anxiety?

This is what a Zhang Xuefeng-style business should preserve.

His speaking speed, jokes, and the conclusions of any single judgment are just the surface. The truly preservable asset is the judgment system that can be continuously calibrated by reality.

A person will eventually leave, and a person’s energy is always limited. But if every judgment leaves behind events, evidence, predictions, and outcomes, the organization no longer depends solely on one person’s physical presence to survive.

AI Organizations Will Be More Like Guilds

TSC also proposes another change: future organizations will be more like guilds, not traditional org charts.

Traditional companies ask: who reports to whom? Guilds ask: what professions are needed for this task?

When a task arises, first understand the difficulties, risks, and critical points. Then allocate roles.

Someone needs to monitor anomalies—that’s the Sentinel. Someone needs to turn raw materials into candidate events—that’s the Intake Officer. Someone needs to extract valuable judgments from the materials—that’s the Distiller. Someone needs to make predictions with expiration dates—that’s the Prophet. Someone needs to surface risks the boss prefers to ignore—that’s the Briefing Officer. Someone needs to execute the actions—that’s the Executor. Someone needs to identify missing capabilities in the system—that’s the Recruiter.

These names have a game-like feel, but they correspond to real functions that have always existed in organizations.

In the past, these functions were scattered across many people, coordinated by the boss, synchronized in meetings, and backstopped by experience. In an AI organization, they can become roles, Agents, Skills, and task configurations.

The boss’s role will also change.

They will no longer chase every action daily. They will write the law, set boundaries, review battle reports, handle exceptions, and make the heaviest, most critical judgments.

What’s saved isn’t just salaries—it’s also the attention of the boss and core employees that was constantly spent re-explaining, tracking progress, plugging gaps, and transmitting experience.

Finally: The Company Thins, the Soul Thickens

The final form of AI organizations cannot stop at assigning an AI assistant to every position, nor can it go to the extreme of cutting the company down to just the boss.

What it must do is extract the judgment power that formerly resided in the boss, senior employees, experienced managers, meetings, and unspoken understanding—and preserve it, making it executable by Agents, calibratable by reality, and usable by future shells.

Cost reduction and efficiency gains are the entry point.

Making it so that experience doesn’t leave with employees, judgment doesn’t retreat with the boss, and direction doesn’t fluctuate with one person’s physical state—this is harder, and more valuable.

OpenTSC provides a runnable shell. It uses events, evidence, judgment codex, calibration, identity, and roles to turn implicit judgment into something a system can process.

TSC provides the underlying organizational law. It clarifies the relationship between soul and shell: the shell can change, the soul must stay.

In the future, many companies will adopt AI.

Some will only get cheaper execution.

Others will gain an organizational brain that can preserve judgment, inherit experience, and continuously calibrate.

In the former, when employees leave, the company still suffers; when the boss steps back, direction still distorts.

In the latter, talent still matters, the boss still matters, but the company no longer piles all its experience and judgment on a few individuals.

AI organizations will ultimately move here: the company thins, the soul thickens.

This article references open-source projects. I strongly recommend analyzing the source code: OpenTSC: https://github.com/opentsc/opentsc TSC: https://github.com/opentsc/tsc Project author: AI’s Sternest Father https://x.com/dashen_wang

About the Author

Miles | 💰 Harbin Institute of Technology (BS & MS), left big tech to start a business, made first 1M | 2026 ALL IN AI, making money with AI | Public sharing: methods, pitfalls, results

@ma_zhenyuan

Similar Articles

@ba_niu80557: https://x.com/ba_niu80557/status/2071277244287426980

X AI KOLs Timeline

The article deeply analyzes the internal changes Anthropic faces as AI-generated code becomes extremely efficient: the bottleneck shifts from 'writing' to 'verification', traditional management, long-term planning, and effort measurement become ineffective, attention becomes the new scarce resource, and engineers even feel lonely. These phenomena foreshadow the challenges other companies may face in the future.

@hongming731: Alibaba's article on organizational R&D in the AI Native era is well worth reading. It addresses a critical foundational issue: for the past two millennia, organizational structures have been built around human limitations. Humans forget, get tired, misunderstand, and have emotions. The number of people one can stably collaborate with and manage is limited, and information inevitably degrades as it passes between hierarchies...

X AI KOLs Timeline

Alibaba released insights on organizational R&D in the AI Native era, pointing out that traditional organizational structures need to shift from accommodating human limitations to adapting to the efficient execution of AI Agents. The article emphasizes that the core bottleneck of AI transformation lies in outdated information formats; implicit experience must be transformed into AI-understandable infrastructure, while preserving the human role in innovation and cultural building.

@SaitoWu: https://x.com/SaitoWu/status/2058860578291241071

X AI KOLs Timeline

This article discusses the concept of AI-First organizational structure, transforming AI from a supporting tool to a productivity leader, redesigning company processes, and introducing new ideas such as Harness Engineering and Agent Economy.

@manateelazycat: YC's video is worth watching. He hit the nail on the head sharing how AI-native companies should think about organizational structure. I really agree with several key points: 1. The company is a Roman legion, where individual soldiers are strong and there are no weak links, so they never fall into chaos during any tactical execution. 2. The co-pilot model is wrong; we should let AI do it completely because AI executes 10 to 100 times faster than you. If it makes mistakes, just redo it; the second and third attempts are still much faster than you writing code manually. 3. Burn tokens, not heads. That is so true. I think any AI-native company should give employees unlimited tokens. Like our company: many ask how we reimburse AI costs. We don't reimburse; we give everyone unlimited GPT 5.5 tokens, use as much as you want, no reimbursement process. Only with unlimited tokens will people use them and unleash their creativity without psychological burden. 4. Make everything clear and readable for AI. Let me interpret: previously you wrote documents manually, and people didn't want to. Now open up all document interfaces and MCP to AI as much as possible. When you open up to AI, it can use its organizational capabilities to create new company processes. Previously, building internal infrastructure systems was difficult due to huge workloads and many aspects. Now, as long as you expose enough MCPs and APIs, new processes are a matter of one sentence. 5. People are temporary, but contextual documents are important. That's also well said. In the future, the most important things for software companies will be requirement documents, context documents, and process documents. Because code is easy to recreate, but these documents and thought processes are the company's real assets. Alright, that's today's share. Welcome to like, bookmark, and repost. Follow me, I'm a veteran who has been working on operating systems for over 20 years. My daily job is browsing Twitter and reposting valuable content to save your time.

X AI KOLs Timeline

User shares agreement with the views from YC's video on AI-native company organizational structure, including burning tokens instead of heads, letting AI fully autonomously execute tasks, and the importance of documents as core assets.