projects

README.md

@@ -19,7 +19,8 @@ Current foundation scope includes:
 - purchase orders with searchable vendor and SKU entry, restricted to purchasable inventory items
 - purchase receiving with warehouse/location posting and receipt history against purchase orders
 - branded quote, sales-order, and purchase-order PDFs through the shared backend document pipeline
-- shipping shipments linked to sales orders with packing-slip PDFs
+- shipping shipments linked to sales orders with packing slips, shipping labels, bills of lading, and logistics attachments
+- projects with customer/commercial/shipment linkage, owners, due dates, notes, and attachments
 - file storage and PDF rendering
 
 ## Product Map
@@ -31,21 +32,21 @@ Current completed foundation areas:
 - inventory foundation
 - sales and purchasing foundation
 - shipping foundation
+- projects foundation
 - branding, attachments, auth/RBAC, and PDF infrastructure
 
 Planned cross-module execution areas:
 
-- projects and program management
 - manufacturing execution
 - planning and gantt scheduling
 
 Near-term priorities:
 
-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-facing operational depth
-5. Sales approvals and revision history
+1. Manufacturing execution
+2. Vendor invoice/supporting-document attachments and broader vendor-facing operational depth
+3. Sales approvals and revision history
+4. Planning and gantt scheduling with live project/manufacturing data
+5. Inventory transfers, reservations, and deeper stock controls
 
 Revisit / deferred items:
 
@@ -54,7 +55,6 @@ Revisit / deferred items:
 - sales approvals and revision history
 - inventory transfers, reservations, and deeper stock controls
 - deeper audit-trail coverage
-- projects are not yet first-class records even though planning/manufacturing flows will need them
 
 Dashboard direction:
 
@@ -63,7 +63,8 @@ Dashboard direction:
 - new modules should add reusable dashboard cards/panels instead of replacing the whole layout
 - future additions should emphasize relevant metrics, next actions, alerts, and workflow shortcuts
 - richer recent-activity widgets and exception queues are a planned QOL follow-up, not a separate landing-page redesign
-- projects should eventually feed dashboard widgets for active jobs, overdue milestones, shortages, and shipment readiness
+- projects now feed dashboard widgets for active programs, overdue work, and risk
+- future project widgets should deepen milestones, shortages, and shipment readiness
 
 Navigation direction:
 
@@ -73,18 +74,21 @@ Navigation direction:
 
 ## Projects Direction
 
-Projects should become the long-running program and delivery layer tying together commercial work, engineering context, purchasing, manufacturing, shipping, and customer-facing execution.
+Projects are now the long-running program and delivery layer for cross-module execution. The current slice ships project records with customer linkage, owner assignment, priority, due dates, notes, commercial document links, shipment links, attachments, and dashboard visibility.
 
-Planned interactions:
+Current interactions:
 
 - CRM: each project should link to a customer account and relevant contacts
-- Sales: quotes and sales orders should be able to spawn or attach to projects
+- Sales: quotes and sales orders can already attach to projects
+- Shipping: shipments tied to project deliverables are visible from the project record
+- Dashboard: projects now contribute status, risk, backlog, and overdue widgets
+
+Next expansion areas:
+
 - Inventory: projects should reference item/BOM scope and later expose shortages or allocations
 - Purchasing: project material demand should be visible to purchasing and receiving workflows
-- Shipping: shipments tied to project deliverables should be visible from the project record
 - Manufacturing: work orders should link back to projects without turning projects into the manufacturing module
 - Planning: project milestones and execution dates should feed gantt scheduling and dependency views
-- Dashboard: projects should contribute status, risk, backlog, and milestone widgets
 
 ## Manufacturing Direction
 
@@ -252,12 +256,12 @@ The current shipping foundation supports:
 - shipment quick status actions from the shipment detail page
 - related-shipment visibility from the sales-order detail page
 - branded packing-slip PDF rendering from shipment detail pages
+- branded shipping-label and bill-of-lading PDF rendering from shipment detail pages
+- logistics attachments directly on shipment records
 
 QOL direction:
 
-- shipment labels
-- bills of lading
-- logistics attachments and reprint/history actions
+- reprint/history actions for generated logistics PDFs
 - partial-shipment and split-shipment UX
 
 This module introduces `shipping.read` and `shipping.write` permissions. After updating the code, restart the server against the migrated database so bootstrap can upsert the new permissions onto the default administrator role.
@@ -303,17 +307,18 @@ As of March 14, 2026, the latest committed domain migrations include:
 - inventory default price support
 - sales totals and commercial fields
 - shipping foundation
+- projects foundation
 
 Recent roadmap-driving migrations should always be applied before validating new CRM, inventory, sales, shipping, or purchasing features in a running environment.
 
 ## UI Notes
 
 - Dark mode persistence is handled through the frontend theme provider and should remain stable across page navigation.
-- The shell layout is tuned for wider desktop use than the original foundation build, and now exposes Dashboard, CRM, inventory, sales, shipping, settings, and planning modules from the same app shell.
+- The shell layout is tuned for wider desktop use than the original foundation build, and now exposes Dashboard, CRM, inventory, sales, shipping, projects, settings, and planning modules from the same app shell.
 - The active module screens now follow a tighter density baseline for forms, tables, and detail cards.
 - The dashboard should continue evolving as a modular metric board for future purchasing, shipping, manufacturing, and audit data.
 - The client build still emits a Vite chunk-size warning because the app has not been code-split yet.
 
 ## PDF Generation
 
-Puppeteer is used by the backend to render HTML templates into professional PDFs. The current PDF surface includes the branded company-profile preview, sales quotes, sales orders, purchase orders, and shipment packing slips. The Docker image includes Chromium runtime dependencies required for headless execution.
+Puppeteer is used by the backend to render HTML templates into professional PDFs. The current PDF surface includes the branded company-profile preview, sales quotes, sales orders, purchase orders, shipment packing slips, shipping labels, and bills of lading. The Docker image includes Chromium runtime dependencies required for headless execution.