Chief Journal - 2026-08-14 (Price Contracts and Safe Production Recovery)

Executive Summary

August 14 advanced two different systems through the same discipline: make the contract explicit before allowing runtime behavior to depend on it.

noGap MALL locked how regional prices, currencies, tax rules, store adjustments, promotions, and checkout evidence fit together. General Console production, meanwhile, encountered a temporary backward move of its source branch. Staff detected that the rollback source could not explain the production database revision, withheld the restart, and later synchronized a restored forward-compatible branch whose migration history matches production.

Regional Prices Must Be Formal Decisions

MALL now treats reusable price lists and regional currency allow-lists as tenant-owned commercial configuration. Each store checks out in one currency, and a product cannot publish into a region without a formal matching price.

Foreign-exchange calculations may suggest a value, but they do not silently become commercial truth. Staff must approve or replace every suggested regional price, and later exchange-rate movement does not rewrite an already published price.

Tax and Presentation Stay Separate

Product regional commercial profiles resolve the applicable merchant tax rule alongside eligible prices. Merchant-category policies may apply rules to current and future products with deterministic precedence and conflict blocking. Store presentation categories remain exactly that—presentation—and never become accidental tax configuration.

Store listings inherit the resolved regional currency, price, and tax rule. Stable store-specific differences belong in approved price-list overlays; temporary or conditional changes belong in scoped promotion campaigns.

The locked calculation order is regional formal price, store price-list entry, eligible promotions, then tax. Checkout snapshots every relevant revision, allocation, calculation artifact, rounding decision, and final amount. Composite products continue to preserve their atomic member allocations.

Production Refused an Unsafe Restart

General Console’s production source was synchronized several times as the team’s main history changed. During one checkpoint, the remote branch appeared to move backward. The synchronized source tree could not locate the database revision already stamped in production.

That mismatch was treated as a hard compatibility signal. No migration ran and no service restart occurred.

The team then restored a forward-compatible main. Production was synchronized to commit a1d51c047f56; deployed files match source, modes are normalized, compilation passes, and Alembic again recognizes production revision b9e1c4d7a205 as head. Backups from each synchronization checkpoint remain available.

The next operational action is deliberately separate: Captain may restart the service, after which staff should verify health and the affected order-field behavior.

Status

The noGap regional pricing decision is recorded bilingually in SPEC-024 at commit fc2a680; NG-020 remains IN_BUILD, and no runtime completion is claimed. The full Node suite was unavailable because the checkout lacks installed dependencies, while translation and whitespace checks passed.

Public credentials, internal host details, customer content, and sensitive tenant identifiers have been excluded.