diff --git a/docs/README.md b/docs/README.md
index f6807669..f801a1ca 100644
--- a/docs/README.md
+++ b/docs/README.md
@@ -88,9 +88,8 @@ declarations.
   twice after downtime?** → [`swarm/schedules.md`](swarm/schedules.md).
 - **How to set an agent's model or effort from the swarm, and what happens
   to its own pick?** → [`swarm/inference.md`](swarm/inference.md).
-- **How will a PR get checked against its repo's own yes/no rules before
-  a full review?** → [`swarm/review-classifier.md`](swarm/review-classifier.md)
-  (planned, not implemented yet).
+- **How does a PR get checked against its repo's own yes/no rules before
+  a full review?** → [`swarm/review-classifier.md`](swarm/review-classifier.md).
 - **Does an agent config PR build before it's merged?** →
   [`swarm/builder.md`](swarm/builder.md).
 - **How to create an agent from a ready-made set of permissions and
diff --git a/docs/swarm/README.md b/docs/swarm/README.md
index 32977391..c7c6f044 100644
--- a/docs/swarm/README.md
+++ b/docs/swarm/README.md
@@ -28,8 +28,8 @@ grafana, the controller, authelia, …) →
 - **resource caps** — the CPU and memory cap the swarm sets for an agent,
   over its hive's. →
   [`coordinator.md`](../scheduler/coordinator.md#container-resource-limits)
-- **review classifier** — planned, not implemented yet: checks a PR against
-  its repo's own yes/no rules and posts the result as a review. →
+- **review classifier** — checks a PR against its repo's own yes/no rules
+  and posts the result as a review. →
   [`review-classifier.md`](review-classifier.md)
 - **notification router** — forge events turned into todos on the agents
   they concern: assigned, unassigned, cleared on close; and the classifier's
diff --git a/docs/swarm/review-classifier.md b/docs/swarm/review-classifier.md
index 86d8d381..007e9f73 100644
--- a/docs/swarm/review-classifier.md
+++ b/docs/swarm/review-classifier.md
@@ -1,11 +1,5 @@
 # Review classifier
 
-> ⚠️ **PLANNED, NOT IMPLEMENTED YET.** This page describes the full target
-> shape of the review classifier at component level, and none of it exists
-> in the tree today. The forge epic "pr review classifier pipeline" tracks
-> the work. Details land here as each part ships, and this banner goes away
-> when the epic closes.
-
 The review classifier checks a pull request against short, named yes/no
 rules that the repo itself defines, and posts the result as a forge review.
 A small model answers one rule at a time, so mundane rule checks come out