HousingLegalDesk (utility-debt recovery / HOA collections) is a counsel-and-legal-team desktop for structured work on housing & utilities arrears, rent, and capital-repair debts.
Management companies, homeowner associations, in-house legal teams, and private lawyers juggling many debtors and cases who want one chain from client intake through court filings — not scattered spreadsheets and memory-only email.
HOA collections are more than one Excel total: client mandates, debtor lists, debt freshness checks, history per personal account, overlaps with filed cases, and team visibility (“who checked what and when”). The app wires this into one flow: mandate → debtors → premises & links → cases & documents → event feed.
Inbound client tasks on the desk: status, owner, channel, dates, linked debtors, mandate-level progress.
Cards with name, address, client, amount and period, status and owner; links to mandates, payments, court matters and documents; side activity log per debtor.
Case number, court, type (including HOA debt recovery), status, claim amount, hearings, links to debtor and lawyer.
Contacts, practice focus, tenure, employment status.
Address, personal account, unit type (flat, parking, etc.), debtor↔premises relationship via ownership/use models.
Categories (HOA meeting minutes, charter, contract, court order, application, etc.) tied to entities.
Global desk timeline plus per-object events — one chronology for stage control and internal coordination.
Local SQLite storage with an in-memory fallback if database init fails — data stays on your machine.
Native SwiftUI app for macOS (project target macOS 15.5). Familiar three-column layout.
Desk inbox: status, owner, channel, dates, linked debtors, progress.
Cards with parties, address, amounts; links to cases/docs; activity sidebar.
Case number, court, HOA debt type, claim amount, hearings, debtor & lawyer links.
Contacts, focus, tenure, employment status.
Address, personal account, unit type; debtor↔premises relationship model.
Minutes, charter, contracts, orders, applications — linked to entities.
Desk-wide timeline plus per-object events for the team.
Local DB; in-memory fallback if database init fails.
