01 / Product problem
Turn market movement into useful context.
Oil prices are only one part of the energy story. WorldSignal is designed to help readers understand how observed oil-market changes relate to gasoline, diesel, and jet fuel, and what recent energy headlines may add to that context.
02 / Product flow
A clear path from signal to explanation.
- ObservePresent a dated market movement with its units and data status.
- CompareShow historical relationships with downstream fuel prices without framing them as a forecast.
- Add contextPair bounded energy-news collection with concise, plain-language notes.
- Label uncertaintyKeep sourced observations distinct from estimates and interpretation.
03 / My contribution
Product implementation across the stack.
I built and locally verified the product across its React interface, TypeScript API and ingestion workers, Python research components, PostgreSQL data layer, authentication work, and API and UI test coverage. The work connects product decisions with the implementation details needed to make information understandable and dependable.
04 / Architecture
Separate layers for distinct responsibilities.
- Interface
- React · TypeScript · Vite
- Application API
- Fastify · TypeScript
- Data collection
- TypeScript workers
- Research
- Python · ML experiments
- Storage
- PostgreSQL
05 / Product decisions
Trust before prediction.
- Label dates, units, and data status instead of hiding uncertainty.
- Keep observed market facts separate from historical relationships and derived notes.
- Use cautious language; do not claim the product can predict the direction of oil prices.
- Do not present the earlier direction-forecasting research as a reliable product feature.