| Edit after actual use | Factor and basis remain editable. Past stock, dose and cost records are not recomputed. | Frames 03–06; product and execution tests |
| New execution | A future 500 mL dose at 1 L/kg consumes 0.5 kg; the previous dose retains its original conversion. | Frames 09, 12 |
| Historical notices | Show recorded/current rates, entered quantity and original warehouse equivalent where they differ. | Frames 06–08, 20–22; notice component tests in English/Japanese |
| Default toggle | Turning volume defaults off keeps the rate and saved mL recipe/plan/usage units. | Frames 13–14; product and controller tests |
| Amendments | A corrected 0.5 kg movement becomes 400 mL at the recorded 0.8 L/kg, even with a current 1 L/kg setting. | Frames 10–11; amendment and undo tests |
| Cost and reports | Historical records use the captured conversion; product-rate changes do not silently restate recorded costs and material totals. | Main browser scenario; service, ledger and statutory-total tests |
| Brink additions/substitutions | Retain the actual ingredient conversion; product edits do not rewrite brink yeast volume. | Frame 21; yeast service regression tests |
| Purchased yeast | Consumption captures the product rate. A draft uses live settings, and later edits do not reinterpret consumed stock. | Frame 22; production service tests |
| Untracked/native use | No physical movement is fabricated. Explicitly captured native usage is not retrospectively assigned a new conversion. | Service and conversion-notice component tests |
| Remaining guards | Saved execution conversions remain immutable; used source units and inventory categories stay protected. Pending volume plans cannot be stranded. | Product, controller, service and migration checks |
| Migration | Schema-only addition of conversion facts; no historical quantity or stock backfill. Reversal and database constraints are checked. | RecordBrewingConversionsOnUsageTest |