<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Hurukan — Blog</title><description>Hurukan is the superintelligent, agentic operating system for the sovereign enterprise: one system of action on open source, extended by agents rather than clicks.</description><link>https://hurukan.com</link><language>en</language><item><title>One identity for people and agents: who may do what</title><link>https://hurukan.com/blog/one-identity-for-people-and-agents</link><guid isPermaLink="true">https://hurukan.com/blog/one-identity-for-people-and-agents</guid><description>Agents acting under a shared service account make every action anonymous. Why an agent needs its own identity, delegated from a person, with scopes that expire.</description><pubDate>Thu, 22 Oct 2026 00:00:00 GMT</pubDate><category>identity</category><category>permissions</category><category>agents</category><category>audit trail</category><category>ontology</category></item><item><title>The live state and the record: two memories of a company operating system</title><link>https://hurukan.com/blog/the-live-state-and-the-record-two-memories-of-a-company-operating-system</link><guid isPermaLink="true">https://hurukan.com/blog/the-live-state-and-the-record-two-memories-of-a-company-operating-system</guid><description>A company operating system needs two memories: the live state modules change every second, and the record of every event, proposal and decision for the audit.</description><pubDate>Wed, 21 Oct 2026 00:00:00 GMT</pubDate><category>record</category><category>lakehouse</category><category>audit</category><category>table formats</category><category>sovereignty</category></item><item><title>An agent that writes to the ERP: the line between read and write</title><link>https://hurukan.com/blog/an-agent-that-writes-to-the-erp</link><guid isPermaLink="true">https://hurukan.com/blog/an-agent-that-writes-to-the-erp</guid><description>Reading from a system of record is cheap and safe. Writing back is where integrations fail. What has to exist before an agent may write, and where Hurukan draws its line.</description><pubDate>Tue, 20 Oct 2026 00:00:00 GMT</pubDate><category>system of record</category><category>ERP</category><category>agents</category><category>idempotency</category><category>approvals</category></item><item><title>Apache Paimon: one state table for the operator, the planner and the agent</title><link>https://hurukan.com/blog/apache-paimon-one-state-table-for-the-operator-the-planner-and-the-agent</link><guid isPermaLink="true">https://hurukan.com/blog/apache-paimon-one-state-table-for-the-operator-the-planner-and-the-agent</guid><description>How Apache Paimon keeps a table that a stream updates thousands of times an hour, how its merge engines express ontology rules, and what it costs to run.</description><pubDate>Mon, 19 Oct 2026 00:00:00 GMT</pubDate><category>Apache Paimon</category><category>LSM tree</category><category>merge engine</category><category>operations</category><category>Data layer</category></item><item><title>One record, readable by the tools you already have: XTable and UniForm</title><link>https://hurukan.com/blog/one-record-readable-by-the-tools-you-already-have-xtable-and-uniform</link><guid isPermaLink="true">https://hurukan.com/blog/one-record-readable-by-the-tools-you-already-have-xtable-and-uniform</guid><description>Apache XTable and Delta UniForm let one record be read as Delta, Iceberg or Hudi without a copy. What they translate, what they do not, where lock-in sits.</description><pubDate>Fri, 16 Oct 2026 00:00:00 GMT</pubDate><category>Apache XTable</category><category>Delta UniForm</category><category>table formats</category><category>lock-in</category><category>Microsoft Fabric</category></item><item><title>Android XR as an enterprise endpoint for on-device agents</title><link>https://hurukan.com/blog/android-xr-as-an-enterprise-endpoint</link><guid isPermaLink="true">https://hurukan.com/blog/android-xr-as-an-enterprise-endpoint</guid><description>Android XR brings Gemini, a camera and agents onto glasses. Before a company rolls them out: what runs on the device, what at the vendor, what in the company&apos;s own system.</description><pubDate>Tue, 13 Oct 2026 00:00:00 GMT</pubDate><category>Android XR</category><category>on-device agents</category><category>smart glasses</category><category>device management</category><category>data sovereignty</category></item><item><title>XREAL Aura on the shop floor: the system sees the workstation</title><link>https://hurukan.com/blog/xreal-aura-on-the-shop-floor</link><guid isPermaLink="true">https://hurukan.com/blog/xreal-aura-on-the-shop-floor</guid><description>XREAL Aura puts a camera, a display and Android XR in front of a frontline worker. What it takes for what the glasses see to end up in the company&apos;s own record.</description><pubDate>Tue, 13 Oct 2026 00:00:00 GMT</pubDate><category>XREAL Aura</category><category>Android XR</category><category>smart glasses</category><category>frontline work</category><category>quality inspection</category></item><item><title>Apache Hudi: the coexistence phase, change data from the old ERP into the record</title><link>https://hurukan.com/blog/apache-hudi-the-coexistence-phase-change-data-from-the-old-erp-into-the-record</link><guid isPermaLink="true">https://hurukan.com/blog/apache-hudi-the-coexistence-phase-change-data-from-the-old-erp-into-the-record</guid><description>Modules take over one process at a time; until then the old ERP keeps writing. How change data capture and Apache Hudi keep the record current meanwhile.</description><pubDate>Fri, 09 Oct 2026 00:00:00 GMT</pubDate><category>Apache Hudi</category><category>change data capture</category><category>coexistence</category><category>ERP migration</category><category>incremental processing</category></item><item><title>The state domain agents read: Paimon for the work queue, stock and approvals</title><link>https://hurukan.com/blog/the-state-domain-agents-read-paimon-for-the-work-queue-stock-and-approvals</link><guid isPermaLink="true">https://hurukan.com/blog/the-state-domain-agents-read-paimon-for-the-work-queue-stock-and-approvals</guid><description>A domain agent needs the company&apos;s state as of now, not a nightly copy. How the Data layer keeps it in Apache Paimon, and why agents only propose.</description><pubDate>Tue, 06 Oct 2026 00:00:00 GMT</pubDate><category>Apache Paimon</category><category>domain agents</category><category>live state</category><category>approval inbox</category><category>Data layer</category></item><item><title>Delta Lake: when the company stands on Microsoft</title><link>https://hurukan.com/blog/delta-lake-when-the-company-stands-on-microsoft</link><guid isPermaLink="true">https://hurukan.com/blog/delta-lake-when-the-company-stands-on-microsoft</guid><description>OneLake stores tables as Delta Parquet. What the Delta log gives a company&apos;s record, what Microsoft Fabric manages for you, and what remains yours to decide.</description><pubDate>Thu, 01 Oct 2026 00:00:00 GMT</pubDate><category>Delta Lake</category><category>Microsoft Fabric</category><category>OneLake</category><category>transaction log</category><category>sovereignty</category></item><item><title>Apache Iceberg: the record you can take with you</title><link>https://hurukan.com/blog/apache-iceberg-the-record-you-can-take-with-you</link><guid isPermaLink="true">https://hurukan.com/blog/apache-iceberg-the-record-you-can-take-with-you</guid><description>Iceberg keeps a table as a tree of immutable metadata with one pointer in a catalogue. Why so many vendors read it, and why the catalogue decides sovereignty.</description><pubDate>Tue, 29 Sep 2026 00:00:00 GMT</pubDate><category>Apache Iceberg</category><category>table format</category><category>catalogue</category><category>exit</category><category>sovereignty</category></item><item><title>The audit trail is a table: Delta Lake, Iceberg or Hudi</title><link>https://hurukan.com/blog/the-audit-trail-is-a-table-delta-lake-iceberg-or-hudi</link><guid isPermaLink="true">https://hurukan.com/blog/the-audit-trail-is-a-table-delta-lake-iceberg-or-hudi</guid><description>Who changed what, and what did the agent see when it proposed it? Delta Lake, Iceberg and Hudi answer differently. Choose by catalogue and infrastructure.</description><pubDate>Sat, 26 Sep 2026 00:00:00 GMT</pubDate><category>table formats</category><category>Delta Lake</category><category>Apache Iceberg</category><category>Apache Hudi</category><category>audit trail</category></item><item><title>Small models on your own hardware: when they are enough</title><link>https://hurukan.com/blog/small-models-on-your-own-hardware</link><guid isPermaLink="true">https://hurukan.com/blog/small-models-on-your-own-hardware</guid><description>Not every task needs a frontier model in someone else&apos;s data centre. Small open-weight models on your own hardware handle many narrow jobs well. How to tell which ones.</description><pubDate>Tue, 22 Sep 2026 00:00:00 GMT</pubDate><category>small language models</category><category>open-weight models</category><category>on-premises</category><category>model evaluation</category></item><item><title>Apache Parquet: how the record is laid out so superintelligence can read the whole company</title><link>https://hurukan.com/blog/apache-parquet-how-the-record-is-laid-out-so-superintelligence-can-read-the-whole-company</link><guid isPermaLink="true">https://hurukan.com/blog/apache-parquet-how-the-record-is-laid-out-so-superintelligence-can-read-the-whole-company</guid><description>Superintelligence reads the record constantly, on the company&apos;s own hardware. Parquet&apos;s layout sets what each question costs: row groups, statistics, codecs.</description><pubDate>Fri, 18 Sep 2026 00:00:00 GMT</pubDate><category>Apache Parquet</category><category>the record</category><category>columnar storage</category><category>cost of reading</category><category>sovereign infrastructure</category></item><item><title>Parquet and Avro: the event between modules and the record superintelligence reads</title><link>https://hurukan.com/blog/parquet-and-avro-the-event-between-modules-and-the-record-superintelligence-reads</link><guid isPermaLink="true">https://hurukan.com/blog/parquet-and-avro-the-event-between-modules-and-the-record-superintelligence-reads</guid><description>An event travels between modules as a row with a contract and rests in the record as columns. Why Avro carries the first and Parquet the second.</description><pubDate>Fri, 11 Sep 2026 00:00:00 GMT</pubDate><category>Apache Parquet</category><category>Apache Avro</category><category>event contracts</category><category>the record</category><category>data layer</category></item><item><title>Retrieval over the ontology beats retrieval over documents</title><link>https://hurukan.com/blog/retrieval-over-the-ontology</link><guid isPermaLink="true">https://hurukan.com/blog/retrieval-over-the-ontology</guid><description>Retrieval over a pile of documents finds text that looks relevant. Retrieval over a model of the company finds the facts that are true now, together with their relations.</description><pubDate>Mon, 07 Sep 2026 00:00:00 GMT</pubDate><category>RAG</category><category>retrieval</category><category>ontology</category><category>knowledge management</category></item><item><title>A system of record cannot act</title><link>https://hurukan.com/blog/a-system-of-record-cannot-act</link><guid isPermaLink="true">https://hurukan.com/blog/a-system-of-record-cannot-act</guid><description>Business software was designed to hold an accurate account of what already happened. That design decision is why a company&apos;s speed is set by how fast its staff can type.</description><pubDate>Fri, 04 Sep 2026 00:00:00 GMT</pubDate><category>system of action</category><category>ERP</category><category>automation</category><category>software design</category></item><item><title>Apache Avro: the contract between modules</title><link>https://hurukan.com/blog/apache-avro-the-contract-between-modules</link><guid isPermaLink="true">https://hurukan.com/blog/apache-avro-the-contract-between-modules</guid><description>Every event between modules is a contract. Apache Avro writes it into the data, and a schema change becomes a proposal a person approves and the system records.</description><pubDate>Wed, 02 Sep 2026 00:00:00 GMT</pubDate><category>Apache Avro</category><category>schema registry</category><category>event contracts</category><category>schema evolution</category><category>data layer</category></item><item><title>One definition of revenue for every report and every agent</title><link>https://hurukan.com/blog/one-definition-of-revenue</link><guid isPermaLink="true">https://hurukan.com/blog/one-definition-of-revenue</guid><description>When finance, sales and the board each compute revenue their own way, agents inherit the confusion at machine speed. A semantic layer fixes each definition once, upstream.</description><pubDate>Mon, 24 Aug 2026 00:00:00 GMT</pubDate><category>semantic layer</category><category>metrics</category><category>data governance</category><category>reporting</category></item><item><title>The integration tax</title><link>https://hurukan.com/blog/the-integration-tax</link><guid isPermaLink="true">https://hurukan.com/blog/the-integration-tax</guid><description>Every company knows what its software costs. Almost none can say what the space between the systems costs, and it is usually the larger number.</description><pubDate>Fri, 21 Aug 2026 00:00:00 GMT</pubDate><category>integration</category><category>data silos</category><category>cost</category><category>enterprise systems</category></item><item><title>Agents, RPA or workflows: which automation for which job</title><link>https://hurukan.com/blog/agents-rpa-or-workflows</link><guid isPermaLink="true">https://hurukan.com/blog/agents-rpa-or-workflows</guid><description>Workflow engines, RPA bots and language-model agents solve different problems. Choosing by fashion gives brittle bots and unpredictable agents. How to choose by the job.</description><pubDate>Wed, 12 Aug 2026 00:00:00 GMT</pubDate><category>RPA</category><category>workflow</category><category>AI agents</category><category>process automation</category></item><item><title>Intelligence has a lawful meaning and an unlawful one</title><link>https://hurukan.com/blog/intelligence-has-a-lawful-meaning</link><guid isPermaLink="true">https://hurukan.com/blog/intelligence-has-a-lawful-meaning</guid><description>Borrowing intelligence vocabulary for a business product is easy and mostly harmless. Borrowing the practices those words describe is a criminal offence.</description><pubDate>Fri, 07 Aug 2026 00:00:00 GMT</pubDate><category>OSINT</category><category>GDPR</category><category>boundaries</category><category>corporate intelligence</category></item><item><title>Voice for hands-busy work: conversation on the shop floor</title><link>https://hurukan.com/blog/voice-for-hands-busy-work</link><guid isPermaLink="true">https://hurukan.com/blog/voice-for-hands-busy-work</guid><description>When both hands hold a scanner, a part or a tool, a screen is the wrong interface. What voice has to do to be useful in a warehouse, a workshop or on a service visit.</description><pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate><category>voice interface</category><category>speech recognition</category><category>warehouse</category><category>field service</category></item><item><title>Code written by agents still gets reviewed</title><link>https://hurukan.com/blog/code-written-by-agents-still-gets-reviewed</link><guid isPermaLink="true">https://hurukan.com/blog/code-written-by-agents-still-gets-reviewed</guid><description>An autonomous software factory is a real advantage and the easiest thing in this field to oversell. Here is exactly where the automation stops.</description><pubDate>Fri, 24 Jul 2026 00:00:00 GMT</pubDate><category>AI engineering</category><category>CI/CD</category><category>review</category><category>software factory</category></item><item><title>When the company changes, the ontology has to change with it</title><link>https://hurukan.com/blog/when-the-company-changes-so-must-the-ontology</link><guid isPermaLink="true">https://hurukan.com/blog/when-the-company-changes-so-must-the-ontology</guid><description>A company adds a service line, splits a region or buys a competitor, and its model of the business goes stale. How to change an ontology without breaking what depends on it.</description><pubDate>Tue, 21 Jul 2026 00:00:00 GMT</pubDate><category>ontology</category><category>versioning</category><category>change management</category><category>data model</category></item><item><title>Compute is a market, not a subscription</title><link>https://hurukan.com/blog/compute-is-a-market-not-a-subscription</link><guid isPermaLink="true">https://hurukan.com/blog/compute-is-a-market-not-a-subscription</guid><description>AI work is bursty and hardware sits idle. A grid where machines trade capacity is an old idea whose obstacles were never technical, and there is no token in it.</description><pubDate>Fri, 10 Jul 2026 00:00:00 GMT</pubDate><category>distributed compute</category><category>grid</category><category>settlement</category><category>infrastructure</category></item><item><title>Which data must never leave the building, and how to decide</title><link>https://hurukan.com/blog/which-data-must-never-leave-the-building</link><guid isPermaLink="true">https://hurukan.com/blog/which-data-must-never-leave-the-building</guid><description>Treating every record as secret makes the rule unworkable, and treating none as secret makes it pointless. A practical way to classify data before any model touches it.</description><pubDate>Fri, 10 Jul 2026 00:00:00 GMT</pubDate><category>data classification</category><category>GDPR</category><category>trade secrets</category><category>local models</category></item><item><title>Classical ML still beats an LLM at forecasting demand</title><link>https://hurukan.com/blog/classical-ml-still-beats-llms-at-forecasting</link><guid isPermaLink="true">https://hurukan.com/blog/classical-ml-still-beats-llms-at-forecasting</guid><description>Asking a chat model how much stock to order produces a fluent number, not a forecast. Demand forecasting is still a job for classical models, a baseline and a backtest.</description><pubDate>Tue, 30 Jun 2026 00:00:00 GMT</pubDate><category>demand forecasting</category><category>machine learning</category><category>backtesting</category><category>procurement</category></item><item><title>Where large language models earn their keep in a company</title><link>https://hurukan.com/blog/where-language-models-earn-their-keep</link><guid isPermaLink="true">https://hurukan.com/blog/where-language-models-earn-their-keep</guid><description>Language models are strong at reading, drafting and translating between people and systems, and weak at arithmetic, recall and final decisions. A map of where to use them.</description><pubDate>Fri, 19 Jun 2026 00:00:00 GMT</pubDate><category>LLM</category><category>use cases</category><category>document processing</category><category>human approval</category></item><item><title>The dashboard nobody opens: BI that answers questions</title><link>https://hurukan.com/blog/the-dashboard-nobody-opens</link><guid isPermaLink="true">https://hurukan.com/blog/the-dashboard-nobody-opens</guid><description>Dashboards are built for the questions someone had last year. Managers have new ones every week. Analytics should start from the decision and the question, not the chart.</description><pubDate>Tue, 09 Jun 2026 00:00:00 GMT</pubDate><category>business intelligence</category><category>dashboards</category><category>metrics</category><category>decision-making</category></item><item><title>Hyperautomation fails at the handover, not the task</title><link>https://hurukan.com/blog/hyperautomation-fails-at-the-handover</link><guid isPermaLink="true">https://hurukan.com/blog/hyperautomation-fails-at-the-handover</guid><description>Each automated step works in the demo, and the process still stalls, because nobody designed what happens between the steps: the handover, the exception and the owner.</description><pubDate>Fri, 29 May 2026 00:00:00 GMT</pubDate><category>hyperautomation</category><category>process design</category><category>exceptions</category><category>ownership</category></item><item><title>A data platform is not a data lake with a dashboard</title><link>https://hurukan.com/blog/a-data-platform-is-not-a-data-lake</link><guid isPermaLink="true">https://hurukan.com/blog/a-data-platform-is-not-a-data-lake</guid><description>Copying every system into one store and pointing a BI tool at it builds a bigger pile, not a platform. A platform is defined by meaning, ownership and a way back to action.</description><pubDate>Tue, 19 May 2026 00:00:00 GMT</pubDate><category>data platform</category><category>data lake</category><category>data ownership</category><category>lineage</category></item><item><title>Your company already has an ontology. It lives in people&apos;s heads</title><link>https://hurukan.com/blog/your-company-already-has-an-ontology</link><guid isPermaLink="true">https://hurukan.com/blog/your-company-already-has-an-ontology</guid><description>Every company runs on a shared model of customers, orders and exceptions that nobody wrote down. How to find where that model lives and how to get it out of people&apos;s heads.</description><pubDate>Fri, 08 May 2026 00:00:00 GMT</pubDate><category>ontology</category><category>tacit knowledge</category><category>business rules</category><category>agents</category></item><item><title>A chat window is not a conversational interface</title><link>https://hurukan.com/blog/a-chat-window-is-not-a-conversational-interface</link><guid isPermaLink="true">https://hurukan.com/blog/a-chat-window-is-not-a-conversational-interface</guid><description>Adding a chat box to business software gives people a new place to type, not a new way to work. A conversational interface needs context, permissions and the right to act.</description><pubDate>Mon, 27 Apr 2026 00:00:00 GMT</pubDate><category>conversational interface</category><category>chat assistant</category><category>agents</category><category>user experience</category></item><item><title>Sovereignty is an architecture decision, not a hosting choice</title><link>https://hurukan.com/blog/sovereignty-is-an-architecture-decision</link><guid isPermaLink="true">https://hurukan.com/blog/sovereignty-is-an-architecture-decision</guid><description>Moving servers to a local data centre does not make a company sovereign. Who holds the keys, the model of the business and the exit does, and that is decided in the design.</description><pubDate>Tue, 14 Apr 2026 00:00:00 GMT</pubDate><category>data sovereignty</category><category>vendor lock-in</category><category>encryption keys</category><category>open source</category></item></channel></rss>