hotlong · Oct 15, 2026 · Oct 5, 2026 · Oct 15, 2026 · Oct 15, 2026 · Oct 6, 2026
diff --git a/content/blog/ai-ontology-open-protocol/index.de.mdx b/content/blog/ai-ontology-open-protocol/index.de.mdx
@@ -3,7 +3,7 @@ title: "Enterprise-AI-Ontologie: Warum Definition und Runtime offen sein sollten
 description: "Ontology MCP wurde im Juni 2026 GA: Die Anbieter haben die Agent-Schnittstelle selbst einem offenen Protokoll überlassen. Die Definition folgt. Offen blieb allein die Runtime — dort wohnt Portabilität."
 author: ObjectStack Team
 date: 2026-06-12
-updated: 2026-10-06T10:00:00+08:00
+updated: 2026-10-15T10:00:00+08:00
 status: published
 topic: governance
 audience: business

diff --git a/content/blog/ai-ontology-open-protocol/index.es.mdx b/content/blog/ai-ontology-open-protocol/index.es.mdx
@@ -3,7 +3,7 @@ title: "Ontología para IA empresarial: por qué la definición y el runtime deb
 description: "Ontology MCP llegó a GA en junio de 2026: los proveedores entregaron la interfaz de agentes a un protocolo abierto. La definición va detrás. Solo el runtime sigue cerrado, y ahí vive la portabilidad."
 author: ObjectStack Team
 date: 2026-06-12
-updated: 2026-10-06T10:00:00+08:00
+updated: 2026-10-15T10:00:00+08:00
 status: published
 topic: governance
 audience: business

diff --git a/content/blog/ai-ontology-open-protocol/index.fr.mdx b/content/blog/ai-ontology-open-protocol/index.fr.mdx
@@ -3,7 +3,7 @@ title: "Ontologie d'entreprise : pourquoi définition et runtime doivent être o
 description: "Ontology MCP est passé en GA en juin 2026 : les éditeurs ont eux-mêmes confié l’interface agent à un protocole ouvert. La définition suit. Seul le runtime est resté fermé — or la portabilité y habite."
 author: ObjectStack Team
 date: 2026-06-12
-updated: 2026-10-06T10:00:00+08:00
+updated: 2026-10-15T10:00:00+08:00
 status: published
 topic: governance
 audience: business

diff --git a/content/blog/ai-ontology-open-protocol/index.ja.mdx b/content/blog/ai-ontology-open-protocol/index.ja.mdx
@@ -3,7 +3,7 @@ title: "企業 AI Ontology：業務定義とランタイムをともにオープ
 description: "2026 年 6 月、Ontology MCP が GA。ベンダー自身が agent インターフェースを開放プロトコルに委ねた。定義層も追随している。開かれなかったのは実行層だけだ。"
 author: ObjectStack Team
 date: 2026-06-12
-updated: 2026-10-06T10:00:00+08:00
+updated: 2026-10-15T10:00:00+08:00
 status: published
 topic: governance
 audience: business

diff --git a/content/blog/ai-ontology-open-protocol/index.ko.mdx b/content/blog/ai-ontology-open-protocol/index.ko.mdx
@@ -3,7 +3,7 @@ title: "기업 AI Ontology: 비즈니스 정의와 런타임을 모두 열어야
 description: "2026년 6월 Ontology MCP가 GA로 전환됐다. 벤더들이 스스로 agent 인터페이스를 개방 프로토콜에 넘긴 것이다. 정의 계층도 뒤따르고 있다. 열리지 않은 것은 런타임뿐이다."
 author: ObjectStack Team
 date: 2026-06-12
-updated: 2026-10-06T10:00:00+08:00
+updated: 2026-10-15T10:00:00+08:00
 status: published
 topic: governance
 audience: business

diff --git a/content/blog/ai-ontology-open-protocol/index.mdx b/content/blog/ai-ontology-open-protocol/index.mdx
@@ -3,7 +3,7 @@ title: "Enterprise AI Ontology: Why the Definition and Runtime Should Be Open"
 description: "Ontology MCP went GA in June 2026 — the vendors made the agent interface an open protocol themselves. Definitions are following. The runtime is the layer nobody opened, and that is where portability actually lives."
 author: ObjectStack Team
 date: 2026-06-12
