From 3a03a4100a14174999e401adf50d044702f66d42 Mon Sep 17 00:00:00 2001
From: blam <ben@blam.sh>
Date: Sat, 9 Jan 2021 19:54:44 +0100
Subject: [PATCH] chore: actually add the adr template which appears to have
 gone missing in the repo

---
 docs/architecture-decisions/0000-template.md | 22 ++++++++++++++++++++
 1 file changed, 22 insertions(+)
 create mode 100644 docs/architecture-decisions/0000-template.md

diff --git a/docs/architecture-decisions/0000-template.md b/docs/architecture-decisions/0000-template.md
new file mode 100644
index 0000000000..d1ad78ffc8
--- /dev/null
+++ b/docs/architecture-decisions/0000-template.md
@@ -0,0 +1,22 @@
+# ADR 0000: [title]
+
+<!-- These documents have names that are short noun phrases. For example, "ADR 1: Deployment on Ruby on Rails 3.0.10" or "ADR 9: LDAP for Multitenant Integration" -->
+
+## Status
+
+<!-- A decision may be "proposed" if the project stakeholders haven't agreed with it yet, or "accepted" once it is agreed. If a later ADR changes or reverses a decision, it may be marked as "deprecated" or "superseded" with a reference to its replacement. -->
+
+## Context
+
+<!--
+This section describes the forces at play, including technological, political, social, and project local. These forces are probably in tension, and should be called out as such. The language in this section is value-neutral. It is simply describing facts. -->
+
+## Decision
+
+<!-- This section describes our response to these forces. It is stated in full sentences, with active voice. "We will ..." -->
+
+## Consequences
+
+<!-- This section describes the resulting context, after applying the decision. All consequences should be listed here, not just the "positive" ones. A particular decision may have positive, negative, and neutral consequences, but all of them affect the team and project in the future. -->
+
+<!-- This template is taken from a blog post by Michael Nygard http://thinkrelevance.com/blog/2011/11/15/documenting-architecture-decisions -->