2.0 KiB
Delivery roadmap
Each substantial subsystem receives its own design and implementation plan. This document orders milestones; it is not a task tracker.
1. Contributor foundation
Establish agent instructions, MVP boundaries, binding architecture, and financial data policy. Complete when the project documents are linked, consistent, and Git exclusions protect local data while synthetic fixtures remain trackable.
2. Runnable application skeleton
Design and scaffold Django, PostgreSQL, Docker Compose, dependency tooling, environment configuration, database roles, migrations, and pytest. Complete when a clean checkout can follow documented setup, start the application, apply migrations, and pass a database-backed smoke test. Use no real data.
3. Financial domain
Design accounts, credit cards, transactions, payees, categories, transfers, refunds, installments, and provenance. Complete when migrations and tests demonstrate the agreed financial invariants and relationships.
4. Reviewed imports
Design the normalized candidate contract and separate parser, normalization, validation, duplicate detection, preview, and persistence stages. Implement bank-account CSV and Banco do Brasil/Ourocard TXT using synthetic or irreversibly sanitized fixtures. Complete when preview issues are understandable, reimport behavior is tested, and committing an import preserves provenance without unintended duplicates. OFX remains unsupported.
5. Local MVP workflows
Add transaction management, categorization, monthly cash-flow and spending summaries, exports, and backups. Complete when an owner can follow the full import-to-report workflow and verify backup restoration with synthetic data.
Status: complete. The local owner workflow, portable export, PostgreSQL 17 backup, and repeatable disposable restore path are documented and covered by the complete synthetic acceptance suite.
Bank APIs, investments, mobile clients, receipt recognition, forecasting, and AI categorization require future scope decisions. See product scope.