From dfe12ce1b01adcd3ce4494e2a5ff6ab80becfff6 Mon Sep 17 00:00:00 2001
From: Adam Shamblin <adam@vexingworkshop.com>
Date: Fri, 2 Sep 2022 13:53:43 -0600
Subject: [PATCH] WIP, add signing section

---
 doc/rfc/cicd.future.md | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/doc/rfc/cicd.future.md b/doc/rfc/cicd.future.md
index 066bff12..1b573153 100644
--- a/doc/rfc/cicd.future.md
+++ b/doc/rfc/cicd.future.md
@@ -22,6 +22,14 @@ In this document I would like to propose some guidelines and processes that can
 help to minimize the impact of malicious actors upon the core Veilid code base
 by way of direct commits and/or to its dependencies.
 
+## Signing
+
+### Commits
+
+### Packages
+
+### PKI
+
 Some of this work will be toil, but most ought to be automated.
 
 ## Forked Dependencies