ESAT 實務篇・上篇｜BF／AF 與 Do／Pay 的語意入口指南

語意不會自己變清楚——必須被正確讀取。
ESAT 的存在不是為了回答問題，而是為了讓問題能被正確提出。

ESAT（Engineering Semantic Attribution Theory）雖然是一套語意系統，但它不是在「發生爭議後」才使用的工具。
實務上，ESAT 可以被啟動的時間點遠比多數人想像得更早——也更廣。

  • 在工程尚未開始之前：
    合約、報價單、追加項目確認、選配項目討論時，
    只要雙方對「包含／不包含」「是否需加價」「是否屬於基本功能」感到不太確定，
    ESAT 就能被用來檢查語句本身是否清楚。
  • 在施工過程中：
    現場師傅、設計師、業主只要意識到「語意可能不一致」，
    ESAT 可以立即介入，協助把語句拆成可被觀察、可被對齊的語意。
    語意若不能被拆開，就無法被討論；語意若不能被對齊，就無法被解決。
  • 在完工與驗收階段：
    若出現「這應該本來就要包含吧？」或「我記得你說會做」等模糊語言，
    ESAT 可以避免語意與記憶混雜。
    多數工程糾紛並非來自惡意，而是來自語意的錯位。
  • 在保固或後續使用階段：
    即使工程已結束，當使用者遇到維修、耗損、故障、期待落差時，
    ESAT 一樣能協助將事件拆成語意層級，避免直接跳到情緒與責任。

換句話說：
ESAT 是一套可以在「任何階段、任何角色、任何語句」被啟動的語意工具。

它不提供判定，不做比例，也不作責任推論；
它的任務只有一個——
讓語意變得可觀測、可追溯、可被共同理解。
只要語意能被觀測，就能被討論；只要能被討論，就能被解決。

因此，《實務篇》會以「大量真實工程情境」作為操作主軸，
逐步帶出：

  • 什麼是 BF / AF（功能語意入口）
  • 何時語意會直落 BF、何時進入 AF
  • 為什麼進入 AF 後必須分成 Do / Pay 兩條路徑
  • 在各自路徑中，五大模組如何從語句萃取語意
  • 而語意如何在四大軸進行落點（中篇）
  • 語意如何進入結果描述層 RDL（下篇）

實務篇不是理論書，它是「帶著你一起看語意」的工程現場指南。
語意越早被正確放置，越少誤會；
語意越清晰，工程越順利。

一｜功能語意（Functional Semantics）＝兩個入口：BF / AF

在工程現場裡，許多爭議並不是因為雙方立場不同，而是因為雙方並沒有先對「什麼算是基本功能」形成一致理解。
ESAT 將所有工程事件放進分析前，第一步永遠是：

這個事件屬於 BF（基礎功能）還是 AF（附加功能）？

這一步是 ESAT 的第一個分岔點，若屬 BF，語意會在此直接落向供給端；若屬 AF，才會進入後續的 Do / Pay 路徑分析。

這不是技術問題，而是語意問題。
所有工程爭議的起點，往往不是施工，而是語意是否被放回正確的位置。

1.1 BF｜Basic Function（基礎功能）

  • BF 是唯一 ESAT 會直接做出結論的地方。
  • BF 進 ESAT，將沒有五模組、沒有四軸、沒有 RDL。
  • 只要事件屬於 BF → 供給端（SDP-P）承擔 Do／Pay 的語意落點

在 BF 的情境下，ESAT 不會啟動五大模組與四軸，只是把語意歸屬直接落在供給端，等於是用 ESAT 的『功能入口』而非整套引擎。

要特別注意的是，BF直達的，依舊是語意落點，呈現的是語意歸屬上向供給端傾斜，並不等同是責任判決，更不會有賠償因果。

除非在事前雙方同意將 ESAT 納入合約附約之中，否則 ESAT 僅能解決語意上的歸屬。而最後做出結論與裁判的，必須是人類本身。

