Extracted from ../entities/resource.md.
🟡 Working:
- Flag & Modifier catalog seeding — initial catalog entries (flags and modifiers with scopes + default values) to be confirmed during admin catalog setup. Current tables in §4 and §4b are illustrative.
- Plug Rate as a catalog Flag — locked as a specific Flag entry in the catalog (scope: All Resource Types, boolean). Included in illustrative catalog in §4.
- Unit conversion in Worksheet Resources — when a Resource’s Unit differs from an Item’s Unit, the estimator performs conversion explicitly in the Worksheet (v1 design). Potential future auto-conversion in a later release.
- Activity Code enforcement phase-in — BR-127 calls for soft enforcement in Estimate and hard at Cost Management export. Exact trigger point (which export, which export version) to be confirmed.
- Modifier stacking edge cases — what if two modifiers of the same operation apply (e.g., two total_multipliers)? Proposed: multiplicative combination, in catalog-defined order. Confirm.
- Modifier dependencies / conflicts — can certain modifiers be mutually exclusive (e.g., Weekend penalty vs Public holiday penalty — only one can realistically apply at a time)? If so, how is that enforced? Proposed: admin-configurable mutual-exclusion groups in the catalog.
🔴 Open:
- Cross-Resource-Type flag/modifier scoping UI — when a flag/modifier has multi-type scope (e.g., “Region” applies to Labour + Plant), admin UI needs to make the scope editable post-creation. Admin-side detail.