projects
This commit is contained in:
15
AGENTS.md
15
AGENTS.md
@@ -17,7 +17,8 @@ MRP Codex is a modular Manufacturing Resource Planning platform intended to be a
|
||||
- CRM customers/vendors, hierarchy, contacts, lifecycle metadata, and attachments
|
||||
- inventory items, BOMs, warehouses, locations, transactions, item attachments, and item pricing
|
||||
- sales quotes, sales orders, and purchase orders
|
||||
- shipping shipments and packing-slip PDFs
|
||||
- shipping shipments, packing-slip PDFs, shipping labels, bills of lading, and logistics attachments
|
||||
- projects with customer/commercial/shipment linkage, owners, due dates, notes, and attachments
|
||||
- Puppeteer PDF foundation
|
||||
- single-container Docker deployment
|
||||
|
||||
@@ -105,7 +106,7 @@ 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
|
||||
- Projects are a first-class domain that anchors long-running program execution across CRM, sales, inventory, purchasing, shipping, and planning, and future work should continue extending that module rather than scattering project state elsewhere
|
||||
- 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
|
||||
- New top-level modules added to shell navigation should ship with a matching SVG icon, not text-only nav entries
|
||||
@@ -114,11 +115,11 @@ If implementation changes invalidate those docs, update them in the same change
|
||||
|
||||
Near-term priorities are:
|
||||
|
||||
1. Shipping labels, bills of lading, and logistics attachments
|
||||
2. Projects and program management
|
||||
3. Manufacturing execution
|
||||
4. Vendor invoice/supporting-document attachments and broader vendor-side operational depth
|
||||
5. Sales approvals and document revision history
|
||||
1. Manufacturing execution
|
||||
2. Vendor invoice/supporting-document attachments and broader vendor-side operational depth
|
||||
3. Sales approvals and document revision history
|
||||
4. Planning and gantt scheduling with live project/manufacturing data
|
||||
5. Inventory transfers, reservations, and deeper stock controls
|
||||
|
||||
When adding new modules, preserve the ability to extend the system without refactoring the existing app shell.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user