-updated: 2026-10-06T10:00:00+08:00
+updated: 2026-10-15T10:00:00+08:00
 status: published
 topic: governance
 audience: business

diff --git a/content/blog/ai-ontology-open-protocol/index.zh-Hans.mdx b/content/blog/ai-ontology-open-protocol/index.zh-Hans.mdx
@@ -3,7 +3,7 @@ title: 企业 AI Ontology：为什么业务定义与运行时都应该开放
 description: 2026 年 6 月 Ontology MCP 正式可用：厂商自己把 agent 接口交给了开放协议，定义层也在跟进。唯独运行时没人打开——而可移植性恰恰住在那一层。
 author: ObjectStack Team
 date: 2026-06-12
-updated: 2026-10-06T10:00:00+08:00
+updated: 2026-10-15T10:00:00+08:00
 status: published
 topic: governance
 audience: business

diff --git a/content/blog/ai-ontology-open-protocol/index.zh-Hant.mdx b/content/blog/ai-ontology-open-protocol/index.zh-Hant.mdx
@@ -4,7 +4,7 @@ title: 企業 AI Ontology：為什麼業務定義與執行時都應該開放
 description: 2026 年 6 月 Ontology MCP 正式可用：廠商自己把 agent 介面交給了開放協議，定義層也在跟進。唯獨執行時沒人開啟——而可移植性恰恰住在那一層。
 author: ObjectStack Team
 date: 2026-06-12
-updated: 2026-10-06T10:00:00+08:00
+updated: 2026-10-15T10:00:00+08:00
 status: published
 topic: governance
 audience: business

diff --git a/content/blog/ai-wrote-your-app-dare-to-merge/index.de.mdx b/content/blog/ai-wrote-your-app-dare-to-merge/index.de.mdx
@@ -3,7 +3,7 @@ title: "Nachdem KI die App geschrieben hat: Können Sie das Diff prüfen und mer
 description: "KI kann schnell eine lauffähige App erzeugen, und CI kann grün sein. Die eigentliche Frage ist, wer einen großen PR verantwortet, den niemand vollständig versteht."
 author: ObjectStack Team
 date: 2026-06-16T18:30:00+08:00
-updated: 2026-10-06T10:00:00+08:00
+updated: 2026-10-15T10:00:00+08:00
 status: published
 topic: app-building
 audience: developer

diff --git a/content/blog/ai-wrote-your-app-dare-to-merge/index.es.mdx b/content/blog/ai-wrote-your-app-dare-to-merge/index.es.mdx
@@ -3,7 +3,7 @@ title: "Después de que la IA escribe la app: ¿puedes revisar el diff y hacer M
 description: "La IA puede generar rápido una app que funciona y pasar CI. La pregunta real es quién puede responsabilizarse de un PR grande que nadie entiende por completo."
 author: ObjectStack Team
 date: 2026-06-16T18:30:00+08:00
-updated: 2026-10-06T10:00:00+08:00
+updated: 2026-10-15T10:00:00+08:00
 status: published
 topic: app-building
 audience: developer

diff --git a/content/blog/ai-wrote-your-app-dare-to-merge/index.fr.mdx b/content/blog/ai-wrote-your-app-dare-to-merge/index.fr.mdx
@@ -3,7 +3,7 @@ title: "Après que l'IA écrit l'application : pouvez-vous relire le diff et mer
 description: "L'IA peut générer vite une app qui fonctionne et passer la CI. La vraie question est de savoir qui peut assumer une grosse PR que personne ne comprend entièrement."
 author: ObjectStack Team
 date: 2026-06-16T18:30:00+08:00
-updated: 2026-10-06T10:00:00+08:00
+updated: 2026-10-15T10:00:00+08:00
 status: published
 topic: app-building
 audience: developer

diff --git a/content/blog/ai-wrote-your-app-dare-to-merge/index.ja.mdx b/content/blog/ai-wrote-your-app-dare-to-merge/index.ja.mdx
@@ -3,7 +3,7 @@ title: "AI がアプリを書いたあと：その diff をレビューして Me
 description: "AI は動くアプリをすばやく生成でき、CI も通るかもしれない。本当の問題は、誰も全体を理解していない大きな PR に、誰が責任を持って Merge できるかだ。"
 author: ObjectStack Team
 date: 2026-06-16T18:30:00+08:00
