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

next slice

Browse Source
This commit is contained in:
jason
2026-03-15 09:22:39 -05:00
parent 18e4044124
commit ce21ad4a4c
13 changed files with 708 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
AGENTS.md
View File

@@ -25,13 +25,14 @@ MRP Codex is a modular Manufacturing Resource Planning platform intended to be a
Read these before major work:
- [CHANGELOG.md](D:/CODING/mrp-codex/CHANGELOG.md)
- [README.md](D:/CODING/mrp-codex/README.md)
- [INSTRUCTIONS.md](D:/CODING/mrp-codex/INSTRUCTIONS.md)
- [STRUCTURE.md](D:/CODING/mrp-codex/STRUCTURE.md)
- [ROADMAP.md](D:/CODING/mrp-codex/ROADMAP.md)
- [UNRAID.md](D:/CODING/mrp-codex/UNRAID.md)
If implementation changes invalidate those docs, update them in the same change set.
If implementation changes invalidate those docs, update them in the same change set. Keep `CHANGELOG.md` current for shipped features, behavior changes, and notable operational updates.
## Architecture rules
@@ -113,11 +114,11 @@ If implementation changes invalidate those docs, update them in the same change
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. Projects and program management
5. Manufacturing execution
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
When adding new modules, preserve the ability to extend the system without refactoring the existing app shell.
@@ -135,7 +136,7 @@ If you cannot run one of those checks, say so explicitly.
## Git and workflow expectations
- Keep commits focused and source-only; do not commit generated local build artifacts
- Update roadmap/docs when major work shifts priorities or architecture
- Update roadmap/docs and `CHANGELOG.md` when major work shifts priorities, architecture, or shipped functionality
- Do not remove or overwrite user changes without explicit instruction
- If a task reveals a persistent operational issue, document it rather than leaving it tribal knowledge