Browse 11 articles tagged approvals across approvals, auditability, plugins, and controlled AI operations.
The configuration underneath an approval gate - durable resume and revalidation, role separation as policy, building gated actions, and the problems still open.
Read Approval Design: Durability, Policy, and Plugins →A single AI-recommended customer refund moves through a two-person review gate, from recommendation to execution record, on real screens inside Latch.
Read Approval Design in Practice: One Refund, End to End →Case management authorization should support flexible rules, numeric thresholds, and audit-ready evidence on every sensitive action.
Read Authorization Logic Audits for Case Management →A plugin action runs on an external system from inside the case with role checks, governed approvals, and immutable audit logging.
Read What Is a Plugin Action? →Governance-first approval systems prove who approved an AI change and under which policy. They do not prove what happened on a specific runtime decision. Bot...
Read Governance-First Approval Systems for AI: What They Prove, What They Miss, and Where Runtime Evidence Fills the Gap →The runtime control layer combines built-in intelligence, governed execution, and immutable case audit trails for operational software.
Read The Runtime Control Layer: What This Category of Software Is and Why It Exists →Approval, authorization, and audit logic should be a carefully tested core, while AI-assisted plugins evolve around it safely.
Read Why Approval, Auth, and Audit Logic Must Stay in the Core →Use ChatGPT for refund and offer suggestions while keeping approvals, role checks, and immutable audit logs in the case workflow.
Read Using ChatGPT Safely for Refunds and Customer Offers →High-risk approval workflows need origin, authority, denied paths, outcomes, and case-linked evidence in one immutable audit log.
Read What Auditors Need to See in a High-Risk Approval Workflow →How to design approval gates for high-risk operations that shrink blast radius, enforce two-person review, and keep the evidence on the case.
Read Approval Design for High-Risk Operations Workflows →Why finance exception handling needs four-eyes control, structured evidence, and audit-ready review before unauthorized actions slip through.
Read Finance Exception Handling Needs Four-Eyes Control →