Metering

Six invariants, and they are the product

verification is never metered — No product may meter, gate, or charge for verification. It is a permanent commitment in the Terms of Service §3 and §14, it survives a change of owner, and it is the product. A paywall belongs on PRODUCING a record, never on CHECKING one.

records outlive billing — A sealed record keeps verifying when a subscription lapses, a card fails, or the account closes. Records are never hostage to billing. A vendor who can switch off a customer's evidence is a vendor whose evidence was never the customer's.

the invoice is re derivable — Where a charge is metered, the customer must be able to recount it from their OWN ledger without our systems. An invoice a customer cannot check is an assertion — which is exactly what this estate exists to refuse. Selling re-derivable decisions and issuing unauditable invoices is a contradiction a buyer will notice.

upgrades are not retroactive — An upgrade changes what may be done next. It does not re-price, re-seal, or re-classify anything already sealed. A downgrade does not invalidate what a higher tier produced.

payment data never enters a record — Card details, billing identity, tax identifiers and payment events are never fields of a sealed record and never evidence. A usage event is not evidence; a payment event is not evidence.

the first one is free — Every product lets a person produce at least one real record before any payment surface appears. A product whose argument is 'do not take our word for it' cannot require a card before it is checkable.

What this page does not do

There is no usage chart, no invoice history and no payment form, and there is no metering code anywhere in this tree — zero lines. The generator that writes the delivery pages says so itself: it names reconciliation, entitlement gating and dunning, and it does none of them. This page states the register and stops.