purchasing-power register · bound register page

Separate a Nominal Raise from a Supplied Price-Index Change

A raise percentage and an inflation percentage do not subtract cleanly. Put the salary series and a dated, compatible price index on one register before discussing what changed in the compensation's modeled purchasing power.

1 · Review code | year | annual salary | price index

FIRST-LOAD

HYPOTHESIS / PROTOTYPE — checkout unavailable. Calculation is local. A draft is saved automatically in this browser profile when storage is available; Reset to sample clears it. Optional Pro history stores only five summaries and has its own deletion control. State links encode your inputs and can remain in browser history, clipboard or recipients’ records; share only non-sensitive rows. Optional external AI formatting leaves this device. The required site analytics beacon reports page activity; shared URLs contain encoded inputs. Do not treat an encoded URL as private. The calculator has no input-collection endpoint.

Data note: The purchasing-power register processes Review code | year | annual salary | price index locally. Starter/sample selection and Run compute in this tab; no input is sent by the calculator. A local draft may be saved; explicit state-link sharing or optional external AI formatting can disclose inputs. Use non-sensitive labels.

Perspective: Before: nominal raise and inflation percentages were casually subtracted. After: compatible salary/index observations produce inspectable deflated endpoints.

2 · Read the purchasing-power register

Compensation/index arithmetic only, not financial, tax or employment-law advice. Verify the price series and salary basis; consult a qualified financial adviser or workplace representative before using this comparison in a consequential decision.

Paid layer: purchasing-power register filing layer

one-time step · the free reading above stays complete

hidden patterns detected after your first run

Free tier

one complete unwatermarked purchasing-power register run in the app
three labeled samples and unlimited article-demo calculations
complete result text and a user-triggered input-state link

What $4 one-time adds

unlimited subsequent purchasing-power register app calculations after a local convenience signal
print the purchasing-power register with visible assumptions and its safety boundary
CSV of the displayed % real endpoint change and row workings; conditional estimate uses your manual-retyping minutes
five local reading summaries (headline/count/time), not saved full inputs or cross-device backups

HYPOTHESIS / PROTOTYPE: $4 is a proposed one-time price for filing the purchasing-power register, not a current sales offer. No measured time saving or buyer demand is claimed. The optional manual-retyping baseline above estimates one export’s retyping budget only; it does not change the calculation or guarantee savings.

Local history (this device)

No saved runs yet — your first run files here.

Filing prototype — checkout unavailable

Checkout is unavailable. Browser-local, profile-scoped convenience gating is best-effort, not server-verified access. A URL or browser flag is not proof of payment. Clearing browser data removes local state; no account or cross-device recovery is provided.

Optional filing controls are a local prototype.

Checkout is unavailable. The reading above is complete; print, CSV and five local summaries are optional enhancements, not hidden answers.

Before using the purchasing-power register

Use one currency, one annual-salary convention and one comparable price-index series across all rows. An index is a relative basket measure, not the inflation experienced by every household. Geographic coverage, period definition and revisions matter; obtain those details from your chosen source. The app does not fetch an official index or validate a salary statement. Years must be increasing from 1900 through 2200, and at least two observations are needed for endpoint change. Salary and index must both be positive. A base of 100 only sets the units of displayed deflated salaries. It does not imply that the first observation's index is 100, or that the tool has verified an inflation rate for that year.

Boundary and sources

Method: For each row, multiply nominal salary by the entered display base and divide by that row's price index. Compare the last deflated salary with the first: last/first minus one, multiplied by 100. This ratio handles compounding. Rows preserve both source quantities so a change in the index can be inspected separately from a change in pay.
All sample records, dates, quantities and labels are invented. No outside policy, contract, rate, clock offset, measurement or accessibility standard is represented as verified.
Google’s official pricing documentation, fetched 2026-10-01, says AI Studio is free in available regions. Optional formatting may require a Google account; manual local entry requires none. Limits can change and free-tier content may be used to improve products. Do not send private records.

Mechanism: competence-autonomy-loop

Optional AI formatting, never the calculation

Manual entry completes this purchasing-power register for free without signup. If available to you, the free AI Studio interface linked in the sources may format fictional or non-sensitive notes; external access may require an account. No API key or AI call is built into this tool. Free-tier content may be used to improve products. Review each cell and transcribe it to the labeled row schema; do not paste the JSON object into the row box.

Format only these fictional or non-sensitive notes for a purchasing-power register. Return strict JSON shaped as {"rows": [{"label": "string", "cells": ["string", "string", "string"]}], "setting": "string"}. The columns are Review code | year | annual salary | price index; the setting is Price-index base for expressing comparable salary. Keep all supplied strings and quantities exactly; do not calculate, infer missing entries, invent dates or add advice. If any required value is missing, return an empty rows array and ask me for it separately. I will verify every cell against my source and manually transcribe rows using vertical bars before running the local calculator.

An AI response is not executed, fetched or trusted as a result. Missing values remain questions; the strict local parser checks the rows you actually enter.