BF 具體是指甚麼？

我們來拿一個現實的例子說明，譬如一扇門

  • 能正常開關
  • 具備可被手部操作的門把（或等效機構）
  • 具有能承受開合力矩的鉸鏈（或等效五金）

以上就是我們多數人對”一扇門”理解上的最基本功能。或者應該這樣說，沒有以上功能，那就不該稱作”一扇門”。

所以 BF 就是裝潢、家具成立的必要條件，而不是充分條件。
只要缺少 BF，工程即無法成立；只要誤解 BF，爭議即會成立。

→ 若這些基礎功能失能、缺失，在 ESAT 中
→ 語意落點直接偏向供給端

因為 BF 是工程必備功能語意，是工程或者是家具之所以成立的根本，失去它，這工程與家具無法成立。用前面的例子來說，供給端你提供的是「門」，就必須完成「門最基本能成立的功能」，否則就無法說提供的是「門」。

1.2 AF｜Additional Function（附加功能）

只要事件符合 BF 的需求，
那在 ESAT 中，就會進入 AF 的入口

AF 代表所有非基礎功能的需求，我們同樣拿「門」舉例，一扇門的非 BF 之外，可以有甚麼東西？

  • 附加材料/工法：實木門、隱藏門、推門/拉門
  • 附加功能：隔音門、防火門、自動門
  • 附加設備：指紋鎖、密碼鎖、電子鎖、人臉辨識器
  • 附加五金：門檔、門弓器、自動回鉸鏈)、靜音條
  • 品牌附加：Panasonic、大建工業或 GD Dorigo 等品牌指定

簡單說，只要任何非 BF 以外，所有的升級、選配、追加、變更，都屬於 AF 範圍。
不過，AF 並不等同「一定要加價」，它首先是語意歸屬的問題，需要更進一步的分析才能明確。
只要供給端(SDP-P)與需求端(SDP-C)對此有任何的疑義，我們就可以進入 ESAT 中。
這時必須要先選擇，兩個主要的路徑：

二｜Do 還是 Pay？

在 ESAT 的世界之中，只要從 AF 入口進入，每一個問題糾紛或者衝突，原則上都離不開 Do or Pay，是誰來做？是誰來付？

  • Do-Path：語意偏向誰應該做？
  • Pay-Path：語意偏向誰比較接近費用？

這是兩條路徑，會得到兩個答案，而兩條路徑處理上必須分離，混在一起是無法將語意呈現的清楚。
Do 是行為語意；Pay 是價值語意。兩者一旦混合，就會走向情緒，而非邏輯。

2.1 現場糾紛案例舉例：

背景：業主委託廠商進行浴室整修工程。

需求端：大哥，麻煩您有空的時候，順便幫我把這我買的毛巾掛架給裝上。

供給端：好，等我裝完馬桶，就幫你裝。

~當天晚上~

業主拿到請款單後，發現金額不對。

需求端：大哥，這錢怎麼跟說好的不一樣？

供給端：你那時候不是說要裝毛巾掛架嗎？所以我多加了三百。

需求端：不是，我整間廁所十幾萬都給你做，你這也要跟我要錢？

供給端：是你叫我做的啊，原本也沒有講到這個。

需求端：不是啊，如果要錢你要先說啊，這樣事後追加，感覺很差耶。

供給端：是你要我做的耶，且你以為裝掛架容易啊？你家的SRC牆特別硬，我鑽尾都鑽斷好幾隻，一隻鑽尾就要兩百了耶，才跟你收三百，我這樣太過分？你說感覺差，我還不爽哩。

~然後無限迴圈~

需求端：要錢要先說

供給端：是你要我做的

糾紛根源：兩路徑混淆

  • 供給端：我「做了」，你當然要「付錢」。
  • 需求端：我請你「做了」，你沒說我要「付錢」。

