Portfolio Performance

The private implementation separates identity, reporting, and brokerage access. Users authenticate through Google; the application reads portfolio records through a repository interface; and IBKR Flex is accessed only by a GitHub Actions worker that imports statements on a schedule or by an authorized manual request. Browser routes neither contact IBKR nor place orders.

During import, the pipeline parses and normalizes the statement, checks selected section totals and snapshot relationships, and then opens the portfolio database transaction. A failed pre-write check leaves the existing rows unchanged. Separate CI tests protect accounting identities and deterministic fixture outputs. These mechanisms test the reporting pipeline; they do not certify the broker’s source data.

The current access model is single-user. Because identity, data access, domain calculations, and presentation are separate boundaries, the architecture can expand toward role-specific views, selective disclosure, and—after account-level data partitioning—multi-account reporting.

The synchronization workflow routes scheduled freshness checks and authorized Settings requests through the same worker. It validates the environment, checks database health, acquires a PostgreSQL advisory lock, polls IBKR with bounded backoff, parses and reconciles the returned XML, commits an idempotent import, performs a post-write read-back check, updates the archive, and releases the lock. Concurrent runs exit safely; a failed reconciliation records a sanitized failure while leaving the last successful portfolio data unchanged.