Local or external AI for operational data?
The model choice matters. So does every record, document passage and tool result the assistant may send to it.
Read the articleField notes
Technical articles
Practical explanations of stable identity, namespace placement, history, and relationships across operational domains.
Why a Unified Namespace matters for operational AI
Follow a cold-storage example from one reading to an evidence-based answer. Shared context makes AI useful; local processing keeps control a deliberate choice.
Read the articleHow to start with a Unified Namespace: follow one signal
Follow one furnace measurement from its source to live consumers, historical queries, and a prepared data service. A practical first step with a Unified Namespace.
Read the articleIs MQTT the same as a Unified Namespace?
MQTT moves messages. A Unified Namespace adds the shared meaning, identity, ownership, and history that let independent systems reuse them safely.
Read the articleWhen does a Unified Namespace make sense?
Use three practical questions to decide when operational data needs a shared namespace, when an API or database is enough, and what a UNS should never replace.
Read the articleThe artwork moved. Its care requirements did not.
Follow a fictional museum loan and see how movement records, environmental measurements, and care documents can meet around one stable identity without turning evidence into an automated conservation verdict.
Read the articleA mold is not its MQTT topic
Follow one injection mold through production, maintenance, and another factory, and see why a Unified Namespace must keep stable identity separate from every path used to find it.
Read the article