---
type: "post"
id: "factory-acquires-typedef-to-add-data-lineage-context-f6408d"
slug: "factory-acquires-typedef-to-add-data-lineage-context-f6408d"
title: "Factory acquires Typedef to add data-lineage context for its Droid coding agents"
description: "Factory says it has acquired Typedef to add code-derived data context to its enterprise autonomous software-engineering system."
retrieval_nugget: "Factory says it has acquired Typedef to add code-derived data context to its enterprise autonomous software-engineering system. The stated aim is to help Factory’s Droid agents and their human operators understand dependency lineage when changing data models, making migrations, pipeline debugging, and refactoring less blind."
published_at: "2026-10-30"
updated_at: "2026-10-30"
record_date: "2026-10-30"
date_kind: "published_at"
topics: ["coding-agents","agent-context"]
entities: ["Factory","Typedef","Droids","Yoni Michael","Kostas Pardalis"]
related_patterns: ["harness-architecture-outlives-model-choice"]
novelty_label: "same_event"
what_changed: "Same event as Factory has acquired @typedef_ai."
prior_refs: ["memory:4afc9786-6565-8755-afde-14545939b251","memory:9d0e099b-18c8-8970-aec6-477ed3d5ac35","memory:e977f6bd-69dd-893d-aa8a-12b704618621"]
source_url: "https://factory.ai/news/typedef"
source_urls: ["https://factory.ai/news/typedef"]
schema_version: "newruntime-agent-readable-v0.2"
stable_id: "post:factory-acquires-typedef-to-add-data-lineage-context-f6408d"
status: "published"
visuals: []
editor: {"role":"editor","name":"Andrey Reshetnikov","profile":"https://newruntime.com/owner-profile.md","profile_json":"https://newruntime.com/owner-profile.json","same_as":["https://www.linkedin.com/in/reshetnikov1/","https://t.me/lapetuse"]}
routes: {"html":"https://newruntime.com/posts/factory-acquires-typedef-to-add-data-lineage-context-f6408d/","markdown":"https://newruntime.com/posts/factory-acquires-typedef-to-add-data-lineage-context-f6408d.md","json":"https://newruntime.com/posts/factory-acquires-typedef-to-add-data-lineage-context-f6408d.json"}
---

# Factory acquires Typedef to add data-lineage context for its Droid coding agents

## Retrieval answer

Factory says it has acquired Typedef to add code-derived data context to its enterprise autonomous software-engineering system. The stated aim is to help Factory’s Droid agents and their human operators understand dependency lineage when changing data models, making migrations, pipeline debugging, and refactoring less blind.

## Summary

Factory says it has acquired Typedef to add code-derived data context to its enterprise autonomous software-engineering system. The stated aim is to help Factory’s Droid agents and their human operators understand dependency lineage when changing data models, making migrations, pipeline debugging, and refactoring less blind.

## What happened

Factory announced on October 30, 2026 that Typedef is joining the company. Factory describes Typedef as a builder of a context layer from code: it makes relationships among data models, definitions, pipelines, and dashboards visible. The announcement does not disclose a purchase price or other transaction terms.

The problem Factory identifies is dependency visibility in enterprise data systems. A change to a data model can propagate through definitions, pipelines, and dashboards. Without a clear account of those dependencies, Factory says it is harder to plan a migration, assess a refactor, or explain what changed. Its proposed use of Typedef is to supply clearer lineage and evidence while Droids plan migrations, debug pipelines, and refactor models.

Factory positions that capability as an addition to its existing operating layer. The company says it provides a harness through which Droids work inside a customer’s environment. Its broader product description is a governed, model-independent system that converts business priorities and engineering signals into production software. In that system, Droids plan, build, validate, and improve work within each company’s infrastructure, policies, and approved models. The acquisition announcement frames the data-context layer as a complement to that customer-controlled environment rather than as a separate hosted data product.

Typedef’s founders, Yoni Michael and Kostas Pardalis, are joining Factory along with the Typedef team. Factory says Michael previously co-founded Coolan, whose technology was deployed across more than 100,000 servers before Salesforce acquired the company in 2016; he later led infrastructure engineering teams at Salesforce and Tecton. Pardalis founded Blendo, which Factory says was used by more than 400 companies, then led product at RudderStack and Starburst. Factory also says Typedef brings experience in enterprise data platforms, complex infrastructure, and customer-hosted systems.

