From proof-of-concept rails to a multi-tenant trading product
A visual roadmap of what existed at submission, what has shipped since, and where Sorites is hardening next.
Product direction, business logic, investment management and commercial structure.
Development, data architecture, business logic and a second review layer across product decisions.
DevOps, infrastructure delivery and a second engineering review layer on business logic.
User perspective, product feedback, business logic validation and content management.
Build path after submission
The shift
At Colosseum submission, Sorites had the core POC: MUTHUR as a sample auto-trader integration, Sorites App and API, Quorm execution/policy infrastructure, and a live oracle path. Since then the stack has moved toward a usable client-trader product: SYNTH, multi-position tenancy, WYSIWYG creation tooling, wallet authority/delegation, oracle reliability, and tighter security boundaries.
Harden SYNTH polling, slim API payloads, and keep Quorm control-plane routes private.
Turn client-trader wallet authority into the default vault trading workflow.
Surface proof, policy, and delegation state directly inside public vault/trader pages.
Keep optimisation waves running as new tenants, positions, and data products come online.