diff --git a/README.md b/README.md
index 9c2b66be..1318dbcb 100644
--- a/README.md
+++ b/README.md
@@ -1,182 +1,45 @@
-# OpenClaw Mission Control
+# ⚠️ Project Archived
-[](https://github.com/abhi1693/openclaw-mission-control/actions/workflows/ci.yml) 
+> **This repository has been archived and is no longer maintained.**
+>
+> Development has moved to **Wardn AI**, which supersedes OpenClaw Mission Control with a significantly improved architecture, better maintainability, and continued active development.
+>
+> **👉 New project:** https://github.com/abhi1693/wardn-ai
+>
+> If you are looking to build, deploy, or operate AI agents, you should use **Wardn AI** instead of this repository.
-OpenClaw Mission Control is the centralized operations and governance platform for running OpenClaw across teams and organizations, with unified visibility, approval controls, and gateway-aware orchestration.
-It gives operators a single interface for work orchestration, agent and gateway management, approval-driven governance, and API-backed automation.
+## Why this project was archived
-
-
-
-
-
+OpenClaw Mission Control was an experimental operations platform for OpenClaw. As the project evolved, its architecture and long term direction diverged significantly from what Mission Control was originally designed for.
-## Platform overview
+Rather than continue maintaining two overlapping projects, development has been consolidated into **Wardn AI**, which provides:
-Mission Control is designed to be the day-to-day operations surface for OpenClaw.
-Instead of splitting work across multiple tools, teams can plan, execute, review, and audit activity in one system.
+* A cleaner and more scalable architecture.
+* Active maintenance and regular feature development.
+* Better long term support.
+* A more complete platform for AI agent orchestration and operations.
-Core operational areas:
+No new features, bug fixes, or security updates will be made to this repository.
-- Work orchestration: manage organizations, board groups, boards, tasks, and tags.
-- Agent operations: create, inspect, and manage agent lifecycle from a unified control surface.
-- Governance and approvals: route sensitive actions through explicit approval flows.
-- Gateway management: connect and operate gateway integrations for distributed environments.
-- Activity visibility: review a timeline of system actions for faster debugging and accountability.
-- API-first model: support both web workflows and automation clients from the same platform.
+## Existing users
-## Use cases
+If you are currently using OpenClaw Mission Control:
-- Multi-team agent operations: run multiple boards and board groups across organizations from a single control plane.
-- Human-in-the-loop execution: require approvals before sensitive actions and keep decision trails attached to work.
-- Distributed runtime control: connect gateways and operate remote execution environments without changing operator workflow.
-- Audit and incident review: use activity history to reconstruct what happened, when it happened, and who initiated it.
-- API-backed process integration: connect internal workflows and automation clients to the same operational model used in the UI.
+* Existing source code will remain available for reference.
+* Releases will remain accessible.
+* Issues and pull requests will no longer be reviewed.
+* New deployments are not recommended.
-## What makes Mission Control different
+Please migrate to **Wardn AI** for all future deployments and development.
-- Operations-first design: built for running agent work reliably, not just creating tasks.
-- Governance built in: approvals, auth modes, and clear control boundaries are first-class.
-- Gateway-aware orchestration: built to operate both local and connected runtime environments.
-- Unified UI and API model: operators and automation act on the same objects and lifecycle.
-- Team-scale structure: organizations, board groups, boards, tasks, tags, and users in one system of record.
+## Migrate to Wardn AI
-## Who it is for
+Repository:
-- Platform teams running OpenClaw in self-hosted or internal environments.
-- Operations and engineering teams that need clear approval and auditability controls.
-- Organizations that want API-accessible operations without losing a usable web UI.
+**https://github.com/abhi1693/wardn-ai**
-## Get started in minutes
-
-### Option A: One-command production-style bootstrap
-
-If you haven't cloned the repo yet, you can run the installer in one line:
-
-```bash
-curl -fsSL https://raw.githubusercontent.com/abhi1693/openclaw-mission-control/master/install.sh | bash
-```
-
-This clones the repository into `./openclaw-mission-control` if no local checkout is found in your current directory.
-
-If you already cloned the repo:
-
-```bash
-./install.sh
-```
-
-The installer is interactive and will:
-
-- Ask for deployment mode (`docker` or `local`).
-- Install missing system dependencies when possible.
-- Generate and configure environment files.
-- Bootstrap and start the selected deployment mode.
-
-Installer support matrix: [`docs/installer-support.md`](./docs/installer-support.md)
-
-### Option B: Manual setup
-
-### Prerequisites
-
-- **Supported platforms**: Linux and macOS. On macOS, Docker mode requires [Docker Desktop](https://www.docker.com/products/docker-desktop/); local mode requires [Homebrew](https://brew.sh) and Node.js 22+.
-- Docker Engine
-- Docker Compose v2 (`docker compose`)
-
-### 1. Configure environment
-
-```bash
-cp .env.example .env
-```
-
-Before startup:
-
-- Set `LOCAL_AUTH_TOKEN` to a non-placeholder value (minimum 50 characters) when `AUTH_MODE=local`.
-- Ensure `BASE_URL` matches the public backend origin if you are not using `http://localhost:8000`.
-- `NEXT_PUBLIC_API_URL=auto` (default) resolves to `http(s)://:8000`.
- - Set an explicit URL when your API is behind a reverse proxy or non-default port.
-
-### 2. Start Mission Control
-
-```bash
-docker compose -f compose.yml --env-file .env up -d --build
-```
-
-If you are iterating on the UI in Docker and want automatic frontend rebuilds on
-source changes, run:
-
-```bash
-docker compose -f compose.yml --env-file .env up --build --watch
-```
-
-Notes:
-
-- Compose Watch requires Docker Compose **2.22.0+**.
-- You can also run watch separately after startup:
-
-```bash
-docker compose -f compose.yml --env-file .env up -d --build
-docker compose -f compose.yml --env-file .env watch
-```
-
-After pulling new changes, rebuild and recreate all services:
-
-```bash
-docker compose -f compose.yml --env-file .env up -d --build --force-recreate
-```
-
-For a fully clean rebuild (no cached build layers):
-
-```bash
-docker compose -f compose.yml --env-file .env build --no-cache --pull
-docker compose -f compose.yml --env-file .env up -d --force-recreate
-```
-
-### 3. Open the application
-
-- Mission Control UI: http://localhost:3000
-- Backend health: http://localhost:8000/healthz
-
-### 4. Stop the stack
-
-```bash
-docker compose -f compose.yml --env-file .env down
-```
-
-## Authentication
-
-Mission Control supports two authentication modes:
-
-- `local`: shared bearer token mode (default for self-hosted use)
-- `clerk`: Clerk JWT mode
-
-Environment templates:
-
-- Root: [`.env.example`](./.env.example)
-- Backend: [`backend/.env.example`](./backend/.env.example)
-- Frontend: [`frontend/.env.example`](./frontend/.env.example)
-
-## Documentation
-
-Complete guides for deployment, production, troubleshooting, and testing are in [`/docs`](./docs/).
-
-## Project status
-
-Mission Control is under active development.
-
-- Features and APIs may change between releases.
-- Validate and harden your configuration before production use.
-
-## Contributing
-
-Issues and pull requests are welcome.
-
-- [Contributing guide](./CONTRIBUTING.md)
-- [Open issues](https://github.com/abhi1693/openclaw-mission-control/issues)
+Please refer to the Wardn AI documentation for installation, deployment, and migration guidance.
## License
-This project is licensed under the MIT License. See [`LICENSE`](./LICENSE).
-
-## Star History
-
-[](https://www.star-history.com/#abhi1693/openclaw-mission-control&type=date&legend=top-left)
+This repository remains available under the MIT License.