-updated: 2026-10-06T10:00:00+08:00
+updated: 2026-10-15T10:00:00+08:00
 status: published
 topic: app-building
 audience: developer

diff --git a/content/blog/ai-wrote-your-app-dare-to-merge/index.ko.mdx b/content/blog/ai-wrote-your-app-dare-to-merge/index.ko.mdx
@@ -3,7 +3,7 @@ title: "AI가 앱을 쓴 뒤: 그 diff를 리뷰하고 Merge할 수 있는가"
 description: "AI는 돌아가는 앱을 빠르게 생성하고 CI도 통과할 수 있다. 진짜 문제는 아무도 전체를 이해하지 못하는 큰 PR에 누가 책임지고 Merge할 수 있느냐다."
 author: ObjectStack Team
 date: 2026-06-16T18:30:00+08:00
-updated: 2026-10-06T10:00:00+08:00
+updated: 2026-10-15T10:00:00+08:00
 status: published
 topic: app-building
 audience: developer

diff --git a/content/blog/ai-wrote-your-app-dare-to-merge/index.mdx b/content/blog/ai-wrote-your-app-dare-to-merge/index.mdx
@@ -3,7 +3,7 @@ title: "AI-Written Apps: Can You Review the Diff and Merge With Confidence?"
 description: "AI can generate a working app in 30 minutes. The hard part is signing off on an 8,000-line PR you did not write. Reviewability, not speed, is the new moat."
 author: ObjectStack Team
 date: 2026-06-16T18:30:00+08:00
-updated: 2026-10-06T10:00:00+08:00
+updated: 2026-10-15T10:00:00+08:00
 status: published
 topic: app-building
 audience: developer

diff --git a/content/blog/ai-wrote-your-app-dare-to-merge/index.zh-Hans.mdx b/content/blog/ai-wrote-your-app-dare-to-merge/index.zh-Hans.mdx
@@ -3,7 +3,7 @@ title: AI 写完应用之后：你敢审查 diff 并点 Merge 吗？
 description: AI 可以很快生成能跑的应用，CI 也可能全绿。真正的问题是：那份几千行、没人完整理解的 PR，谁敢负责合并？当写代码被自动化，瓶颈就从“写”转向“审查与签字”。
 author: ObjectStack Team
 date: 2026-06-16T18:30:00+08:00
-updated: 2026-10-06T10:00:00+08:00
+updated: 2026-10-15T10:00:00+08:00
 status: published
 topic: app-building
 audience: developer

diff --git a/content/blog/ai-wrote-your-app-dare-to-merge/index.zh-Hant.mdx b/content/blog/ai-wrote-your-app-dare-to-merge/index.zh-Hant.mdx
@@ -4,7 +4,7 @@ title: AI 寫完應用之後：你敢審查 diff 並點 Merge 嗎？
 description: AI 可以很快生成能跑的應用，CI 也可能全綠。真正的問題是：那份幾千行、沒人完整理解的 PR，誰敢負責合併？當寫程式碼被自動化，瓶頸就從“寫”轉向“審查與簽字”。
 author: ObjectStack Team
 date: 2026-06-16T18:30:00+08:00
-updated: 2026-10-06T10:00:00+08:00
+updated: 2026-10-15T10:00:00+08:00
 status: published
 topic: app-building
 audience: developer

diff --git a/content/blog/beyond-agentforce-copilot-open-runtime/index.de.mdx b/content/blog/beyond-agentforce-copilot-open-runtime/index.de.mdx
@@ -3,7 +3,7 @@ title: "Agentforce oder Copilot Studio: Wann eine offene Self-Hosted-Runtime pas
 author: ObjectStack Team
 description: "Ein Unternehmen hätte fast Agentforce unterschrieben — bis es merkte, dass die Plattform die halben Daten außerhalb der Mauer nicht erreicht. Wann die geschlossene Suite, wann offen-self-hosted — und warum „beides“ oft gewinnt."
 date: 2026-06-16T11:00:00+08:00
-updated: 2026-10-06T10:00:00+08:00
+updated: 2026-10-15T10:00:00+08:00
 status: published
 topic: ai-agents
 audience: it

