BrewKeeper · Pending changes · Local preview · 9 November 2026

Edit conversions after use.
Keep recorded usage intact.

This separate storyboard follows the pending change that lets brewers update a raw material's conversion even after batches have used it.

17 current browser capturesFictional local test dataUncommitted feature preview
Earlier feature storyboard, preserved at its original URL
Recorded 500 mL → 0.625 kgThe original use keeps 0.8 L/kg
Future 500 mL → 0.5 kgNew execution uses the new 1 L/kg
Editing the rate moves no stockHistorical quantities and costs remain recorded

Previously, actual use locked the product conversion. The pending design lets the product setting change and keeps the conversion used by each recorded addition. Notices explain any difference between that recorded conversion and today's setting.

Turning volume defaults off changes the default for new entries. Existing quantities and units remain intact, and the saved conversion is retained for existing volume entries.

A setting change is not a retrospective inventory correction. It does not rewrite warehouse movements, recorded quantities or historical costs. Any correction to existing stock needs a separate, deliberate inventory action.

An inventory amendment still changes the recorded brewing dose using its original conversion. In this example, correcting removal to 0.5 kg produces a 400 mL dose at the original 0.8 L/kg. To change stock while keeping the dose unchanged, record a separate warehouse adjustment.

The pending workflow

Follow one dose through a conversion change

The main sequence uses the actual browser forms for the original dose, configuration edit, amendment and later execution. The cellar and yeast chapters show the same history protection in their own screens. Click any screenshot to enlarge it.

Checks and practical limits
Verification

What this preview checks

Pending, uncommitted working tree based on e17555081. Captured locally on 9 November 2026. Counts below are separate runs and overlap; this is a focused preview, not a full release certification.

ResultCheck
passed Browser workflow and captures
4 scenarios, 113 assertions; no failures or errors. 17 screenshots.
Command and output
mise exec ruby@3.2.8 -- env BK_TEST_DATABASE=agent PARALLEL_WORKERS=1 SCHEMA=/tmp/brewing_snapshot_structure.sql BK_CONVERSION_STORYBOARD_OUTPUT=/Users/paul/src/kbc/brewkeeper/docs/reports/brewing-conversion-edits-2026-11-09 bin/rails test test/system/production/brewing_conversion_edits_storyboard_test.rb
Captured output
passed Focused configuration, history, yeast, reporting and migration checks
269 tests, 1,675 assertions; no failures or errors.
Command and output
SCHEMA=/tmp/brewing_snapshot_structure.sql bin/rails-test-agent test test/models/product_brewing_units_test.rb test/services/production_brewing_units_test.rb test/services/yeast_service_test.rb test/migrations/record_brewing_conversions_on_usage_test.rb test/components/production/brewing_conversion_notice_component_test.rb test/controllers/production/raw_materials_controller_test.rb test/controllers/production/inventory_amendments_controller_test.rb test/models/production/reports/batch_turn_material_totals_test.rb test/models/production/reports/production_ledger_test.rb
Captured output
passed Served JavaScript build
esbuild completed before the browser captures.
Command and output
mise exec ruby@3.2.8 -- yarn build
Captured output
passed Gallery rendering and controls
All 17 images decoded. Filters, enlargement and keyboard navigation passed; no desktop or narrow-screen horizontal overflow.
Command and output
mise exec ruby@3.2.8 -- bundle exec ruby docs/reports/brewing-conversion-edits-2026-11-09/verify_gallery.rb
Captured output

Rules behind the screens

CasePending behaviourEvidence
Edit after actual useFactor and basis remain editable. Past stock, dose and cost records are not recomputed.Frames 03–06; product and execution tests
New executionA future 500 mL dose at 1 L/kg consumes 0.5 kg; the previous dose retains its original conversion.Frames 09, 12
Historical noticesShow recorded/current rates, entered quantity and original warehouse equivalent where they differ.Frames 06–08, 20–22; notice component tests in English/Japanese
Default toggleTurning volume defaults off keeps the rate and saved mL recipe/plan/usage units.Frames 13–14; product and controller tests
AmendmentsA 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 reportsHistorical 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/substitutionsRetain the actual ingredient conversion; product edits do not rewrite brink yeast volume.Frame 21; yeast service regression tests
Purchased yeastConsumption captures the product rate. A draft uses live settings, and later edits do not reinterpret consumed stock.Frame 22; production service tests
Untracked/native useNo physical movement is fabricated. Explicitly captured native usage is not retrospectively assigned a new conversion.Service and conversion-notice component tests
Remaining guardsSaved execution conversions remain immutable; used source units and inventory categories stay protected. Pending volume plans cannot be stranded.Product, controller, service and migration checks
MigrationSchema-only addition of conversion facts; no historical quantity or stock backfill. Reversal and database constraints are checked.RecordBrewingConversionsOnUsageTest
Scope and limits

This is a local preview of pending, uncommitted changes. It is not a deployed release announcement. Fictional transactional fixtures run in the isolated agent test database. Development and production customer records are not edited.

Recipe, batch, task and stock preparation uses application services. The purchased-yeast knockout is service-backed; the associated history screen is captured in the browser. Other captions identify the actual user actions and database assertions. The scope is conversion editing after usage, rather than a repeat of the complete original feature report.

Recorded conversions remain protected from in-place edits. The inventory-category guard and protection of source units referenced by actual use remain in force. The schema-only migration does not rewrite old stock or backfill historical conversions. Component and service checks cover native and untracked history, substitutions and guard conditions that are not each illustrated by a separate capture.