Is it possible to... enforce chain of custody metadata in Architect data actions?

Background
We manage legal discovery requests requiring immutable audit trails for digital channel recordings. Our current process involves bulk export jobs to S3, but we need to inject specific metadata tags at the moment of interaction capture within the flow.

Issue
Is it possible to append custom key-value pairs to the recording metadata object directly from an Architect data action before the file is committed to storage? The standard recording endpoint seems to lock metadata after session end.

Troubleshooting
Checked the Recording API documentation (v2), but found no clear method for pre-commit metadata injection. Attempted using a custom data action to modify the context, but the changes do not persist in the final exported manifest.

You need to recognize that Architect cannot modify immutable recording metadata at the source. The platform locks these attributes upon generation. Instead, leverage the Data Action to push interaction identifiers to an external audit system. Maintain the chain of custody by linking the S3 object key with your custom metadata in that separate repository.

This is actually a known issue… with the platform’s strict immutability rules. The approach suggested above is correct. Architect cannot mutate recording metadata post-creation. Instead, ensure your Data Action pushes the interaction ID to your external audit system immediately. Linking the S3 key there preserves the chain of custody without violating platform constraints.