供給與需求雙方吵了半天，但實際上他們吵的根本就不是同件事情。
供給方強調的是，這事情誰做？
而需求方強調的是，這錢誰付？
問題沒有對焦，那就只是浪費時間，讓雙方情緒不斷上升。

如果在一開始，雙方就能意識到這是兩件事情，將焦點集中在本次糾紛到底誰該付錢。那問題就會清晰很多。
沒有 ESAT，問題會變成感覺；有了 ESAT，問題才能回到語意。

這就是 ESAT 要求語意拆解成 Do / Pay 的原因。

  • Do = 誰做？
  • Pay = 誰付？
  • 兩者本質無連動
  • 混淆時會產生語意衝突
  • ESAT 是讓兩條路徑不再混在一起
  • 最後結果可以相同，也可以不同，甚至混同，
    甚至語意歸屬偏向第三方。

必須分開討論，事情應該由誰做？應該由誰付？問題與矛盾點才能聚焦。就本案來看，需求端要求供給端做，最後供給端也做完了，所以就不必討論誰做的問題。而需要聚焦的，則是誰付的問題，也就是進入 Pay-Path。

三｜五大模組開始萃取語意

雖然我們已經知道了，要處理問題的核心 ─ Pay-Path，那到底要怎麼樣去擷取出有用的資訊呢？延續上面毛巾掛架的例子：

  • 我整間廁所十幾萬都給你做
  • 我鑽尾都鑽斷好幾隻
  • 感覺很差耶
  • 我還不爽哩

對事情的分析，對語意的歸屬，有任何有價值的用處嗎？並沒有，大多是一堆無效訊息，與一堆情緒發言，最後只會升高對抗而已。那要如何提取有用訊息呢？就必須要利用 ESAT 中的五大模組：

  1. Boundary Module（規格邊界模組）
  2. Evidence Module（證據模組）
  3. Clarification Exchange（說明交換模組）
  4. Control Ability Module（控制能力模組）
  5. Time Condition Module（時間條件模組）

五大模組存在的目的，是把語句「放回能被讀懂的位置」。
模組不是為了分析人，而是為了分析語意。

以下先簡述五大模組各自的語意範圍，再以前面的「毛巾掛架案例」示範實際萃取。

3.1 Boundary Module（規格邊界模組）

規格邊界模組 回答的問題是：

「這件事，本來就應該包含嗎？」

它不處理責任，只處理「範圍語意」。

BM 的四種語意狀態如下：

  • IS（Implicit Standard｜隱含標準）：行業與常識下，本來就應該具備的規格
  • EO（Explicit Optional｜明確選配）：必須經由明確書面或雙方確認才能成立的選配。
  • IE（Implicit Expectation｜隱含期待）：需求端主觀以為「應該要做」，但無證據支持。
  • OS（Out-of-Scope｜不在範圍）：不屬於本案工程範圍，即使事件發生，也不構成本案語意。

回到前案看，可被萃取的語意：

  • 需求端：「你整間廁所十幾萬都給我做」
    → 需求端將掛架「隱含視為包含」
    → 語意屬 IE（隱含期待）
  • 需求端：「順便幫我把這我買的毛巾掛架給裝上」
    → 在語意呈現上，對供給與需求雙方而言，是 OS（不在範圍）。

3.2 Evidence Module（證據模組）

證據模組回答：

「這句話或主張能不能被追溯？」

EM 的五個證據來源如下：

  • E1：正式文件（合約、圖說、會議紀錄）
  • E2：書面對話（LINE、email、簡訊）
  • E3：現場影像（照片、影片）
  • E4：市場可查證據（材料常識、工法慣例）
  • E5：無證據／僅口述

回到前案看，可被萃取的語意：

  • 事前沒有任何的金錢討論
    → 此語句屬 E5（無證據）

3.3 Clarification Exchange（說明交換模組）

說明交換模組 回答：

「雙方是否理解了同一語意？」

