Al Chen separates production systems used by bank customers from prototypes and internal experiments. The talk describes deployment constraints in restricted bank environments and argues that engineering work must address each institution's image approval, infrastructure and security processes rather than promise a universal rollout timeline.
Al Chen's first two pillars concern vulnerability remediation and recovery. Changing a package version is not enough without evidence that the relevant vulnerability is addressed in the application. Likewise, a successful backup job does not prove restored data is current or replicas agree. Recovery design also needs to account for where sensitive records are stored.
Al Chen then examines how evaluation explanations can reproduce sensitive information even when the visible application redacts it. The talk explores restricting persisted reasoning, checking outputs and using a separate redacted evaluation path, while acknowledging additional cost. The central message is evidence-based trust and organizational readiness, not a guarantee that the proposed checks eliminate every leak or compliance delay.
Watch on YouTube
