A trading record
An anonymized example of a system that turns broker fills into positions, a history, and a journal. No account or measured result is named.
Anonymized
An example, not a named engagement
This page describes a kind of system. It does not name a client, an organisation, or a measured result.
The problem
Fills arrive as a file and, sometimes, as a feed from a broker. The useful record is not the raw fill. It is the position, the closed trade, and a note the person writes afterwards. The broker should not be the only copy of that history.
Approach
How the work is shaped
- An organisation owns the accounts. Membership is checked before an account is read
- A statement can be imported, previewed, and then applied
- A read-only broker connection can sync into the same pipeline
- Executions are reconstructed into positions and trades
- The person keeps a history, a journal, and a daily review
- Sign-in is a session, with email confirmation and a second factor available
Architecture
How the pieces sit
- Domain rules do not know about HTTP or the database
- Use cases depend on ports. Adapters talk to the database and, when configured, to a broker
- One API process. The web app is a separate frontend
- A liveness check does not touch the database. Readiness checks the database and the cache
Stack
The kind of tools
- Compiled API
- Browser application
- PostgreSQL
- Redis
A similar workflow
Describe the job. These pages are examples of a build. They do not report a result.