Manifesto!
I. The Question That Drives Us
Every generation of engineers faces the same temptation: to build for now.
The pressures are real. Deadlines. Markets. The relentless pace of technological change. And so we build systems that work — for a while. Systems that scale — until they don’t. Systems we are proud of — until we inherit their successors and wonder what we were thinking.
But some systems endure. UNIX has outlasted entire generations of competitors. TCP/IP quietly routes the modern world. The principles behind the Roman arch are still used in bridge engineering. Evolution has been running the same core algorithm for billions of years.
What do these systems know that we don’t?
This is the question that drives ObjectSpread.
II. Why This Is Hard
The failure mode of most engineering culture is this: we study what works without asking why it works.
We copy patterns. We follow best practices. We learn frameworks. And these things are useful. But they are not the same as understanding.
Understanding is what lets you see that a feedback loop in a mechanical governor and a feedback loop in a distributed consensus algorithm are the same thing at a deeper level. Understanding is what lets you know, before you build, whether an architecture will hold.
That kind of understanding requires more than engineering. It requires mathematics — the language in which system behavior can be stated precisely and analyzed rigorously. It requires philosophy — the discipline that asks foundational questions without flinching. And it requires the patience to synthesize across domains, to resist the comfortable specializations that modern academia and industry reward.
This is why systems architecture, as a discipline, remains underdeveloped. The questions are hard. The timescale is long. The work doesn’t fit neatly into a quarter, a PhD, or a product roadmap.
III. What We Believe
We believe systems architecture is a science. Not just a craft. Not just an art. A discipline with foundations in mathematics and testable claims about the world. One that can be studied rigorously, taught systematically, and advanced collaboratively.
We believe design philosophy matters. The choices baked into a system’s architecture reflect values — about what is important, what is difficult, what is worth optimizing for. Understanding these values is not a soft, secondary concern. It is essential to understanding why systems succeed or fail.
We believe great insights are cross-domain. The principles behind UNIX are not unique to operating systems. The mathematics of control theory is not unique to mechanical engineering. The study of emergent behavior in ant colonies illuminates distributed computing. Specialization is necessary. But so is synthesis.
We believe independent research has a role to play. Not every important question can be answered inside a company or a university. Some questions are too slow, too foundational, or too honest for institutional incentives. Independent researchers — unbound by tenure, quarterly earnings, or fashionable trends — can ask questions that others can’t.
We believe research belongs to everyone. The history of science is a history of gatekeeping that slowed progress. We reject the notion that rigorous research requires prestigious credentials. What it requires is rigor, curiosity, and commitment — qualities that appear at every level of education and every stage of career.
IV. What We Are Building
ObjectSpread is a community, not a company. A research program, not a product.
We are building a body of knowledge about systems architecture and design philosophy — published openly, developed collaboratively, and grounded in mathematical and empirical rigor.
We are building a culture of long-term thinking in a field dominated by short-term incentives.
We are building a place where a curious undergraduate and an experienced systems architect can work on the same problem and both be taken seriously.
This is ambitious. We know that. The best systems always start with an ambitious specification.
V. The Standard We Hold Ourselves To
ObjectSpread is independent. That means no one funds our conclusions. No institutional agenda shapes our questions. No quarterly pressure distorts our timelines.
This freedom comes with responsibility. We hold ourselves to the standard that intellectual independence demands: that our work is honest, our arguments are grounded, and our conclusions follow from evidence and reasoning — not from what is convenient, fashionable, or popular.
We do not pursue novelty for its own sake. We do not publish to build CVs. We publish because we believe the work matters, and because the field is better when good ideas are in the open.
VI. An Invitation
If you have read this far, you are probably the kind of person we are looking for.
Not someone who has all the answers — we don’t either. Someone who takes the questions seriously. Someone who is willing to do slow, careful work in the direction of understanding.
The era of systems abundance is here. Distributed computing, artificial intelligence, autonomous systems — they are everywhere, and their architectures will shape the world for decades. The quality of the thinking that goes into those architectures matters enormously.
We think it’s time for a community dedicated to getting it right.
Welcome to ObjectSpread.
To get involved, visit our Join Us page.