> ## Documentation Index
> Fetch the complete documentation index at: https://docs.phylax.systems/llms.txt
> Use this file to discover all available pages before exploring further.

# Review and deploy changes

> Review, deploy, replace, and remove circuit-breaker releases.

Use the [Phylax platform](https://ethereum.phylax.systems) to review and deploy circuit-breaker releases. Your Protocol Manager signs deployments and removals. Assertions are managed as a complete release; you cannot remove them individually from an active release.

## Check Active Policies

Open **Assertions** to review circuit-breaker activity against its window and threshold. Select an assertion to check its enforcement status and linked contracts.

> [tab] Circuit Breakers
>
> ![Assertions page showing two production circuit breakers, their outflow windows and thresholds, and the full assertion list](https://mintcdn.com/phylaxsystems/mPqsEKYktcjMz8lr/images/platform/assertions.png?fit=max\&auto=format\&n=mPqsEKYktcjMz8lr\&q=85\&s=0cf0982ad76a617e1b706166e6de0be8)
>
> Review each circuit breaker's environment, window, threshold, and current activity

> [tab] Assertion Details
>
> ![Enforced production assertion showing its linked contract, constructor arguments, triggers, and View source code action](https://mintcdn.com/phylaxsystems/mPqsEKYktcjMz8lr/images/platform/assertion-detail.png?fit=max\&auto=format\&n=mPqsEKYktcjMz8lr\&q=85\&s=dd028b82dc3a015d3558fa2de2c311d9)
>
> Inspect an assertion's configuration and use View source code to read its policy

## Review a Release

Open the release marked **Needs Review** under **Latest Releases** on the project overview, or select it under **Releases → Needs your review**. **All passed** reports completed checks; the release still needs your review and deployment authorization.

> [tab] Project Overview
>
> ![Project overview with Release 3 marked Needs Review and Release 2 still active](https://mintcdn.com/phylaxsystems/mPqsEKYktcjMz8lr/images/platform/project-home-needs-review.png?fit=max\&auto=format\&n=mPqsEKYktcjMz8lr\&q=85\&s=2cefb6b6a8cc36abb7eabef9e42c2bba)
>
> Open the new release marked Needs Review

> [tab] Releases
>
> ![Releases page with Release 3 under Needs your review, All passed checks, and an Inactive deployment state](https://mintcdn.com/phylaxsystems/mPqsEKYktcjMz8lr/images/platform/release-review-needs-review.png?fit=max\&auto=format\&n=mPqsEKYktcjMz8lr\&q=85\&s=a9c4ba8d3c4cf33ec3089f1c2a0fc67d)

Check the environment, target contracts, and **Release Diff** against the approved changes. Review **Assertion verification**, **Source code**, and **Backtesting**. Investigate unexpected results with your FDE before signing.

![Inactive production release with three passed checks, its Release Diff, and the Deploy to Production button](https://mintcdn.com/phylaxsystems/mPqsEKYktcjMz8lr/images/platform/release-review-deploy-ready.png?fit=max\&auto=format\&n=mPqsEKYktcjMz8lr\&q=85\&s=275513a5e866ea80d56421d20fb524ea)

Review the release contents and completed checks before selecting Deploy to Production

[Review and Deploy Policies](https://docs.phylax.systems/credible/deploy-assertions-dapp.md#step-4-review-release-checks) explains each check. [Backtesting Results](https://docs.phylax.systems/credible/backtesting.md) shows how to assess the tested history and findings.

## Authorize the Change

1. Connect your [assigned Protocol Manager](https://docs.phylax.systems/credible/assign-protocol-manager.md) and confirm the release's environment.
2. Select **Deploy to Production** for the production release shown here.
3. Review and authorize the transaction in your wallet. For a multisig, collect the required approvals and execute it.
4. Wait for transaction confirmation, then check activation in the platform.

![Wallet showing a signed and confirmed Ethereum deployment transaction alongside the platform release list](https://mintcdn.com/phylaxsystems/mPqsEKYktcjMz8lr/images/platform/release-deployment-signed.png?fit=max\&auto=format\&n=mPqsEKYktcjMz8lr\&q=85\&s=22162658d83760d286bfdff45da0fb56)

Confirm the deployment transaction in your wallet, then check policy activation

In **Assertions**, newly added policies can show **Awaiting activation** with a remaining block count. Wait for that delay to finish and confirm their enforcement status. A deployment notification or an **Active** release badge alone does not establish that every new assertion is enforcing.

> [tab] Awaiting Activation
>
> ![Production circuit breaker showing Awaiting activation with eight blocks remaining](https://mintcdn.com/phylaxsystems/mPqsEKYktcjMz8lr/images/platform/release-activation.png?fit=max\&auto=format\&n=mPqsEKYktcjMz8lr\&q=85\&s=8e8824252e6b97af0ff3308a3c75037f)
>
> This circuit breaker still has eight blocks remaining before activation

> [tab] Deployed Release
>
> ![Release 3 overview showing its deployment transaction, Active status, completed checks, and Remove Release button](https://mintcdn.com/phylaxsystems/mPqsEKYktcjMz8lr/images/platform/release-active.png?fit=max\&auto=format\&n=mPqsEKYktcjMz8lr\&q=85\&s=01fb7d7f1ccf7d8fcdaddf897d45515e)
>
> The release overview records the deployment transaction and provides the Remove Release action

Your FDE verifies production protection with you. See [live enforcement checks](https://docs.phylax.systems/credible/deploy-assertions-dapp.md#verify-ethereum-enforcement). Project access and [deployment authority](https://docs.phylax.systems/credible/managing-policy-deployments.md) are separate.

## Replace or Remove a Release

To change or remove an individual assertion, prepare a **replacement release** with your FDE, developer, or [AI coding agent](https://docs.phylax.systems/credible/agentic-pcl.md). Include the complete set of policies you intend to keep. Review its diff and checks, then deploy it through the same signing process. Changes take effect after their configured delays.

To remove the entire release:

1. Open the active release and select **Remove Release**.
2. Check the network and the full **Assertions to remove** list.
3. Confirm **Remove Release** and authorize the onchain transaction with the Protocol Manager.
4. Wait for the indexed deactivation blocks and confirm that removal has taken effect.

![Remove Release 3 confirmation listing the network and eight assertions to remove, with a notice that enforcement continues until their deactivation blocks](https://mintcdn.com/phylaxsystems/mPqsEKYktcjMz8lr/images/platform/remove-release.png?fit=max\&auto=format\&n=mPqsEKYktcjMz8lr\&q=85\&s=50bfa8da98dd6a2c65b13ed2f02870ed)

Remove Release schedules removal of all assertions in the release

Assertions remain enforced until their deactivation blocks. A removed release cannot be reactivated. To restore policies after removal takes effect, create and deploy a new release.

For an emergency, follow your agreed [fallback and recovery procedure](./work-with-phylax#fallback-paths-and-recovery).

For invalidation analysis, follow [Investigate a Rejected Transaction](https://docs.phylax.systems/credible/investigate-rejected-transaction.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.