DO NOT MERGE - just playing with assembly ai

[Mephistic]

Summary

Add a short summary of the changes, and a reference to the original issue using # and the issue number, like #1

Checklist

• On the frontend, I've made my strings translate-able.
• If I've added shared components, I've added a storybook story.
• I've made pages responsive and look good on mobile.

Screenshots

Add some screenshots highlighting your changes.

Known issues

If you've run against limitations or caveats, include them here. Include follow-up issues as well.

Steps to test/reproduce

For each feature or bug fix, create a step by step list for how a reviewer can test it out. E.g.:

1. Go to the home page
2. Click on a testimony
3. See that it's loaded with a loading spinner

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
maple-dev	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 4, 2025 9:26am

[Mephistic]

For this to actually work, we still need to update the firestore rules to allow users to read transcriptions. This is just a draft PR and that change would require this to be deployed, but here are the base rules we would need to enable this:

match /transcriptions/{id} {
  allow read: if true
  allow write: if false
  match /utterances/{utteranceId} {
    allow read: if true
    allow write: if false
  }
}

I've been adding this rule change on the dev Firestore instance every now and then to test this, but it will get overwritten by any other backend deploy until the above change actually gets merged. I may make this change in a separate PR if the current state is insufficient for user testing.

[Mephistic]

Just leaving a note for posterity here - we should now be using the paragraphs subcollection of transcriptions instead of utterances for the text breakdowns (utterances is often useless when there are too many speakers at a hearing, and paragraphs provides much more consistently sized text chunks). @mertbagt