diff --git a/content/blog/beyond-agentforce-copilot-open-runtime/index.es.mdx b/content/blog/beyond-agentforce-copilot-open-runtime/index.es.mdx
@@ -3,7 +3,7 @@ title: "Más allá de Agentforce y Copilot Studio: cuándo elegir un runtime abi
 author: ObjectStack Team
 description: "Una empresa estuvo a punto de firmar Agentforce, hasta descubrir que no alcanzaba la mitad de sus datos fuera del muro. Cuándo elegir la suite cerrada, cuándo el runtime abierto y autoalojado, y por qué «usar los dos» suele ganar."
 date: 2026-06-16T11:00:00+08:00
-updated: 2026-10-06T10:00:00+08:00
+updated: 2026-10-15T10:00:00+08:00
 status: published
 topic: ai-agents
 audience: it

diff --git a/content/blog/beyond-agentforce-copilot-open-runtime/index.fr.mdx b/content/blog/beyond-agentforce-copilot-open-runtime/index.fr.mdx
@@ -3,7 +3,7 @@ title: "Au-delà d'Agentforce et Copilot Studio : quand choisir un runtime ouver
 author: ObjectStack Team
 description: "Une entreprise a failli signer Agentforce — avant de voir qu'il n'atteignait pas la moitié de ses données hors les murs. Quand choisir une suite fermée, quand l'ouvert auto-hébergé, et pourquoi « les deux » l'emporte souvent."
 date: 2026-06-16T11:00:00+08:00
-updated: 2026-10-06T10:00:00+08:00
+updated: 2026-10-15T10:00:00+08:00
 status: published
 topic: ai-agents
 audience: it

diff --git a/content/blog/beyond-agentforce-copilot-open-runtime/index.ja.mdx b/content/blog/beyond-agentforce-copilot-open-runtime/index.ja.mdx
@@ -3,7 +3,7 @@ title: "Agentforce、Copilot Studio の先へ:なぜ一部の企業はオープ
 author: ObjectStack Team
 description: "Agentforce や Copilot Studio は自社エコシステム内で強い。だがデータ、権限、モデル選択が複数システムにまたがる企業では、オープンでセルフホスト可能なランタイムも比較軸になる。"
 date: 2026-06-16T11:00:00+08:00
-updated: 2026-10-06T10:00:00+08:00
+updated: 2026-10-15T10:00:00+08:00
 status: published
 topic: ai-agents
 audience: it

diff --git a/content/blog/beyond-agentforce-copilot-open-runtime/index.ko.mdx b/content/blog/beyond-agentforce-copilot-open-runtime/index.ko.mdx
@@ -3,7 +3,7 @@ title: "Agentforce, Copilot Studio 너머: 왜 어떤 기업은 개방형, 셀
 author: ObjectStack Team
 description: "한 회사가 Agentforce에 서명하기 직전, 벽 바깥에 있는 데이터 절반에 닿지 못한다는 사실을 발견했다. 닫힌 스위트와 열린 셀프 호스팅 런타임을 정직하게 비교하고, 언제 무엇을 고를지 — 그리고 왜 '둘 다 쓰기'가 정답일 때가 많은지 짚는다."
 date: 2026-06-16T11:00:00+08:00
-updated: 2026-10-06T10:00:00+08:00
+updated: 2026-10-15T10:00:00+08:00
 status: published
 topic: ai-agents
 audience: it

diff --git a/content/blog/beyond-agentforce-copilot-open-runtime/index.mdx b/content/blog/beyond-agentforce-copilot-open-runtime/index.mdx
@@ -3,7 +3,7 @@ title: "Agentforce vs. an Open Self-Hosted Runtime: When to Choose Each"
 author: ObjectStack Team
 description: "A company nearly signed with Agentforce until it found that half its data lived outside the suite. Here is when to choose a closed suite, when to choose open self-hosting, and when to use both."
 date: 2026-06-16T11:00:00+08:00
-updated: 2026-10-06T10:00:00+08:00
+updated: 2026-10-15T10:00:00+08:00
 status: published
 topic: ai-agents
 audience: it

