diff --git a/specs/SUMMARY.md b/specs/SUMMARY.md
index 58adf84da..9d253062a 100644
--- a/specs/SUMMARY.md
+++ b/specs/SUMMARY.md
@@ -87,6 +87,6 @@
     - [Transaction Pool](./interop/tx-pool.md)
     - [OptimismPortal](./interop/optimism-portal.md)
     - [ETH Lockbox](./interop/eth-lockbox.md)
-  - [OP Contracts Manager](./experimental/op-contracts-manager.md)
+  - [OP Contracts Manager](./protocol/op-contracts-manager.md)
   - [Governance Token](./experimental/gov-token.md)
 - [Glossary](./glossary.md)
diff --git a/specs/protocol/configurability.md b/specs/protocol/configurability.md
index 0b73ef1e1..e3ced68c1 100644
--- a/specs/protocol/configurability.md
+++ b/specs/protocol/configurability.md
@@ -77,7 +77,7 @@ Standard Chain within the superchain.
 These requirements are currently a draft, pending governance approval.
 
 The recommended way to deploy L1 contracts for an OP chain that meet the standard configuration will be with the
-[OP Contracts Manager](../experimental/op-contracts-manager.md).
+[OP Contracts Manager](./op-contracts-manager.md).
 
 ## Consensus Parameters
 
diff --git a/specs/experimental/op-contracts-manager.md b/specs/protocol/op-contracts-manager.md
similarity index 98%
rename from specs/experimental/op-contracts-manager.md
rename to specs/protocol/op-contracts-manager.md
index 37b6a81ae..15cc52600 100644
--- a/specs/experimental/op-contracts-manager.md
+++ b/specs/protocol/op-contracts-manager.md
@@ -2,10 +2,10 @@
 
 [Optimism Monorepo releases]: https://github.com/ethereum-optimism/optimism/releases
 [contract releases]: https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/meta/VERSIONING.md
-[standard configuration]: ../protocol/configurability.md
+[standard configuration]: ./configurability.md
 [superchain registry]: https://github.com/ethereum-optimism/superchain-registry
 [ethereum-lists/chains]: https://github.com/ethereum-lists/chains
-[Batch Inbox]: ../protocol/configurability.md#consensus-parameters
+[Batch Inbox]: ./configurability.md#consensus-parameters
 
 The OP Contracts Manager is a contract that deploys the L1 contracts for an OP Stack chain in a single
 transaction. It provides a minimal set of user-configurable parameters to ensure that the resulting
@@ -58,7 +58,7 @@ The OP Contracts Manager corresponding to each release can be used to:
 2. Upgrade the contracts for an existing OP chain from the previous release to the new release.
 3. Orchestrate adding a new game type on a per-chain basis
 
-Upgrades must be performed by the [Proxy Admin Owner](../protocol/stage-1.md#roles-for-stage-1) Safe for a chain.
+Upgrades must be performed by the [Proxy Admin Owner](./stage-1.md#roles-for-stage-1) Safe for a chain.
 
 ## Getter Methods