dashboard

INSTRUCTIONS.md

@@ -25,6 +25,7 @@ This repository implements the platform foundation milestone:
 6. Any non-filter UI that looks up records or items must use a searchable picker/autocomplete, not a long static dropdown.
 7. Inventory items must carry both `defaultCost` and `defaultPrice`; sales documents should default line pricing from the selected item `defaultPrice`.
 8. Maintain the denser UI baseline on active screens; avoid reintroducing oversized `px-4 py-3` style controls, tall action bars, or overly loose card spacing without a specific reason.
+9. Treat the landing page as `Dashboard`: a metric-oriented, modular command surface that should accumulate reusable operational panels over time.
 
 ## Operational notes
 
@@ -36,6 +37,7 @@ This repository implements the platform foundation milestone:
 - Back up the whole `/app/data` volume to capture both the database and attachments.
 - Treat searchable lookup as a standing UX requirement for inventory, BOM, sales, purchasing, manufacturing, customer, vendor, and other operational record-picking flows. Filter-only controls can still use dropdowns.
 - Extend the existing Puppeteer document pipeline when adding customer-facing or logistics PDFs instead of creating a parallel export mechanism.
+- Add future dashboard features as modular metric/action panels instead of one-off hero sections or static marketing-style content.
 
 ## Next roadmap candidates