From 76c31c6303eb595c006a4a090c6f8516aa9f3f5b Mon Sep 17 00:00:00 2001
From: Hidde Beydals <hello@hidde.co>
Date: Fri, 21 Oct 2022 11:07:18 +0000
Subject: [PATCH] RFC: outline design details

Signed-off-by: Hidde Beydals <hello@hidde.co>
---
 rfcs/XXXX-artifact-revision-format/README.md | 28 ++++++++++++--------
 1 file changed, 17 insertions(+), 11 deletions(-)

diff --git a/rfcs/XXXX-artifact-revision-format/README.md b/rfcs/XXXX-artifact-revision-format/README.md
index 5a220cc3..99201a4e 100644
--- a/rfcs/XXXX-artifact-revision-format/README.md
+++ b/rfcs/XXXX-artifact-revision-format/README.md
@@ -235,17 +235,23 @@ API. This does not strike as a better alternative.
 
 ## Design Details
 
-<!--
-This section should contain enough information that the specifics of your
-change are understandable. This may include API specs and code snippets.
-
-The design details should address at least the following questions:
-- How can this feature be enabled / disabled?
-- Does enabling the feature change any default behavior?
-- Can the feature be disabled once it has been enabled?
-- How can an operator determine if the feature is in use?
-- Are there any drawbacks when enabling this feature?
--->
+### Artifact Revision format
+
+#### Format
+
+#### Parsing the Revision field
+
+### Artifact Digest
+
+#### Library
+
+#### Configuration
+
+#### Calculation
+
+#### Verification
+
+#### Deprecation of Checksum
 
 ## Implementation History