Audit Logging and Compliance for Automated Schema Changes

Act as a Database Compliance Officer. For a fintech organization bound strictly by the [COMPLIANCE_STANDARD] (e.g., SOC2 Type II, PCI-DSS), architect an absolutely tamper-proof, cryptographic audit trail tracking every single automated database schema migration. Every executed DDL change must be programmatically linked to a specific approved Jira ticket ID, the exact Git commit SHA, and the associated CI/CD pipeline Run ID. Design the architecture to securely stream these metadata events directly into a centralized [LOGGING_STACK] (e.g., ELK, Splunk, Datadog) utilizing an unalterable [AUDIT_TOOL]. You must physically describe the implementation of a 'Four-Eyes' principle workflow within the pipeline architecture, mathematically ensuring that no migration script can ever be executed against the production database without two distinct, verified digital signatures (approvals) from authorized personnel.