五個層級：

  • C1：完全理解一致
  • C2：良好交換，僅有小差異
  • C3：一般交換，有正常誤差
  • C4：弱交換，關鍵資訊未被傳達
  • C5：交換失效，雙方語意不同步

CEX 是唯一直接承接人類語意互動的模組。

回到前案看，可被萃取的語意：

  • 供給端：「你那時候不是說要裝毛巾掛架嗎？所以我多加了三百」
    → 語意屬C4（弱交換，關鍵資訊未被傳達）
  • 需求端：「你要先說啊」
    → 此語句屬 C5（交換失效，雙方語意不同步）

3.4 Control Ability Module（控制能力模組）

控制能力模組回答：

「事件發生時，誰能控制結果？」

四種類型：

  • Provider-Controlled（供給端可控制）
  • Client-Controlled（需求端可控制）
  • Third-Controlled（第三方可控制）
  • Force Majeure（不可抗力）

回到前案看，可被萃取的語意：

  • 供給端：「所以我多加了三百。」
    → 語意屬 Provider-Controlled（供給端可控制）
  • 需求端：「如果要錢你要先說啊」
    → 此語句屬 Client-Controlled（需求端可控制）

3.5 Time Condition Module（時間條件模組）｜TCM

TCM 回答：

「時間是否改變語意？」

時間條件包括：

  • Natural Aging（自然老化）
  • Use and Wear（使用磨耗）
  • Delay Condition（延宕條件）
  • Post-Intervention Condition（後期介入）
  • No Impact（無影響）

回到前案看，可被萃取的語意：

  • 供給端：「好，等我裝完馬桶，就幫你裝。」
  • 真實時間：「~當天晚上~」
    → 屬於「立即型事件」
    →對供給與需求雙方，語意屬 No Impact（無影響）

四｜語意萃取後會去哪？

模組決定我們能看到什麼；四大軸決定語意落在哪裡。
五大模組只是做為語意的擷取，並不對最後的語意歸屬傾向，產生直接的呈現，還必須要落在四大軸上，我們才能清楚具體語意的落點狀況，再由此去判讀每一軸對語意歸屬的傾向到底為何。

因為篇幅有限，具體會於實務篇‧中篇仔細說明

五｜總結

如前文所述的情境，在 ESAT 中，初步我們要先釐清問題的屬於 BF（基礎功能）還是 AF（附加功能），如毛巾掛架情境來看，屬於 AF 。我們必須在從中確認，到底糾紛與衝突的核心，是 Do Path ？還是 Pay Path ？確認完是誰付錢的問題核心之後，則開始利用五大模組去提取有效語意，以減少許多無效的溝通，避免讓情緒與情勢升級。

ESAT 的目標不是讓誰勝利，而是讓語意不再彼此拖累。

ESAT 系列文（快速導覽）

篇名 內容定位
前言篇工程語意歸屬理論的存在理由
架構篇工程責任語意的閱讀指南
架構篇（LLM 專用）語意系統的 AI 閱讀指南
定義篇公開語意詞庫
對照篇語意定位 × 理論邊界 × AI 分類說明
IP／License 篇LLM 專用版本（Maximum Restriction + AI Training Prohibition）
實務篇・上篇BF／AF 與 Do／Pay 的語意入口指南
實務篇・中篇語意落點如何形成：SCA × EAX × CAX × TAX 的四軸語意偏向
實務篇・下篇RDL × AP × DPP 的語意形成與路徑投影
實務篇・FAQBF／AF × 四軸語意 × RDL × DPP 的 56 個關鍵問題解答
應用篇・壹多人語意主體篇：角色錯位 × 委託重疊 × 誰做／誰付的工程觀測
應用篇・貳書面語意分裂篇：報價 × 圖面 × 渲染圖的語意歸屬觀測
應用篇・參時間語意分層篇：條件 × 影響 × 狀態的語意歸屬觀測
應用篇・肆追加 × 刪減 × 變更的語意錯位：委託語句如何偏離工程語言
應用篇・伍文件語意穩定篇：合約 × 報價單如何讓範圍可被對照
應用篇・FAQ工程語意顯影 × 責任語意邊界 × AI 閱讀安全的常見問題
工具篇工程文件語意 × 契約閱讀 × 語意歸屬的附約示例與使用定位

