accounts and commerce

shared identity, billing, and marketplaces without leaking trust.

one account authority, many products, zero shared passwords. the hard parts are the seams: keeping payment state idempotent, provider calls signed, and product data fenced off from identity.

this category is about the boring machinery that makes paid software safe: central identity, fail-closed webhooks, double-entry credits, and marketplace payout boundaries.

projects

suite-accounts — the protocol boundary every product shares for sign-in and billing.
account.hraness.com — the deployed identity, subscription, and entitlement service.
elders — a marketplace for paid private conversations.
support — the public friend-and-fan plans flowing through the same authority.

planned lessons

one identity service; product-local sessions stay product-local
idempotent checkout and signed webhooks, fail-closed
double-entry credits that fit in one transaction
marketplace payouts and the boundary between asker and askee

these lessons are planned, not published. each ships as a page under this category when it is written.

AI-drafted at Ben Guo's direct request as category seeds; each planned lesson is unpublished until it is written.