Receipts Are Proof of Assembly
What a new theory of life tells us about coordination — and what only receipt data can show.
In 2023, a paper in Nature proposed a new way to measure the difference between living and non-living systems. The idea, called Assembly Theory, is disarmingly simple: count the minimum number of steps required to produce a given object. If that number is high enough, the object almost certainly wasn't produced by chance. It was produced by selection — by something that remembers, iterates, and builds on previous results.
The researchers — Lee Cronin and Sara Walker — were trying to solve the origin of life. They needed a way to look at a molecule and determine, without knowing its history, whether life made it. Their answer: measure its complexity. Not its size or weight, but the number of irreducible steps in its assembly path. Above a threshold of roughly 15 steps, the molecule was almost certainly biological. Below it, chemistry alone could account for it.
That threshold is a boundary. Below it: randomness. Above it: selection. Below it: things that happen. Above it: things that were built.
We think this same boundary exists in coordination.
The coordination gap is an assembly problem
Here is the state of digital coordination in 2026: billions of claims, almost zero verified assembly paths.
A project manager writes "on track" in a status update. That's a claim. It has an assembly index of approximately one — a single act of typing. No steps were required to produce it other than the decision to type those words. It carries no evidence of the actual project state. It could be true. It could be fiction. There is no way to distinguish the two from the claim alone.
Now imagine the same project manager opens GetReceipts, talks through what actually happened this week, attaches the three artifacts that prove it, and seals the receipt. That receipt has a meaningfully higher assembly index. It required multiple steps: the work itself, the evidence gathering, the structured reflection, the attachment, the seal. Each step added complexity that couldn't have been produced without the prior step. The sealed receipt is a high-assembly-index object. The status update is a low-assembly-index object.
Assembly Theory says you can distinguish life from non-life by measuring assembly index. We believe you can distinguish real coordination from performance coordination the same way.
Not by detecting lies. Not by training classifiers. Not by observing behavior and inferring intent. By measuring the assembly path of the claim itself.
What receipt data reveals that nothing else can
Every platform in the world has data about what people say they did. Slack messages. Status updates. Performance reviews. LinkedIn profiles. The entire digital economy runs on claims.
Almost no platform has data about the assembly path of those claims — the evidence trail, the steps that produced them, the gap between what was aimed for and what was actually built.
GetReceipts is, as far as we know, the first system that captures the full assembly path of a coordination claim: the aim, the evidence, the reflection, and the seal. This means our data can answer questions that no other dataset can.
Here are four.
Question 1: What is the assembly index distribution of real-world coordination?
When people create receipts — honest, evidence-backed records of what they did — how many steps does the average receipt require? Assembly Theory predicts that living systems produce objects with characteristically high assembly indices. If coordination is alive in the Assembly Theory sense — if it's a system that remembers, selects, and iterates — then coordination receipts should show a characteristic complexity signature. We expect to find that real coordination clusters above a threshold, just as biological molecules cluster above an assembly index of 15. Below that threshold: noise, theater, status updates that could have been generated by autocomplete. Above it: coordination that required actual contact with reality.
Nobody has measured this before. You can't measure it without receipts.
Question 2: Do coordination patterns show convergent selection?
Assembly Theory's deepest claim is that when independent processes arrive at the same configuration, that configuration is an attractor — not a coincidence. If two teams solving different problems independently develop the same coordination structure, that structure is real. It exists in the possibility space regardless of who finds it.
Receipt data can detect this. If we see teams across different industries, different sizes, different contexts independently producing receipts with similar structural signatures — similar evidence patterns, similar aim-to-outcome ratios, similar sealing rhythms — that's convergent selection. It means those coordination patterns aren't arbitrary choices. They're attractors in the coordination landscape. They're the shapes that work.
No survey can reveal this. No behavioral analytics can detect it. You need the assembly path — the receipt — to see what the coordination actually looked like from the inside.
Question 3: Are coordination systems autocatalytic?
An autocatalytic system is one where the outputs of the process become inputs to the next cycle. In chemistry, autocatalytic sets are considered a precondition for life — they're how simple reactions bootstrap into self-sustaining complexity.
We believe coordination has the same property, and receipts are how you detect it. When a sealed receipt from one project becomes evidence in the next project's receipt — when proof compounds — that's autocatalysis. The receipt isn't just documentation. It's feedstock. The output of one coordination cycle becomes the input of the next.
If this is happening, the data will show it. Receipt chains — sequences where each receipt references or builds on a previous one — would grow in complexity over time. The assembly index of the tenth receipt in a chain should be meaningfully higher than the first, because each receipt inherits the assembly work of its predecessors.
This is what "trust compounding" looks like in Assembly Theory terms. It's not a metaphor. It's measurable. But only if you have the receipts.
Question 4: Can you detect coordination frequency signatures?
Every recurring process has a frequency. Weekly standups. Monthly reviews. Quarterly planning. These are oscillators — repeating cycles of aim, action, evidence, and assessment. Assembly Theory doesn't just measure static complexity. It measures how complexity accumulates over time through repeated selection cycles.
Receipt data captures the timestamp and rhythm of coordination acts. With enough receipts from enough teams over enough time, we should be able to detect characteristic frequencies — coordination rhythms that correlate with outcomes. Do teams that seal receipts at a weekly cadence outperform teams that seal monthly? Do individuals with regular receipt rhythms show higher assembly indices over time than those with irregular ones?
These are frequency correlations, not causal claims. Assembly Theory is explicit about this: you measure correlation between assembly index and observed patterns, and the correlation itself is the signal. The receipt timestamp is the oscillator measurement. The sealed evidence is the amplitude. The pattern across time is the frequency signature.
Nobody has this data. Nobody can get this data without a system that captures the full assembly path of coordination claims, at the moment they're made, with evidence attached.
Why this matters beyond theory
This isn't academic. The practical consequence is that receipt data could reveal the physics of coordination — the actual patterns that distinguish teams, organizations, and individuals that coordinate well from those that merely perform coordination.
Every management framework in history has tried to answer this question with surveys, interviews, OKRs, KPIs, and retrospectives. All of these capture claims about coordination. None of them capture the assembly path.
GetReceipts captures the assembly path. The aim before the work. The evidence during the work. The sealed proof after. The chain across projects. The rhythm over time. This is the dataset that Assembly Theory predicts should contain the signal — and that no other system produces.
We're not claiming we've found it yet. We're saying we know where to look, we know what to measure, and we're building the instrument.
The oldest theory of coordination
Assembly Theory was published in 2023. But the principle it describes — that you can measure the complexity of a thing to determine whether it was built intentionally — is 5,400 years old.
The Sumerians pressed tokens into clay to create receipts. Those receipts were, in Assembly Theory terms, objects with a specific assembly index: the transaction happened, the evidence was gathered, the tokens were pressed, the clay was fired. The fired tablet was a high-assembly-index object. A verbal promise was a low-assembly-index object. The entire Sumerian economy was built on the ability to distinguish the two.
Writing itself emerged from this process. The first written symbols weren't poetry or prayer. They were receipt marks — compressed proofs of assembly. The sign for "barley" on a clay tablet was a record that barley had been counted, allocated, and delivered. The sign was the seal on the assembly path.
Civilization didn't scale because people became more honest. It scaled because the cost of producing a high-assembly-index coordination object — a receipt — dropped below the cost of disputing a low-assembly-index one — a verbal claim.
Clay made assembly cheap. Fire made it permanent. The seal made it portable.
We're doing the same thing with different materials. Chat makes assembly cheap. Evidence makes it verifiable. The seal makes it permanent.
The physics hasn't changed. The substrate has.
What we're building toward
The hypothesis is simple: receipt data contains the assembly signature of coordination, and that signature is measurable, predictive, and actionable.
If Assembly Theory is right that high-assembly-index configurations are the signature of life and selection, then high-assembly-index coordination records — receipts with real evidence, real reflection, real seal — should be the signature of real coordination. And the patterns in that data should reveal the attractors, frequencies, and autocatalytic loops that make coordination work.
We can't prove this without the data. And nobody can produce the data without receipts.
That's what GetReceipts is for. Not a productivity tool. Not a documentation system. An instrument for measuring the assembly index of coordination.
Reality speaks in receipts. Assembly Theory tells us why: because a receipt is proof that something was built, step by step, through selection rather than chance. A receipt is proof of assembly.
And assembly is the universe's word for life.
GetReceipts: Measuring what coordination is actually made of. Start at getreceipts.com. Feel the Seal. 𒐛