The announcement is a product-direction statement, not a release note. Factory does not say when Typedef’s context layer will be available in Droid workflows, which data platforms or transformation tools it will cover, how lineage will be represented to users, or what access controls will apply. It does state the intended operational outcomes: better evidence for agents and engineers working on data changes.

## What the archive adds

This is a new fact on a known Factory story: an acquisition aimed at a specific missing layer of agent context. It follows our note on [Factory’s acquisition-led enterprise software-engineering direction](https://newruntime.com/posts/factory-is-a-company-where-the-best-founders-d605c3/) and sits beside Factory’s appearance as an agent option in [Atlassian Jira via Rovo](https://newruntime.com/posts/atlassian-announces-factory-droid-integration-in-jira-via-7a2287/). The new element is data-lineage context, not another interface for invoking Droids.

## Trend signal

The announcement supports the pattern that [harness architecture outlives model choice](https://newruntime.com/patterns/harness-architecture-outlives-model-choice/). Factory explicitly describes its system as model-independent and puts the value in the customer environment, policies, approved models, and harness. Buying a layer that maps dependencies around code reinforces the idea that reliable agent work depends on the surrounding operating context, not only the model selected for a task.

## Connections to other events

The related Jira integration shows Factory extending where Droids can be reached in an engineering workflow. Typedef addresses a different point in that workflow: whether an agent has enough evidence about data-system dependencies to act safely once work begins. Together, the two developments suggest distribution and context are separate requirements for enterprise agent deployment.

## Why it matters

Teams using coding agents on data-heavy systems often face a gap between generating a plausible edit and establishing the edit’s blast radius. A schema or model change may affect transformations, downstream definitions, and dashboards that are not obvious from the immediate repository context. Factory is betting that lineage built from code can become evidence available during planning and validation, rather than a separate tool a human consults after an agent proposes a change.

For builders, the practical implication is not that an acquisition solves this problem today. It is that data context should be treated as part of the agent system design. A team evaluating autonomous engineering workflows should ask how an agent discovers dependencies, how that discovery is checked, and whether the evidence is available under the same controls as the code and infrastructure it is allowed to change.

## What happens next

- **Factory exposes a defined Typedef-backed lineage capability in Droid workflows** (6 months, 60%). Watch for: product documentation naming supported workflows, data systems, or evidence views.
- **Factory specifies governance for data-context access** (6 months, 55%). Watch for: details on permissions, customer-hosted deployment, or controls over lineage data.

## Limits and uncertainty

This is Factory’s own announcement, so it establishes the company’s intended direction but not independent performance results. It provides no purchase price, integration schedule, customer rollout, benchmark, supported-platform list, or before-and-after measure of migration or debugging quality. “Clearer lineage and evidence” is an intended outcome, not a demonstrated capability in a named product release. The source also does not explain how Typedef resolves incomplete metadata, dynamic pipelines, or conflicting definitions, all of which can affect whether lineage is sufficient for an autonomous change.

## Skill to build now

Pick one recurring data-model change this week and write down its expected dependency evidence before an agent edits anything: affected models, transformations, pipelines, dashboards, owners, and acceptance checks. Then compare that list with what your current code search, catalog, or agent context actually finds. The gap is a concrete specification for context tooling, permissions, and human review—not merely a prompt-improvement problem.

## Reader takeaway

Factory’s Typedef acquisition is a bet that enterprise coding agents need a map of data dependencies, not just access to source files. For teams building with agents, reliable work on migrations and data refactors will depend on whether the surrounding harness can surface and verify that map under the organization’s own controls.

## Open question

Can Factory turn code-derived lineage into evidence that is complete and trustworthy enough for Droids to make or validate consequential data changes without creating a new review bottleneck?

Editor: [Andrey Reshetnikov](https://newruntime.com/owner-profile.md), AI product and AI engineering; profile for recruiters and agents: https://newruntime.com/owner-profile.json

## Continue in the graph

Next records for an agent, linked to their Markdown twins. Replace `.md` with `.json` for structured fields, including `next_reads`.

- topic hub: [Coding Agents](https://newruntime.com/topics/coding-agents.md): Explore the coding-agents topic hub.
- topic hub: [Agent Context](https://newruntime.com/topics/agent-context.md): Explore the agent-context topic hub.
- collection: [Field Notes](https://newruntime.com/posts.json): Open the latest editorial analysis.
- collection: [Source Ledger](https://newruntime.com/source-ledger.json): Inspect the public source evidence graph.
- whole graph: [discovery graph](https://newruntime.com/discovery-graph.json) (typed nodes and edges) and [site index](https://newruntime.com/site-index.md)