salt-label receipt · till receipt with a tear-off foot

Reconcile Salt-Gram and Sodium-Milligram Labels at the Weight Eaten

A jar can list salt in grams while a carton lists sodium in milligrams. Add those printed numbers directly and the total has no meaning. This receipt makes the label convention and portion mass visible before combining anything.

1 · Food code | sodium or salt | label amount per 100 g | grams eaten

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 salt-label receipt processes Food code | sodium or salt | label amount per 100 g | grams eaten 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: salt and sodium label numbers were added without a common unit. After: each eaten portion carries its label convention and converted milligrams.

2 · Read the salt-label receipt

Label-conversion arithmetic only, not nutrition or treatment advice. Confirm the label basis and any medically relevant intake goal with a registered dietitian or qualified clinician; do not change a prescribed diet from this tally.

Paid layer: salt-label receipt filing layer

one-time step · the free reading above stays complete

hidden patterns detected after your first run

Free tier

one complete unwatermarked salt-label receipt 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 salt-label receipt app calculations after a local convenience signal
print the salt-label receipt with visible assumptions and its safety boundary
CSV of the displayed mg sodium-equivalent 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 salt-label receipt, 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 salt-label receipt

Use only labels expressed per 100 grams and portions measured in grams. A per-serving label needs a verified serving-mass conversion before it belongs in this log; a liquid per-100-milliliter label cannot silently become a per-100-gram label. The supplied 400 mg-per-gram model corresponds to dividing salt grams by 2.5 and converting grams to milligrams. It is a labeling convention, not a test of a food's chemical composition. Change it only to match a verified convention in your source. No recommended daily ceiling is built in. This tool is useful for organizing a conversation about labels, particularly when records from different countries use different terms, without determining what anyone should eat.

Boundary and sources

Method: For a sodium row, multiply its mg-per-100-g amount by portion grams divided by 100. For a salt row, first multiply salt grams by the supplied sodium-mg-per-salt-g factor, then use the same portion fraction. Sum the resulting milligram quantities only after both conversions; the row notes retain the original type and factor.
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 salt-label receipt 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 salt-label receipt. Return strict JSON shaped as {"rows": [{"label": "string", "cells": ["string", "string", "string"]}], "setting": "string"}. The columns are Food code | sodium or salt | label amount per 100 g | grams eaten; the setting is Sodium milligrams per gram of salt under your label convention. 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.