Founder letter
Relaunching the public institutional surface
Mustardseed.group as the public institutional surface
Most institutional websites are really two things pretending to be one: a genuine attempt to communicate what an organisation does, and a performance of what the organisation wishes it were perceived to be. The gap between those two impulses is where all the bad writing lives: the vague mission statements, the portfolio pages with the right logos, the about sections that read like someone threaded a job advertisement through a brand deck.
Mustardseed.group is being rebuilt because we want to close that gap. Not eliminate it entirely, every public surface involves some degree of curation, but narrow it to the point where the site is actually useful to someone trying to understand the institution, rather than simply impressive to someone who has already decided to work with it.
What the site is actually for
The simplest version of the answer: this is a public record of an institution being built in real time.
The archive you are reading is not a portfolio in any conventional sense. It does not exist to surface the best work and bury the difficult years. It exists to do something more structurally important: create a public record of what was being thought, built and understood at each point in time, so that the coherence of the institution can be traced rather than simply asserted.
There is a meaningful difference between an organisation that says it has a thesis and one that can demonstrate, through its own public writing, that the thesis has been consistently present across years. The first requires you to take the institution at its word. The second gives you something to verify. These articles, from 2017 onwards, covering research moments, product decisions, the emergence of AI as a productive force rather than an aspiration, are intended to serve the second function.
So far, that test has been harder than expected.
The identity problem that precedes the site problem
Mustard Seed Group is a holding company building systems that increase human capability. Arriving at that sentence took longer than it should have: not because the underlying intention was unclear, but because the available vocabulary was wrong.
Mustard Seed Group is a holding company building systems that increase human capability. That sentence has taken longer to arrive at than it should have, not because the underlying intent was unclear, but because the vocabulary available kept dragging the description toward categories that did not fit. Fund. Agency. Incubator. Studio. Lab. Each of these words comes loaded with assumptions about how the entity operates, who it serves, what it wants.
What exists here is closer to a private operating group with a single, sustained thesis: that human capability is the right thing to build for, and that AI and software, in particular the rapid development of intelligent systems that can reason, remember, act and adapt, represent the most significant change to what capability looks like in a generation. The work across the portfolio follows from that thesis. It does not require the thesis to be explained every time, but it does require the thesis to be stated and held clearly somewhere.
The closest model is something closer to a private operating group: a structure that has research, products, services and consumer work all running as coordinated bets on the same underlying thesis, with one founder holding the logic together across them. There are not many good reference points for that from the outside, which is partly why the site always risked defaulting to a template that looked familiar even if it was wrong.
This relaunch is an attempt to get the identity stated clearly enough that the site can be useful to people who are genuinely trying to understand the work, without performing a more legible version of the institution than the one that actually exists.
What the archive is doing
One of the decisions that shaped this version of the site is the emphasis on building a genuine archive rather than keeping only current, polished content live.
Benediction Lab works at the edge of what the tools can actually do: memory architectures, agent orchestration, GUI control, the question of what it means for a system to genuinely understand context rather than simulate understanding it. Orbit turns that research into commercial product: a B2B operating system that handles the full workflow from lead to launched product, powered by Orion, the AI intelligence layer underneath. TUXX proves patterns in live client environments, taking the research-to-product pipeline and testing it against real commercial constraints. CheekyGains and All Purpose ask whether the same capability logic, intelligent systems that extend what a person can do, applies when the person you are serving is not a business team but an individual trying to perform at their life.
There is a kind of institutional confidence in being willing to leave early thinking visible. It means accepting that some of the earlier positions will look incomplete, or that the questions being asked in 2017 will not yet have the answers that arrive in 2023. That is honest. A curated-only archive, where everything that appears has the benefit of hindsight, is a different kind of document. It is more flattering, less true.
The archive here is intended to show a thread. Not a triumphant arc, not a clean narrative of success: just a thread. The same questions about capability and intelligence and systems surfacing across different years, from different angles, against different technological conditions. That continuity is itself meaningful.
There is a real cost to building and maintaining a site like this: not the engineering cost, which is not negligible, but the intellectual cost. Writing for a public archive means being precise about what you are saying and honest about what you are leaving out. It means maintaining enough discipline over the voice and position that the site communicates something coherent even to someone encountering it for the first time without any prior context.
One of the things a public site like this has to solve for is intelligibility across a portfolio that looks, from the outside, genuinely diverse.
The first is internal. A public record creates a kind of accountability that internal documents cannot. It is harder to drift from a thesis you have stated publicly than one that exists only in Notion. When the archive here says that capability is the organising principle, a decision made for reasons unrelated to capability creates a tension, not a public controversy, but a visible inconsistency to anyone reading carefully. That is a useful constraint.
The second is a form of signal. The people who would find Benediction Lab's research direction genuinely interesting, researchers, engineers, founders thinking seriously about what agents can become, are not always reachable through conventional channels. They might find their way here through an article written in 2021 about Codex and the emotional shape of building, or through a 2017 piece on attention mechanisms that treats the Transformer not as a technical milestone but as a shift in what language can be. A public surface reaches people who read.
Benediction Lab researches the edges of what those tools can actually do. Orbit turns research patterns into commercial product. TUXX proves things in live client environments. CheekyGains and All Purpose explore the consumer dimension: the question of whether the same capability logic applies when the person you are serving is not a business team but an individual trying to perform at their life.
That is the thread. Mustardseed.group is where it gets stated.
On the decision to invest in public documentation
Building a site like this takes real time. Not just the engineering time. The thinking time. Writing for a public record means being deliberate about what is said, what is left out, and what the overall picture communicates. For a group operating across multiple products and research directions simultaneously, that deliberateness has a cost.
The AI work across the portfolio, Orion inside Orbit, the research agenda at Benediction Lab, the systems built through TUXX, is real. But it is in service of something that predates the current wave: the question of what people and organisations can actually do, and how to build things that extend that capacity without reducing the human in the process. The tools are changing fast. The thesis does not change with them.
An AI-first framing would make the tools the story. The tools are not the story. They are the current best instrument for the work. When better instruments exist, the work continues. That distinction is not rhetorical: it shapes what gets built, how research directions get chosen, and what counts as progress. It also shapes what this site is allowed to say.
The second is recruitment. Not in the conventional sense of job listings, though those exist, but in the broader sense of drawing the right people into the orbit of the work. The researchers, operators, engineers and founders who would find the Benediction Lab thesis genuinely interesting are not always the same people looking at job boards. They might find their way here through an article, through a footnote, through a piece about transformers or memory systems or the shape of agent architectures. A public surface is a signal to people who read carefully.
This relaunch is not a completion. The archive will grow. Positions stated here will be refined by later thinking, and the later thinking will be visible too, part of the same record rather than quietly replacing it. Some of the current products will evolve into forms that look different from how they are described today. The research will move forward.
The goal of the site is not to produce a definitive account of the institution. It is to keep a public record that is honest enough to be useful, to the researchers and operators who might join the work, to the collaborators and clients trying to understand what the group actually does, and to the institution itself, which benefits from having its own logic stated clearly enough to be tested.
If something here is unclear, that is useful information. The site should be able to communicate without a mediator. Where it cannot, something either needs better articulation, or, worse, is not yet thought through clearly enough to be stated. Both outcomes point somewhere real. That is what makes the surface worth building and worth keeping current.