refinement
This commit is contained in:
@@ -104,6 +104,9 @@ If implementation changes invalidate those docs, update them in the same change
|
||||
- Purchase-order item lookup must only expose inventory items flagged as purchasable
|
||||
- Customer-facing and logistics PDFs should continue to use the backend documents module and Puppeteer pipeline
|
||||
- The landing experience should remain `Dashboard`, not `Overview`, and should evolve as a modular metric-first operational surface
|
||||
- Projects should be treated as a first-class future domain that anchors long-running program execution across CRM, sales, inventory, purchasing, shipping, and planning
|
||||
- Manufacturing should remain a separate future domain for work orders, routings, labor, and shop-floor execution
|
||||
- Planning should remain the scheduling/visibility layer over projects and manufacturing, not a replacement for either
|
||||
|
||||
## Feature expectations
|
||||
|
||||
@@ -112,8 +115,8 @@ Near-term priorities are:
|
||||
1. Purchase receiving flow and vendor-side operational depth
|
||||
2. Sales and purchasing PDF templates
|
||||
3. Shipping labels, bills of lading, and logistics attachments
|
||||
4. Live manufacturing gantt scheduling
|
||||
5. Audit and operations maturity
|
||||
4. Projects and program management
|
||||
5. Manufacturing execution
|
||||
|
||||
When adding new modules, preserve the ability to extend the system without refactoring the existing app shell.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user