Muthukrishnan Bommiah · muthub.org
The tempting answer to fragmented context is to pour everything into one place. We tried that with data, and many lakes became swamps. A context layer has to be a curated overlay: retrieval-first, owned, and pointing back to the systems that hold the truth.
Context engineering6 min readData platforms built for people asking questions will strain when the main consumer is software taking actions. Five principles for designing data platforms where agents are first-class users, and why an open lakehouse helps.
Data & AI platforms6 min readThe lakehouse unified analytics and AI. Bringing operational Postgres into it points toward one governed source of truth for agents.
Note1 min readAn experimental agent built pipelines, changed schemas, reverted its own mistakes and generated quality checks from plain language. Self-correction was the part that mattered.
Note1 min readOnly about 2.5% of open-source Java repositories use production assertions. LLMs can write them, adding the verification layer AI-written code needs.
Note1 min readWhen business meaning, data products and relationships live in one open catalog, agents stop guessing at tables and governance travels with the data.
Note1 min read