diff --git a/subcommittee/coding-guidelines/initiatives/safe-use-of-unsafe-guidelines/learn_unsafe_rust/src/core_unsafety/intrinsics.md b/subcommittee/coding-guidelines/initiatives/safe-use-of-unsafe-guidelines/learn_unsafe_rust/src/core_unsafety/intrinsics.md
new file mode 100644
index 0000000..f2efe27
--- /dev/null
+++ b/subcommittee/coding-guidelines/initiatives/safe-use-of-unsafe-guidelines/learn_unsafe_rust/src/core_unsafety/intrinsics.md
@@ -0,0 +1,15 @@
+
+# Intrinsics
+
+Rust provides a set of compiler intrinsics as part of `core` and `std` respectively (https://doc.rust-lang.org/std/intrinsics/index.html).
+
+Most of them are marked as experimental, unstable and useable in nightly versions of the compiler.
+
+Many intrinsics are accessible though a stabilized API located elsewhere in the Standard or Core Library. The documentation for each intrinsic typically references the stabilized API.
+
+Thus, the clear recommendation is not using the experimental compiler intrinsics in a safety-critical project.
+
+There are only few functions that are not marked as experimental: `copy`, `copy_nonoverlapping`, `write_bytes`, `transmute`.
+`transmute` is probably the most well-known and widely used of these APIs.
+`transmute` is handled in other parts of the guidelines.
+