diff --git a/text/0000-utilities-profile.md b/text/0000-utilities-profile.md
new file mode 100644
index 0000000..109474c
--- /dev/null
+++ b/text/0000-utilities-profile.md
@@ -0,0 +1,38 @@
+- Start Date: 2015-12-03
+- RFC PR: (leave this empty)
+- Refract Issue: (leave this empty)
+
+# Summary
+
+This proposes we move `extend`, `select`, and `option` from the base
+specification to its own profile.
+
+# Motivation
+
+The main motivation is to make the base specification as simple as possible. In
+every implementation we've created for consuming Refract, such as from the Parse
+Result or API Description results, we have not needed to use any of these
+elements.
+
+In light of simplifying, this keeps the base specification concerned with
+primitive, meta elements, and addressability.
+
+# Detailed design
+
+This proposal is to move `extend`, `select`, and `option` to its own
+profile/namespace. Once there, the Data Structure namespace would then
+reference that specification as a dependency.
+
+# Drawbacks
+
+This removes functionality from the base specification, and therefore limits it
+in some way. The original argument was that these elements were important to
+have for all other namespaces, but this has proven to not be true.
+
+# Alternatives
+
+The alternative is to of course not implement this RFC.
+
+# Unresolved questions
+
+None at this moment.