cashflow-projectionlisted

# Cashflow Projection Models business-level risk before it arrives: income vs. outgoings, break-even, and runway over the next 90 days. ## Steps ### 0. Load business context Read `/media/data/Dropbox/Work/Admin/Financial/Accounting/aletheia-codex.md` before anything else. This is the authoritative record of account topology, money flow, and operating conventions. Use it to interpret which accounts obligations come from and how income is routed. ### 1. Read the financial snapshot Read `/media/data/Dropbox/Work/Admin/Financial/Accounting/accounts.json`. If more than 24 hours old, run `python3 studio/collectors/gnucash_collector.py` to refresh. Key fields: - `total_eur` — current bank balance - `upcoming_30d` — bills due in the next 30 days - `upcoming_30d_total` — total obligations next 30 days - `balance_after_30d` — cash after 30-day obligations - `monthly_pl_recent` — last 3 months income/expenses/net - `breakeven_allin` — €4,115/month (all costs + owner's draw) - `fixed_costs` — €717.38/month ### 2. Read the pipeline Read `/media/data/dev/misc/upwork-proposals/context/portfolio/project-database.csv`. Identify active projects (no End Date or End Date in the future). For each, note expected invoice amount and approximate timing. Read `accounts.json`'s `harvest.invoices` field for outstanding (unpaid) invoices (sourced live from Harvest, not a local log). If `harvest.configured` is false or the field is missing, note that Harvest isn't wired up rather than silently t