A good result is published with the same precision as a discrepancy.
We compare the service outcome and connections after refusal with the state before choice. A non-observation remains a non-observation; it does not become a claim that a service can never appear.
Payment remained available and no additional destination appeared.
Select a state to compare the three sources at the same moment. All states remain available when JavaScript is disabled or the receipt is printed.
The app displayed the fee and options without optional services.
The policy describes only service infrastructure and the payment processor.
The store label declares financial data for functionality.
Only config.platitest.example and api.platitest.example were observed.
connection observedLimit: The test does not establish what unexercised features might use.
There was no analytics choice; optional notifications were refused without affecting payment.
The policy separates notifications from core payment.
The store label describes notifications as optional.
Payment remained available and no additional destination appeared.
service outcome and connectionsLimit: This does not establish that every future notification is impossible.
The test payment was initiated and cancelled before bank authorisation.
The policy names the fictional processor and data categories.
The store label declares financial information.
The synthetic token INV-TEST-884 was observed going to pay.example; no card data was entered.
exact synthetic tokenLimit: The test did not proceed through the bank processor page.
Analytics withdrawal was not applicable. No account was created.
The policy describes payment without an account.
The store label says deletion can be requested.
No account or persistent identifier was created in the tested journey.
local and network observationLimit: Absence of an account does not establish server-side payment-log retention.
A domain, infrastructure owner and legal recipient are different propositions. Each relationship carries its own provenance state.
api.platitest.examplefirst partyThe test fee code and amount were observed.
pay.exampleprocessorThe synthetic payment reference was observed; no card details were entered.
Claims are stored separately so a response, correction or retest can change one proposition without silently rewriting the rest.
Maximum wording: We can describe consistency in this journey, not certify the whole app.
The actor, minimum change and verification test remain attached to the original claim.
No repair is required by this calibration result.
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
A real receipt would link every public claim to a sanitised evidence artefact and retain raw captures in a restricted vault.