The strongest systems here start with operational truth: what makes a
transaction unique, which event may advance it, what can safely repeat,
and where a person needs to decide.
WordPress is often the application host, but the engineering work is
custom backend behavior: data models, signed boundaries, lifecycle
rules, REST interfaces, atomic writes, third-party coordination, and
operational recovery.
Technical descriptions are derived from inspected implementation
evidence. First-person ownership and operating context are Jake's
account. Diagrams are reconstructed, and no raw client data, source,
workflow exports, production logs, or private endpoints are published.