When generating markdown tables with expected long content, the AI will generate the dash line that signifies the header line. If this is very long, the AI gets stuck at generating the dashes and eventually starts returning random content. By removing the excessive dashes in previous messages (which are not necessary for MD display), the AI can continue to use this shorter pattern and run in a stable format.
Example:
| Parameter | Rationale / Notes | Specification / Description |
| :------------------------------------------------------------ | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Anticipated Planning Horizon / Design Cycle for the EUC** | The EUC serves a dynamic research and development environment within a startup. Design iterations and significant modifications are expected based on evolving research needs and resource availability. Therefore, defining a long-term fixed lifespan is unrealistic. A shorter planning horizon reflects the intended development cycle. A significant modification that impacts the safety concept would necessitate a re-evaluation of the risk assessment and potentially constitute a "new machine" from a conformity assessment perspective, resetting this horizon. | The current design iteration and this risk assessment are based on an anticipated operational and development timeframe of approximately **2 years**. Future major redesigns or modifications will require a review and update of this risk assessment. |
maybe the model can be finetuned to generate a maximum of 20 dashes