diff --git a/content/blog/beyond-agentforce-copilot-open-runtime/index.zh-Hans.mdx b/content/blog/beyond-agentforce-copilot-open-runtime/index.zh-Hans.mdx
@@ -3,7 +3,7 @@ title: Agentforce、Copilot Studio 之外：何时选择开放自托管运行时
 author: ObjectStack Team
 description: Agentforce、Copilot Studio、ServiceNow AI Agents 在各自生态内都很强。问题是你的数据、流程和权限是否也在同一个生态内；若不是，开放自托管运行时或混合架构可能更稳。
 date: 2026-06-16T11:00:00+08:00
-updated: 2026-10-06T10:00:00+08:00
+updated: 2026-10-15T10:00:00+08:00
 status: published
 topic: ai-agents
 audience: it

diff --git a/content/blog/beyond-agentforce-copilot-open-runtime/index.zh-Hant.mdx b/content/blog/beyond-agentforce-copilot-open-runtime/index.zh-Hant.mdx
@@ -4,7 +4,7 @@ title: Agentforce、Copilot Studio 之外：何時選擇開放自託管執行時
 author: ObjectStack Team
 description: Agentforce、Copilot Studio、ServiceNow AI Agents 在各自生態內都很強。問題是你的資料、流程和權限是否也在同一個生態內；若不是，開放自託管執行時或混合架構可能更穩。
 date: 2026-06-16T11:00:00+08:00
-updated: 2026-10-06T10:00:00+08:00
+updated: 2026-10-15T10:00:00+08:00
 status: published
 topic: ai-agents
 audience: it

diff --git a/content/blog/context-bottleneck-read-half/index.mdx b/content/blog/context-bottleneck-read-half/index.mdx
@@ -3,7 +3,7 @@ title: "Context Is the Bottleneck in Enterprise AI: Every Fix Solves Only the Re
 description: "Two of the largest data platforms built their June 2026 keynotes around the same claim, and it is correct. But semantic layers, catalogs and ontologies all ground what an agent reads. The write half runs on borrowed enforcement."
 author: ObjectStack Team
 date: 2026-08-31T10:00:00+08:00
-updated: 2026-10-06T10:00:00+08:00
+updated: 2026-10-15T10:00:00+08:00
 status: published
 topic: ai-agents
 audience: it

diff --git a/content/blog/enterprise-agent-true-cost/index.de.mdx b/content/blog/enterprise-agent-true-cost/index.de.mdx
@@ -3,7 +3,7 @@ title: "AI-Agent-Kosten: Aktionspreise und Self-Hosting-Laufzeitkosten vergleich
 description: "Aktions- oder Token-Preise wirken flexibel, doch je autonomer ein Agent wird, desto mehr Tool-Aufrufe entstehen. Kosten müssen mit Nutzungsprofil, Datenabfluss, Lock-in und Betriebsmodell gerechnet werden."
 author: ObjectStack Team
 date: 2026-06-16T12:00:00+08:00
-updated: 2026-10-06T10:00:00+08:00
+updated: 2026-10-15T10:00:00+08:00
 status: published
 topic: governance
 audience: business

diff --git a/content/blog/enterprise-agent-true-cost/index.es.mdx b/content/blog/enterprise-agent-true-cost/index.es.mdx
@@ -3,7 +3,7 @@ title: "Coste de AI Agents: comparar precio por acción y runtime autoalojado"
 description: "El cobro por acción o por token parece flexible, pero cuanto más autónomo es un agent, más llamadas a herramientas produce. El coste debe verse junto a uso, salida de datos, lock-in y operación propia."
 author: ObjectStack Team
 date: 2026-06-16T12:00:00+08:00
-updated: 2026-10-06T10:00:00+08:00
+updated: 2026-10-15T10:00:00+08:00
 status: published
 topic: governance
 audience: business

diff --git a/content/blog/enterprise-agent-true-cost/index.fr.mdx b/content/blog/enterprise-agent-true-cost/index.fr.mdx
@@ -3,7 +3,7 @@ title: "Coût des agents IA : comparer prix par action et runtime auto-hébergé
 description: "La facturation par action ou par token semble flexible, mais plus un agent devient autonome, plus il appelle d'outils. Le coût doit être lu avec usage, sortie de données, lock-in et exploitation propre."
 author: ObjectStack Team
 date: 2026-06-16T12:00:00+08:00
-updated: 2026-10-06T10:00:00+08:00
+updated: 2026-10-15T10:00:00+08:00
 status: published
 topic: governance
 audience: business

