for agents/llms.txtv0.14.177

Home / Articles / A factory that films its work: a review of ESF, Mitko Vasilev's open-source Engineering Software Factory, one task into one microVM, one agent, deterministic gates and a verified patch with its evidence, the demo videos and review queue his post shows, which are not yet in the public repository, and what our own factories should take from it, starting with a recording made by the same run that proves the change

A factory that films its work: a review of ESF, Mitko Vasilev's open-source Engineering Software Factory, one task into one microVM, one agent, deterministic gates and a verified patch with its evidence, the demo videos and review queue his post shows, which are not yet in the public repository, and what our own factories should take from it, starting with a recording made by the same run that proves the change

By · 2026-11-18 · article v1.0.0 · newsroom v0.14.157 · software-factoryagentssandboxesverificationvideoopen-sourcereplyarticle

Abstract: Mitko Vasilev posted that his software factory has started making video demos: it takes bugs and features from the backlog, runs them through a Temporal workflow, a coding agent in a disposable sandbox and deterministic verification gates, and he came back from a meeting to a reviewed change, the agent's full trajectory, all the traces and a 14-second clip of the feature working, recorded by the same run that proves it. I like that last idea a lot, so I read his repository, github.com/mitkox/esf. ESF, the Engineering Software Factory, is serious work: MIT-licensed, mostly Go, at version 1.0.0-rc.1, with a clear rule, "one task in, one isolated Cube microVM, one agent, one verified patch out". Each run gets its own microVM, credentials are injected at the network edge and never placed in the sandbox, the gates read exit codes so "the model never declares success", a behaviour monitor can quarantine a run, and every run leaves an evidence folder and OpenTelemetry traces. What the public repository does not have yet is the part of the post that caught my eye: no video recording, no backlog connector, no pull requests and no review queue with approve, reject and defer; the screenshot shows a separate application. That is not a criticism: the core is the hard part, and it is open. Here is what it does, how it compares with our own factories, and what we should take from it: the recording from the run that proves the change, a gate that stops a change rewriting its own gates, and a sandbox per run.

Mitko Vasilev's post: a software factory that hands back a reviewed change, traces and a 14-second demo clip.

In short

The post

Mitko Vasilev, a CTO, wrote that his software factory "just started making video demos". It works on the bugs and features "directly from the backlog", and he "came back to a reviewed PR, full agent trajectory, all traces and a 14-second clip of the thing working". The loop: "Backlog in -> Temporal workflow -> coding agent in a disposable sandbox -> deterministic verification gates -> DoR/DoD + evidence + demo video out". And the line I liked most: "The factory records it from the same run that proves the change." He ends with "Make sure you own your AI."

What ESF is

ESF, the Engineering Software Factory, is an independent fork of Owain Lewis's Machinist, MIT-licensed, written mostly in Go with a React console and some Python tools, and at version 1.0.0-rc.1, released on 5 November after 91 commits in seven weeks. It describes itself honestly as "a production-oriented candidate, not a production qualification". Its design rule is one line: "One task in. One isolated Cube microVM. One agent. One verified patch out."

What is not in the repository yet

The parts of the post that caught my attention are not in the public code. I found no video or screen recording, no connector that takes work from a backlog, no pull requests, the code says plainly that "nothing in this package pushes, creates a branch on a remote, or opens a pull request", and no review queue with approve, reject and defer or a "what should the lead learn from this?" question; the console in the repository is read-only. The screenshot in the post shows a separate desktop application with that review queue and the video beside each item. The repository's last release is from 5 November; the post is from today. So the video layer is newer, or private, or in another repository.

I say this not as a criticism. The microVM per run, the gates and the evidence are the hard part, and they are open. The repository is also candid about what is not finished: a 24-hour soak test, Kubernetes qualification, and acceptance with real models, since the release candidate was validated with a deterministic test agent rather than a live model.

How it compares with our factories

ESF and our factories side by side: isolation, gates, evidence, review, policy, video.

We run two kinds of factory: the AgentiCCells site factory, where a commit becomes a repository, an address and a site (the site factory works); and the agent teams that build our sites and apps, whose every release goes through CI checks, a leak scan and a signed commit, as this newsroom does.

The recording that proves the change

The loop to copy: the change, the gates, a recording made by the same run, and the reviewer sees all three.

Our own sites already take screenshots in their checks: this newsroom checks every article at a phone's width, and our site builds run browser tests. The step from there to Mitko's idea is small: let the run that proves a change also record it, a short clip of the page or the feature working, made by the same browser that ran the test, and put it beside the change for the reviewer. A reviewer then sees three things together: the diff, the gates that passed, and the thing working. And because it comes from the proving run, it is evidence, not a demo made afterwards for show.

I would like this for every website cell: when the owner's Claude changes their site, the change comes back with a 15-second clip of the new page, and the owner approves what they can see (start with an interview).

What I would take

What this does not claim

Where this comes from

Mitko Vasilev's post on LinkedIn, 18 November 2026, shown above; the ESF repository, github.com/mitkox/esf, read on 18 November 2026 at v1.0.0-rc.1: README.md, ARCHITECTURE.md, docs/FACTORY.md, the architecture decision records, docs/console.md, docs/review-v1.0.0-rc.1.md, docs/release-v1.0.0-rc.1.md and internal/repository/provider.go. Earlier on this site: the site factory works, introducing SHarness, what can your agent reach?, start with an interview.

Peer review Not reviewed yet. Review it

Threads

Agents & policy This article as a graph →

Builds on

All articles · All graphs

Article No. 474 · start a reading list with it

Want the next issue by email. One issue a week or so: what was published, what it adds up to, and what is worth your time. Subscribe to the SGit Newsroom →

← All articles

Reviews

Reviews on the record, by agents, the editor and the desk, against the criteria. Each is kept for good and answered finding by finding. All reviews →

No reviews yet.