Prompt

You are a Senior Software Engineer tasked with refining the existing code architecture based on the following client conversation: 

"I think the structure looks good as far as pasting, editing, and committing to the database. I noticed the LLM doesn't seem to parse the full raw TXT. For example, from this TXT it parsed 'black 1' and only up to the first set in Block 2 (perhaps because it had a question on the first set). What if we break it down into sub-tasks: process raw TXT to Blocks (chain to 2.), trigger a group of parallel tasks to process each Block, and use a Chord callback - once sub-block tasks are complete, their collective results are passed to the chord's callback function for final aggregation. This can be backend processing, no 'chatbot' for questions. Chatbot-type gap filling can be a separate pass once the aggregated JSON is returned from the Celery Chord callback. Sounds good. Make sure you check out the Celery task groups types, Chain and Chord for example."

Your objectives are as follows:
1. **Review the Current Code Structure**: Analyze the existing architecture and identify areas for improvement.
2. **Plan and Define Tasks**: Create a detailed plan that breaks down the client's requirements into actionable tasks, ensuring each task aligns with the overall project goals.
3. **Implement SOLID Principles**: Write clean, maintainable code that adheres to the SOLID principles, ensuring that the codebase remains robust and scalable.
4. **Maintain Functionality**: Ensure that the overall functionality of the project is preserved. If you identify any obsolete code, remove it carefully to avoid breaking existing features.
5. **Testing**: Develop comprehensive test cases that validate the functionality of the new implementation and ensure that all requirements are met.

**Edge Cases**: Consider scenarios where the raw TXT may be malformed or contain unexpected data. Ensure that your code handles these cases gracefully without crashing.

**Success Criteria**: The project is deemed successful when:
- All client requirements are met with 100% accuracy.
- The codebase remains functional and free of errors.
- All new features are thoroughly tested and documented.