Builder's guide · Section 14

A recommended build order

Build in chunks. Each chunk ends with screens someone can click through, tests, and a short “what to try” note for the owner. Review each before starting the next.

#ChunkWhat gets built
1Foundations and shellConsole server, sign-in, people and roles, the relay, company switcher, navigation, the command palette, drill-down panel, audit trail
2General ledgerChart of accounts, control mapping, periods, manual journals, trial balance with drill-down
3BankingBank accounts, transactions, transfers, statement import, reconciliation
4Master dataCustomers, vendors, products, units, warehouses, tax; opening balance screens
5–7Procure to payPurchase orders with approvals, receiving and put-away, bills, holds, payments, AP aging
8ProductionRecipes, production orders, component issues, finished goods, labor, variances (if you make things)
9–11Order to cashSales orders and credit, picks and shipping, invoices, receipts, credits, dunning, AR aging
12Assets and leasesRegister, depreciation, disposals, leases
13Reporting and closeStatements, notes, the tie-outs page, the close checklist
14A realistic yearA simulator that posts a year of activity through the API, so the books look lived-in; reset and snapshot
15+OptionalGroup companies and intercompany trade; voice or AI assistance through the command registry

Skip what your business doesn't do. A services firm might need only chunks 1–4, 9–11 and 13. If you prefer fewer review stops, review procure-to-pay and order-to-cash each as one cycle.

When the API is missing something

Sometimes a screen needs a read the API doesn't offer yet, such as a list, a field it stores but doesn't return, or a typed row. Write the gap down (the reference console keeps docs/api-gaps.md), work around it in one place, and raise it with the GAAPcore maintainers. Several GAAPcore routes, for example the journal registers, exist because a console asked for them.