SPCT（Spatial Planning & Capacity Theory，空間規劃與尺寸理論）是一套「尺寸語意整理」與「衝突標註」系統
它不提供設計方法、不給配置建議
它只把自然語句中的尺寸，放回可追溯的語意位置，並在語意地圖（SM）中標示是否成立、是否衝突
本篇為 SPCT ENGINE v3.0 的定義篇
只鎖定 Public Semantic Layer（公開語意層） 的名詞定義與名詞之間的固定關係
不包含任何流程、優先序以外的推導、或可被視為演算法的描述
1｜法律與 BFS 最優先級
1.1 法規優先（Regulatory Priority）
法規優先是 SPCT 的外部邊界條件
任何違反當地現行法規之配置，一律視為不成立
SPCT 不讀法規、不解釋法條、不提供法律意見
SPCT 只允許輸出「需要由 SDP 進行適法性複查」之提示，該提示在結果層中歸入 RL（Regulatory Layer）
1.2 BFS 絕對優先級（BFS Absolute Priority）
**BFS（Basic Framework Size）**是建築不可更動的基礎框架邊界
任何尺寸語意只要與 BFS 衝突，一律不成立
BFS 的優先序高於 AVS／OBS／SUS 以及所有外掛模組
BFS 改變代表建築本體變更，視為全新 BFS，必須重新執行整張 SPCT
2｜三大空間（3+1 Space Categories）
SPCT 要求 SDP（空間決策者）在使用前先宣告空間類型
因為同一尺寸語意在不同空間類型下，其常態性與使用情境可能不同
此差異只影響 SDP 的輸入與決策，不改寫 SPCT 的衝突定義
空間類型為 3+1：
- OFF：Office
- HOM：Home
- SHP：Shop
- CUS：Custom（由外掛導入）
SPCT 本體只定義尺寸語意架構
各空間類型的家具設備清單與尺寸資料庫，屬外掛責任
3｜兩個最小語意（Minimal Semantics）
SPCT 的最小語意單元只有兩個
- 物體本體尺寸（Object Body Size）
- 使用空間最小尺寸（Space-Use Minimum Size）
所有空間語句中的尺寸，最終都必須回到這兩種語意
SPCT 的四大模塊（BFS／AVS／OBS／SUS）是上述最小語意在不同語意角色下的歸屬與升格。
「歸屬與升格」僅描述語意角色對應關係，不構成步驟、流程或推導。
4｜四大模塊（BFS／AVS／OBS／SUS）
四大模塊的目的不是複雜化
而是讓「衝突可以追溯到明確的語意來源」，並對應到可重跑的輸入入口（RESET）
4.1 BFS（Basic Framework Size｜基礎框架尺寸）
BFS是不可移動、不可壓縮、不可任意更改的建築框架邊界
包含但不限於：
- 結構牆／剪力牆／梁柱／外牆
- 建築主體固定容積
- 主排水路線／主要管道位置
- 電箱／弱電箱位置
- 建築主要出入口
- 樓板（天花）與地板高程（v3.0 納入）
BFS 的語意特性：
- 不可被 AVS／OBS／SUS 的任何調整行為改變
- 任何超出 BFS 的尺寸語意（不論來自 AVS／OBS／SUS）一律不成立
- BFS 是「邊界框架」與「可投影之尺寸語意」
- BFS 不在其內部新增「本體尺寸」與「最小使用空間」的拆分欄位，以保持邊界語意純度
補充：地板高程可使「門的使用空間最小尺寸」失效（例如刮地、門檻、落差）
其成立/不成立仍指回 BFS／AVS 的邊界語意條件
4.2 AVS（Adjustable Volume Size｜可調容積尺寸）
AVS是可調整的內部容積邊界
例如：
- 可拆移分間牆
- 天花與包梁包柱
- 非結構性矮牆
- 可重畫的房間範圍
- 房間門之邊界性構件（門洞、門框等）（v3.0 明確納入）
AVS 的語意特性：
- 可由 SDP 調整位置與範圍
- 不得與 BFS 衝突，否則 AVS 不成立
- AVS 調整時需 RESET，重新計算所有模塊的落點
- AVS 不具內建優先序（除 BFS 絕對優先外）
- AVS 不在其內部新增「本體尺寸」與「最小使用空間」的拆分欄位，以保持邊界語意純度
4.3 OBS（Object Size｜物件本體尺寸）
OBS 描述物件所對應之本體尺寸，並承載「物體本體尺寸」作為其語意來源。
包含家具、櫃體、設備
人體與寵物在 FA 軸的投影中可被視為 OBS。
OBS 的語意特性：
- 若 BFS／AVS 無法容納 OBS，除人體與寵物外，OBS 必須被修改或更換
- 可移動與否不由 OBS 決定，而由投影軸決定
- 投影於 FX → 固定 OBS
- 投影於 MA → 可移動 OBS
多態存在（Multi-State Existence）
同一物件可具有多種狀態（展開／收合等）
其處理方式：
- 視為同一物件的多狀態語意
- 每一狀態各自具有對應 OBS 與 SUS 的落點需求
- 多狀態可投影於同一位置（因現實中不會同時存在），不視為兩物件 OBS 衝突
4.4 SUS（Space-Use Size｜使用空間尺寸）
「使用空間最小尺寸」為最小語意，SUS 為其在四大模塊中的語意角色名稱， SUS 描述行為所對應之使用空間需求，並承載「使用空間最小尺寸」作為其成立門檻。
例如：
- 開門／關門擺動空間
- 抽屜外拉退縮空間
- 坐下、起身、轉身所需空間
- 站立操作空間（廚房等）
- 維修與檢查設備可達空間
- 搬運迴轉半徑（板車／輪椅／娃娃車）
SUS 的語意特性：
- 具有最小尺寸門檻：低於門檻即視為該 SUS 不成立
- SUS 可與 AVS／OBS 在平面上重疊，但不得被壓縮至低於門檻
- SUS 只在行為發生時存在，不代表持續占用，但必須可被預留
- 不同 SDP 可對同一 OBS 設定不同 SUS，屬輸入差異，SPCT 不評價
4.5 門（Door）的歸屬規則（v3.0）
門為跨語意存在體，但在 SPCT 中統一歸入「邊界語意」處理：
- 門洞／門框之邊界性 → BFS／AVS
- 門相關落點在語意地圖上統一指回 BFS／AVS
- 不對 BFS／AVS 內新增「門本體尺寸／門使用空間」拆分欄位
- 門的使用性若受地板高程、門檻、落差影響，仍屬 BFS／AVS 邊界語意導致之成立/不成立條件，由 SDP 回溯判讀
5｜三軸投影（FA／FX／MA）
5.1 三軸定位（不是分類）
FA／FX／MA 不是物件分類法
而是描述尺寸語意在空間中的存在方式：
- 位置保持變動 → FA
- 位置不能動 → FX
- 位置可移動可不移動 → MA
同一物件可跨軸投影
跨軸投影只代表同一組尺寸語意在不同存在狀態下被觀測
不生成新物件、不複製尺寸、不新增語意來源
5.2 三軸覆蓋率（Coverage = 100%）
所有出現在室內空間中的尺寸語意，無例外必然投影於 FA／FX／MA 其中之一
三軸覆蓋率為 100%，不存在落點缺口
5.3 三軸互不干涉（v3.0）
FA／FX／MA 為三套相互獨立的投影運算：
- 各軸不得傳遞資訊
- 各軸不得互相影響
- 三軸投影階段只負責落點與存在方式
- 投影階段不得做衝突判定
本篇僅鎖定衝突判定的語意位置，不描述任何運算方式。
5.4 共同投影原則（2D 與高度）
SPCT 語意地圖以二維平面呈現三軸落點關係
若平面重疊但高度不干涉，視為合法重疊（不標記 CV）
若高度干涉，屬 CV（垂直衝突）
5.5 FA（Flow Axis｜動線軸）
FA 描述移動、通行、到達、搬運相關尺寸語意
人體／寵物在 FA 軸的投影中可被視為 OBS
行走、轉身、通行等行為需求在 FA 軸的投影中可被視為 SUS
5.6 FX（Fixed Axis｜固定軸）
FX 描述安裝後位置不變的固定存在
例如固定櫃體、壁櫃、流理台、洗手台、衛浴設備、內嵌式設備位置
FX 的語意規則：
- FX-OBS 原則上不允許兩固定存在在同一位置同時占用
- 例外：多態存在之多狀態可投影同點
- FX-SUS 描述使用固定存在時所需的最小空間（開門、站立、操作等）
5.7 MA（Mobile Axis｜可移動軸）
MA 描述可被移動、調整位置的物件與其使用語意
例如沙發、茶几、桌椅、推車、輕量家電（除濕機、空氣清淨機等）
MA 的語意規則：
- MA 只描述可移動性
- 同一位置落點重疊是否能透過時序性移動被接受，由 SDP 決定
- MA 軸本身不判定可否接受（接受行為在 CACC）
本篇僅指出接受與否由 SDP 決定，不描述任何接受方式或調整方法。
5.8 同一位置重複投影
重複投影是指向不同觀測視角
不是生成、不是複製、不是新增語意
例外只有多態存在：同一物件多狀態語意
6｜語意地圖（SM｜Semantic Map）
6.1 語意地圖的定位
語意地圖（SM）是 SPCT 的最終且唯一產物
它不是平面配置建議圖、不是最佳化結果、不是碰撞檢測的替代品
SM 必須同時保留：
- 尺寸語意來源：BFS／AVS／OBS／SUS
- 存在方式投影：FA／FX／MA
目的在於確保衝突可追溯、可重跑、可供 SDP 決策
6.2 語意地圖的內容（必備輸出項）
SM 包含：
- BFS 框架邊界（含樓板/天花與地板高程）
- AVS 可調邊界（含門之邊界歸屬）
- OBS 本體尺寸落點
- SUS 使用空間最小尺寸投影
- 三軸投影落點（FA／FX／MA）
- 衝突標示（CP／CV）
- SDP 接受衝突標示（CACC）
- 未被 SDP 接受者以 CP／CV 呈現（即 CREQ 的公共呈現方式）
7｜衝突（CP／CV／CACC／CREQ）
本篇所稱「成立／不成立」僅指尺寸語意在語意地圖（SM）中的成立狀態，不包含舒適度、美感、成本、風險或法規判定。
7.1 衝突判定時機（核心鎖定）
衝突判定只允許在語意地圖整合後發生
三軸投影階段不進行衝突判定
7.2 衝突一句話定義
衝突是：多組尺寸語意在同一語意地圖中無法同時成立的狀態
衝突不是不舒服、不是不美、不是風險預測
衝突只表示本體尺寸或使用空間最小尺寸在語意地圖上常態性、持續性、必然地發生重疊，因而無法共存
7.3 CP／CV
- CP（Conflict Planar）：平面上無法共存
- CV（Conflict Vertical）：高度方向互相干涉
和諧狀態不標註
「不成立」可由 BFS 絕對優先級直接造成；「CP／CV」為語意地圖整合後之衝突標註，兩者為不同語意層級。
7.4 常態性／持續性條件
SPCT 只標註常態性、持續性衝突
偶發、瞬間、可預期的事件不構成 SPCT 的衝突標註條件
7.5 CACC／CREQ
- CACC（Conflict Accepted）：SDP 知道此處為 CP／CV，但選擇接受
CP／CV 本質不會因此消失 - CREQ（Conflict Requires Adjustment）：未被 SDP 標為 CACC 的 CP／CV
CREQ 不新增新的衝突類型，不替代 CP／CV
CACC 為 SDP 的狀態標記，獨立於三軸投影本身，不構成任何軸的判定規則。
8｜五大結果描述層（CL／AL／UL／FL／RL）× RESET
8.1 描述層總則
五層都不得修改 CP／CV，也不得修改語意地圖
描述層唯一能做的是協助 SDP 決定是否 RESET
8.2 五層定義
- CL（Comfort Layer）：人體舒適度描述，不提供人體工學數值，不背書任何判準
- AL（Aesthetic Layer）：美感／視覺心理描述，不背書任何美學框架，含 SDT
- UL（Usage Layer）：使用頻率／生活強度描述，只描述頻率，不輸出優先順序，不改寫衝突定義
- FL（Folk & Culture Layer）：文化／風水心理描述，選配外掛描述層，含文公尺
- RL（Regulatory Layer）：適法性複查描述，SPCT 不讀法規；若 SDP 判定違法 → 強制 RESET
8.3 RESET（重啟）
RESET 是否發生由 SDP 決定（唯 RL 違法狀態必須 RESET）
- 改 BFS → 等同換框架，必須重跑整張 SPCT
- 改 AVS → 必須重跑整張 SPCT
- 改 OBS → 可局部重跑（實作層由外掛決定）
- 改 SUS → 可局部重跑（實作層由外掛決定）
SPCT 的行為只有：再跑一次，再輸出一次語意地圖
RESET 僅為重啟語意標示之固定關係，不描述任何操作流程。
9｜外掛（Plugins）
SPCT 不產出平面配置圖或立面櫃體圖
SPCT 的唯一輸出為語意地圖（落點與衝突狀態）
SDP 可外掛：
- 空間功能清單
- OBS 尺寸資料庫（家具、設備、櫃體）
- SUS 尺寸資料庫（操作、行走、維修、搬運）
- BFS／AVS 設定工具
- 衝突後的調整優先序（外掛決策，非 SPCT 本體）
- 任何基於 SPCT 生成圖面、配置或自動設計之系統（均屬外掛責任）
外掛所產生的圖面、配置與決策責任，歸外掛系統與其使用者（SDP），不歸 SPCT 公開語意層
10｜免責宣告（Disclaimer）
SPCT 不提供任何數值、標準、比率、最佳化結論
所有尺寸由 SDP 輸入；輸入不足不推論、不補預設值
SPCT 不提供 AVS／OBS／SUS 的優先級與判斷式，只標示衝突（例外：法規與 BFS 絕對優先）
SPCT 不做工程判定、法律判定、安規檢核
SPCT 不推論使用者意圖、不推估行為模式、不推估人口與偏好
SPCT 不參與美感判斷或美感優化
SPCT 不提供最佳解、不提供方案排序、不提供替代方案
SPCT 僅顯示尺寸語意衝突，不負責解決，需由 SDP 調整並 RESET
SPCT 不參與成本與預算分析、不提供材料建議、不做報價計算
SPCT 不具法律效力，除非人類明文寫入合約
SPCT 不保證外掛資料正確性
CUS 類型空間規範由人類自行編纂外掛，SPCT 本體不負責
11｜名詞鎖定（Vocabulary Lock｜縮寫版 v3.0）
以下字彙不得任意變形，不得自創新詞替換
11.1 主要系統
SPCT／BFS／AVS／OBS／SUS
11.2 空間類型
OFF／HOM／SHP／CUS
11.3 三大投影軸
FA／FX／MA
11.4 衝突類型與狀態
CP／CV／CACC／CREQ
11.5 語意輸出
SM／語意地圖
11.6 五大結果描述層與重啟
CL／AL／UL／FL／RL／RESET
11.7 其他固定詞彙（無英文縮寫）
法規優先／絕對優先級／最小語意／物體本體尺寸／使用空間最小尺寸／基礎框架尺寸／可調容積尺寸／物件尺寸／使用空間尺寸／三軸覆蓋率／投影不是分類／重複投影／多態存在／高度差合法重疊／衝突判定時機／常態性／持續性／語意落點／語意地圖／外掛模塊／免責宣告
以下為英文翻譯版（English Version Below）
SPCT Definition｜Public Semantic Layer Vocabulary
SPCT (Spatial Planning & Capacity Theory) is a semantic system for size semantic organization and conflict annotation.
It does not provide design methods and does not provide configuration suggestions.
It only places sizes from natural language back into traceable semantic positions, and annotates on the Semantic Map (SM) whether they are established and whether they are in conflict.
This article is the Definition section of SPCT ENGINE v3.0.
It locks only the fixed term definitions and fixed relationships within the Public Semantic Layer.
It contains no Process, no derivation beyond priority, and no description that can be treated as an algorithm.
1｜Regulatory Priority and BFS Absolute Priority
1.1 Regulatory Priority
Regulatory Priority is an external boundary condition of SPCT.
Any configuration that violates local regulations is considered not established.
SPCT does not read regulations, does not interpret legal provisions, and does not provide legal opinions.
SPCT only allows an output prompt stating that a regulatory compliance review by the SDP is required, and this prompt belongs to RL (Regulatory Layer) in the Result Description Layers.
1.2 BFS Absolute Priority
BFS (Basic Framework Size) is the immutable foundational framework boundary of a building.
Any size semantic that conflicts with BFS is considered not established.
BFS has priority over AVS／OBS／SUS and all Plugin Module.
A change in BFS represents a change to the building body and is treated as a new BFS, requiring the entire SPCT to be rerun.
2｜Space Categories (3+1 Space Categories)
SPCT requires the SDP to declare the space category before use.
This is because the same size semantic may have different normalized conditions and usage contexts across different space categories.
This difference affects only the SDP’s inputs and decisions; it does not rewrite SPCT’s conflict definition.
Space categories are 3+1:
- OFF: Office
- HOM: Home
- SHP: Shop
- CUS: Custom (Plugin)
SPCT itself defines only the size semantic framework.
The furniture/equipment lists and size databases for each space category are the responsibility of Plugins.
3｜Minimal Semantics
SPCT has only two Minimal Semantics units:
- Object Body Size
- Space-Use Minimum Size
All sizes in spatial statements must ultimately be attributed back to these two Minimal Semantics.
The four core modules of SPCT (BFS／AVS／OBS／SUS) are the attribution and elevation of the above Minimal Semantics under different semantic roles.
“Attribution and elevation” describes only semantic role correspondence and does not constitute steps, Process, or derivation.
4｜Four Modules (BFS／AVS／OBS／SUS)
The purpose of the Four Modules is not to add complexity,
but to allow conflicts to be traced back to explicit semantic sources, and to correspond to rerunnable input entry points (RESET).
4.1 BFS (Basic Framework Size)
BFS is the building framework boundary that is non-movable, non-compressible, and not arbitrarily changeable.
It includes, but is not limited to:
- Structural walls / shear walls / beams and columns / exterior walls
- Fixed building body volume
- Main drainage routes / primary pipeline positions
- Electrical panel / low-voltage panel positions
- Primary building entrances and exits
- Slab/ceiling and floor elevation (included in v3.0)
Semantic characteristics of BFS:
- BFS cannot be changed by any adjustment behavior of AVS／OBS／SUS
- Any size semantic that exceeds BFS (whether from AVS／OBS／SUS) is considered not established
- BFS is both a boundary framework and a projectable size semantic
- BFS does not add internal split fields for Object Body Size and Space-Use Minimum Size, in order to preserve boundary semantic purity
Supplement: floor elevation can invalidate the Space-Use Minimum Size of Door usage (for example, scraping, thresholds, level differences).
Its established/not established state still traces back to boundary semantic conditions of BFS／AVS.
4.2 AVS (Adjustable Volume Size)
AVS is an adjustable internal volume boundary, for example:
- Removable partition walls
- Ceilings and beam/column wrapping
- Non-structural low walls
- Redrawable room boundaries
- Boundary components of room doors (Door Opening / Door Frame, explicitly included in v3.0)
Semantic characteristics of AVS:
- AVS may be adjusted in position and range by the SDP
- AVS must not conflict with BFS; otherwise AVS is considered not established
- When AVS is adjusted, RESET is required to recalculate placements for all modules
- AVS has no built-in priority (except BFS Absolute Priority)
- AVS does not add internal split fields for Object Body Size and Space-Use Minimum Size, in order to preserve boundary semantic purity
4.3 OBS (Object Size)
OBS describes the Object Body Size of an object as its semantic source.
It includes furniture, cabinetry, and equipment.
Humans and pets may be treated as OBS in FA projection.
Semantic characteristics of OBS:
- If BFS／AVS cannot contain OBS, then except for humans and pets, OBS must be modified or replaced
- Whether OBS is movable is not determined by OBS, but by the Projection Axes
- Projection to FX → fixed OBS
- Projection to MA → movable OBS
Multi-State Existence
The same object may have multiple states (expanded / folded, etc.).
Its handling is:
- Treated as multi-state semantics of the same object
- Each state has corresponding placement requirements for OBS and SUS
- Multi-state semantics may be projected to the same position (because they do not exist simultaneously in reality) and are not treated as an OBS conflict between two objects
4.4 SUS (Space-Use Size)
Space-Use Minimum Size is a Minimal Semantics unit.
SUS is its semantic role name within the Four Modules.
SUS describes the usage space requirements corresponding to behaviors, and carries Space-Use Minimum Size as its establishment threshold.
For example:
- Door opening/closing swing space
- Drawer pull-out clearance space
- Space for sitting down, standing up, turning
- Standing operation space (kitchens, etc.)
- Accessible space for maintenance and inspection
- Transport turning radius (dollies / wheelchairs / strollers)
Semantic characteristics of SUS:
- Has a minimum-size threshold: below the threshold, that SUS is considered not established
- SUS may overlap with AVS／OBS in plan, but must not be compressed below its threshold
- SUS exists only when the behavior occurs; it does not represent continuous occupation, but it must be reservable
- Different SDPs may set different SUS for the same OBS; this is an input difference and SPCT does not evaluate it
4.5 Door Semantic Attribution (v3.0)
Door is a cross-semantic entity, but in SPCT it is uniformly treated as boundary semantic attribution:
- Boundary components of Door (Door Opening / Door Frame) → BFS／AVS
- Door-related placements in the Semantic Map uniformly trace back to BFS／AVS
- No split fields for “Door Object Body Size / Door Space-Use Size” are added inside BFS／AVS
- If Door usability is affected by floor elevation, thresholds, or level differences, it still belongs to established/not established conditions caused by boundary semantics of BFS／AVS, and is to be traced and interpreted by the SDP
5｜Projection Axes (FA／FX／MA)
5.1 Axis Positioning (Not Classification)
FA／FX／MA are not an object classification system.
They describe how size semantics exist in space:
- Position remains changing → FA
- Position cannot move → FX
- Position may move or may not move → MA
The same object may be projected across axes.
Cross-axis projection only means that the same set of size semantics is observed under different existence states.
It does not generate new objects, does not duplicate sizes, and does not introduce new semantic sources.
5.2 Axis Coverage (100%)
All size semantics appearing in interior space must be projected to one of FA／FX／MA without exception.
Axis Coverage is 100% and has no placement gaps.
5.3 Non-Interference of Axes (v3.0)
FA／FX／MA are three independent projection operations:
- Axes must not transmit information
- Axes must not influence one another
- The projection phase is responsible only for placements and modes of existence
- The projection phase must not perform conflict determination
This article locks only the semantic position of conflict determination and describes no operational method.
5.4 Shared Projection Principle (2D and Height)
The SPCT Semantic Map presents axis placements in 2D plan.
If planar overlap exists without vertical interference, it is treated as Valid Overlap (no CV annotation).
If vertical interference exists, it is CV (Conflict Vertical).
5.5 FA (Flow Axis)
FA describes size semantics related to movement, passage, arrival, and transport.
Humans/pets may be treated as OBS in FA projection.
Behavior requirements such as walking, turning, and passing may be treated as SUS in FA projection.
5.6 FX (Fixed Axis)
FX describes fixed existence whose position does not change after installation, such as fixed cabinetry, wall cabinets, counters, sinks, bathroom fixtures, and embedded equipment positions.
Semantic rules of FX:
- FX-OBS does not allow two fixed existences to occupy the same position simultaneously in principle
- Exception: Multi-State Existence may be projected to the same point
- FX-SUS describes the minimum space needed to use fixed existences (Door operation, standing, operation, etc.)
5.7 MA (Mobile Axis)
MA describes movable objects and their usage semantics, such as sofas, coffee tables, tables and chairs, carts, and lightweight appliances (excluding dehumidifiers and air purifiers, etc.)
Semantic rules of MA:
- MA describes mobility only
- Whether overlap at the same placement can be accepted through temporal movement is decided by the SDP
- MA itself does not determine acceptability (acceptance behavior is in CACC)
This article only states that acceptance is decided by the SDP, and describes no acceptance method or adjustment method.
5.8 Repeated Projection at the Same Position
Repeated Projection points to different observational perspectives.
It is not generation, not duplication, and not creation of new semantics.
The only exception is Multi-State Existence as multi-state semantics of the same object.
6｜Semantic Map (SM)
6.1 Positioning of the Semantic Map
The Semantic Map (SM) is the final and only product of SPCT.
It is not a configuration recommendation, not an optimization result, and not a substitute for collision detection.
SM must simultaneously retain:
- Size semantic sources: BFS／AVS／OBS／SUS
- Existence projections: FA／FX／MA
Its purpose is to ensure that conflicts are traceable, rerunnable, and usable for SDP decision-making.
6.2 Contents of the Semantic Map (Mandatory Outputs)
SM includes:
- BFS framework boundaries (including slab/ceiling and floor elevation)
- AVS adjustable boundaries (including Door boundary attribution)
- OBS Object Size placements
- SUS Space-Use Minimum Size projections
- Projection placements on FA／FX／MA
- Conflict annotations (CP／CV)
- SDP conflict acceptance annotation (CACC)
- CP／CV presentation for those not marked as CACC (the public presentation of CREQ)
7｜Conflict (CP／CV／CACC／CREQ)
In this article, “established / not established” refers only to the establishment state of size semantics within the Semantic Map (SM).
It does not include comfort, aesthetics, cost, risk, or regulatory judgment.
7.1 Conflict Determination Timing (Core Lock)
Conflict determination is allowed only after Semantic Map integration.
No conflict determination occurs during the projection phase.
7.2 One-Sentence Conflict Definition
Conflict is the state in which multiple size semantics cannot be established simultaneously within the same Semantic Map.
Conflict is not uncomfortable, not unaesthetic, and not risk prediction.
Conflict only indicates that Object Body Size or Space-Use Minimum Size overlap in a normalized and persistent manner within the Semantic Map, and therefore cannot coexist.
7.3 CP／CV
- CP (Conflict Planar): cannot coexist in plan
- CV (Conflict Vertical): interferes in height
Harmony states are not annotated.
“Not established” may be directly caused by BFS Absolute Priority.
“CP／CV” are conflict annotations after Semantic Map integration.
They are different semantic levels.
7.4 Normalized and Persistent Conditions
SPCT annotates only normalized and persistent conflicts.
Occasional, instantaneous, or predictable events do not qualify as conflict annotation conditions in SPCT.
7.5 CACC／CREQ
- CACC (Conflict Accepted): the SDP knows the area is CP／CV and chooses to accept it
CP／CV do not disappear in essence - CREQ (Conflict Requires Adjustment): CP／CV not marked as CACC
CREQ does not create a new conflict type and does not replace CP／CV
CACC is a state marker by the SDP, independent of the Projection Axes, and does not constitute a determination rule for any axis.
8｜Result Description Layers (CL／AL／UL／FL／RL) × RESET
8.1 General Rule
None of the five layers may modify CP／CV or the Semantic Map.
The only function of the layers is to assist the SDP in deciding whether to RESET.
8.2 Definitions of the Five Layers
- CL (Comfort Layer): description of human comfort; provides no ergonomics values and endorses no criteria
- AL (Aesthetic Layer): description of aesthetics / visual psychology; endorses no aesthetic framework, including SDT
- UL (Usage Layer): description of usage frequency / life intensity; describes frequency only, provides no priority ordering, and does not rewrite the conflict definition
- FL (Folk & Culture Layer): description of culture / feng-shui psychology; an optional Plugin description layer
- RL (Regulatory Layer): description for regulatory compliance review; SPCT does not read regulations; if the SDP determines illegality → forced RESET
8.3 RESET
Whether RESET occurs is decided by the SDP (only RL illegality requires RESET).
- Modify BFS → equivalent to framework replacement; rerun entire SPCT
- Modify AVS → rerun entire SPCT
- Modify OBS → partial rerun (Plugin-defined)
- Modify SUS → partial rerun (Plugin-defined)
SPCT performs only one action: run again and output a new Semantic Map.
RESET is only a fixed relationship for restarting semantic annotations and describes no operational Process.
9｜Plugins
SPCT does not produce floor plans or elevation cabinetry drawings.
The sole output of SPCT is the Semantic Map (placements and conflict states).
The SDP may use Plugins to provide:
- Space function lists
- OBS size databases (furniture, equipment, cabinetry)
- SUS size databases (operation, walking, maintenance, transport)
- BFS／AVS configuration tools
- Post-conflict adjustment priorities (Plugin decisions, not SPCT itself)
- Any system that generates drawings, configurations, or automated design based on SPCT (Plugin responsibility)
Responsibility for drawings, configurations, and decision outputs produced by Plugins belongs to the Plugin systems and their users (SDP), not to the Public Semantic Layer of SPCT.
10｜Disclaimer
SPCT provides no values, standards, ratios, or optimization conclusions.
All sizes are input by the SDP; if inputs are insufficient, SPCT does not infer and does not supply default values.
SPCT provides no priority or decision rules for AVS／OBS／SUS and only annotates conflicts (exceptions: Regulatory Priority and BFS Absolute Priority).
SPCT performs no engineering judgment, no legal judgment, and no safety inspection.
SPCT does not infer user intent, behavior patterns, population, or preferences.
SPCT does not participate in aesthetic judgment or aesthetic optimization.
SPCT provides no optimal solution, no proposal ranking, and no alternatives.
SPCT only presents size semantic conflicts and does not solve them; adjustments must be made by the SDP and then RESET.
SPCT does not participate in cost or budget analysis, provides no material recommendations, and performs no quotation calculations.
SPCT has no legal effect unless explicitly written into a human contract.
SPCT does not guarantee Plugin data correctness.
CUS space specifications are compiled by humans via Plugins, and SPCT itself is not responsible.
11｜Vocabulary Lock (Abbreviation Edition v3.0)
The following terms must not be arbitrarily altered, and no new terms may be substituted.
11.1 Core System
SPCT／BFS／AVS／OBS／SUS
11.2 Space Categories
OFF／HOM／SHP／CUS
11.3 Projection Axes
FA／FX／MA
11.4 Conflict Types and States
CP／CV／CACC／CREQ
11.5 Semantic Output
SM／Semantic Map
11.6 Result Description Layers and RESET
CL／AL／UL／FL／RL／RESET
11.7 Other Fixed Terms (No Abbreviation)
Regulatory Priority／Absolute Priority／Minimal Semantics／Object Body Size／Space-Use Minimum Size／Basic Framework Size／Adjustable Volume Size／Object Size／Space-Use Size／Axis Coverage (100%)／Projection Is Not Classification／Repeated Projection／Multi-State Existence／Height-Based Valid Overlap／Conflict Determination Timing／Normalized Condition／Persistent Condition／Semantic Placement／Semantic Map／Plugin Module／Disclaimer