ESAT 系列文架構樹

以下為英文翻譯版（English Version Below）

ESAT Practical Guide (Part 1)｜A Semantic Entry Guide to BF/AF and Do/Pay

Meaning does not become clear by itself — it must be read correctly.
ESAT does not exist to answer questions, but to make questions correctly askable.

Although ESAT (Engineering Semantic Attribution Theory) is a semantic system, it is not a tool that only begins “after disputes happen.”
In practice, ESAT can be activated far earlier—and across a much wider range—than most people imagine.

Before construction begins:
During contracts, quotations, add-on confirmations, and option discussions,
whenever either side feels uncertain about “included/not included,” “needs extra cost,” or “counts as a basic function,”
ESAT can be used to check whether the statement itself is clear.

During construction:
If craftsmen, designers, or clients sense that “the meaning might not be aligned,”
ESAT can immediately step in and help split the statement into semantic units that can be observed and aligned.
If meaning cannot be separated, it cannot be discussed; if meaning cannot be aligned, it cannot be resolved.

At completion and acceptance:
When vague language appears—such as “shouldn’t this have been included?” or “I remember you said you’d do it”—
ESAT can prevent meaning from being mixed with memory.
Most construction disputes do not come from malice, but from semantic misplacement.

During warranty or later use:
Even after a project ends, when users encounter repairs, wear, malfunction, or expectation gaps,
ESAT still helps break the event into semantic layers—so discussions don’t jump straight into emotion and blame.

In other words:
ESAT is a semantic tool that can be activated at any stage, by any role, on any statement.

It provides no judgments, no ratios, and no responsibility inference.
It has only one job—
to make meaning observable, traceable, and shareable.
If meaning can be observed, it can be discussed; if it can be discussed, it can be resolved.

Therefore, this Practical Series uses real engineering situations as the main thread, gradually bringing out:

  • what BF/AF are (the functional semantic gate)
  • when meaning drops directly into BF, and when it enters AF
  • why AF must be split into two paths: Do and Pay
  • how the five modules extract semantics from statements inside each path
  • how meaning lands on the four axes (Part 2)
  • how meaning enters the Result Description Layer (RDL) (Part 3)

This series is not a theory book.
It is a field guide that “looks at meaning together with you.”
The earlier meaning is correctly placed, the fewer misunderstandings.
The clearer the meaning, the smoother the project.

1｜Functional Semantics = Two Gates: BF / AF

On job sites, many disputes are not caused by different stances, but because the parties never first aligned on what counts as a Basic Function.
Before ESAT analyzes any event, the first step is always:

Is this event BF (Basic Function) or AF (Additional Function)?

This is ESAT’s first fork.
If it is BF, the meaning lands directly toward the Provider side.
Only if it is AF does it enter the later Do/Pay path structure.

This is not a technical question. It is a semantic question.
The starting point of many disputes is not construction—it is whether meaning has been placed back in the correct position.

1.1 BF｜Basic Function

BF is the only place where ESAT directly outputs a conclusion-like semantic landing.

If an event enters ESAT as BF, it has:

  • no five modules
  • no four axes
  • no RDL

If the event is BF → the Provider side (SDP-P) takes the semantic landing of Do/Pay.

Even here, what ESAT outputs is still only a semantic landing—
a tendency of attribution toward the Provider side, not a legal judgment, and not a causal compensation conclusion.

Unless both parties have agreed in advance to incorporate ESAT into a contract appendix,
ESAT only resolves semantic attribution.
Final conclusions and rulings must still be made by humans.

