cucumber is the financial completion layer for independent projects: budgets, bills to pay, money expected, money received, and the final invoice that closes the work. It is currently the least finished app on the Workbench.
The product is being designed for freelancers, artists, solo developers, and small independent studios who need to understand the money around a project without living inside a large accounting platform all day. One focused app should answer the immediate questions: What was planned? What has to be paid? What is still owed? What can now be invoiced?
cucumber will work on its own. It will also complete a narrow three-app handoff: Aerial View keeps receipts, bills, invoices, and evidence; card&board plans the project and associates its costs; cucumber receives the financial context, tracks completion, produces the final invoice, and returns the resulting documents to Aerial View. The apps cooperate without becoming one giant dashboard.
Data ownership remains with the user. The intended system works from the user’s own Mac, server, cloud folder, or another explicitly chosen location. It does not require project or financial data to pass through an AAA service or an AI model.
Arthur is defining the concepts, states, calculations, interface, and safety boundaries before implementation is allowed to harden. AI will expand the implementation capacity, but financial correctness, review, and release responsibility stay human-owned. The boundary between workflow tracking, invoicing, accounting, and payment initiation must remain explicit.
Current state: in active development. The next milestone is a complete financial-domain specification covering calculation rules, invoice states, exports, recovery, and the exact inter-app exchange.