docs: refine roadmap and article data architecture
This commit is contained in:
@@ -221,6 +221,17 @@ Important data rule:
|
||||
- Article data is generated from ERP-derived sources.
|
||||
- These values should not be manually changed unless the task is explicitly data maintenance.
|
||||
|
||||
Article-data architecture decision:
|
||||
|
||||
- Article data should evolve from a simple article catalogue into a shared production knowledge base.
|
||||
- Each article may optionally provide production-related default values.
|
||||
- Initial defaults include `Product Thickness`, `Area Weight`, `Core Diameter`, and `Roll Width`.
|
||||
- Future production-related defaults can be added without changing the overall architecture.
|
||||
- When an article is selected, available defaults are copied into the calculator fields.
|
||||
- Missing optional values must never overwrite existing user input.
|
||||
- All automatically populated values remain editable by the user.
|
||||
- The planned Article-Data-Admin application will become the authoritative editor for these production defaults.
|
||||
|
||||
Known domain caveat from existing project notes:
|
||||
|
||||
- For articles in the groups Secugrid, Combigrid, Carbofol MF/MF, Carbofol F/F, Carbofol s/F, and Carbofol BF/s, the thickness from `article-data.json` must not be used without domain validation.
|
||||
|
||||
Reference in New Issue
Block a user