---
# System prepended metadata

title: Design Document

---

# Design: <!-- title here -->
**Author**: @USER
<!-- Status of the document - draft, in-review, etc. - is conveyed via HackMD labels -->

## Description (what)

<!-- Describe the feature at a high level. -->

## Motivation (why, optional)

<!-- Why do we need to do this? Who does it benefit? How much impact does it have? -->

## Goals

<!-- 
- Goals the implementation should achieve
- ...
-->

### Non-Goals (optional)

<!--
- What are we explicitly not doing?
- ...
-->

## Design (how)

<!-- Keep it short and sweet. Prefer "API-driven Design": use diagrams, gRPC interfaces, protos, DB tables, etc. to describe the system. -->

### Required changes (how)

<!--
- A short list of changes required to implement the design
- ...
-->

## Rejected Alternatives (optional)

<!-- Other ideas that were considered but rejected, including reasoning. -->

