History is the integration trail and the security trail

Context

This audit choice applies to integration mutations; extension and workflow storage have their own declared behavior.

Decision

Record audited integration mutations in both the integration event trail and Security’s audit storage within the mutation transaction. This lifecycle-oriented history is distinct from field-level change capture.

Alternatives Considered

Use field-level record change capture for all lifecycle history. Verification, rotation and binding changes are meaningful events rather than simple field differences.

Consequences

A refused audited mutation retains its prior state and writes no successful-change history.

Registry registration remains unaudited and requires a separate decision.

Deletion purges protected integration history first through a privileged function.