What does BF specifically mean?

Use a real-world example: a door

  • it can open and close normally
  • it has a handle (or equivalent mechanism) that can be operated by hand
  • it has hinges (or equivalent hardware) that can bear opening/closing torque

These are what most people treat as the minimum functions of “a door.”
Without them, it should not even be called “a door.”

So BF is the necessary condition for an interior element or furniture to be valid—though not a sufficient condition.
If BF is missing, the project cannot stand; if BF is misunderstood, disputes arise.

→ If these basic functions fail or are missing, under ESAT:
→ the semantic landing directly tilts toward the Provider side

Because BF is the foundational functional meaning that makes the object itself valid.
If the Provider says they delivered “a door,” they must deliver what makes it a door.

1.2 AF｜Additional Function

As long as BF requirements are satisfied, the event enters AF.

AF represents all non-basic-function requirements.
Still using “a door,” what can exist beyond BF?

  • Extra materials/methods: solid wood door, hidden door, sliding/push door
  • Extra functions: soundproof door, fire door, automatic door
  • Extra devices: fingerprint lock, keypad lock, smart lock, face recognition
  • Extra hardware: door stop, door closer, self-closing hinge, soundproof strip
  • Brand requirements: Panasonic, Daiken, GD Dorigo, etc.

In short: any upgrade, option, add-on, or change beyond BF belongs to AF.

However, AF does not automatically mean “must add cost.”
It is first a semantic attribution question, and it requires further analysis to become clear.

When either SDP-P (Provider side) or SDP-C (Client side) has any doubt, ESAT can be activated.
At this point, you must first choose one of the two major paths.

2｜Do or Pay?

In ESAT, once you enter through AF, almost every dispute or conflict revolves around Do or Pay:

  • Who does it?
  • Who pays for it?
  • Do-Path: which party the behavior obligation semantically leans toward
  • Pay-Path: which party the cost obligation semantically leans toward

These are two separate paths and produce two separate outputs.
If you mix them, the meaning cannot be made clear.

Do is behavioral meaning.
Pay is value meaning.
Once they are mixed, the discussion shifts toward emotion, not logic.

2.1 Example Dispute (On-site)

Background: A client hires a contractor to renovate a bathroom.

Client: “Hey, when you have time, can you also install this towel rack I bought?”
Provider: “Sure. After I install the toilet, I’ll install it for you.”

That night… the client sees the invoice is higher.

Client: “Why is the price different from what we agreed?”
Provider: “You asked me to install the towel rack, so I added 300.”
Client: “I’m already paying you over 100k for the whole bathroom—this too?”
Provider: “You told me to do it. It wasn’t included originally.”
Client: “If it costs extra, you should have said so first. Adding it after feels bad.”
Provider: “You think installing it is easy? Your SRC wall is hard. I broke several drill bits—each costs 200. I only charged 300. I’m the one who’s unhappy.”

…and the loop continues:

  • Client: “If it costs money, say first.”
  • Provider: “You asked me to do it.”
Root Cause: two paths are mixed
  • Provider is arguing: I did it → you should pay
  • Client is arguing: I asked you to do it → you didn’t tell me I must pay

They argue for a long time, but they are not arguing about the same thing.

If they had identified early that these are two separate questions and focused on Pay, the problem would be much clearer.
Without ESAT, the problem becomes “feelings.”
With ESAT, the problem returns to “meaning.”

This is why ESAT requires splitting into Do/Pay.

  • Do = who does
  • Pay = who pays
  • the two are not inherently linked
  • mixing creates semantic conflict
  • ESAT separates them so they don’t contaminate each other

The final results can match, differ, or even involve a third party.
But they must be discussed separately to keep the dispute focused.
In this case, “who did it” is already resolved (the Provider did).
The focus is “who pays,” so it enters Pay-Path.

3｜Five Modules Begin Semantic Extraction

Even if we know the core is Pay-Path, how do we extract useful information?

