Authors: Name <Email>, Name <Email>
Reviewers
Change log
| Status | Description | Date |
|---|---|---|
| Draft | Draft status set | <When status was set> |
| YYYY-MM-DD | ||
| This logic was revised | <Date of modification> | |
| YYYY-MM-DD | ||
| Verified | Verified status set | <When status was set> |
| YYYY-MM-DD | ||
| This line of code was modified to improve accuracy | <Date of modification> | |
| YYYY-MM-DD | ||
| Merged | Merged status set | <When status was set> |
| YYYY-MM-DD |
<aside> 💡
Explain the purpose of the RFC. It must be clear why we want to introduce the proposed change at a high level. Briefly describe any measurable evidence supporting the change and include a short summary of the analysis outcomes. More detailed discussion should be in the Discussion.
</aside>
<aside> 💡
Explain the core idea of the proposal and the changes required to the key specifications.
</aside>
<aside> 💡
[Optional] Discuss how the change affects system properties. Detailed discussion can focus on any aspect of the system, including (but not limited to) performance, security, or user experience. Justify any recommended values for the chosen parameters.
</aside>
<aside> 💡
[Optional] Provide a detailed description of all changes required across specifications if the Proposal section is not sufficient.
</aside>
<aside> 💡
[Optional] List smaller, included changes (e.g., naming/terminology updates). Include it at the end of details.
</aside>
<aside> 💡
List all specifications impacted by this change. Reviewers must verify that this list is complete.
Each specification listed here must be a duplicated copy of the latest version (a Merged or Stable spec with the highest version number). Do not change the version number until the RFC is granted verified status and implementation begins.
Specifications to Deprecate or Retire must be linked in their respective sections. You may link relevant specifications under multiple statuses (for example, link merged and stable specifications of the same type).
If any listed specification is updated before the RFC reaches Merged, then all of these specifications must be updated to reflect the latest spec. This is Notion-specific overhead and will be handled by Git when merging changes to the main branch.
</aside>