STRATEGIC-MANAGEMENT FRAMEWORK战略管理框架
Core Code Theory核心代码理论
Core Code Theory (CCT) is a strategic-management framework that separates an organisation's codifiable Performance UI from its tacit, identity-based Core Code, and uses that separation to locate the precise boundary along which artificial intelligence can substitute for human work. It was originated by Dr. Tong Yin.核心代码理论（CCT）是一套战略管理框架，它把组织中可编码的「表现层界面」与内隐的、基于身份的「核心代码」区分开来，并以这一区分来确定人工智能可替代人类工作的确切边界。该理论由殷彤博士原创提出。
Definition. Core Code Theory holds that every organisation runs on two layers. The Performance UI is the visible, describable, transferable layer: procedures, scripts, metrics, outputs. The Core Code is the tacit layer that produces judgement under conditions no procedure anticipated. The first can be documented, outsourced, and automated. The second cannot.
定义。核心代码理论认为，每一个组织都运行在两个层次上。表现层界面是可见、可描述、可转移的一层：流程、话术、指标、产出。核心代码是内隐的一层，它在任何流程都未曾预设的情况下产生判断。前者可以被记录、外包、自动化，后者不能。
The problem问题所在
Organisations describe themselves in the language of the Performance UI, because that is the only layer that can be written down. Strategy documents, job descriptions, quality manuals, and consulting deliverables are all Performance UI artefacts. This creates a systematic blind spot: the layer that determines whether an organisation survives is the layer least represented in its own documentation.组织用表现层界面的语言描述自己，因为那是唯一能被写下来的一层。战略文件、岗位说明、质量手册、咨询交付物，全部是表现层的产物。这造成一个系统性盲区：决定组织能否存活的那一层，恰恰是在它自己的文档里最不被呈现的一层。
The blind spot became expensive in the 2020s. When an organisation evaluates automation, it inventories what it has written down — and what it has written down is, by construction, the automatable layer. The inventory therefore returns an inflated estimate of what can be replaced, and a deflated estimate of what will be lost. Core Code Theory exists to make the second layer visible before that decision is made, not after.这个盲区在 2020 年代变得昂贵。当一个组织评估自动化时，它清点的是自己写下来的东西——而写下来的东西，按其构造本身，就是可自动化的那一层。于是清点结果高估了可被替代的部分，低估了将会失去的部分。核心代码理论的存在，是为了在那个决策做出之前让第二层变得可见，而不是之后。
The mechanism — five components机制 · 五个组件
Performance UI表现层界面
Everything an organisation can document, train others to replicate, and allow outsiders to audit: standard operating procedures, KPIs, service scripts, reporting systems. Its defining trait is not simplicity but transferability — a person who has never worked here could execute it after reading the file.组织中可被文档化、可被培训复制、可被外部审计观察的全部能力。包括标准作业流程、绩效指标、服务脚本、报表体系。它的定义性特征不是“简单”，而是可转移：一个从未在此工作过的人，读完文档后能够执行。
Core Code核心代码
The capacity to produce correct judgement in situations no procedure anticipated. Not “experience” and not the catch-all of “culture”, but a specific set of situational judgement rules embedded in particular people — rules never fully articulated, often inexpressible even by those who carry them.在流程未曾预设的情境下产生正确判断的能力。它不是“经验”，也不是“企业文化”这类含混说法，而是一组具体的、嵌在特定人群身上的情境判断规则，这些规则从未被完整表述过，往往连持有者自己也说不清。
The Substitution Test替代性测试
The operational criterion separating the two layers. Ask one question: if everyone doing this work were replaced by newcomers who had read all the documentation — or by a model — would output be equivalent? If yes, it is Performance UI; the gap, if not, is Core Code. The test matters because it can actually be executed, not merely asserted.区分二者的操作性判据，只问一个问题：如果把执行这项工作的全部人员替换为读过全部文档的新人（或一套模型），产出是否等价？等价则为表现层界面；不等价则差额部分就是核心代码。这个测试的价值在于它可以真的被执行，而不只是概念区分。
Code Drift内核漂移
Core Code transmits through shared experience, never through documents. When the transmission chain breaks — high turnover, rapid scaling, post-merger integration, dispersal to remote work — the code drains away silently while Performance UI metrics show nothing unusual. The signature of drift: every dashboard reads normal until the first situation no procedure anticipated.核心代码只通过共同经历传递，不通过文档传递。当传递链条断裂——高流动率、快速扩张、并购后整合、远程化——内核会在表现层指标毫无异样的情况下静默流失。漂移的特征是：所有仪表盘都正常，直到出现第一个流程未预设的情境。
Code Integrity内核完整性
The degree to which an organisation can still call on its Core Code under pressure. This is CCT's dependent variable, and its interface with The Home Model: the covenant structure the Home Model describes is precisely the mechanism that maintains code integrity.组织在压力下仍能调用其核心代码的程度。这是核心代码理论的因变量，也是它与《家园模型》的接口：家园模型描述的契约结构，正是维持内核完整性的机制。
Diagnostic — test yourself诊断 · 自测问题
- In the past twelve months, which decisions could not be made “by process” and were in the end made by a few specific people? List those people — that list is the carrier inventory of your Core Code.过去十二个月里，哪些决定是“按流程做不出来”、最终靠某几个具体的人做出来的？把这些人列出来——这份名单就是你核心代码的载体清单。
- How many of the people on that list are no longer in the organisation?这份名单上的人，有多少已经不在组织内？
- In your most recent crisis, how much of the response that actually worked was written in the contingency plan?你最近一次危机中，实际起作用的应对方案，有多少写在应急预案里？
- If you ran the Substitution Test on a given department, where would the output gap fall? Are those exactly the links you plan to automate first?如果对某个部门做替代性测试，产出差额落在哪些环节？那些环节是否正好是你打算最先自动化的？
- Does your organisation hold a single document that records judgement rather than process? If not, your Core Code has no redundant backup.你的组织有没有任何一份文件，记录的是判断而不是流程？如果没有，你的核心代码没有任何冗余备份。
Worked example实例
The AI-substitution debate in service industries is usually framed as a percentage: what share of tasks can be automated? Core Code Theory reframes it as a boundary question, and the boundary is not where intuition places it.服务业的 AI 替代讨论通常被表述为一个百分比：多少比例的任务可以自动化？核心代码理论把它重新表述为一个边界问题——而边界并不在直觉所放置的位置上。
Reservation handling, rate loading, forecast generation, and report production are Performance UI in full: documented, rule-governed, transferable, and now cheaper to automate than to staff. The judgement of when to break the rate rule — when a booking pattern signals something the model has not seen, when a guest situation requires a decision the policy does not cover — is Core Code. Organisations that automate the first layer while preserving the carriers of the second gain capacity. Organisations that treat headcount as undifferentiated cost remove both layers at once, and discover the difference only at the first unanticipated event.预订处理、房价加载、预测生成、报表产出，全部是完整的表现层界面：有文档、有规则、可转移，且现在自动化的成本已低于雇人。而何时应当打破房价规则的判断——当一个预订模式暗示了模型未曾见过的东西，当一个客人的处境需要一个政策未曾覆盖的决定——那是核心代码。自动化第一层、同时保住第二层载体的组织，获得的是产能。把人力视为无差别成本的组织，一次性移除了两层，并且要到第一个未预期事件发生时才会发现差别。
This is the analytical core of AI Cannot Replace the Front Desk (Hotel News Resource, 24 July 2026) and of the two Hospitality Net essays on technology and human capability that preceded it.这是《AI Cannot Replace the Front Desk》（Hotel News Resource，2026 年 7 月 24 日）以及此前两篇 Hospitality Net 技术与人性文章的分析内核。
What it is not它不是什么
Not “core code” in the software-engineering sense. The code here is not program code but a code of conduct — a cipher of judgement. The theory concerns organisations of people, not software systems.不是软件工程意义上的 “core code”。这里的 code 不是程序代码，而是“行为准则集合”意义上的密码/编码。理论讨论的是人的组织，不是软件系统。
Not a renaming of tacit knowledge. Polanyi's tacit knowledge describes a property of knowledge; CCT describes a structural division at the level of the organisation, and supplies an operational criterion for drawing it (the Substitution Test) and a dependent variable (code integrity). CCT accepts tacit knowledge as a constituent of Core Code, but is not equivalent to it.不是“隐性知识”（tacit knowledge）的换名。波兰尼的隐性知识描述知识的属性；核心代码理论描述的是组织层面的结构划分，并且提供了一个可执行的划分判据（替代性测试）与一个因变量（内核完整性）。本理论承认隐性知识是核心代码的组成部分，但不等同于它。
Not “corporate culture”. Culture is a descriptive concept; Core Code is an operational one. Culture cannot be tested — Core Code can, by the Substitution Test.不是“企业文化”。文化是一个描述性概念，核心代码是一个操作性概念：文化无法被测试，核心代码可以——用替代性测试。
Common misreading: That Core Code means “important people”. It is not about ability rank: a junior employee can carry critical Core Code while a senior executive may carry only Performance UI. Carrier identity is independent of rank.常见误读：把核心代码理解为“重要的人才”。它不是关于人的能力等级的，一个初级员工可以携带关键核心代码，而一位高管可能只承载表现层。载体身份与职级无关。
Origin & status起源与状态
- Originator: Dr. Tong Yin (殷彤), Ph.D. Hospitality Management, Auburn University; M.B.A., Eastern Illinois University原创者:殷彤博士，奥本大学酒店管理博士；东伊利诺伊大学 MBA
- First public articulation: 2026, in applied essays for Hospitality Net and Hotel News Resource首次公开表述:2026 年，见于 Hospitality Net 与 Hotel News Resource 的应用文章
- Monograph: Core Code — under review at Academy of Management Review专著:《Core Code》——已在《Academy of Management Review》评审中
- Applied in: Hospitality Net and Hotel News Resource columns, 2026应用见于:Hospitality Net 与 Hotel News Resource 专栏，2026 年
How to cite引用格式
Yin, T. Core Code Theory. InsightBridge Global. https://insightbridge.global/theories/core-code-theory.html
Frequently Asked Questions常见问题
What is Core Code Theory?什么是核心代码理论？
Core Code Theory is a strategic-management framework, originated by Dr. Tong Yin, that separates an organisation's codifiable Performance UI from its tacit, identity-based Core Code. Its practical use is to locate the boundary along which artificial intelligence can substitute for human work.
核心代码理论是殷彤博士原创的战略管理框架，它把组织中可编码的表现层界面与内隐的、基于身份的核心代码区分开来。其实际用途是确定人工智能可替代人类工作的边界。
How do you tell Performance UI from Core Code?如何区分表现层界面与核心代码？
By the Substitution Test. Replace the people doing the work with people who have read all the documentation, or with a model trained on it. If output is equivalent, the capability was Performance UI. The gap is Core Code.
用替代性测试。把执行这项工作的人替换为读过全部文档的人，或替换为以此训练的模型。若产出等价，该项能力是表现层界面；差额就是核心代码。
Is Core Code the same as tacit knowledge?核心代码等同于隐性知识吗？
No. Tacit knowledge describes a property of knowledge. Core Code Theory describes a structural division within an organisation, and supplies an operational test for drawing it plus a dependent variable — code integrity — for measuring it.
不是。隐性知识描述知识的属性；核心代码理论描述组织内部的结构划分，并提供划分的操作性测试，以及用于度量的因变量——内核完整性。
Can Core Code be documented?核心代码可以被文档化吗？
Partially and imperfectly. Core Code transmits through shared experience rather than text. Documentation can create partial redundancy, which is worth doing, but an organisation that has documented its Core Code has not thereby made its carriers replaceable.
只能部分地、不完美地做到。核心代码通过共同经历而非文字传递。文档化可以创造部分冗余，这值得做，但把核心代码写成文档，并不等于让它的载体变得可替代。
What is code drift?什么是内核漂移？
Code drift is the silent loss of Core Code when the transmission chain breaks — through turnover, rapid scaling, post-merger integration, or dispersal. Its distinguishing feature is that every performance indicator stays normal until the first situation no procedure anticipated.
内核漂移是传递链条断裂时核心代码的静默流失——经由人员流动、快速扩张、并购整合或远程分散。它的识别特征是：所有绩效指标保持正常，直到第一个流程未预设的情境出现。
Who originated Core Code Theory?谁提出了核心代码理论？
Dr. Tong Yin, Founder and Chief Scientist of InsightBridge Global LLC.
殷彤博士，InsightBridge Global LLC 创始人兼首席科学家。