Tagged articles

runtime state

2 articles · Page 1 of 1
Data Bricklaying Diary
Data Bricklaying Diary
Sep 5, 2026 · Backend Development

Why Dynamic Ontologies Need Four Separate Governance Paths, Not One Auto-Update Button

The article argues that dynamic ontologies must route four distinct change types — terminology mapping, model evolution, runtime state, and agent negotiation — through separate governance paths with dedicated verification, release, and failure handling, rather than funneling all changes through a single auto-update mechanism, to preserve stable baselines, action contracts, and audit trails.

agent negotiationchange routingdynamic ontology
0 likes · 16 min read
Why Dynamic Ontologies Need Four Separate Governance Paths, Not One Auto-Update Button
Data Bricklaying Diary
Data Bricklaying Diary
Sep 4, 2026 · Artificial Intelligence

Dynamic Ontology: Four Change Types That Must Not Share One Auto-Update Mechanism

The article distinguishes four distinct dynamics in ontology systems — terminology mapping, model evolution, runtime state, and agent negotiation — each with separate lifecycles, authorities, and validation requirements, warning against conflating them into a single auto-update mechanism.

agent negotiationdynamic ontologyindustrial AI
0 likes · 18 min read
Dynamic Ontology: Four Change Types That Must Not Share One Auto-Update Mechanism