- **Description**: A single sentence description summarizing the items in the desiderata. - **Authors**: [Author](mailto:author@email.com) <!-- READ HIP-0 BEFORE USING THIS TEMPLATE! This template is for drafting Desiderata. It ensures a structured representation of wishes, requirements, or needs related to the overarching objective mentioned in the title. After filling in the requisite fields, please delete these comments. Note that an HD number will be assigned by an editor. When opening a pull request to submit your HD, please use an abbreviated title in the filename, `README.md`. The title should be 44 characters or less. It should not repeat the HD number in title. The author should add himself as a code owner in the `.github/CODEOWNERS` file for the HD. TODO: Remove this comment before finalizing. --> ## Overview <!-- Provide a brief, high-level overview of the desiderata. This section should illuminate the unified objective of the desired elements, functionalities, or features. More granular specifications should be provided below. TODO: Remove this comment before finalizing. --> ## Desiderata <!-- List out the specific desiderata. Each entry should consist of: 1. Title: A concise name for the desideratum. 2. User journey: A one or two-sentence statement focusing on the "user" (could be a human, machine, software, etc.) and their interaction or experience. 3. Description (optional): A more detailed explanation if needed. 4. Justification: The reasoning behind the desideratum. Why is it necessary or desired? 5. Recommendations (optional): Suggestions or guidance related to the desideratum. Format as: ### D<number>: Desideratum Title **User journey**: [user] can [action]. **Description**: <More detailed explanation if needed (optional)> **Justification**: <Why this is a significant or required desideratum> **Recommendations**: <Any specific guidance or suggestions (optional)> TODO: Remove this comment before finalizing. --> # Changelog <!-- The changelog should be maintained after publication. 1. **Transparency and Clarity**: The changelog acknowledges any corrections made post-publication, ensuring that readers are not misled and are always equipped with the most accurate information. 2. **Accountability**: By noting changes openly, we maintain a high level of responsibility and ownership over our content. It’s an affirmation that we value precision and are ready to correct oversights. Each changelog should briefly describe each change made, accompanied by a reference to the date, version and PR in which the change was implemented. The format should be as follows: - **2025-08-21**: Description of change. [PR#](link-to-PR) TODO: Maintain this comment. -->
Overview
Desiderata
Changelog