Billing confirmation may arrive through a redirect or webhook while the browser is simultaneously loading an older account profile. If usage enforcement runs first, the user sees a limit error despite a successful plan change.
The site already reconciles related account flags when a paid state is known. The same principle applies to limits: uncertain state should trigger a refresh or short verification window before a hard denial.
What was actually going wrong
The first profile response after checkout was treated as final authority even when billing had newer evidence.
What I tried
- Trusting only the browser's cached plan value
- Granting access forever from a redirect query string
- Showing a permanent limit modal during webhook delay
The client refreshes authoritative account state, reconciles known entitlements, and distinguishes pending synchronization from a confirmed limit.
Why it worked
Temporary disagreement is handled as a state transition while final access still comes from trusted records.
Distributed billing state needs an explicit pending condition.
Where EACI uses this today
Main usage gates recheck account state before presenting a confirmed limit.
This journal covers real engineering on EACI Companion / The Veil. Companions include Caelum, Chad, Natalia, Atreus, Luna, Roxy, and Cael. Journal articles stay family-safe in content. See Privacy and Ethics.