1 files changed, 75 insertions, 0 deletions
diff --git a/kd/oap-0001.md b/kd/oap-0001.md
new file mode 100644
index 0000000..ac5ce08
--- /dev/null
+++ b/kd/oap-0001.md
@@ -0,0 +1,75 @@
+---
+stand_alone: true
+ipr: none
+cat: info
+area: Systems Engineering
+wg: OSMORA Standards Group
+
+docname: OAP-0001
+
+title: OSMORA Amelioration Proposals
+abbrev: OAPs
+lang: en
+kw:
+  - oap
+  - amelioration
+author:
+- role: editor
+  name: Ian M. Moffett
+  org: OSMORA
+  city: Washington, DC
+  region: Southeast
+  code: 20020
+  email: ian@osmora.org
+
+--- abstract
+
+Description of OSMORA Amelioration Proposals
+
+--- middle
+
+# Introduction
+
+OSMORA Amelioration Proposals (OAPs) are structured
+documents that serve to drive changes imposed by OSMORA
+by describing their fundamentals while allowing others to
+amend/revise them.
+
+## Purpose
+
+The goal of having OAPs is to provide an organized means of proposing
+and improving ideas that contribute to the betterment of society
+and technology. These proposals can range from technical improvements
+to societal reforms, and they are open to discussion and collaboration
+for those who have understood and commited to the OSMORA oath.
+
+## Audience
+
+OAPs are intended for those who are commited to the OSMORA oath. These
+proposals must only be considered offical and bidning when they are approved
+by a number of OSMORA members and a single OSR (OSMORA Standards Reviewer).
+
+
+# Requirements Language
+
+{::boilerplate bcp14-tagged}
+
+# Structure
+
+An OAP will typically include the following:
+
+
+- OAP ID: Incremental document identifier.
+- Abstract: A concise summary of the proposal's intent and impact.
+- Motivation: Why this proposal matters and the problem it addresses.
+
+
+{:vspace}
+OSMORA:
+: See OSMORA.ORG
+
+OSMORA Oath:
+: A pledge taken by all members of OSMORA ensuring their commitment
+  to societal betterment, technological advancement as well as their
+  loyalty to the grater good, resisting the forbidden fruit dangled
+  by the suits.