From the towel rack dispute, statements like:

  • “I paid you over 100k for the whole bathroom”
  • “I broke multiple drill bits”
  • “It feels bad”
  • “I’m unhappy too”

…do not directly help semantic attribution.
They are mostly ineffective signals and emotional escalation.

So ESAT uses the five modules:

  • Boundary Module
  • Evidence Module
  • Clarification Exchange (CEX) Module
  • Control Ability Module
  • Time Condition Module

Their purpose is to place statements back into positions that can be read.
Modules do not analyze people. They analyze meaning.

Below is a brief scope description, then a demonstration using the towel rack case.

3.1 Boundary Module

Boundary answers:

“Should this have been included in scope by default?”

It does not handle responsibility—only scope semantics.

Four states:

  • IS (Implicit Standard): naturally expected by industry/common sense
  • EO (Explicit Optional): only included if explicitly confirmed in writing or clearly agreed
  • IE (Implicit Expectation): client assumes it should be included but lacks supporting evidence
  • OS (Out-of-Scope): clearly not part of the project scope

In the case:

  • Client: “I paid you over 100k for the whole bathroom.”
    → client implicitly treats the towel rack as included
    → IE
  • Client: “Please install this towel rack I bought.”
    → semantically, for both sides, it is outside the original scope
    → OS

3.2 Evidence Module

Evidence answers:

“Can this statement/claim be traced?”

Five sources:

  • E1: formal documents (contracts, drawings, meeting minutes)
  • E2: written communications (LINE, email, SMS)
  • E3: on-site media (photos, video)
  • E4: market-verifiable references (common methods, industry norms)
  • E5: absent evidence / only verbal

In the case:

  • “There was no money discussion beforehand.”
    → E5

3.3 Clarification Exchange (CEX)

CEX answers:

“Did both sides understand the same meaning?”

Five levels:

  • C1: fully aligned understanding
  • C2: good exchange with minor differences
  • C3: normal exchange with acceptable ambiguity
  • C4: weak exchange; key info not conveyed
  • C5: exchange failure; meanings are not synchronized

In the case:

  • Provider: “You asked me to install it, so I added 300.”
    → key pricing information was not delivered in advance
    → C4
  • Client: “You should have said it costs money first.”
    → meanings are not synchronized
    → C5

3.4 Control Ability Module

Control answers:

“At the time of occurrence, who could control the result?”

Four types:

  • Provider-Controlled
  • Client-Controlled
  • Third-Controlled
  • Force Majeure

In the case:

  • Provider: “So I added 300.”
    → Provider controls pricing action
    → Provider-Controlled
  • Client: “You should have said it costs money first.”
    → client controls whether to accept/pay if informed
    → Client-Controlled

3.5 Time Condition Module (TCM)

Time answers:

“Does time change the meaning?”

  • Natural Aging
  • Use and Wear
  • Delay Condition
  • Post-Intervention Condition
  • No Impact

In the case:

  • “I’ll install it after I install the toilet.”
  • then “that night” the invoice appears
    → immediate-type event
    → No Impact

4｜Where Does Extracted Meaning Go?

Modules determine what we can see.
The four axes determine where meaning lands.

The five modules only extract meaning; they do not directly present the final semantic leaning.
Only after projection onto the four axes can we see the concrete semantic landing situation, and then interpret the leaning of each axis.

Due to length, this will be explained in detail in Practical Guide (Part 2).

5｜Summary

As described above, ESAT first determines whether the event is BF or AF.
In the towel rack dispute, it is AF.

Then we confirm whether the core is Do-Path or Pay-Path.
Here, the key conflict is Pay-Path (who pays).

After that, ESAT uses the five modules to extract effective semantics, reducing ineffective communication and preventing escalation into emotion and confrontation.

ESAT’s goal is not to make someone “win,”
but to prevent meaning from dragging everyone down together.

Tags: , , , , , , , ,