diff --git a/docs/self-scoping/outcomes/20260515-192916__repo-scoping-known-bad-2026-05-15-run-39__repo-scoping-post-wp0016-native-2026-05-15__prefer_challenger__245606d1.json b/docs/self-scoping/outcomes/20260515-192916__repo-scoping-known-bad-2026-05-15-run-39__repo-scoping-post-wp0016-native-2026-05-15__prefer_challenger__245606d1.json
new file mode 100644
index 0000000..6a9c517
--- /dev/null
+++ b/docs/self-scoping/outcomes/20260515-192916__repo-scoping-known-bad-2026-05-15-run-39__repo-scoping-post-wp0016-native-2026-05-15__prefer_challenger__245606d1.json
@@ -0,0 +1,38 @@
+{
+  "baseline_assessment_artifact_id": "repo-scoping-known-bad-2026-05-15-run-39",
+  "baseline_assessment_path": "assessments/repo-scoping-known-bad-2026-05-15-run-39.json",
+  "baseline_engine_identity": {
+    "candidate_generator_version": "unversioned-pre-self-scoping-baseline",
+    "engine_commit": null,
+    "engine_dirty_state": "unknown",
+    "engine_release": null,
+    "prompt_version": null,
+    "quality_criteria_version": "none",
+    "release_binding_note": "This historical database run recorded scanner version and target commit, but not the repo-scoping engine commit or release tag that generated the candidate graph.",
+    "release_binding_status": "historical_incomplete",
+    "repo_scoping_version": "0.1.0",
+    "scanner_version": "deterministic-v0.1"
+  },
+  "challenger_assessment_artifact_id": "repo-scoping-challenger-run-1",
+  "challenger_assessment_path": "assessments/repo-scoping-post-wp0016-native-2026-05-15.json",
+  "challenger_engine_identity": {
+    "candidate_generator_version": "unversioned",
+    "engine_commit": "2c3dad80d646869827335cb6de849cdca272c85b",
+    "engine_dirty_state": "clean",
+    "engine_release": null,
+    "prompt_version": null,
+    "quality_criteria_version": "repo-scoping-quality-criteria/v1",
+    "release_binding_note": "Engine commit was captured from git.",
+    "release_binding_status": "complete",
+    "repo_scoping_version": "0.1.0",
+    "scanner_version": "deterministic-v0.1"
+  },
+  "comparison_status": "needs_review",
+  "created_at": "2026-05-15T19:29:16Z",
+  "decision_scope": "assessment-pair-comparison",
+  "notes": "Massive improvement to the old infrastructure!",
+  "outcome": "prefer_challenger",
+  "outcome_id": "20260515-192916__repo-scoping-known-bad-2026-05-15-run-39__repo-scoping-post-wp0016-native-2026-05-15__prefer_challenger__245606d1",
+  "reviewer": "codex",
+  "schema_version": "self-scoping-review-outcome/v1"
+}
diff --git a/workplans/RREG-WP-0018-agentic-hierarchy-and-intent-scope-review.md b/workplans/RREG-WP-0018-agentic-hierarchy-and-intent-scope-review.md
index 9fa2a7d..f246e47 100644
--- a/workplans/RREG-WP-0018-agentic-hierarchy-and-intent-scope-review.md
+++ b/workplans/RREG-WP-0018-agentic-hierarchy-and-intent-scope-review.md
@@ -4,11 +4,11 @@ type: workplan
 title: "Agentic Hierarchy And Intent/Scope Review"
 domain: capabilities
 repo: repo-scoping
-status: active
+status: done
 owner: codex
 topic_slug: foerster-capabilities
 created: "2026-05-15"
-updated: "2026-05-15"
+updated: "2026-05-16"
 state_hub_workstream_id: "83df7082-789f-440e-b7a8-d1f8ecd01cc6"
 ---
 
@@ -197,7 +197,7 @@ Acceptance criteria:
 
 ```task
 id: RREG-WP-0018-T07
-status: in_progress
+status: done
 priority: medium
 state_hub_task_id: "cd1a3c14-076b-42da-8319-48310a964611"
 ```
@@ -266,6 +266,18 @@ Corrected assessment results:
   nominalized capability names such as `Analysis of...` to `Analyze...`, and
   trim explanatory dash clauses from scope one-liners.
 
-T07 remains in progress until `railiance-infra`, `railiance-apps`, and
-`helix-forge` are rerun and the corrected assessment report is captured as the
-comparison artifact.
+Final T07 closeout 2026-05-16: the corrected assessment now shows all Railiance
+repositories with source-linked lower hierarchy or approved hierarchy:
+`railiance-infra` (`1/3/3/3` candidate and approved), `railiance-cluster`
+(`1/3/3/3` candidate), `railiance-platform` (`1/3/3/3` candidate),
+`railiance-enablement` (`1/2/2/2` candidate), and `railiance-apps` (`1/1/1/1`
+candidate and approved). `ops-warden` and `vergabe-teilnahme` no longer prefer
+template README text over repo-specific evidence, and every repository with
+facts has a non-empty dependency graph. `helix-forge` remains a useful follow-up
+quality case for intent-outcome extraction, but it is outside the original T07
+Railiance/ops/vergabe acceptance criteria and should not keep WP-0018 open.
+
+WP-0018 is complete. Follow-up work should start from a new workplan if the
+next goal is to improve non-Railiance intent-heavy repositories such as
+`helix-forge` or to persist corrected assessment artifacts for broader release
+comparison.