We are consolidating the substrate, not the market.

Collectibles is a hundred-billion-dollar market running on spreadsheets, screenshots, and a handful of closed marketplaces. Nobody owns the connective tissue — what a thing is, who owns it, what it is worth, and whether you can trust the person selling it.

The fragmentation is the problem

Value, ownership, and reputation live in incompatible silos. A collector retypes the same card into four tools. A shop runs five systems that disagree about how many of something it has, and reconciles them by hand on a Sunday. A developer who wants to build something durable finds no stable ground to build it on — every integration is a scrape, a CSV, or a private arrangement that breaks without notice.

None of that is a marketplace problem. It is an infrastructure problem that everyone has worked around for twenty years by doing the work manually.

One graph, four layers

So we build the layer underneath: identity — what a thing is and who a person is; inventory — who owns how many, with reservation integrity so a unit is never sold twice; trust — whether the other side can be relied on; and liquidity — a path from ownership to value, and back again.

Inventory is the root that everything binds to. The liquidity graph is the compounding asset built on top of it. Fragment the first and you degrade the second — which is why we will not ship a feature that creates a parallel copy of ownership truth, however convenient it would be in isolation.

The ecosystem map shows what this looks like in practice. Every relationship on it is derived from the products themselves rather than drawn by hand.

Information should compound

Every action on the platform should make future actions smarter. Scanning improves identification. Marketplace activity improves pricing. Trades improve reputation. Sales improve valuation. Community activity improves recommendations.

That is not a slogan about synergy — it is the reason a portfolio is the right shape for this company rather than an indulgence. A shelf reading taken by someone using Scout improves the price shown to someone using the marketplace, who has never heard of Scout. Products that merely coexist do not do that.

Revenue is a consequence

We optimise for healthy communities, a deep inventory graph, and high trust — and revenue follows through a chain we can name: community → liquidity → revenue. Communities create participation; participation creates liquidity; liquidity is what a marketplace earns from. Run it in that order and the business compounds. Run it backwards and you extract from a shrinking base.

So a feature that pulls revenue forward while weakening community, inventory integrity, or trust is a net loss even when it is profitable in isolation. That is a real constraint, and we have declined things because of it.

What we refuse

We don't fragment inventory truth, create parallel liquidity pools, weaken reservation integrity, or ship features that extract short-term revenue at the cost of community, trust, or long-term market health.

How we make and record decisions like these is written down — how we work.