> ## 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.

# Use the Phylax Platform

> Find your project, review releases and backtests, monitor invalidations, and configure alerts.

Use the [Phylax platform](https://ethereum.phylax.systems) to review the work prepared with your FDE and manage your protection.

## Before You Start

Ask your FDE or project admin for access. Have the target contracts and approved policies available for review.

[Assign a protocol manager](https://docs.phylax.systems/credible/assign-protocol-manager.md) to sign deployments. Platform access alone does not grant deployment authority.

## 1. Open Your Project

Sign in to [ethereum.phylax.systems](https://ethereum.phylax.systems). Open your protocol under **Projects** and check its network and contract addresses.

If needed, [create the project](https://docs.phylax.systems/credible/deploy-assertions-dapp.md#step-2-create-a-project) with your FDE.

## 2. Review a Release

Your FDE or developer prepares a release with [`pcl apply`](./apply-assertions). Open it under **Releases**.

Check the proposed policies against your requirements. Review the [release checks](https://docs.phylax.systems/credible/deploy-assertions-dapp.md#step-4-review-release-checks) and [backtesting results](https://docs.phylax.systems/credible/backtesting.md) with your FDE. Creating a release does not activate it.

Follow [Review and deploy changes](https://docs.phylax.systems/credible/managing-your-circuit-breakers.md#review-a-release) for the walkthrough.

## 3. Deploy to Alerting and Observe

Authorize the release targeting **Alerting** through your signing process. Wait for its activation delay.

Review **Invalidations → Alert-only** with your FDE. Exercise the operations in your [test plan](https://docs.phylax.systems/credible/testing-strategy.md). Investigate false positives and retest policy changes.

Alerting records violations without blocking live transactions. Production requires a separate release.

## 4. Authorize Production and Verify Protection

Complete the integration tests and recovery rehearsal with your FDE. Follow [Review and Deploy Policies](https://docs.phylax.systems/credible/deploy-assertions-dapp.md) to authorize the production release.

After the activation delay, [verify live enforcement](https://docs.phylax.systems/credible/deploy-assertions-dapp.md#verify-ethereum-enforcement) with your FDE. Check the active policies, guard coverage, and transaction routes.

## 5. Investigate an Invalidation

Open **All invalidations** and select an event. Follow the [transaction investigation walkthrough](https://docs.phylax.systems/credible/investigate-rejected-transaction.md).

Review unexpected findings with your FDE. Policy changes require a reviewed release and your signing process.

## 6. Configure and Test Alerts

Follow [Setting Up Alerting](https://docs.phylax.systems/credible/setting-up-alerting.md) to connect Slack and test notification delivery. Agree with your FDE who investigates alerts and who can authorize recovery.

## 7. Keep Access and Project Information Current

Manage collaborators and project details under **Settings**. Use **Audit Log** to review project changes.

When policies change, [replace the release](https://docs.phylax.systems/credible/managing-your-circuit-breakers.md#replace-or-remove-a-release) with the complete policy set to retain. Review and authorize it, then verify the resulting protection. Use your agreed [recovery procedures](./work-with-phylax#fallback-paths-and-recovery) during an incident.


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