jason/mrp
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

refinement

Browse Source
This commit is contained in:
jason
2026-03-15 01:05:54 -05:00
parent 9d8f6767fb
commit d9b60859d9
5 changed files with 121 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
INSTRUCTIONS.md
View File

@@ -29,6 +29,8 @@ This repository implements the platform foundation milestone:
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.
10. Purchase-order item selection must be restricted to inventory items where `isPurchasable = true`.
11. Treat future `Projects` work as a first-class cross-module domain tying together CRM, sales, inventory, purchasing, shipping, and planning; do not bury it as a one-off manufacturing subfeature.
12. Keep `Projects`, `Manufacturing`, and `Planning` distinct: projects are long-running program records, manufacturing is execution, and planning is scheduling/visibility.
## Operational notes
@@ -41,11 +43,15 @@ This repository implements the platform foundation milestone:
- 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.
- When implementing projects, model the relationships explicitly so project records can anchor execution across customer, order, material, schedule, and shipment workflows.
- When implementing manufacturing, keep work orders, routings, labor, and shop-floor execution in their own domain rather than collapsing them into projects.
## Next roadmap candidates
- purchase receiving flow and vendor-side operational depth
- sales and purchasing document templates
- shipping labels, bills of lading, and logistics attachments
- manufacturing gantt scheduling with live project data
- projects and program management
- manufacturing execution
- planning and gantt scheduling with live project/manufacturing data
- broader audit and operations maturity