Repository navigation
Ecosystem
| Project | Responsibility |
|---|---|
| STRATHEX | Judge-facing event setup, fields, schedules, review, results, advancement, payouts, saves and exports. |
| STRATHMARK | Predictions, calibration, mark optimization, history and signed competition evidence. |
| MNEMEX | Portable competitor identity and finalized history. |
| Missoula Pro-Am Manager | Its own live/provisional event results and operator workflow. |
STRATHEX uses local data and its selected STRATHMARK runtime. MNEMEX must not become a race-day network requirement: event laptops use pinned local snapshots and reconcile afterward.
V2 direct Python, the public V2 HTTP demo, local Linux V3 and the V7 service are different integrations. Optional Missoula shadow integration uses a separate trusted contract; it is not STRATHEX's public stateless calculation route.
Live and provisional results belong to the event application. Portable finalized history belongs to MNEMEX. Prediction and settlement receipts belong to STRATHMARK. An integration must not silently take over another project's authority.
See Architecture for STRATHEX's active connections.
Home · Quick start · FAQ · Repository
Run a competition
- Home
- Quick start
- Choose V2 or V3
- Shared managed events
- Tournament workflow
- Multi-event days
- Brackets
- Backups and recovery
- Troubleshooting
- FAQ
Understand the system
- Handicaps explained
- Workbook and data
- Prediction methods
- Championship simulator
- Simulation and fairness
- Rules and officials
Develop and integrate