diff --git a/proposals/README.md b/proposals/README.md
index 909f5be4dcec..ea46a75889cb 100644
--- a/proposals/README.md
+++ b/proposals/README.md
@@ -52,5 +52,6 @@ request:
 -   [0162 - Basic Syntax](p0162.md)
     -   [0162 - Decision](p0162_decision.md)
 -   [0175 - C++ interoperability goals](p0175.md)
+    -   [0175 - Decision](p0175_decision.md)
 
 <!-- endproposals -->
diff --git a/proposals/p0175_decision.md b/proposals/p0175_decision.md
new file mode 100644
index 000000000000..eb7d94b1f81d
--- /dev/null
+++ b/proposals/p0175_decision.md
@@ -0,0 +1,48 @@
+# Decision for: C++ interoperability goals
+
+<!--
+Part of the Carbon Language project, under the Apache License v2.0 with LLVM
+Exceptions. See /LICENSE for license information.
+SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
+-->
+
+Proposal accepted on 2020-11-24
+
+Affirming:
+
+-   [austern](https://github.com/austern)
+-   [chandlerc](https://github.com/chandlerc)
+-   [geoffromer](https://github.com/geoffromer)
+-   [gribozavr](https://github.com/gribozavr)
+-   [josh11b](https://github.com/josh11b)
+-   [zygoloid](https://github.com/zygoloid)
+
+Abstaining:
+
+-   [noncombatant](https://github.com/noncombatant)
+-   [tituswinters](https://github.com/tituswinters)
+
+## Open questions
+
+All open questions in the document are intended to be answered later after we
+have more experience.
+
+## Rationale
+
+The core team agrees with the mapping of the proposed interoperability goals to
+the overall Carbon goals as rationale.
+
+Embedding of C++ bridge code inside Carbon code is inspired in part by
+experience with CUDA and SYCL, where users provided feedback that these were
+preferred over alternatives such as OpenCL due to the ability to embed bridge
+code and device kernels in the same source file as host C++ code. It also
+matches the approach of bridging between C++ and C where bridge code is often
+embedded as `extern "C"` within C++ source files.
+
+The non-goals seem appropriately motivated by the non-interoperability
+priorities, without undermining the effectiveness of the interoperability as a
+whole.
+
+We agree with ensuring some level of C interoperability in order to effectively
+interoperate with both some parts of the C++ ecosystem that rely on the C ABI as
+well as all other languages which target C-based interoperability.