Yoni Michael is a co-founder of Typedef, which builds a context layer for data-engineering agents. His work focuses on giving agents the relationships and business definitions needed to make reliable changes across a data platform.[1]
Start with The Data Context Layer →
Links
Typedef: About LinkedInCo-founder · Typedef
Career
Before Typedef, Michael worked on infrastructure at Salesforce. A Salesforce engineering account of Dreamforce 2017 identifies him with work on predicting hard-drive failures. His team had to clean and standardize metrics from different drive vendors before using machine learning to associate conditions with failures. That earlier work illustrates a recurring concern in his current writing: a capable algorithm still depends on a usable representation of the system it operates on. Typedef lists Michael and Kostas Pardalis as co-founders.[3][1]
Contributions
Typedef also publishes fenic, a semantic DataFrame engine. It combines familiar filtering and joining with model-backed extraction, classification and summarization in inspectable pipelines. Those pipelines can be rerun and examined instead of leaving the result as an unstructured chat session. This is company work; Michael’s verified connection is as co-founder, not sole author of the codebase.[4][1]
Ideas
In their data-context essay, Michael and Pardalis use a join-key change to explain the gap between reading SQL and understanding a data system. A syntactically valid change can alter the grain, the unit represented by each row, causing an aggregation to double-count revenue further downstream. Their context layer is intended to connect code, lineage, metric definitions and dependencies so an agent can examine those consequences. The contribution is a system model around the agent, rather than a claim that better text generation alone solves data correctness.[2]
Tools, writing & talks
Writing, research & talks
Start here
The Data Context Layertypedef.aiAn explanation of why agents need business semantics and dependency relationships beyond code and database access.
Read the data-context essay first if you know basic SQL joins and aggregations. Its join-key example shows how a locally reasonable edit changes downstream business meaning, giving a concrete test for any proposed agent context layer.
Co-author with Kostas Pardalis[2]Typedef presenters build a symbol-level context graph over Rust crates using tree-sitter, Rustdoc and Neo4j, and show agents ignoring it for grep. They cover tool naming, trace inspection and repeated-run evals, plus lineage checks for data systems.
Catalog workOriginal source