AI Should Explain Your Business Before It Tries to Run It
Why enterprise AI should start with permission-scoped explanations, evidence and draft actions before it is allowed to execute consequential business operations.
Long-form technical writing on software architecture, infrastructure, AI, mobility and the operational questions behind technology.
Why enterprise AI should start with permission-scoped explanations, evidence and draft actions before it is allowed to execute consequential business operations.
Retries are inevitable. Duplicate money movement is not. A practical look at idempotency keys, concurrency, webhook deduplication, ledgers and reconciliation.
A first-person field note on why an overly rigid third-party verification journey became a product problem, and how I built document recognition around OCR, MRZ parsing, guided capture and address intelligence instead.
A production field note on tracing a receipt failure across different thermal printers, isolating the transport boundary and deploying one compatibility fix across a multi-branch operation.
Enterprise software is about authority, approvals, auditability, reversibility, branch boundaries and operational control, not the number of modules on a feature sheet.
Offline should not mean pretending transactions succeeded. A practical architecture for drafts, retry queues, idempotency, conflict handling, reconciliation and server-confirmed finality.