diff --git a/content/blog/enterprise-agent-true-cost/index.ja.mdx b/content/blog/enterprise-agent-true-cost/index.ja.mdx
@@ -3,7 +3,7 @@ title: "AI Agent の料金：アクション課金とセルフホスト実行コ
 description: "アクション単位や token 単位の課金は柔軟に見えるが、agent が自律的になるほどツール呼び出しは増える。コストは使用量曲線、データ域外、ロックイン、自社運用の分岐点を一緒に見る必要がある。"
 author: ObjectStack Team
 date: 2026-06-16T12:00:00+08:00
-updated: 2026-10-06T10:00:00+08:00
+updated: 2026-10-15T10:00:00+08:00
 status: published
 topic: governance
 audience: business

diff --git a/content/blog/enterprise-agent-true-cost/index.ko.mdx b/content/blog/enterprise-agent-true-cost/index.ko.mdx
@@ -3,7 +3,7 @@ title: "AI Agent 가격: 동작당 과금과 셀프 호스팅 실행 비용"
 description: "동작 단위나 token 단위 과금은 유연해 보이지만, agent가 자율적일수록 도구 호출은 늘어난다. 비용은 사용량 곡선, 데이터 반출, 락인, 자체 운영의 분기점을 함께 봐야 한다."
 author: ObjectStack Team
 date: 2026-06-16T12:00:00+08:00
-updated: 2026-10-06T10:00:00+08:00
+updated: 2026-10-15T10:00:00+08:00
 status: published
 topic: governance
 audience: business

diff --git a/content/blog/enterprise-agent-true-cost/index.mdx b/content/blog/enterprise-agent-true-cost/index.mdx
@@ -3,7 +3,7 @@ title: "AI Agent Pricing: Per-Action Billing vs. Self-Hosted Runtime Cost"
 description: "At $0.10 per Agentforce action, a successful agent can make usage-based pricing rise quickly. Compare per-action billing with a self-hosted runtime before you scale."
 author: ObjectStack Team
 date: 2026-06-16T12:00:00+08:00
-updated: 2026-10-06T10:00:00+08:00
+updated: 2026-10-15T10:00:00+08:00
 status: published
 topic: governance
 audience: business

diff --git a/content/blog/enterprise-agent-true-cost/index.zh-Hans.mdx b/content/blog/enterprise-agent-true-cost/index.zh-Hans.mdx
@@ -3,7 +3,7 @@ title: AI Agent 定价：按动作计费与自托管运行时成本
 description: 按动作或按 token 计费看起来灵活，但 agent 越自主，中间工具调用越多。真正的成本账要同时看用量曲线、数据出域、平台锁定，以及什么时候自托管才划算。
 author: ObjectStack Team
 date: 2026-06-16T12:00:00+08:00
-updated: 2026-10-06T10:00:00+08:00
+updated: 2026-10-15T10:00:00+08:00
 status: published
 topic: governance
 audience: business

diff --git a/content/blog/enterprise-agent-true-cost/index.zh-Hant.mdx b/content/blog/enterprise-agent-true-cost/index.zh-Hant.mdx
@@ -4,7 +4,7 @@ title: AI Agent 定價：按動作計費與自託管執行時成本
 description: 按動作或按 token 計費看起來靈活，但 agent 越自主，中間工具呼叫越多。真正的成本賬要同時看用量曲線、資料出域、平臺鎖定，以及什麼時候自託管才划算。
 author: ObjectStack Team
 date: 2026-06-16T12:00:00+08:00
-updated: 2026-10-06T10:00:00+08:00
+updated: 2026-10-15T10:00:00+08:00
 status: published
 topic: governance
 audience: business

diff --git a/content/blog/enterprise-ontology-race-open-vs-closed/index.de.mdx b/content/blog/enterprise-ontology-race-open-vs-closed/index.de.mdx
@@ -3,7 +3,7 @@ title: "Offene Unternehmens-Ontologie: Wem sollte die semantische Geschäftsschi
 description: "Zwischen Nov. 2025 und Aug. 2026 haben fünf Plattformen eine semantische Geschäftsschicht ausgeliefert und meist einen MCP-Lesepfad geöffnet — die Definition blieb drinnen. Protokoll offen, Definition geschlossen."
 author: ObjectStack Team
 date: 2026-06-16T17:00:00+08:00
