
Papers
Research.
Applied research on language models inside industrial operations, run alongside the systems we build. Drafts are marked as such; nothing here is peer-reviewed unless the header says so.
Research directions
R/01 Context infrastructure 1 draft
R/02 Protocol servers for physical operations In preparation
R/03 Agentic operations In preparation
R/04 Substrate audit methodology In preparationResearch notes
Technical notes for engineers working with industrial records and language models. Owners will find the plain-language writing under Writing.
The 6-Question Context Engine Audit (And What Your Score Means) Six questions that tell you whether your AI system has a real context engine or a pile of half-built parts. Score in 15 minutes. What each band means.Storage for AI vs Object Storage (S3, R2, GCS): The Comparison Nobody Else Writes S3, R2, and GCS hold bytes. They do not know what is in them. A storage for AI layer holds the record an agent reads from. When to use each, and both.Your AI Demo Worked. Your AI Project Failed. Here's Why. Frontier LLMs are stateless. Every conversation starts cold. The gap between a demo and a shipped project is the state layer your business does not have.Every AI Team Builds a Context Engine. Most Don't Realize It. Every team building with AI rebuilds the same 6 components: connectors, retrieval, storage, review, protocol, drift detection. That is a context engine.Storage for AI vs Vector Databases: When to Use Which (and How They Work Together) A storage for AI layer holds the canonical record. A vector database indexes over it. Different problems, different layers. Most systems need both.The 5-Question Substrate Audit (And What Your Score Means) Five questions that tell you whether your business has an AI substrate. Score in 15 minutes. What each band means and what to fix first.Vector DBs Aren't Storage. They're Indexes. A vector database is an index. The storage sits somewhere else, usually a Postgres table nobody talks about. The missing category is storage for AI.AI Substrate Glossary: Definitions for the Terms KoldOps Uses Definitions for AI substrate, storage for AI, context engineering, decision-state, code-state, drift detection, and substrate audit. Refreshed quarterly.Decision-State, Airlocked to Code-State: Defining the AI Substrate The AI substrate isn't compute. It's the discipline that fuses business decisions to your codebase with the same git, review, and audit you use for code.