My Recording Notes Need the Recording Date
We updated recording filenames, the web interface and exports to carry recording time, while preserving originals and processing results.
Today my AI team and I updated how TraDiSum, my recording workflow, handles timestamps. New imports now use dated recording filenames, and the web interface and exports show the recording time. Originals and processing results remain preserved.
It is a small change with a specific purpose: the date attached to a recording should help explain when the recorded material happened.
Two dates, different questions
Recording time and processing time are not interchangeable. One locates the source material in time. The other describes work done to it. A summary can be produced later without making the recording itself newer.
That distinction matters when notes leave the application. An export needs enough context to stand on its own. Showing recording time there carries an important piece of the source context into the document, rather than leaving it only in the interface.
We made the convention visible in new import filenames as well. The point is consistency across the places where I encounter the material, not simply making one screen look tidier.
Keep the source behind the summary
Preserving originals and processing results is part of the same change. A filename or displayed timestamp is useful context, but it is not a substitute for retaining the material behind the output.
Today's work journal reports that the live import/export check passed, alongside 78 passing tests. That supports a bounded result: the updated convention was exercised through import and export. It does not establish that every historical recording has been renamed or checked, and I am not claiming a complete archive migration.
The practical lesson from today's work is straightforward. When we build AI workflows around recordings, the generated text needs to retain its connection to the source. Dates are part of that connection, not just decoration around the summary.
Evidence note: this account follows today's scoped work journal. The implementation and test results are reported there; this post is not an independent re-test of the recording system.