Markdown source

Software Factories

Overview

Software factories are coordinated systems for turning ideas, issues, designs, tests, agents, and human review into shipped software. In an AI-native version, multiple agents may handle planning, coding, testing, review, documentation, and release support under explicit workflow rules.

Conference Context

The idea comes from assembly-line metaphors in software engineering, CI/CD, DevOps, internal developer platforms, and automated code generation. AI agents make the factory metaphor more literal because parts of the SDLC can be delegated to tool-using systems.

How This Theme Evolved

Confidence: medium-high. Boundary: Earlier event wikis are comparison context only. They are not primary evidence for World's Fair 2026 claims, and no local fixture is represented as a public live site. Comparison source: aie wiki generation delta.

Significance

A single coding assistant is useful, but organizations need repeatability, governance, and quality gates. Software factories focus on the whole production system: intake, context, implementation, validation, review, deployment, and learning.

Why This Matters Now

The unit of engineering is shifting from an isolated assistant interaction to a repeatable production system that delegates, verifies, and records software work.

WF26 evidence gate: this section was emitted only because the page links to configured local evidence. Relevant configured evidence: 2026 06 29 nnenna ndukwe how to build quality gates into agentic coding workflows, 2026 06 29 uday kiran medisetty agentic sdlc at uber building blocks for uber s software factory, 2026 06 30 suraj gupta warp building self improving agent software factories.

Confidence: medium-high. Comparison history is context; linked WF26 pages remain the evidence for current-event claims.

Applied Use

Model the workflow as stages with inputs, outputs, owners, and acceptance checks. Give agents scoped roles, shared artifacts, test gates, traceability, and rollback paths. Measure cycle time, defect rate, review burden, and production outcomes.

They fit engineering organizations, platform teams, internal tools groups, migration projects, and product teams with repeatable implementation patterns.

Use a software-factory approach when many similar tasks flow through the same path or when agent work needs governance. Avoid overbuilding it for occasional one-off tasks.

Model the workflow as stages with inputs, outputs, owners, and acceptance checks. Give agents scoped roles, shared artifacts, test gates, traceability, and rollback paths. Measure cycle time, defect rate, review burden, and production outcomes.

They fit engineering organizations, platform teams, internal tools groups, migration projects, and product teams with repeatable implementation patterns.

Use a software-factory approach when many similar tasks flow through the same path or when agent work needs governance. Avoid overbuilding it for occasional one-off tasks.

Model the workflow as stages with inputs, outputs, owners, and acceptance checks. Give agents scoped roles, shared artifacts, test gates, traceability, and rollback paths. Measure cycle time, defect rate, review burden, and production outcomes.

They fit engineering organizations, platform teams, internal tools groups, migration projects, and product teams with repeatable implementation patterns.

Use a software-factory approach when many similar tasks flow through the same path or when agent work needs governance. Avoid overbuilding it for occasional one-off tasks.

Model the workflow as stages with inputs, outputs, owners, and acceptance checks. Give agents scoped roles, shared artifacts, test gates, traceability, and rollback paths. Measure cycle time, defect rate, review burden, and production outcomes.

They fit engineering organizations, platform teams, internal tools groups, migration projects, and product teams with repeatable implementation patterns.

Use a software-factory approach when many similar tasks flow through the same path or when agent work needs governance. Avoid overbuilding it for occasional one-off tasks.

Model the workflow as stages with inputs, outputs, owners, and acceptance checks. Give agents scoped roles, shared artifacts, test gates, traceability, and rollback paths. Measure cycle time, defect rate, review burden, and production outcomes.

They fit engineering organizations, platform teams, internal tools groups, migration projects, and product teams with repeatable implementation patterns.

Use a software-factory approach when many similar tasks flow through the same path or when agent work needs governance. Avoid overbuilding it for occasional one-off tasks.

Model the workflow as stages with inputs, outputs, owners, and acceptance checks. Give agents scoped roles, shared artifacts, test gates, traceability, and rollback paths. Measure cycle time, defect rate, review burden, and production outcomes.

They fit engineering organizations, platform teams, internal tools groups, migration projects, and product teams with repeatable implementation patterns.

Use a software-factory approach when many similar tasks flow through the same path or when agent work needs governance. Avoid overbuilding it for occasional one-off tasks.

Practical Lesson

Evaluate the complete agent loop: task definition, context assembly, tool permissions, sandbox execution, verification, review, and provenance. Model capability alone is not the system boundary.

Confidence: medium-high. Treat this as synthesis derived from the linked evidence graph, not as an official schedule claim.

Connections

Evidence Graph

Transcript-backed resources

Transcript-backed resources

This evidence graph consolidates scheduled talks, linked videos, transcripts, and slide-derived material connected to this topic.

Linked Sessions

Media Signals

Source Coverage

This table summarizes the local evidence already linked from this topic. It is a navigation aid, not a claim that every linked page has been fully reviewed.

| Evidence type | Count | Review note |
| --- | ---: | --- |
| other | 29 | Related pages outside the main evidence categories. |
| resources | 7 | Video/resource pages; check source status before treating as primary event evidence. |
| slides | 9 | OCR or reconstructed slide evidence; mark claims as OCR-derived unless image-reviewed. |
| talks | 14 | Official schedule pages; use for titles, speakers, tracks, and stated talk framing. |
| transcripts | 1 | Transcript markdown; check session matching and caption quality. |

Talks

Resources

Slides

Transcripts

This table summarizes the local evidence already linked from this topic. It is a navigation aid, not a claim that every linked page has been fully reviewed.

Talks

Resources

Slides

Transcripts

This table summarizes the local evidence already linked from this topic. It is a navigation aid, not a claim that every linked page has been fully reviewed.

Talks

Resources

Slides

Transcripts

This table summarizes the local evidence already linked from this topic. It is a navigation aid, not a claim that every linked page has been fully reviewed.

| resources | 8 | Video/resource pages; check source status before treating as primary event evidence. |

Talks

Resources

Slides

Transcripts

This table summarizes the local evidence already linked from this topic. It is a navigation aid, not a claim that every linked page has been fully reviewed.

Talks

Resources

Slides

Transcripts

This table summarizes the local evidence already linked from this topic. It is a navigation aid, not a claim that every linked page has been fully reviewed.

Talks

Resources

Slides

Transcripts

This table summarizes the local evidence already linked from this topic. It is a navigation aid, not a claim that every linked page has been fully reviewed.

Talks

Resources

Slides

Transcripts

This table summarizes the local evidence already linked from this topic. It is a navigation aid, not a claim that every linked page has been fully reviewed.

Talks

Resources

Slides

Transcripts

This table summarizes the local evidence already linked from this topic. It is a navigation aid, not a claim that every linked page has been fully reviewed.

Talks

Resources

Slides

Transcripts

Active Use Cases

Livestream Source

Neighboring Subjects