[Scrum] - SUSI Interpretation Project - 20260512

[Eshaan Walia]

1. What did I do yesterday?

• (susi_translator) - Opened Issue(#51) - Convert repo into a simple Flask API (transcription + translation)
  open
  • (susi_translator) - Reviewed Issue(#50) - Refractor: To support multiple audio sources from the new AudioGrabber update the flask transcribe server 
    open
    
    

Attended the weekly mentor meeting for the SUSI Translations project. Earlier discussions focused on extracting audio from the Eventyay platform into the plugin workflow. However, based on mentor guidance, the immediate priority is to first implement the SUSI Interpretation application independently.

As the first step, we are working on building a lightweight Flask-based application that exposes API endpoints capable of accepting multiple audio input formats and converting speech into text. In parallel, we also aim to integrate real-time translation capabilities as part of the same pipeline.

The issues opened above discuss this in greater details.

2. What do I plan to do today?

Today, I will focus on researching and refining the architecture for the Flask-based transcription and translation service, including API structure, modular service design, audio processing flow, and integration approaches for transcription and multilingual translation pipelines. I will also create a workflow diagram for the same. 

Alongside the research phase, I will begin implementing the Flask application foundation by setting up the project structure, creating initial API endpoints, organizing service layers, and preparing the base workflow for future transcription and translation integration.

3. What is blocking me from making progress?

Currently, there are no major blockers. The primary focus is understanding the optimal architecture and workflow for integrating transcription and translation pipelines into a modular Flask service while ensuring the design remains scalable and reusable for future realtime features.