-updated: 2026-10-06T10:00:00+08:00
+updated: 2026-10-15T10:00:00+08:00
 status: published
 topic: governance
 audience: business

diff --git a/content/blog/enterprise-ontology-race-open-vs-closed/index.es.mdx b/content/blog/enterprise-ontology-race-open-vs-closed/index.es.mdx
@@ -3,7 +3,7 @@ title: "Ontología empresarial abierta: quién debería poseer la capa semántic
 description: "Entre nov. 2025 y ago. 2026 cinco plataformas lanzaron una capa semántica de negocio y la mayoría abrió una vía de lectura por MCP, dejando dentro la definición. Protocolo abierto, definición cerrada."
 author: ObjectStack Team
 date: 2026-06-16T17:00:00+08:00
-updated: 2026-10-06T10:00:00+08:00
+updated: 2026-10-15T10:00:00+08:00
 status: published
 topic: governance
 audience: business

diff --git a/content/blog/enterprise-ontology-race-open-vs-closed/index.fr.mdx b/content/blog/enterprise-ontology-race-open-vs-closed/index.fr.mdx
@@ -3,7 +3,7 @@ title: "Ontologie d'entreprise ouverte : qui doit posséder la couche sémantiqu
 description: "Entre nov. 2025 et août 2026, cinq plateformes ont livré une couche sémantique métier et la plupart ont ouvert une voie de lecture MCP, en gardant la définition à l'intérieur. Protocole ouvert, définition fermée."
 author: ObjectStack Team
 date: 2026-06-16T17:00:00+08:00
-updated: 2026-10-06T10:00:00+08:00
+updated: 2026-10-15T10:00:00+08:00
 status: published
 topic: governance
 audience: business

diff --git a/content/blog/enterprise-ontology-race-open-vs-closed/index.ja.mdx b/content/blog/enterprise-ontology-race-open-vs-closed/index.ja.mdx
@@ -3,7 +3,7 @@ title: "オープンな企業オントロジー：業務セマンティックレ
 description: "2025年11月から2026年8月にかけて5つのプラットフォームが業務セマンティックレイヤーを投入し、その多くが MCP の読み取り経路を開放した。だが定義そのものは内部に残る。プロトコルは開放、定義は封鎖——所有権の問いはより鋭くなった。"
 author: ObjectStack Team
 date: 2026-06-16T17:00:00+08:00
-updated: 2026-10-06T10:00:00+08:00
+updated: 2026-10-15T10:00:00+08:00
 status: published
 topic: governance
 audience: business

diff --git a/content/blog/enterprise-ontology-race-open-vs-closed/index.ko.mdx b/content/blog/enterprise-ontology-race-open-vs-closed/index.ko.mdx
@@ -3,7 +3,7 @@ title: "열린 기업 온톨로지: 비즈니스 의미 계층은 누가 소유
 description: "2025년 11월부터 2026년 8월까지 다섯 플랫폼이 비즈니스 의미 계층을 출시했고, 대부분 MCP 읽기 경로를 열었다. 그러나 정의 자체는 안에 남는다. 프로토콜은 열리고 정의는 닫혔다 — 소유권 질문은 더 날카로워졌다."
 author: ObjectStack Team
 date: 2026-06-16T17:00:00+08:00
-updated: 2026-10-06T10:00:00+08:00
+updated: 2026-10-15T10:00:00+08:00
 status: published
 topic: governance
 audience: business

diff --git a/content/blog/enterprise-ontology-race-open-vs-closed/index.mdx b/content/blog/enterprise-ontology-race-open-vs-closed/index.mdx
@@ -3,7 +3,7 @@ title: "Open vs. Closed Enterprise Ontologies: Who Owns the Business Semantic La
 description: "Five platforms shipped a business semantic layer between Nov 2025 and Aug 2026, and most opened an MCP read path while keeping the definition inside. Protocol-open, definition-closed — and the ownership question got sharper."
 author: ObjectStack Team
 date: 2026-06-16T17:00:00+08:00
-updated: 2026-10-06T10:00:00+08:00
+updated: 2026-10-15T10:00:00+08:00
 status: published
 topic: governance
 audience: business