If the core engine genuinely is domain-agnostic, a fair question follows: why stop at six domains, rather than expanding indefinitely into every category where signal-based intelligence might theoretically apply? The answer isn't a technical limitation — it's a deliberate choice to prioritise depth and validation over unconstrained breadth.
Why breadth without depth would undermine the actual product
Each live domain requires genuine, working collectors and detectors — not placeholder logic. Collectibles didn't go live with a vague promise of tracking "trading cards generally"; it launched with five specific, validated detector types and a defined initial entity set. Spreading the same engineering effort across sixty domains instead of six would mean each domain receives a fraction of the validation rigor the current three live domains actually have.
What determines whether a domain belongs on this list
- A genuine, observable category of upstream signal that's currently underexploited by existing market participants
- A plausible detector stack that can be built using the existing collector and normaliser architecture, without requiring fundamentally new core infrastructure
- Enough genuine commercial or research interest to justify the engineering investment required to validate the domain properly
What this means for future domain additions
Six is the current plan, not a permanent ceiling. Any future domain beyond these six would need to clear the same bar — genuine signal structure, technical feasibility on the existing engine, and real demand — rather than being added simply because the architecture theoretically permits it.