A live multi-user operating system for discovering sports markets, routing strategy decisions, executing through guarded wallets, and reconciling order state against on-chain activity.
recreatedRecreated operations surface using synthetic values only.
At a glance
What I owned
Period
2026; active private product and public reference
Role
Product and systems work for live operations
Team
Private side-project team; separate public reference implemented by Franco
Users
Operators managing automated sports-market workflows across multiple user accounts
Status
Private live operation; separate public reference implementation
Contribution
Worked across sports-market discovery, per-user strategy routing, wallet onboarding, guarded CLOB execution, order-state reconciliation, dashboard and Telegram operations, tests, and release diagnosis.
Tradeoff
Show the operational product and its engineering boundaries without exposing strategies, credentials, users, wallets, production data, infrastructure, or financial claims.
Evidence
The private product operates live. The linked repository is a separate paper-only reference with clean provenance, bounded public reads, idempotent state, diagnostics, tests, containers, and browser acceptance.
Product
Live multi-user system
Modes
Paper and production
Execution
Guarded per strategy
Public proof
Bounded reference repo
01
Live sport becomes an actionable market
The discovery layer combines live scoreboard data with Gamma metadata and CLOB liquidity. It resolves event identity, timing, market availability, and tradable outcome tokens before a strategy receives an opportunity.
recreatedDiscovery resolves a live event into a verified, tradable market before strategy routing.
02
Every user gets a controlled execution path
Configuration is independent by user and strategy. Each decision passes through its selected paper or production mode, isolated wallet, balance validation, kill switch, limits, and pre-trade checks before it can reach the CLOB.
recreatedUser and strategy isolation keeps execution mode, wallet readiness, and safety controls explicit.
03
An order is not a result
Submission begins an order lifecycle; it does not settle the outcome. The system tracks acknowledgements, open quantity, partial and complete fills, cancellations, rejects, and active exits while preserving the intent that created the order.
recreatedOrder intent and exchange state remain connected across every lifecycle transition.
04
Operations continue after execution
Exchange responses, recorded fills, and on-chain activity can disagree or arrive at different times. Reconciliation workers compare those surfaces, repair stale state idempotently, and expose exceptions through the dashboard and Telegram for diagnosis.
recreatedReconciliation turns asynchronous exchange and chain events into inspectable operating state.
05
Public evidence without exposing private logic
The linked Ops Lab is an independent, deliberately paper-only implementation. It demonstrates exact read allowlists, an idempotent ledger, diagnostics, tests, containers, and clean provenance without publishing private code, strategies, data, wallets, users, or infrastructure.
recreatedThe public reference proves engineering boundaries while private product logic remains outside the artifact.
